Has anyone else had problems with the new ATI 5.12 drivers?I could not find a non-catalyst control center version at ATI's web site this month so I bit the bullet and down loaded that version. I also loaded the MS Net Framework software and its update as per the instructions in the ATI drivers. All I would get is hang ups in the FS2004 program and blurry ATC windows that I could hardly read. I even reloaded FS2004 and still no better. Finally I removed the 5.12 drivers and went back to the 5.11 drivers which use the ATI Control Panel instead of the Catalyst Control Center and now everything works just fine. Oh I also removed that MS Net Framework program too.Terry

Don't know whether it was the drivers or something else.I am currently running the 5.9 version. Just before trying to install the 5.12's, I had two automatic updates from windows. After that, I removed all ATI items and went through the installation routine for the new version (As I have done successfuly many many times in updateing to newer drivers).During installation I get an error message: "This display driver is not compatible with the display adapter (s) installed in your system." (Radeon 9800 Pro).My only recourse has been to go back to my starting point with MSXP's System Restore, however, my CCC also will no longer activate. Therefore, I cannot install new drivers, nor have any control over my settings. Everything else appears to work normally.I have contacted ATI with no solution thus far. Upon their advice, I removed Net Framework and all ATI items and reinstalled being sure all background programs and my firewall were shut down. No luck. In fact, now I cannot remove net framework for another try.Best of luck:RTHEdit Adder: You might want to access my earlier post below, "XP Windows / ATI Driver Conflict

Terry,>>Has anyone else had problems with the new ATI 5.12 drivers?<

The 5.12 ATI drivers with no CP can be downloaded from -http://downloads.guru3d.com/download.php?det=1276Shep

Thanks, Shep!I hope they will keep making them available like this. I very much prefer the CP control over the clunky, slow-starting, overdone control center.Also, I hope this version will fix the problem I had with the control-center version: I couldn't get anti-aliasing to work.BTW I did not have the problem with the latest windows XP updates.Best,Martijn

Thanks to all that took the time to write down their coments. To JB, yes I loaded all of the Net Work 1.1 and it's SP1. To Shep, thanks for the link. I should have seen it there as that was the site I found my old 5.11 drivers. I agree that the ccc is too much show and probably eats up too much system memory. Bottom line is my computer and FS2004 run great now that the MS Net Works and the their drivers are gone.Terry

I just downloaded and installed that CP-version of the driver.AA working again like it should!Best,Martijn

Terry,Glad it works for you now. I sorta like the CCC using the 'All Settings" mode in 3D...none of the video bits, I can scroll through and see what i need. Each to their own, and yes, it is a RAM hog, but having used the standard CP in the past never noticed a performance impact (1GB RAM). And the ATI Tray Tools seemed especially cumbersome for *me*, some love 'em.I did do some log searching and search-by-date comparisons, and the wmiprov.log errors were oddly coincident with new ATI driver installs. My logs go back to Sept. 29 2004, and there's a marked increase in these errors (this example for instance from Aug. 24, 2005, the day I installed 5.8, same sort of results go back to 2004 ATI installs and newer installs):(Wed Aug 24 05:18:57 2005.38781) : Received Event(Wed Aug 24 05:22:42 2005.263984) : WDM call returned error: 4200(Wed Aug 24 05:24:15 2005.356859) : Impersonation failed - Access deniedI don't attribute *all* of these to the ATI stuff (Sandra Lite seems to cause the same results). Bottom line, it hasn't caused me any noticeable problems, though could explain the usually slow and odd CCC opening (sometimes it blinks in the TB like it can't get itself to be the top window) . Also, as the logs rollover after ~65k, I only have one prior log (they're labled with a .lo_ extension). Who knows when it really started? May post some of this to the A-Team at ATI, see what they think ;-) Then again, everything works, so if it ain't broke...jb