Meant to be Seen

I have the following hardware :
Asus P5B
Crucial RAM, has passed every memtest with flying colors
Core 2 Duo at 3.2 GHZ. Yes, it is overclocked but I have run toast and CPU burn and other programs for many hours without every having an error
Sound blaster X-fi

The video card is the XFX factory overclocked 7900GS.
I suppose I should probably try underclocking it before I give up on the 93.81 drivers.

For some reason, 93.81 is criminally unstable on my machine. It is basically a junk product, crashing 80% of the time I tried to do ANYTHING, including boot up.

93.71 never crashes. Ever, in 20 hours of gaming. (except when I hit cntrl-T in some games)

What does 93.81 fix, anyhow? The main thing I want is to use HDR lighting and FSAA at the same time in Far Cry. 93.71 screws up the level geometry with both AA and HDR on. HDR by itself leaves all sorts of artifacts in the distance.

Please help, Neil.

Gerald wrote: What does 93.81 fix, anyhow? The main thing I want is to use HDR lighting and FSAA at the same time in Far Cry. 93.71 screws up the level geometry with both AA and HDR on. HDR by itself leaves all sorts of artifacts in the distance.

I thought Geforce 7 series do not support HDR and FSAA at the same time?

That might actually be true. The game loads with both on, but the graphics are heavily corrupted.

I'm also just frustrated because others claim 93.81 works for them, so I feel that my hardware or configuration must somewhere be at fault.

Did you remember to turn off one of the cores via MSCONFIG?

That is usually the culprit.

Neil

Neil wrote:Did you remember to turn off one of the cores via MSCONFIG?

That is usually the culprit.

Neil

As I've learned recently, most or all games will freeze in dual core mode. Freezing can also be because both the Microft dual core drivers (KB896256) are loaded as well as the AMD.

Actually, better off [except for that recent disappearance] to have the BOOT.INI with two separate lines, one with dual core and one with the " /numproc=1" set.

Using MSCONFIG ain't the best way as you have to go back and forward and remembering to reboot after changes.

My setup (NOTE: Yours may differ because of the number and types of dics and setup):
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro Gaming" /noexecute=optin /fastdetect /usepmtimer /numproc=1

FIXED! I suppose I should be annoyed at only being able to use one core, but the problem is totally fixed! I can use 93.81 without ANY crashes, ever, and it solves a major glitch in Far Cry's graphics!

I did the boot menu thing : there's a single core option, as well as one for my 64-bit OS that I save for everyday use.

Gerald wrote:FIXED! I suppose I should be annoyed at only being able to use one core, but the problem is totally fixed! I can use 93.81 without ANY crashes, ever, and it solves a major glitch in Far Cry's graphics!

I did the boot menu thing : there's a single core option, as well as one for my 64-bit OS that I save for everyday use.

It's probably the easiest. But you just need to remember to select which option.