Skyscraper wrote:

It sounds like driver issues to me, the drivers are probably overclocking the cards.
At least I think this is what is happening to the Voodoo Rush.

but why should the reference drivers overclock the cards?

nemail wrote:

Skyscraper wrote:

It sounds like driver issues to me, the drivers are probably overclocking the cards.
At least I think this is what is happening to the Voodoo Rush.

but why should the reference drivers overclock the cards?

Back then reference drivers did lots of stuff we would not accept today.
Perhaps the exact model the reference driver is made for can handle it, or perhaps all cards could handle it when they were new.

Im not sure this is whats happening but I have seen that some Voodoo drivers do change the clocks.

Skyscraper wrote:

Back then reference drivers did lots of stuff we would not accept today. Perhaps the exact model the reference driver is made fo […]
Show full quote

nemail wrote:

Skyscraper wrote:

It sounds like driver issues to me, the drivers are probably overclocking the cards.
At least I think this is what is happening to the Voodoo Rush.

but why should the reference drivers overclock the cards?

Back then reference drivers did lots of stuff we would not accept today.
Perhaps the exact model the reference driver is made for can handle it, or perhaps all cards could handle it when they were new.

Im not sure this is whats happening but I have seen that some Voodoo drivers do change the clocks.

hmm i've downloaded the CT6670 driver from falconfly.de for the voodoo 2 which is a ct6670 and for the stingray i used the original installation cd.
alternatively i used the most recent voodoo 2 reference driver and the most recent 3rd party stingray driver... none of them worked.

i'll keep looking into that however, maybe there's an issue with the mainboard, i'll test the cards in other systems...

You could download a tool and set the clocks manually on the Rush to see if that fixes the problem.
I think its the 2D part that is the issue on the Rush as you had artifacts in Windows.

Im almost sure someone else had this issue with a Voodoo Rush here on Vogons recently.

But if you use the drivers that came with the card then its probably something else.

ok thanks, will check that too - currently giving the voodoo 2 another chance 😀

Skyscraper wrote:

It sounds like driver issues to me, the drivers are probably overclocking the cards.
At least I think this is what is happening to the Voodoo Rush.

I had this issue also. It would sometimes get set to 93 MHz instead of 90 (or was it 103 instead of 100 can't remember) and that would cause lock ups.

Rush is set to 72mhz for alliance 2d chip and that is too high.
Set 55mhz in registry and all problems are gone.

V2 can be picky about pci slots, So try different slot. Alsof try DirectX 7a.

I really suggest going for a Voodoo3 PCI (which I did in my MMX233 system), if it is available. If you have an AGP Socket 7 board, you can even go for an AGP Voodoo3. Voodoo2's are sometimes a hassle to setup.

V3 AGP is awesome for Windows but what about DOS?

What about the classic duo of Matrox AGP + V2 (and SLI)?

Or a V3 and V1 with V1 disabled in device manager and only used for DOS?

What combination would cover the most games?

The Voodoo 3 along with the Banshee has the best 2D compatibility out there except for the very early S3 AGP cards which may be even better.

Hmm V3 AGP and V1 could be a nice combo? I know you can get lots of V1 games to run on V2 but that means working with patches and batch files.

nemail wrote:

the V2 just disappeared from dxdiag (only s3 is shown now) and also 3dmark 99 doesn't see it, although i can see it in the device manager. that happened during the system ran (1st time i opened dxdiag the voodoo was there, second time it wasn't). reboot, driver reinstall etc. didn't help.
as there also were random lockups with the voodoo 2, i guess it really may be faulty (i used creative and also most recent reference drivers).

I wouldn't give up yet. Try moving the V2 to another PCI slot, try them all if you need to. Also consider using reference drivers instead of the stock ones.

Glide was the 3D king back then and you won't do better in that department. Either a V1 or V2 would be a nice fit in your P233, coupled with any decent 2D card. I've gone with the Diamond 3D-2000/Voodoo 1 combo in my P233, but a V2 would give better performance.

hey all

it appears that i managed to get the voodoo 2 to work normally. i've used the creative driver now and downclocked it from 93mhz to 90mhz.
so far all games were working and no more freezes or crashes. even need for speed porsche runs well at 800x600.

neither my P1 233MMX nor my P2 333MMX box has an AGP slot so i have to stick to PCI cards here. as i only own one voodoo 3 pci card, one voodoo 2 pci and one hercules stingray 128/3D i'd keep the voodoo 3 pci for the P2 system and use the voodoo 2 in my P1 233MMX.

my other systems (AMD K6-2 550 and P3 1000) have AGP and are equipped with V3 3000 AGP and V5 5500 AGP

my 486 box has some V7 (Spira or something like that) VLB card which supports even 1024x768 or more (never had something like that back in the days) 😁 no PCI here, so no voodoo possible...

thanks for all your help!!

edit: ah yeah and i played around with the memory timing settings (set them to more defensive values) and i found one 64MB SD-RAM module so no uncached memory in that system anymore!

Cool. You're covered 😀