Recommended Posts

Solved my ATI x1600 problem. Bought a BFG Geoforce 7800 GS AGP card from CompUsa and now have Areo Glass and could not be happier.

My advice...

Drop the crappy ATI card on ebay and buy nVidia. As a long time ATI user I realized I had only been buying ATI cards because the boxes are cool. ATI drivers are simply crap.

:rolleyes: :sleep:

You're not very bright are you. This is beta software, it is bound to have problems. To trash something as such is idiotic. I and many others have had problems with nvidia drivers, they are hardly perfect and ATI's drivers have thus far given me little to no problems at all for the last 4 years.

ATI are badly built, never had one last more than 11 months.

My last two ATI cards have been running for 1 and 4 years without so much as a hickup. You have obviously had bad luck.

Well now, this bites. I've had the same Code 43 error issue since Beta 2 (5384), and I'm now running RC1 (5600) and apparently it still exists. I've tried all the suggestions in this thread to no avail, and I'm activated and everything. The driver shows up in safe mode as having memory and IRQ assigned, but in normal mode it gives Code 43. All the Vista drivers do it. WDDM from MS, and Beta 2, AND RC1. The XP 6.6 Catalyst does not, although it BSODs on reboot, and does not let me actually use Aero.

Any ideas?

:rolleyes: :sleep:

You're not very bright are you. This is beta software, it is bound to have problems. To trash something as such is idiotic. I and many others have had problems with nvidia drivers, they are hardly perfect and ATI's drivers have thus far given me little to no problems at all for the last 4 years.

My last two ATI cards have been running for 1 and 4 years without so much as a hickup. You have obviously had bad luck.

I'm just fed up with ATI. It's a free country...who are you to judge me? You must be one of those people that thinks they're better than everyone. How's that working out for you?

I'm just fed up with ATI. It's a free country...who are you to judge me? You must be one of those people that thinks they're better than everyone. How's that working out for you?

Yeah, that's it. Or maybe it's that you stated something that was based in no part on fact. I mean really, judging a product based on beta software is as useful as twiddling your thumbs. Yeah, there is currently a bug with ATI cards and Vista, this is by no means an old bug as it was first revealed in the last build; are you really going to sit there and say nvidia has never had bugs in beta drivers? You might as well admit you had no patience so you ran out and bought something else to satisfy your need for instant gratification.

You have the right to state what you want but I also have the right to refute you and contrary to your claims ATI makes very good products that have not given me any problems based on my own experience. Frankly, I don't understand where all the blind nvidia loyalty comes from.

I'm just fed up with ATI. It's a free country...who are you to judge me? You must be one of those people that thinks they're better than everyone. How's that working out for you?

Au contraire. Who are you to judge ATI, then?

*bzzkt* Pot, this is kettle. Over *bzzkt*

*click* Kettle, this is pot. You are black. Repeat. You are black, over. *click*

*bzzkt* Copy. I am black. Out. *bzzkt*

Is everyone getting the Code 43 running a dual core/processor system? After poking around various .inf files (specifically hal.inf), it seems to me that the only change updating the Computer ACPI driver makes is swapping out the multiprocessor HAL.DLL with the single processor version.

The conflict certain ATI cards have is likely with the multiprocessor HAL.DLL, and this conflict doesn't exist with the single core version.

Anyone care to confirm or discredit this?

Well, I might be able to discredit this. I have a single core Pentium 4. Although, I do have hyperthreading turned on. I'll turn it off and see what happens. (Since HT is pretty much an emulation of a second core)

Nope, no luck. I turned it off in the BIOS but Code 43 still remains.

Edited by Takuya

Au contraire. Who are you to judge ATI, then?

A disatisified customer, that's who. I've had driver problems in XP ever since I've purchased this card.

The ongoing problem with Vista was the last straw. This was a simple upgrade decision based on the fact the x1600 is a lemon. If you love ATI so much I'll be selling this card on eBay and will happily sell it to you.

A disatisified customer, that's who. I've had driver problems in XP ever since I've purchased this card.

The ongoing problem with Vista was the last straw. This was a simple upgrade decision based on the fact the x1600 is a lemon. If you love ATI so much I'll be selling this card on eBay and will happily sell it to you.

And based off your apparent level of knowledge and competency, I wouldn't be surprised if you shipped the card with half a ham sandwich.

As it seems, ATI is not at fault for the code 43 error. After doing some research i've notice that certain system drivers will cause vista to give the code 43 error. My error was caused by my nforce ide drivers for xp. As long as i don't install the xp drivers, My ATI 9800 Pro works fine and has been since sept. 5

Once more motherboard companies start releaseing Vista Drivers, Code 43 should go away.

don't blame the video card for the motherboards problem.

how did this become ati vs nvidia? Both cards have there advantages and disadvantages. Hell I ran nvidia since the voodoo's but i'm running ATI know b/c it was better then the card i had and it was free and truthfully, I

haven't notice a difference in either ones.

Well, there goes your precious "infallible" company tanoanian.

BTW if you look through the post other people are having issues with AMD as well. Its not the company, its the fact that Vista is still not finall, hence why we are having these issue. In all due time everyone will get there **** straight and everything will be running as well as a windows OS can run.

For those who remember Whistler, there where similure issues with hardware as well. Thats just something people have to work around while testing beta software.

Which is why I said it's idiotic to make any decisions such as buying new hardware and spewing crap when you're using beta software.

(Y)

I'm reminded of the legions of people who purchased new graphics cards just so the leaked Half Life 2 Beta would run better...

OK, someone over on www.<< spam >> posted a easy solution which fixed the code 43 problem.

