3dfx Archive - Print Page

3dfx Archive
http://www.falconfly.de/cgi-bin/yabb2/YaBB.pl 3dfx Section >> 3dfx Drivers >> Problems with a Obsidian2 X-24 http://www.falconfly.de/cgi-bin/yabb2/YaBB.pl?num=1363180958 Message started by Max_R on 13.03.13 at 14:22:38

Title: Problems with a Obsidian2 X-24
Post by Max_R on 13.03.13 at 14:22:38

I was trying to use the X-24 in my old rig
P3 1GHz (core coppermine, 133mhz)
2x256MB Pc133
all mounted on a HP Vectra VL400 DT (desktop)
I've installed the official Q3D Obsidian2 Drivers 6CF but the system hangs
Sometimes I can't see the screen properties (with a strange error message) and sometimes I can see the properties without the Q3D panel
Any idea?

p.s.
I have two X-24 and both have the same problem
Under Windows Xp both run well

Title: Re: Problems with a Obsidian2 X-24
Post by Max_R on 15.03.13 at 13:44:04

KoolSmoky seems to be less problematic but, again, I have no control panel and the games don't recognize the card.
Any idea?
Thanks

Title: Re: Problems with a Obsidian2 X-24
Post by subhumangarbage on 16.03.13 at 19:32:51

hi, I think disabling CPU to PCI post write will solve the problem, but this will decrease performance.

Title: Re: Problems with a Obsidian2 X-24
Post by Max_R on 18.03.13 at 00:20:20

I will try soon! Thanks :)

Title: Re: Problems with a Obsidian2 X-24
Post by subhumangarbage on 19.03.13 at 21:41:06

No problem :) Quantum3D Obsidian drivers seem to be quite problematic on anything higher than a 440bx motherboard. Something like that happened to me when I fired up my 200SBi on an Athlon 2800. You can opt to do what I said or just use the normal V2 drivers by throwing the following variables into regedit's 3dfx interactive glide and d3d section:

SSTV2_FT_CLKDEL = 5
SSTV2_TF0_CLKDEL = 7
SSTV2_TF1_CLKDEL = 7
SSTV2_TF2_CLKDEL = 7
SSTV2_SLIM_VIN_CLKDEL = 3
SSTV2_SLIM_VOUT_CLKDEL = 2
SSTV2_SLIS_VIN_CLKDEL = 3
SSTV2_SLIS_VOUT_CLKDEL = 2
SSTV2_GRXCLK = 90

Regards

Title: Re: Problems with a Obsidian2 X-24
Post by Queso on 03.03.16 at 02:43:22

Hey there, was this problem ever solved?
I have a similar issue with my 200sbi...