Hi and thanks for the quick reply.

I can't change the PCI frequency in BIOS.
There's a set of jumpers on the motherboard to set the fsb at 133, 166 and 200 for the CPU.
In BIOS there's a menu to adjust or overclock the fsb, and another one for the memory. I haven't tried overclocking as the computer is not stable. I have tried with cpu fsb @ 166 and ram @ 133, still crashes.

So far it looks like this voodoo3 doesn't like anything over 133 fsb. I don't really understand why, as, to my knowledge, the PCI frequency should stay within standards when using standard values for the rest of the motherboard.

When I get more time and courage, I will try it on another motherboard (AsRock PE Pro) with a Pentium4 or a nForce2 motherboard, with my other Athlon XP 3000 @ 166 fsb. I guess that won't happen for another 10 days or so. In the meantime, if anybody has some explanation, I look forward to reading them.

Hallo Leute!

Gosh, it's so quiet here, I guess those 3dfx days are really getting old.
Anyway, I've recently built a setup around a V3-2000 PCI and it'all peachy as long as I keep the fsb at 133 mhz. As soon as I put it at 166, the computer boots to windows 95% of the time, and then gets stuck within maximum 30 minutes, both with Windows 98 SE or Windows XP PRO SP3.
Here's the rest of the setup:

AsRock K7S8XE
Athlon XP 3000+ (fsb 166)
2*1 gig DDR PC 2700 (A-Data Technology)
Soundblaster 128 PCI
ExcelStore Technology J360 hard drive
Powercolor ATI Radeon 9200 Pro

I've changed the CPU and put an Athlon 2400 (fsb 133) and it's 100% stable.

Earlier efforts to troubleshoot:

• Swapped athlon xp 3000 for another athlon xp 3000: same results: stable with fsb @ 133, crashes with fsb @ 166.


• Removed v3-2000 and set fsb @ 166: no problem.


• Removed soundblaster and kept v3-2000: same problem  


• Tried V3-2000 in my Dell XPS 8100 (Intel® Core™ i7-860 Processor
  (8M Cache, 2.80 GHz)) under win xp pro 32b: crashes after a while

Have you guys ever seen anything like this?

Let me know!

Now the Voodoo 5s! I have both an AGP and a PCI (for Mac, flashed). I have tested them with a PIII-S 1.4, a Sempron 2600, a Turion 64 ML-37 and an Athlon64 Mobile 3400

Voodoo 5 5500 PCI (Mac, flashed)

Config 1

CPU: Sempron 2600 @ 1864 gHz
RAM: 1024 DDR 400 CL3
MB: K8T Neo-v (ms-7032 rev1, Bios 5.1)
OS: Win 98SE + Unofficial Service pack
- 3D Mark 2000 (1024x768, 16b color, 16b textures, 16b Z-buff, Triple F. buffer, AMD Athlon opt.): 3465
- 3D Mark 2001SE (1024x768, 16b color, compressed textures, D3D Soft TnL, no AA): 1645

Image Insert:

397.46 KB

Image Insert:

177.43 KB

Config 2

CPU: Turion 64 ML37
RAM: 1024 DDR 400 CL3
MB: ASUS K8N4-E, Latest bios
OS: Win XP Pro SP3 (Amigamerlin 3.1)
3D Mark 2001SE (1024x768, 16b color, compressed textures, D3D Soft TnL, no AA): 3305

Image Insert:

219.71 KB

Config 3

CPU: p3-s 1.4 default
RAM: 512 SDRAM
MB: MSI-6309 (ms-694T Pro)
OS: Win 98SE
- 3D Mark 2000 (1024x768, 16b color, 16b textures, 16b Z-buff, Triple F. buffer, Intel P-III opt.): 4708
- 3D Mark 2001SE (1024x768, 16b color, 16b textures, D3D Soft TnL, no AA): 1907

Config 4

CPU: Athlon64 Mobile 3400
RAM: 1024 DDR 400 CL3
MB: ASUS K8N4-E, Latest bios
Win XP Pro SP3 (Amigamerlin 3.1)
3D Mark 2001SE (1024x768, 16b color, 16b textures, D3D Soft TnL, no AA):
-----Default (fsb 200): 3084
-------------(fsb 215): 3215
-------------(fsb 225): 3330

