Does it work with only the rage agp?

Haven't tried without Voodoo 2 connected, but if I select Rage for 3D card in 3DMark it completes successfully every time.

Haven't tried Unreal yet, I have to find patch which adds D3D to it. Version I have install of only has Software, S3 API and Glide.
I'll have to dig up Unreal collection BOX I have somewhere. Maybe it has some newer, updated, version on DVD. If it has Unreal and not only Unreal Tournament versions on it 🤔. It's been a long time since I used it last time so I don't remember what's on it 😅.

having recently done a bunch of voodoo 2 testing, the fastvoodoo driver clocks the cards to 93MHz, once I set them to the default 90MHz the crashes got a lot better (but not 100% gone) and a card that wouldn't work at all before suddenly played fine in SLI

edit: nvm, sorry I missed that you also tried the reference drivers... maybe the OC somehow persisted though?

Could be, I first installed fastvoodoo driver and maybe it leaves something in the registry... or reference drivers don't overwrite it. Although I used same fastvoodoo drivers on P233 configuration and it worked fine.

I'll try setting the clock back to 90 and see what happens. When I figure out how to do it 😅. I checked card properties in device manager and display settings and haven't noticed it. 🤔

posted this in another thread recently ^^ Re: Voodoo 2 Orchid Righteous 3D fastvoodoo 4.6 drivers

imi wrote on 2022-08-13, 14:11:

where you installed the FastVoodoo driver, under ...\Tools\Tweaker\V2_OC
after you run it you should have the panel in the display properties

Thanks!

Hopefully that will do something. Maybe P233 can't feed it with data fast enough for this instability to present itself so that's why it works.

could very well be, I've been testing on a Slot A Athlon and it was crashing a lot without clocking down

Results are a bit mixed 😅, reduced OC from 93 to default 90.

Unreal castle flyby now doesn't freeze, card even gets a bit hotter than before at 51°C vs 48°C from before (I guess because it froze before it had the chance).
But 3DMark2000 still freezes at same spot. First time I tried it even managed to complete, second run it froze. I also tried 3DMark99, it also freezes, but instead at FPS like test. And it freezes worse than 2k version, computer completely locks up and I have to hard reset it. I also did this before, so this is not a new development. I forgot to mention that it happens also in version 99.

I'm even thinking of putting it in my Athlon XP machine just to see if it'll also happen.