Ok nightbird my machine is intel p2 333mhz with 240mb ram radeon 7000 with 64mb ram and my voodoo2 with 12mb. I have a dual boot with win98se and win2000. i´m using FastVoodoo2 4.0 XP Gold Edition in win 2000 and FastVoodoo2 4.6 in win98se. I have tried with counter-strike and jedi knight2 im gonna trie more later. Yes im using directx9 also but tried with 8.1 and i got the same error.

Hi Nike,

simplest way for running games like CS and/or JK2 with Voodoo2 cards is using MesaFX, beside FastVoodoo2 series.

You open this document - https://www.3dfxzone.it/dir/3dfx/mesafx/ - for getting more info about MesaFX setup and download.

Let'me know,

Bye bye,


Glide

I already got mesafx Glide but i havent tried it out yet. But thats not the problem, when i run the direct3d test i get the error and when i try a opengl game i get a white screen.

have you tried some native Glide games?
maybe it's related to hardware but not software..

No i havent tried any glide games yet but i do it tommorow. I tell you then how it goes.

Ok, by your other words I can understand you are getting errors for bad software configuration.

So, remove ATI software with Catalyst Unistaller tool (it's is here: http://www.hwsetup.it/periferiche/schedevideo/ati/utilities.htm); then unistall FastVoodoo2 by Windows Control Panel and reboot pc.

At this time, install in this order:

1)DirectX 9c located here: http://www.hwsetup.it/software/directx.htm

2)Latest Catalyst located here: http://www.hwsetup.it/periferiche/schedevideo/ati/win2kxp.htm
Please make sure that you install before display driver then reboot and run Catalyst Control Panel setup, then again reboot.

3)FastVoodoo2 4.0 XP (read installing procedure in driver release notes).

Reboot and run your applications now.

Let us know,

Good luck

Bye bye

Glide

Ok guys i got it to work. Stupid me i hadent put the monitor cable to the card instead it was in my mpeg card and then it workt. Sorry for stupidity

"lol"
The monitor cable, indeed this is a good reason...

LOL X2
seems my guess is right, it's a hardware problem (althoughg i've never gurssed the cable would cause the problem..)
XDDDDD

It's good for you , you can play with your v2 now..