Voodoo 5 5500 AGP

Config 1

CPU: p3-s 1.4 OC @ 1687 mHz
RAM: 512 SDRAM
MB: MSI-6309 (ms-694T Pro)
OS: Win 98SE
- 3D Mark 2000 (1024x768, 16b color, 16b textures, 16b Z-buff, Triple F. buffer, Intel P-III opt.): 5543
- 3D Mark 2001SE (1024x768, 16b color, 16b textures, D3D Soft TnL, no AA): 2454


Image Insert:

138.46 KB

Image Insert:

166.49 KB


Hardware Settings     3D Mark 2000 3D Mark 2001 SE CPU Mark 99 V1.0

cpu fsb: 133 / Ram freq: 133 4742 2186 124
cpu fsb: 145 / Ram freq: 109 5301 2221
cpu fsb: 150 / Ram freq: 113 5389 2296
cpu fsb: 160 / Ram freq: 120 5543 2454 143
cpu fsb: 160 / Ram freq: 160 ---- 2699 --- *Voodoo freq @ 180





Ok, that's about all I have. I know it's all over the place, but there you go.

Found some old benchmark screenshots from previous configs (I moved and gave away all the hardware, except the voodoos. They don't match the original posting rules, but since some posts already don't match them anymore, I thought it'd be OK to put them here.

I also have records of previous runs, but don't have screenshots for some of them, I'll put them here too.

Voodoo 3 3000 PCI 16MB@166 mHz

Config 1

CPU: Sempron 2600 @ 1864 gHz
RAM: 1024 DDR 400 CL3
MB: K8T Neo-v (ms-7032 rev1, Bios 5.1)
OS: Win 98SE + Unofficial Service pack
- 3D Mark 2000 (1024x768, 16b color, 16b textures, 16b Z-buff, Triple F. buffer, AMD Athlon opt.): 2787
- 3D Mark 2001SE (1024x768, 16b color, 16b textures, D3D Soft TnL, no AA): 1521

Image Insert:

437.53 KB

Image Insert:

466.57 KB



Config 2

CPU: p3-s 1.4 OC @ 1582 mHz
RAM: 512 SDRAM
MB: MSI-6309 (ms-694T Pro)
OS: Win 98SE
- 3D Mark 2000 (1024x768, 16b color, 16b textures, 16b Z-buff, Triple F. buffer, Intel P-III opt.): 3362
- 3D Mark 2001SE (1024x768, 16b color, 16b textures, D3D Soft TnL, no AA): 1789

Image Insert:

395.84 KB

Image Insert:

390.83 KB
P-III wins thanks to its L2 cache (512 vs. 128 for the Sempron)


Voodoo 2 SLI (2x12, mismatched)

CPU: p3-s 1.4 OC @ 1687 mHz
RAM: 512 SDRAM
MB: MSI-6309 (ms-694T Pro)
OS (driver): Win 98SE (FastVoodoo 2.4.6)
Primary VGA: Voodoo 5 5500 AGP
- 3D Mark 2000 (1024x768, 16b color, 16b textures, 16b Z-buff, Triple F. buffer, Intel P-III opt.): 2774
- 3D Mark 2001SE (1024x768, 16b color, 16b textures, D3D Soft TnL, no AA): 1153

Image Insert:

439.04 KB

Image Insert:

463.78 KB

Hi,

Do you have another computer you can try the V2-SLI in? It could be a hardware incompatibility.
If not, do you have another video card to replace the S3 Virge? Also, remove anything that is not needed from that setup (soundcard, leave only one memory stick).
You can also explore the bios settings and try different PCI ports.
My reference game for testing glide is Supreme Snowboarding, you can get a demo version easily enough. Your CPU might be too slow, but when you start the game, you can choose the mode (Software, DX6, DX7, glide) and then you have the list of available resolutions (handy to check if the SLI if set up correctly).
Good luck and let us know your findings.
Edit: just saw that you're using an SSD with a pentium 1. I would swap it for a good old harddrive until everything is working fine.
In the BIOS, if you have the option, set PNP OS on No.

Got my hands on a Celeron 1000 (fsb = 100) and a Pentium 3 866 (fsb = 133).
The Diamond Monster 3d refused to display anything with either cpu at their default frequency.
It did work when running the Pentium 3 at 66 and 83 mhz though, so the Voodoo 1 really doesn't like fsb over 100, at least with Intel CPUs.
I will keep the Pentium 3 in that box, then it's just a matter of changing some jumpers from 66 to 133 mhz to get the voodoo1 running. On the plus side, the setup is very stable with the p3 866 and 2x256 mb of pc150 sdram when I set the fsb at 150.



I also got back an old K7VTA3 for my AMD cpus, will do more testing later.

Hi there,

Ok, I got my hands on some spare old motherboards and I also found some spare time, and here is my conclusion: get a Diamond Monster 3D (Voodoo1).

More info:
I had the opportunity to try different combinations out of the following hardware:

2 A-Trend helios 3d
    http://www.3dfx.ch/gallery/v/3dfx_collectors/3dfx+Collection+by+Xion/Voodoo+Graphics/A-Trend+Helios+3D+Voodoo
     http://www.3dfx.ch/gallery/v/3dfx_collectors3dfx+Collection+by+Xion/Voodoo+Graphics/A-Trend+Helios+3D+Voodoo_001/
1 Diamond Monster 3d
1 Matrox Mystique 4meg
1 geforce2 mx-400 64meg
1 voodoo2 12 meg SLI
1 voodoo5 5500pci
1 voodoo5 5500agp

along with the following motherboards/CPU/Memory

ASUS - P4B-E - rev 1.03 / P4 1800@2400 / 512 SDRAM @ 133
Epox - EP-3VCM / Celeron 666@750 / 1024 SDRAM @ 114
Soltek 75drv5 / Athlon XP 1700+(should be 2400+ or similar, not stable at 166 fsb so 133) / 512 DDRAM @ 166

After many attempts, none of the 2 helios 3d worked with any of the dos drivers I found, and I was thorough.

The Diamond Monster 3D however, works like a charm in any of the motherboards listed here.
To play it safe, I've put it on the Epox, along with the geforce2, and with a dedicated CRT. It works great in DOS (Screamer 2 and Screamer Rally, SWIV 3D), in windows 98se + unofficial Service Pack (Turok, NFS2SE, Half life (only tried a couple of minutes), Dethkarz). I cannot put my V5 AGP in there (unless I removed the network card,  as the onboard sound is broken so I put a SB PCI, and the Monster 3D (small motherboard)), so the geforce is not really used (and it's crap anyway). So there you go, one nice config(#1):

Epox - EP-3VCM / Celeron 666@750 / 1024 SDRAM @ 11 / geforce (pas trop) + Monster 3D (Voodoo 1): so far, excellent for DOS and Windows 98SE.

With the leftovers (only 2 boxes and PSUs), I went for the fastest combination. The Athlon XP / Soltek / DDR left the P4@2400 800 points behind in 3dmarks 2001SE. In Supreme Snowboarding, the Athlon XP is about 10 fps faster @ 1280x1024 than the P4 (~60fps). The V2-SLI also runs fine but is actually not so useful, as it's a bitch to get running properly in DOS (even more with the V5 around).

Another config (#2):
Soltek 75drv5 / Athlon XP 1700+ / 512 DDRAM @ 166 + V5 5500 AGP and V2 12 meg SLI


With the P4, the motherboard's AGP is 1.5v, so I used the V5 PCI.
It performed well and was stable. I don't remember putting the Monster 3D along with it or with another graphic card. For another time.

If I hadn't been limited by the boxes, both in number and in size (one is micro ATX and goes with the epox), I would have kept both the Pentium 4 and the Athlon XP, with v5pci + v1 for the pentium, and the current v5agp+v2SLI for the Athlon.

And if I had to take only one, I would probably try a v5AGP + V2 SLI and a V3PCI+ V1 with 2 LCDs for the v3 and v5 and 2 CRTs for the v2sli or a 4 ports KVM. That's only 4 PCI and 1 AGP... Maybe in my next post, maybe not.

Anyway, if you want to buy a voodoo1, get a Diamond Monster3D.

Some numbers:

Config 1 (Cely + V1)

Dethkarz test config

test 1: metro city: 27 fps
test 2: the pole: 30


3dmark2001SE: default settings 1024x768, 32bit, d3d hrdware T&L: 1095 (for the geforce)



Quake 2

timedemo
MAP DEMO1.DM2

V1 (640x480): 21.5 fps
geforce (640x480): 59.fps


Config 2 (Athlon + v5 and v2 sli)

Dethkarz test config

test 1: Metro City Long
V2: 52 fps (1024x768@75 Hz)
V2: 114 fps (640x480@60 Hz)


test 2: the pole
V5: 74 fps (1024x768@75 Hz)
V2: 61 fps (1024x768@75 Hz)

Anybody with a faster CPU managed to get a voodoo1 running in dos and windows?
Slot1 cpu?
Celeron at 66fsb?

What about AMDs like duron & athlon?

Hi,

following my unsuccessful attempts are getting my Voodoo 1's to run on my P3 1440 S, I would like to know the details of some working configs.

Could you please leave them here.

Useful info would be:

CPU: Multiplier, FSB
Motherboard: Brand, Model, Revision, BIOS, Socket (Slocket if used)
RAM: Frequency and Timings
OS: DOS, Windows
3dfx drivers: as detailed as possible


Thank you for your input. This could be useful to many.

In case you've missed this.

http://vogons.zetafleet.com/viewtopic.php?t=35721&highlight=

Feel free to relocate the post in a more appropriate section if needed.


Cheers,

Interesting fascination going on there.

I understand people who collect the v5 6000 getting annoyed at TM failures when he decides to hack at some rare hardware, but ultimately, it is his money he's spending so he may do as he likes.

As for the v5 6000 community people thinking he should stop buying them, well, maybe they can stop selling them to him. I mean, he's kind of easy to track with google; from the start he said he has some projects of tweaking them and he's been keeping the world informed about his collection expanding and his projects to come.
I mean, if someone owns a v5 6000 and parts from it for a comfortable amount of money, they shouldn't go crying about what happens to it when it's out of their hands. They shouldn't have sold it in the first place.

All in all, I find this all thing quite interesting. On one side, one rich guy who decides to get his hands on many rare and collectible items, not only to drive the prices up but also to try to extract the last bits of performance out of them. On the other side, a church of firm believers in that the remaining items should be preserved.
In the mean time, I'd be happy with a working voodoo1.

Cheers all, and as they say around here, happy new year of the snake!

[Joke mode on]
Haha, thanks for the tips!
[Joke mode off]

Finally got to try both the voodoo1 under win95, win98 and XP...
They both show at POST time but they're dead. They get detected, the drivers install, but when it's time to fire up a glide game under windows or dos, nothing. Good thing they were cheap.

Hi there, and happy Snake year for those who are concerned.

Just got 2 Voodoo 1 on the [too] cheap:
 * One A-Trend Helios 3D http://www.falconfly.de/identify/ATC-2465.jpg
 * One Diamond Monster 3D http://www.falconfly.de/identify/Diamond_Monster_3D.jpg

To celebrate, I put an old 10 gig hard drive in my old computer (p3-s 1400, 512 meg sdram on MSI 6309, Matrox Mystique 2meg) and installed Win95 (b or c).
Why Win95? Because I never managed to get Ultimate Race Pro running properly under Win 98 or later and I also wanted to run Screamer 2 and Screamer Rally (DOS).

As usual, I also installed Supreme Snowboarding, which is for me the best game to test if a Voodoo card works ok (used it with great success with V2, V2-SLI mismatched, V3pci and V5 (pci and agp)).

The Diamond monster does not even get detected. Some connectors on the PCI port have been redone and there's a scratch on the pcb on the back side. I give up on that one for now.

The A-Trend Helios 3D is seen by the bios during POST, detected by Windows 95 and the drivers installed with no complaint.

Problems:

 * In Device Manager, under the 3dfx property pages, there is no information about the driver version.

 * Supreme Snowboarding: before starting, there's a configuration screen in which you choose the 3d engine, then the card, then the resolution.
If I choose DirectX 6 or 7, I can then choose the Mystique and the resolution.
If I choose Glide, then there is only the Voodoo card (normal), but there are no resolution available (list is blank).

 * I tried other old Windows glide games (Dethcarz, Croc) and they don't start in Glide, some of them give me "wingrSstOpen failed" (or similar).

 * Under DOS, for Screamer Rally, the configuration detects both the Mystique and the Voodoo, but if I start the voodoo version, I get the following error message: "grSstOpen failed".
I tried that: https://groups.google.com/forum/?fromgroups=#!topic/3dfx.game.support/-hhz1hgc05I. No luck so far.
I have tried all the glide2x.ovl that I have (6 different versions: some complained that there was no voodoo, some gave me the grsst crap, one got me a messed up screen: this one makes me think the card is not dead).


Anyone has any idea? Is this Voodoo also dead? Hardware conflicts?
Wrong drivers? Wrong Glide settings in autoexec?

I do not have any older motherboard to try the cards but I have a Soltek 75drv5 mobo. I also have smaller SDRAM sticks and an ATI Rage (pci).

I will try with a fresh install of win98se later this week to see what Supreme snowboarding says. In the mean time, feel free to suggest your Voodoo troubleshooting tips.

As often, the answer is in the question... (and probably many times in this forum).
However, this being Friday, having 10 idle minutes before finishing work, and being in the mood, here's my suggestion: make 2 systems.

First:
[Rig 1]
AMD Atlhon XP 1700+ Thoroughbred-B @ 1.66ghz (133 x 12.5)
Asus A7V133 (Via KT133)
Voodoo 3 3000 PCI
OS: dual boot win98se/win xp

Second:
[Rig 2]
Intel Pentium III 600mhz @ 798 (133 x 6)
Asus P2B-F (Intel 440BX)
NVIDIA Riva TNT2 m64 AGP
Voodoo 1 PCI
OS: DOS and win95

Or make 2 in 1:
[Rig 1]
AMD Atlhon XP 1700+ Thoroughbred-B @ 1.66ghz (133 x 12.5)
Asus A7V133 (Via KT133)
NVIDIA Riva TNT2 m64 AGP + Voodoo1 on screen 1
Voodoo 3 3000 PCI on screen two
OS: Multiboot DOS, win95, win98, winXP


You will find that the early glide games will be very happy with your voodoo1, especially under DOS.

You might also want to grab a CRT screen for the voodoo1, or a 4/3 flat screen.
I've tried many voodoos with quite a few motherboards: I could have done with a CRT screen many times as my TFT went out of sync. However, a good flat screen can work.

As for enjoying the games the most, my advice is to start with XP. If it works, then play and enjoy; if it doesn't, then win98. This will get you through the vast majority of glide games on windows.

For the real early windows ones, try win95.
For the dos ones, DOS.

Keep several versions of the glide files in separate, well labeled folders. If a game "should" work but doesn't, COPY the files in the game folder, where the exe file is and try again. This is particularly useful in case you put 2 voodoos in the same box; it's worked fine for me with a v5500 and v2-sli.

DOS:
There are a couple of program that can emulate a CD from an iso file (a la daemon tools), but for DOS. I've used them with ISOs from screamer2 and screamer rally. One of them is called FakeCD. I don't remember where I got them, but google is your friend. Read the instructions and do the copying in windows (mount iso in daemon tools, copy content to "virtual cd" folder, run the dos utility in a window), then go back to dos and voila (more or less, we can discuss this later). Oh some dos tools there: http://sta.c64.org/dosprg.html

That's all I can think of now. You'll find a lot of good info on this forum; use the search function.

Happy new year

The voodoo drivers might have to be modified for this I guess.
I've read through the pages a little bit, it could be a week end project for someone who has the necessary hardware, the patience and some linux knowledge.
I don't have the hardware for this at this time, and doubt that I will get it anytime soon... Might check how much it costs to gather up though,,,

http://www.overclock.net/t/1205216/guide-create-a-gaming-virtual-machine might prove a useful read too.