Go into device manager, expand the "Computer" and right click the ACPI Computer, and choose "update driver software" -> "browse my computer..." -> "let me pick from list...". Then choose the only other option that is available, which should Advanced Configuration and Power Interface PC. After making this change video worked as it should, including Aero with all the eye candy.

Hope this helps someone.

I tried this plus uninstalling the drivers in safe mode and still no luck. each time it reboots i get the code 43 error. I'm on day two of looking for a fix but i'm starting to get annoyed.

BTW I have an AIW x800 XT and i've been trying to use the Beta Drivers for RC1 (i have RC1 as well)

I hope someone fixes this soon.

I tried this plus uninstalling the drivers in safe mode and still no luck. each time it reboots i get the code 43 error. I'm on day two of looking for a fix but i'm starting to get annoyed.

BTW I have an AIW x800 XT and i've been trying to use the Beta Drivers for RC1 (i have RC1 as well)

I hope someone fixes this soon.

I also tried this fix (ATI 9800 Pro), but it did bugger all. Interestingly, when I tried to install my AGP drivers, it nerfed my Vista install. Resets before a stage where I can even reach Safe Mode. :laugh:

Guess I'll wait for the final release, now.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
    • Microsoft Edge 149.0.4022.52 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.52 changelog: Migration to improved V2 architecture for Workspaces. Workspaces, introduced in Edge in 2022, allows users to create durable sets of tabs that can be saved and shared with others. In order to improve reliability and performance of this feature, the following changes are being made: Migrating data for saved Workspaces from OneDrive/SharePoint to Edge Sync service Removing the collaboration/share functionality of this feature For organizations who have disabled Sync through policy, the existing v1 Workspace data will still be migrated to the new architecture. New v2 Workspaces created after migration won't sync across devices and will remain local to each device. This update occurs on a progressive rollout beginning in Edge Stable v145 and will continue rolling out in Edge v149. For more information, see Getting started with Microsoft Edge Workspaces. Feature Updates Passkey Sync for Enterprise Users. Microsoft Edge is introducing support for passkey synchronization for enterprise users, enabling secure, passwordless authentication across devices. Passkeys created in Edge can now be synced seamlessly, improving sign-in experience while maintaining strong security standards. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout. Enterprise WebView2 runtime downgrade via DowngradeVersion policy. Administrators can temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2) using the new DowngradeVersion policy in msedgewebview2.admx. The Downgrade Version policy allows enterprises to mitigate critical regressions by specifying per-application exe-to-version mappings. The Edge Updater installs the target version side-by-side, and the WebView2 Loader redirects targeted apps accordingly. Downgrades auto-expire with each new WebView2 release: apps pinned to N-1 remain on the same version (now becoming N-2) and will auto-update in the next release, while apps pinned to N-2 will revert to the current Evergreen version. The policy applies only to enterprise-managed devices (domain-joined or MDM-enrolled). For more information, see Microsoft Edge WebView2 Policy Documentation | Microsoft Learn. Collections retirement. Collections has been removed in this update. Users can no longer access or use the feature. To keep saved content, users can export it, or move all pages to Favorites before updating to Microsoft Edge Stable 149. For more information, see Organize your ideas with Collections in Microsoft Edge - Microsoft Support. Modern, unified, and updated Look and Feel. Microsoft Edge has updated the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This changes multiple elements of the UX such as spacing, corners, fonts, default colors, etc. Clarify choices surrounding third-party cookie settings. Language under Settings > Privacy, search, and services > Cookies are clarified to better describe the choices users have in managing third-party cookies. Custom primary password retirement. Users are no longer able to create a new custom primary password in Edge Settings edge://settings/autofill/passwords/settings. Any users who are still using a custom primary password will be automatically migrated to device authentication. Additionally, the PrimaryPasswordSetting policy will no longer support the WithCustomPrimaryPassword option. For more information, see Keep your saved passwords private in Microsoft Edge | Microsoft Support. Unifying Copilot Chat policy controls. The Microsoft365CopilotChatIconEnabled policy is the standard for configuring Copilot Chat. Previously, this behavior was controlled by blocking the Copilot extension, either explicitly or by using the * wildcard via the ExtensionSettings or ExtensionInstallBlockList policies. Extension and sidebar policies no longer affect the appearance or functionality of Copilot Chat. Copilot address bar suggestions were also tied to extension policy settings. Starting in Microsoft Edge version 149, admins can use the CopilotAddressBarSuggestionsEnabled policy to manage this behavior. Intune MAM Protected Downloads. The protected downloads feature for Intune MAM is now available for BYOD (Bring Your Own Device) devices, which aren't managed by a tenant. Policy Updates / New policies CopilotAddressBarSuggestionsEnabled - Enable Copilot address bar suggestions CpuPerformanceTierOverride - Override for the CPU performance tier DataUrlInWebWorkerOpaqueOriginEnabled - Enable opaque origins for data URLs in Web Workers DefaultLocalFontsSetting - Default Local Fonts permission setting ForceForegroundPriorityForUrls - Force foreground priority for specific URLs LocalFontsAllowedForUrls - Allow Local Fonts permission on these sites LocalFontsBlockedForUrls - Block Local Fonts permission on these sites Deprecated policies WalletDonationEnabled - Wallet Donation Enabled (deprecated) EdgeWalletEtreeEnabled - Edge Wallet E-Tree Enabled (deprecated) Additional policy changes ForceForegroundPriorityForUrls - ForceForegroundPriorityForOrigins is renamed to ForceForegroundPriorityForUrls OnSecurityEventEnterpriseConnector - Add macOS platform support ProtectedContentIdentifiersAllowed - Remove macOS platform support Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      59
  • Tell a friend

    Love Neowin? Tell a friend!