pyrogx wrote:

Baoran wrote:

Do you know that those registers are exactly the same in Apollo pro 133A chipset and in yout KT133A?

Yes, they are. I checked the datasheet.

It doesn't work. device id/vendor id are different, because it can't find those in the bat file.

Then try changing the device id to the one that your chipsets northbrige uses. I tried to guess the correct one for you but apparently I was wrong...

pyrogx wrote:

Then try changing the device id to the one that your chipsets northbrige uses. I tried to guess the correct one for you but apparently I was wrong...

System information viewer finds VIA VT8605 ProSavage PM133 at device ID 0605
Am I looking at the right thing?

There is also VT82C686A PCI to ISA bridge at device ID 0686 which I assume is the southbridge

Device-ID 0605 should be the correct one.

pyrogx wrote:

Device-ID 0605 should be the correct one.

It didn't change anything with archimedean dynasty. Still with 2.50 ovl file gave error that voodoo not detected after running that batch file with 0605 device id. Perhaps that vt8605 prosavage has different registers?

Maybe, I couldn't find a datasheet for that one. Do other DOS-based Glide games run?

pyrogx wrote:

Maybe, I couldn't find a datasheet for that one. Do other DOS-based Glide games run?

I managed to get the other games tomb raider and Lands of lore 2 to work with 2.56 glide2x.ovl from V3.03.00 voodoo 2 drivers without slowing down the pc from bios. Archimedean dynasty and those 2 games are the only dos 3dfx games that I own. Main problem is that archimedean dynasty doesn't work with any other ovl file except that old 2.50 version and since that 2.56 was the only one that detected voodoo 2, it is a problem.

I don't want to start a new topic so I'll write here.

I have an unusual problem with Voodoo2 that appeared recently (InnoVision MIghty II 3D 8MB).
When I run any game or program that uses Voodoo2 (Direct3D, OpenGL, GLlie), the PC speaker starts making random noises (beep....beep...), sometimes after a few seconds, sometimes right away, sometimes with longer pause, no any rule. This only happens when using Voodoo2, under Win98SE and under DOS (Tomb Raider 1), but when I run the same games on Matrox G400, everything is ok. I installed Voodoo2 about 2 months ago and everything was working fine until now.

I've tried everything, different PCI slots, different drivers, throwing variables from autoexec.bat, various changes in the BIOS.
The only thing I found is that when I install only 128MB of RAM (one module) in the PC, everything back to normal. But when I install 256MB (one module) I can hear the sounds, if it is 128+256 it is also bad, if it is 256+245+128MB it is also wrong. All memory tested with memtest86+, they are fine.
The voltages are rather ok, sometimes 5V drops to 4.6V (HWINFO), but this also happens when I use Matrox G400.

Could anyone advise what could happen that above 128MB the PC speaker makes sounds when using Voodoo2? Motherboard is dying?
The only simple solution I have is to disconnect the PC speaker 😀

I'm 99% sure it's a hardware problem, because under Dos Tomb Raider 1 uses the built-in glide in the .exe

Configuration: Pentium 3 700MHz (7*100MHz), MB: GA-6BX7 (i440BX), Matrox G400 AGP 16MB, Win98SE, USB2.0 PCI controller, Sound card ESS Solo1, SSD 60GB+2x DVD-ROM, PSU: Ultramedia ATX PIV 400W.

Faust66 wrote on 2023-07-21, 13:19:

Could anyone advise what could happen that above 128MB the PC speaker makes sounds when using Voodoo2? Motherboard is dying?
The only simple solution I have is to disconnect the PC speaker 😀

Which Voodoo2 driver are you using? Getting PC Speaker beeps is not normal and the latest reference ones should work fine on a PIII-700 CPU with such amount of RAM.

I'm 99% sure it's a hardware problem, because under Dos Tomb Raider 1 uses the built-in glide in the .exe

Configuration: Pentium 3 700MHz (7*100MHz), MB: GA-6BX7 (i440BX), Matrox G400 AGP 16MB, Win98SE, USB2.0 PCI controller, Sound card ESS Solo1, SSD 60GB+2x DVD-ROM, PSU: Ultramedia ATX PIV 400W.

For that version of Tomb Raider, try setting the FSB to 66 MHz. It is a speed-sensitivity issue with early DOS Glide API.

I am using last reference drivers v30202 for v2. Yesterday I have installed win XP sp3 pro + koolsmoky voodoo 2 drivers 20100221- The same issue.
Changing fsb to 66mhz solved this problem, no any sound from pc speaker. But having cpu with speed 466mhz instead 700 makes me not so happy. I am wondering why everything was fine in last 2 months.

In the end, it turned out that the reason for the sounds from the PC speaker is not Voodoo2. Yesterday I replaced the graphics card with a Matrox G400 for a Geforce 4 440MX, and when using this card there were also sounds.
I looked at the voltages in detail, it turned out that under heavy load the voltage of the +5V line drops to 4.40V. Below 4.60V they start beeping and at 4.4V there is an almost continuous sound, everything works fine. Nevertheless, the power supply needs to be replaced.
It turns out that Voodoo2 was more power-hungry than Matrox G400 and it caused more voltage drops.