Catalyst 3.6 Are Out!

Wow, that was fast, Rage3D hasn't even posted anything about em yet., nor has ATI but:

Win XP-http://mirror.ati.com/support/drivers/winxp/radeonwdm-xp.html?type=graphic&driveros=windows+xp&prod=productsXPdriver&submit.x=19&submit.y=3

-Win 98:http://mirror.ati.com/support/drive...rod=productsME98driver&submit.x=7&submit.y=11

PS: 900 POSTS!!!!

 

thanks for the heads up.... I have had probs in the past (part of the infamous thread!) but I'll give it a shot...
Thanks!!!

 

Here is a direct link to the whole bundle for XP:

Clickity Click for Drivers (16Mb)

 

wow, yep that fast. I am happy with 3.5, what the improvements on 3.6? I bet we will see 3.7 next month?

 

Holy Poop Stains Batman!! They worked!!!
I did nothing different than when I have tried earlier versions....
(previous unnamed threads discussed many problems I have had with CAT drivers newer than 2.3)

They work!
I get good FPS (well at least for my little ole Radeon 7500) and better 3dMark01 scores than I have ever had

Must have changed something in the drivers....

Hmm looks like it WAS a software issue and NOT a hardware issue..
Go figure

Yipee!!

 

Great, heh. Here are the changes:
Fixed in this driver:
---------------------------------------------------------------------------------------
Switching to the program Second Life using the ALT-Tab command no longer results in the system not responding or looping indefinitely
Running the demo game Lord of the Realms 3 under Windows XP with a RADEOIN 9000 series card installed no longer results in the system not responding when a 3 stage effect is used
The game Unreal Tournament 2003 no longer hangs when loading the CTF-December level
The geometry flashing throughout the background of Second Life is now resolved
Flickering and display corruption in the game NeverWinter Nights is now resolved
Running ViewPerf 6.1.2 under Windows ME with any RADEON™ family product installed no longer results in the application not being able to render an image
Objects are now generated and the VP is no longer gray when running 3ds max in D3D mode
Loss of focus when switching between different layers in Studio Tool 10.1 is now resolved
Full Screen Anti-Aliasing no longer causes corrupt geometry in model viewer program
Overlay no longer disappears when moving the mouse around in panning mode on the secondary display adapter in the application Overfly
Multimedia mode scaling and positioning issues have now been resolved when using TV out
Display corruption noticed on the ATI Demo Rachel running under Windows XP is now resolved
The lighting and triangle culling on the 3D pipes screensaver no longer is incorrect when using a RADEON™ 7000 series card under Windows 2000
Significant CPU usage is no longer noticed when Hardware Overlay Alpha Deblocking is in use
Enabling Overlay Theater Mode and playing an HDTV source through the ATI File Player, no longer results in the system rebooting
The TV can now be disabled using the Troubleshoot button in the ATI displays tab
Connecting a secondary DFP and attempting to enable extended desktop mode no longer now results in the secondary display device becoming active
Setting an LCD as the primary display, and a CRT as the secondary display followed by enabling Overlay Theater Mode, no longer results in display corruption when preview the screen saver on the secondary display
Enabling extended desktop at certain resolutions and colour depths no longer results in display corruption on the secondary controller
Installing a RADEON™ 9600 series card in a motherboard supporting AGP 8X no longer results in some 3D applications failing to respond

 

Well, don't know how many of you saw my posting re: the last catalyst drivers... but since then I have a new mobo, processor, psu and even a case... And guess what... the new install did the same damned thing.

When running the setup.exe to extract and install the drivers, everything works fine until reboot when my machine reboots with all direct 3D capability disabled. I have to roll back the drivers to get it back. Fortunately I learned the trick to just update the driver through device manager and that avoids the problem, for some reason...

This is a mystery for sure...

spaz

 

Soounds uhhh, good.