phil stanbridge Posted January 22, 2004 Share Posted January 22, 2004 Just to let you guys know if you've installed the 4.1 cats you wont be able to do a flick back to the desktop without the famed "black screen of death". 0 Quote Link to comment Share on other sites More sharing options...
Schrullenhaft Posted January 22, 2004 Share Posted January 22, 2004 Which Windows version do you run ? There has been a 'patch' to the Microsoft-originated problem with the WM_TIMER patch. This updated version might fix this problem, but this may also just be related to Antialiasing code within the driver. Thanks for the heads-up. It definitely good to hear what problems people are having so others don't have to experience it themselves. 0 Quote Link to comment Share on other sites More sharing options...
phil stanbridge Posted January 23, 2004 Author Share Posted January 23, 2004 No problem, it might actually be another problem entirely because I've gone back to the 3.10's and I now have the same problem - weird. I'm using XP Pro sp1 with all of the critical updates. 0 Quote Link to comment Share on other sites More sharing options...
Bone_Vulture Posted February 22, 2004 Share Posted February 22, 2004 My Sunday was ruined when I made the mistake of installing the fresh Catalyst drivers; my copy was infected with the black screen bug as well! Then I obviously tried to revert to the old drivers (the January release), no help. Are you guys sure there isn't some Rage3D tweaker option that we've missed? Since I did... something... And got rid of the stupid bug the last time. But now it's back. I want a clear answer, dammit! :mad: 0 Quote Link to comment Share on other sites More sharing options...
Schrullenhaft Posted February 22, 2004 Share Posted February 22, 2004 Have you uninstalled the Catalyst driver completely from your system (and not just 'installed over' it) ? I usually suggest that people uninstall their previous driver and reboot before installing the newer driver. Sometimes a special uninstaller program may be necessary in order to get rid of certain registry entries or INF files. If you have the Rage3D Tweaker installed, then I suggest uninstalling it too (at least temporarily) before installing the newer driver. 0 Quote Link to comment Share on other sites More sharing options...
Bone_Vulture Posted February 22, 2004 Share Posted February 22, 2004 Obviously I uninstalled the drivers before installed the new drivers... It's common routine with Catalyst. I'm not sure whether installing Rage3D back and forth will help, as it appears to be a mere extension of Catalyst. I will try, but not tonight. Oh no, not tonight. :mad: 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.