Nice one, Obi-Wan, did you got it THAT clean ? It looks like it was made yesterday =)
Mine was soooo dirty (it was running in open case for three years, i had to disassemble every cooler )

AFAIK it's simple - b0rken glide3x lib in Mandrake 10 and many other newer distributions
all you need is to dl working glide3x.

Apple - "We won't allow OS X on non-Mac x86 blah-blah..." And... another XPostHACKto will come and here it is - native OS X on your PC

Great !

BTW Your screenshots suck, real game looks  much better

QuoteOriginally posted by Kreshna Aryaguna Nurzaman

Is it because FSAA, or those games simply won't work with Voodoo5? How about Voodoo5 compatibility with DOS Glide games?

Quote
It's not FSAA, i can't run those games with V5 or V4 (and Voodoo3 too)

After reading some articles on the internet, I got the impression that compatibility problem for DOS Glide games was started from Voodoo2. Thus, there are many DOS Glide games that works with Voodoo Graphics but won't work with Voodoo2. On the other hand, Glide games (be it DOS or Windows) that work with Voodoo2 should always work with Voodoo5. Am I correct about this? Please confirm.
Not exactly. Shadow Warrior works fine with Voodoo2 but shows only horizontal blue stripes with Voodoo3 or V4/5
99.9999% of Windows glide2x games will work flawless with Voodoo4-5.
It looks like glide2x.ovl for Voodoo3 and up is broken (and Extreme Assault uses some internal way to access 3Dfx hardware so there's no problems).

So if you want to play DOS glide games,best solution is another machine with Voodoo2.
For newer Windows games (GLQuake,Q2,Q3,Turok and Unreal engine games of course) Voodoo5 is much better.

The reason I'm asking such question is because I'm purchasing both 2xVoodoo2 SLI (Monster 3D) and Voodoo5. I buy Voodoo2 to maintain compatibility with DOS Glide games.

For compatibility with DOS Glide games (such as Jetfighter III, Archimedean Dynasty, etc), should I:
- keep the Voodoo2?
- sell the Voodoo2 and look for Voodoo Graphics instead?
- just play the DOS Glide games using Voodoo5, because it's compatible with all Glide titles (DOS and Windows)?

Thanks

I can run only one DOS Glide game - Extreme Assault. And FSAA 8x works fine
But i can't run Shadow Warrior, Carmageddon or Descent 2 - black screen with yellow dot or blue  horizontal stripes and nothing more...

Oh. Forgot Dreams to reality - it works in single chip mode

http://voodoodrivers.org/files/bios/V5_5500_x.xx-pci(dv-mac).rar

BTW I have V5 5500 Mac but it's not here. I'll dump and post file later.

I have Voodoo2 Mac - all chips with new 3Dfx logo

Chaintech CT-7VJL (KT333) - works fine w/ Barton 2600+ and 6K

QuoteOriginally posted by Obi-Wan Kenobi

QuoteOriginally posted by Flash

The best mobo for Voodoo5 5500-6000 is MSI K8T Master2
How about Dual Opteron system ?

Well that's not gonna work dude, because that mobo has an AGP x8 Pro slot which is 1.5Volt. AGP x8 isn't compatible with AGP x2 3dfx cards, so you can forget by trying to put a Voodoo5 5500/6000 AGP in it.

A Voodoo5 5000 wil work because it has an AGP x4 conector like the Voodoo4 4500 has.

AFAIK chipset supports 3.3v and it's possible to modify slot and use 2x cards.

V5 5000. Eh... it's waaay harder to find than V5 6K and it's not much faster than 4500.

BTW I have now Chaintech 7VJL (KT333) mobo - works fine w/ 5K5/6K

QuoteOriginally posted by dborca

QuoteOriginally posted by vykupitel

That is really good to hear that. Will it be available as binary package?

yes, namely tdfx_dri.so! i might release the patch, too... i dunno...

Damn ! I really want both SLI  and Doom3 support (Better SLI w/o Doom 3 than only Doom3, i have Win98 for that monster butt kickin' stuff). It's not good to have three chips just for more noise and heat.

QuoteOriginally posted by Phalanx

Unlikely.
Especially now that PCIe (PCI Express) is becoming mainstream.

Actually R9200 256Mb is quite enough to play most games at 1024x768x32

QuoteOriginally posted by dborcaone more thing... can Worms3D run in 16bpp? if so, force MesaFX into 16bpp with MESA_FX_IGNORE_PIXEXT=y, then check the log.

Nope. Can't. It crashes and it's in the log:
fxMesaCreateContext: ERROR: grSstWinOpen

I'll try with V5 6K and Opteron 248 tomorrow but i think it will be the same.
BTW here's the log from Doom 3:

Voodoo Using Glide 3.10.00.0658
Voodoo Board: 1/1, Voodoo5 (tm), 2 GPU
Voodoo Memory: FB = 3694592, TM = 2 x 28717056
Voodoo Screen: 640x480:32 RGB, no vertex snapping
Voodoo TMU0 configuration:
Voodoo   00000000-28717040
Mesa: User error: GL_INVALID_VALUE in glTexParameter(param)
Mesa: User error: GL_INVALID_VALUE in glTexParameter(param)
Misc Stats:
 # swap buffer: 5164
Textures Stats:
 Free texture memory on TMU0: 28717040
 Free texture memory on TMU1: 0
 # request to TMM to upload a texture objects: 1246
 # request to TMM to upload a texture objects per swapbuffer: 0.24
 # texture objects uploaded: 1246
 # texture objects uploaded per swapbuffer: 0.24
 # MBs uploaded to texture memory: 14.43
 # MBs uploaded to texture memory per swapbuffer: 0.00
Pixels Stats:
 # pixels processed (minus buffer clears): 7640420
 # pixels not drawn due to chroma key test failure: 0
 # pixels not drawn due to depth test failure: 14314445
 # pixels not drawn due to alpha test failure: 14420947
 # pixels drawn (including buffer clears and LFB writes): 9891105

Looks similar but doom3 is definitely not software rendered - it's too fast for that - 7-30 fps

And Worms - it took about two minutes just to move mouse and close game

here's the log

Voodoo Using Glide 3.10.00.40404
Voodoo Board: 1/1, Voodoo5 5500 (tm), 2 GPU
Voodoo Memory: FB = 9445376, TM = 2 x 11483136
Voodoo Screen: 1024x768:32 RGB, no vertex snapping
cpu vendor: GenuineIntel
MMX cpu detected.
Not testing OS support for SSE, leaving enabled.
SSE cpu detected.
Voodoo TMU0 configuration:
Voodoo   00000000-22966256
Mesa: User error: GL_INVALID_ENUM in glDisable(0x1802)
Mesa: User error: GL_INVALID_ENUM in glDisable(0x1802)
Misc Stats:
 # swap buffer: 364
Textures Stats:
 Free texture memory on TMU0: 22966256
 Free texture memory on TMU1: 0
 # request to TMM to upload a texture objects: 72
 # request to TMM to upload a texture objects per swapbuffer: 0.20
 # texture objects uploaded: 72
 # texture objects uploaded per swapbuffer: 0.20
 # MBs uploaded to texture memory: 3.39
 # MBs uploaded to texture memory per swapbuffer: 0.01
Pixels Stats:
 # pixels processed (minus buffer clears): 1708030
 # pixels not drawn due to chroma key test failure: 0
 # pixels not drawn due to depth test failure: 193198
 # pixels not drawn due to alpha test failure: 13286212
 # pixels drawn (including buffer clears and LFB writes): 2231188