leonardo wrote on 2022-12-13, 09:50:

I would honestly try either Windows 95 OSR2 or Windows 98 SE depending on what games you intend to play (95 tops out at DirectX […]
Show full quote

loveburn wrote on 2022-12-13, 06:52:

So, I tried to do step by step all what @dionb recommended... But same effect... 0. Load bios default 1. I reinstall windows me […]
Show full quote

So, I tried to do step by step all what @dionb recommended... But same effect...
0. Load bios default
1. I reinstall windows me
2. Install via 4in1 v4.35 driver then reboot
3. Install Nvidia 12.41 driver, reboot again
4. Install game and test on d3d in GeForce (works perfectly)
5. Install voodoo2 reference drivers 30202
After reboot I try to open screen settings and click to 3dfx voodoo tab, but screen cpl is freeze...
Nothing not changes , may be you have other variant?

I would honestly try either Windows 95 OSR2 or Windows 98 SE depending on what games you intend to play (95 tops out at DirectX 8, 98 at Direct X 9). Windows ME is just asking for extra trouble, especially if you intend to do DOS-gaming too.

dionb wrote on 2022-12-12, 18:21:

...My suggestion would then be to try the V2 in a different PCI slot. In fact, try all of them one by one. It could be that one particular slot shares an interrupt line with some integrated stuff that doesn't like sharing with Voodoo. As there are only four interrupt lines on a PCI bus, any system with more than four slots (and any system with integrated or onboard functionality with more than three slots) will of necessity share interrupt lines. PCI spec says devices need to play nice with each other, but IRL things don't always work as smoothly.

^ Also this, with the notice that you may want to go over some peripheral-related BIOS settings, especially if they have something to do with resource sharing or the PCI bus.

Dear, I am also tried in win98se all about talk above

loveburn wrote on 2022-12-13, 09:57:

leonardo wrote on 2022-12-13, 09:50:

I would honestly try either Windows 95 OSR2 or Windows 98 SE depending on what games you intend to play (95 tops out at DirectX […]
Show full quote

loveburn wrote on 2022-12-13, 06:52:

So, I tried to do step by step all what @dionb recommended... But same effect... 0. Load bios default 1. I reinstall windows me […]
Show full quote

So, I tried to do step by step all what @dionb recommended... But same effect...
0. Load bios default
1. I reinstall windows me
2. Install via 4in1 v4.35 driver then reboot
3. Install Nvidia 12.41 driver, reboot again
4. Install game and test on d3d in GeForce (works perfectly)
5. Install voodoo2 reference drivers 30202
After reboot I try to open screen settings and click to 3dfx voodoo tab, but screen cpl is freeze...
Nothing not changes , may be you have other variant?

I would honestly try either Windows 95 OSR2 or Windows 98 SE depending on what games you intend to play (95 tops out at DirectX 8, 98 at Direct X 9). Windows ME is just asking for extra trouble, especially if you intend to do DOS-gaming too.

dionb wrote on 2022-12-12, 18:21:

...My suggestion would then be to try the V2 in a different PCI slot. In fact, try all of them one by one. It could be that one particular slot shares an interrupt line with some integrated stuff that doesn't like sharing with Voodoo. As there are only four interrupt lines on a PCI bus, any system with more than four slots (and any system with integrated or onboard functionality with more than three slots) will of necessity share interrupt lines. PCI spec says devices need to play nice with each other, but IRL things don't always work as smoothly.

^ Also this, with the notice that you may want to go over some peripheral-related BIOS settings, especially if they have something to do with resource sharing or the PCI bus.

Dear, I am also tried in win98se all about talk above

Did you try installing Windows with ACPI disabled (setup /p i) and/or taking notice of...

leonardo wrote on 2022-12-13, 09:50:

...you may want to go over some peripheral-related BIOS settings, especially if they have something to do with resource sharing or the PCI bus. For Win9x it sometimes makes a difference whether 'Plug & Play compatible OS' is set to Enabled/Disabled. For some configurations I've found it's better to let BIOS determine the resources, for others it's the reverse (better let Windows decide). Unfortunately the only way to know is trial and error...

?

I know it may not make you feel better, but I had to do roughly ten reinstalls of Windows on one of my systems before I found out how to do it "the right way"...

leonardo wrote on 2022-12-13, 10:13:

Did you try installing Windows with ACPI disabled (setup /p i) and/or taking notice of... […]
Show full quote

loveburn wrote on 2022-12-13, 09:57:

leonardo wrote on 2022-12-13, 09:50:

I would honestly try either Windows 95 OSR2 or Windows 98 SE depending on what games you intend to play (95 tops out at DirectX 8, 98 at Direct X 9). Windows ME is just asking for extra trouble, especially if you intend to do DOS-gaming too.

^ Also this, with the notice that you may want to go over some peripheral-related BIOS settings, especially if they have something to do with resource sharing or the PCI bus.

Dear, I am also tried in win98se all about talk above

Did you try installing Windows with ACPI disabled (setup /p i) and/or taking notice of...

leonardo wrote on 2022-12-13, 09:50:

...you may want to go over some peripheral-related BIOS settings, especially if they have something to do with resource sharing or the PCI bus. For Win9x it sometimes makes a difference whether 'Plug & Play compatible OS' is set to Enabled/Disabled. For some configurations I've found it's better to let BIOS determine the resources, for others it's the reverse (better let Windows decide). Unfortunately the only way to know is trial and error...

?

I know it may not make you feel better, but I had to do roughly ten reinstalls of Windows on one of my systems before I found out how to do it "the right way"...

Ok I will try it with disable acpi

Upd: disabling acpi before windows 98se installation not helping.... Same trouble!

loveburn wrote on 2022-12-13, 05:14:

Gta1, shadow warrior, of cause I tried copy do game folder ovl file ....run exe with or without ovl ... Same results

For GTA1, try using the GLIDE2X.OVL file from the Voodoo2 3.03.00 (non-beta and not the latest one) driver. It has slightly better compatibility with DOS games.

Don't bother running the 3dfx version of Shadow Warrior, it isn't faster, doesn't look better than software rendering and lacks support for voxels.

Just interested, how Nvidia drivers version affect on voodoo 2, and voodoo2 in pure dos......

It is extremely unlikely that the Voodoo2 will be affected by nVidia hardware in Pure DOS/MS-DOS mode. As others mentioned, it is better to keep the things simple for now and get the Voodoo2 card working on Windows first.

Gmlb256 wrote on 2022-12-13, 12:28:

For GTA1, try using the GLIDE2X.OVL file from the Voodoo2 3.03.00 (non-beta and not the latest one) driver. It has slightly bett […]
Show full quote

loveburn wrote on 2022-12-13, 05:14:

Gta1, shadow warrior, of cause I tried copy do game folder ovl file ....run exe with or without ovl ... Same results

For GTA1, try using the GLIDE2X.OVL file from the Voodoo2 3.03.00 (non-beta and not the latest one) driver. It has slightly better compatibility with DOS games.

Don't bother running the 3dfx version of Shadow Warrior, it isn't faster, doesn't look better than software rendering and lacks support for voxels.

Just interested, how Nvidia drivers version affect on voodoo 2, and voodoo2 in pure dos......

It is extremely unlikely that the Voodoo2 will be affected by nVidia hardware in Pure DOS/MS-DOS mode. As others mentioned, it is better to keep the things simple for now and get the Voodoo2 card working on Windows first.

I try not to complicate , but no progress with any manipulation above, and results is same.... Not working...

I have also a via 133 pro chip running a coppermine. I found out that v1 does not work with more than 500 mhz. I run my p3 1000 at 500 with 66 fsb and everything is fine. Tried it on a 800 with 100 fsb running at 600 mhz. No luck with dos games. They hang up or pc crashes. Some windows games run but there is a very big delay in input.

I have a diamond monster card using original diamond drivers here from the site and no isdues at all atm. What card do you have

atom1kk wrote on 2022-12-13, 17:59:

I have also a via 133 pro chip running a coppermine. I found out that v1 does not work with more than 500 mhz. I run my p3 1000 at 500 with 66 fsb and everything is fine. Tried it on a 800 with 66 running at 600 mhz. No luck with dos games. They hang up or pc crashes. Some windows games run but there is a very big delay in input.

I have a diamond monster card using original diamond drivers here from the site and no isdues at all atm. What card do you have

V1 or v2 is diamond...

i have only v1 and this one is diamond

I am not sure if you tried this, but do you have a 2D PCI card to test with instead of AGP?

drosse1meyer wrote on 2022-12-13, 21:35:

I am not sure if you tried this, but do you have a 2D PCI card to test with instead of AGP?

Yes sure, I tried s3 trio64v2+

loveburn wrote on 2022-12-13, 21:37:

drosse1meyer wrote on 2022-12-13, 21:35:

I am not sure if you tried this, but do you have a 2D PCI card to test with instead of AGP?

Yes sure, I tried s3 trio64v2+

damn 🙁 you really do have a stubborn motherboard

drosse1meyer wrote on 2022-12-13, 21:40:

loveburn wrote on 2022-12-13, 21:37:

drosse1meyer wrote on 2022-12-13, 21:35:

I am not sure if you tried this, but do you have a 2D PCI card to test with instead of AGP?

Yes sure, I tried s3 trio64v2+

damn 🙁 you really do have a stubborn motherboard

Yes( tomorrow I try other Voodoo2 card, if this card same not working, then just Fu.....off glide and I am be use only perfect d3d or opengl via gf4 ti4200...

loveburn wrote on 2022-12-13, 21:44:

drosse1meyer wrote on 2022-12-13, 21:40:

loveburn wrote on 2022-12-13, 21:37:

Yes sure, I tried s3 trio64v2+

damn 🙁 you really do have a stubborn motherboard

Yes( tomorrow I try other Voodoo2 card, if this card same not working, then just Fu.....off glide and I am be use only perfect d3d or opengl via gf4 ti4200...

or better yet build another retro system for Glide games 😁

drosse1meyer wrote on 2022-12-13, 21:58:

loveburn wrote on 2022-12-13, 21:44:

drosse1meyer wrote on 2022-12-13, 21:40:

damn 🙁 you really do have a stubborn motherboard

Yes( tomorrow I try other Voodoo2 card, if this card same not working, then just Fu.....off glide and I am be use only perfect d3d or opengl via gf4 ti4200...

or better yet build another retro system for Glide games 😁

No thanks, one is enough for me

First of all: VIA chipsets for Intel platforms sucks. If you can, don't use slot1/sk370/sk 478 etc motherboards that have VIA chipsets.
However, in your case, you could try two things.
1. Downclock the CPU, try FSB 66 if you can, you'll get a 600 MHz CPU. It will still be a little too fast for V2 and way too fast for V1, but it might help.
2. Point a good fan to blow air under the V1 / V2.

It should help, but the system will probably still be unstable on the long term. With or without Voodoo.

RaverX wrote on 2022-12-14, 12:45:

First of all: VIA chipsets for Intel platforms sucks. If you can, don't use slot1/sk370/sk 478 etc motherboards that have VIA ch […]
Show full quote

First of all: VIA chipsets for Intel platforms sucks. If you can, don't use slot1/sk370/sk 478 etc motherboards that have VIA chipsets.
However, in your case, you could try two things.
1. Downclock the CPU, try FSB 66 if you can, you'll get a 600 MHz CPU. It will still be a little too fast for V2 and way too fast for V1, but it might help.
2. Point a good fan to blow air under the V1 / V2.

It should help, but the system will probably still be unstable on the long term. With or without Voodoo.

For firstly, my motherboard is absolutely stable with any installed hardware except 3dfx....
Second: all incompatibility hardware what people are talking about working perfectly on me too....... Exactly not from the box, but after small tuning works perfectly! And finally on VIA chipset voodoo 1 and 2 works fine on other people...... So I think need to install other 100% working and tested on other systems voodoo2

My Voodoo 2 works fine on PIII 900E and 440BX.

Finally I have the solution... I just find other Voodoo 2 card, machine running on 133mhz fsb and ram and CPU have full speed at 1.2ghz , and it perfectly works on my boards, I think some voodoo have a revision which are not compatible with via based Mobo.., but perfectly working on other Intel chipset. Thanks all for any ideas!!!!

Most likely it is just a worn out card and therefore not stable on your VIA motherboard. VIA chipsets were quite common back then so I find it unlikely that it wouldn't be stable on one when new.

AlexZ wrote on 2022-12-16, 21:43:

Most likely it is just a worn out card and therefore not stable on your VIA motherboard. VIA chipsets were quite common back then so I find it unlikely that it wouldn't be stable on one when new.

I thinking like you, but some people above, think differently)