@Ragnax said:
@blakeyrat said:Knock it up a notch. Remove the Catalyst manager app (or whatever it's called) completely, and update the driver to the version in Microsoft's repository. Unless you need to do something really funky, like rotate a monitor 90 degrees or have two monitors pretend to be one, you don't need the Catalyst thing at all.
QFT. Blakey's spot on here. The Catalyst Control Center management app is a complete piece of trash. Nine out of ten times it doesn't install correctly or boot up correctly, which results in Windows event logs being hammered with error entries continuously. If you have an ATI card and have noticed that something is continuously accessing your harddrive, then uninstall CCC and enjoy the blisfull silence thereafter.
Unless you are a control freak who wants to tune everything you really don't need CCC for anything. The important stuff can all be configured from Windows' own control panel. Atleast with installing the Catalyst driver through Windows Update you'll get a WHQL-certified driver that ATI had to ship to Microsoft for review. Stands within reason those will have been given a more critical review than the flavor of the week ATI directly puts out on the web. (Oh; and you won't have to deal with yet another 'auto-updater-packaged-into-PoS-customized-installer'.)
Oh yes. And I think I've found at least one reason why it sucks. I recently had a HD-failure and had to reinstall on a fresh disk. ATI HD5770 with catalyst and drivers from 2009 on CD. (Not sure why I installed from CD first instead of downloading directly, I guess I was in the groove of slapping in CDs and didn't think). That driver of course had no openGL-support, so upgrade it was or no minecraft for me.
When I tried upgrading the driver windows (7 x64) bluescreened with the error originating in atiwhatever.sys and upon reboot catalyst was gimped and didn't detect any displays. (Oh, and that bloody overscan-setting is back with its annoying black border. Easily solved but grar!). I rolled back the driver and went online to find out why this happened, and found a certain nugget.. The drivers with openGL-support requires a certain minimum version of catalyst (10.6 iirc). When I did a custom install catalyst wanted to upgrade the drivers first and then itself. So it happily upgraded to an incompatible driver and bluescreened before it could upgrade itself. Billiant depenency handling there. A manual install of only catalyst first and then the driver solved the issue.
(Well, it still bluescreened, but it seems to work when I rebooted, catalyst at least detects my displays now (and I've got my minecraft back \o/))