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

    • Google are hyprocrites for signing this. They have been pulling the same dirty tactics as Microsoft, only they do it on Android and ChromeOS.
    • In some countries the law has forced Microsoft to display a menu on a fresh install of Windows which asks which web browser you want and it will install that browser. This doesn't add any bloat to Windows. It simply an additional step when setting up a new PC.
    • Chrome is also a first party browser on Android and ChromeOS. And on those systems, Google is pulling the same dirty tactics as Microsoft does on Windows.
    • Unofficial script lets you install unreleased Windows 11 features without Microsoft Account by Sayan Sen Microsoft has been steadily evolving the Windows Insider Program over the years, introducing new channels and testing paths that allow enthusiasts to experience upcoming and yet-to-be-released Windows features (some interesting hidden ones too) before they reach the public. However, one long-standing requirement has remained largely unchanged as users are generally expected to enroll in the Program and with a Microsoft account. That's where a third-party tool called "OfflineInsiderEnroll" can help. OfflineInsiderEnroll is said to be a lightweight script that enables access to Windows Insider Program builds on systems that are not signed in with a Microsoft account. Essentially the tool configures the necessary Insider settings locally and hence allows users to select and switch between available preview channels while continuing to receive builds through the normal Windows Update channel. If you are wondering how it manages to do so, it is made possible by a Registry value known as TestFlags. When configured to"0x20", Windows stops communicating with Microsoft's online Insider enrollment services thus preventing locally configured Insider settings from being overwritten. This allows the script to apply its own channel configuration directly through the Registry as Windows Update does not verify whether a device has been officially enrolled in the Insider Program or not. Previously the utility has had already supported the traditional Insider branches including Dev, Beta, and Release Preview. However following Microsoft’s recent restructuring of its preview channels, the script has now been updated. The latest OfflineInsiderEnroll version, 2.6.6, adds support for the newly introduced Insider channel lineup. As such, users can now choose from several Experimental channels in addition to Beta and Release Preview options. The update also retains tools for refreshing the Insider cache, resetting Insider settings, and completely stopping Insider enrollment when needed. Keep in mind though that will need elevated privileges when running the script (run as Admin). You can get the latest version of OfflineInsiderEnroll from this page on its official GitHub repo.
  • 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
      472
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!