J
J.Clarke
Anyone got anything good/bad to say about them?
Is there a list anywhere in what is fixed/altered?
There's a link to the list on the download page at ati.com.
Anyone got anything good/bad to say about them?
Is there a list anywhere in what is fixed/altered?
BF1942 still worksAnyone got anything good/bad to say about them?
Is there a list anywhere in what is fixed/altered?
MS Flight Sim 2004 wouldn't run on my system* with Cat 3.6 so I had to
backup to 3.2. I loaded 3.7 and all's well . IMHO, ATI is doing a
pretty good job solving problems with new drivers. Rumor has it that
there are awesome goodies in store for us with 3.8.
* ABIT BE6II, P3 600 MHz Coppermine, 256 RAM, ATI 95900 Pro, 2-WD 80G
JB HDs, Formac 20" LCD display. I know, I know, it's a terribly slow
system but I'll put together my new box in a few months. ABIT IC7-G,
P4 3.2G CPU, 512 Mushkin Hi-Perf RAM, PC Power & Cooling Turbo Cool
510 Deluxe PS. Plextor Premium 52/32/52 CDRW, Plextor 48/24/48 CDRW,
Lian-Li PC-75 USB aluminum full tower case, blah, blah.
Works fine for me - Gigabyte 9700 Pro, Windows 2000 Pro.The Call of Duty demo crashes every time with a corrupted display with
Catalyst 3.7, and had no crashes under 3.6.
This is on a Abit NF7-S + 9700pro + WinXP.
Cold said:JAD,
Thanks for the suggestion. Unfortunately that was the first thing I
have checked.
Dean
BF1942 still works
I was disappointed. 3.7 still hasn't addressed my brightness issue.
Coming out of a 3D screensaver or game, the brightness settings (as well
as the rest of the settings under the color tab) all reset back to
defaults. This makes my LCD very bright and very washed out.
It's a small thing but still a pain to have to open up the control panel
every time it changes.
problem in explorer only began with the Cat 3.5 drivers. If I go back to
3.4 the problem disappears.
IC yes! i have an NEC also Multisync 5 or 6 efg or something like that (its on the system in the garage) anyway I had that
problem also under XP....under Win ME its works perfectly.
This 2D
Well yeah if the driver revertion solves it then It sounds like its the driver....although why wouldn't be common? At least one more
person here would have the problem, you would think.