Anyone know which version of GLiDE2X.OVL works best for DOS games on an AthlonXP system? ???

I read on another thread that the most recent version of glide2x.ovl is v2.58 or something... :P

Anyone know where I can get my mitts on this? ???

Or anyone know which version works best with AthlonXP machines...? ???

Lemme' know if ya' find anything... :P

Cheers...

Paul.

paul it dont matter what version gilide you run on your  
amd xp  processor . the most compatibl;e driver ive found for playing newer games is nuangels 5 driver.
at nuangel net.if you can get this driver to work on the newer games like ut 20003 and nolf2 ill tell you how
to make it even better.

Umm, this would be really useful IF I had a Voodoo 5, but I DON'T! :P

I'm running two Voodoo 2's in SLI, and the whole point of getting them is so I can run OLDER games! ;D

So I'll say it again...Thanx, but is there anyone out there with some better advice (like something I can actually use!) >:(

Hey, I'm tryin' not to be 'too' bitchy about this! :P

WTF! This message board substitutes words!!! >:(

It 'should' read B!TCHY, not "pregnant doggy" :o

AND it can't spell doggy right either! :P

Stoopid scripts... :P

;D

Yep, those are in place, and have screwed even myself from time to time *g*

But an Asterix ( * ) in the right place will still allow for all expressions you like ;)

Anyway, I haven't heard of any significant updates for the glide2x.ovl ::)

My best advice is to take the latest one from the Voodoo2 Win9x V3.02.02 Driver.
You might also want to have a look at the Athlon compatible Voodoo2 Driver's glide2x.ovl, although I don't think this particular File changed....

FalconFly's right.  The glide2x.ovl files all seem functionally very similar (although they do vary in size a bit).

Since they only run in DOS the games that glide2x.ovl supports tend to be pretty undemanding (640x480 and so forth).  So, if it works at all you can be pretty sure it's running smoothly on a system with a recent processor!

I did have a problem with the glide2x.ovl file from the 3.02.02s at one time (it went away after a full format and reinstall and I never could understand why).  I just substituted the version from the older DirectX 6 driver.

Do you have a specific problem with a DOS game and your Voodoo2s Paul?

The game I'm testing with is Tomb Raider, but it seems to be affecting others too (DOS only), as GTA won't run either!

The problem is basically that the games 'start', but then as soon as GLiDE2X.OVL is loaded, the game will 'black screen'!

My specs are as follows...

AthlonXP 2400+
256MB DDR PC2700
WD Caviar 60GB
Relysis 12x DVD-ROM
HP CD-RW (can't remember which one)
SB128PCI sound
100Mbps NWK card
Kyro 2 64MB AGP GFX - Main GFX
Creative 12MB Voodoo 2 SLI setup - secondary GFX
Relysis 15" monitor
HUGE amounts of custom cooling (WAY too much to list here)
550W Dual fan PSU.

Can't think of anything else specific, just standard stuff like KBd., Mouse, speakers, etc...

I could check my GLiDE driver versions once I get home (at UNI. at the mo.) if that would help too...

That's all for now, gotta go do some work!

BYE!

I take it that the Voodoo2s work okay in Windows?  If they don't it could be as simple as needing to swap the passthrough and monitor cable over to the other Voodoo2 (only one of them is master and it varies according to the order in which your BIOS prioritises the PCI slots).

I take it you mean the original Tomb Raider game?  For that you need to patch the game to the 3dfx version and then run the game in DOS using a batch file that configures the Voodoo2s to look like a Voodoo Graphics card to the game.  To quote from Moody's Voodoo2 game FAQ (now sadly vanished)-

"Tomb Raider/Tomb Raider - Unfinished Business - works with latest glide patch and the preceding SST batchfile. Here's a more detailed one:

Cut 'n paste...(Game loader for Voodoo 2 based 3D Cards, by Stephen Moore)
set SST_GRXCLK=90
set SST_FT_CLK_DEL=0x4
set SST_TF0_CLK_DEL=0x6
set SST_TF1_CLK_DEL=0x6
set SST_VIN_CLKDEL=0x1
set SST_VOUT_CLKDEL=0x0
set SST_TMUMEM_SIZE=2
SET SST_SCREENREFRESH=60
pause
tomb.exe"

Although, personally, I'd change the last SET line to "=75" or something unless your monitor's more than a hundred years old.

But since GTA isn't working either I think it may be the case that you need to experiment with different glide2x.ovls as you suggest.  If you are running the 3.02.02 reference driver the logical thing would be to try swapping just the glide2x.ovl file from either the 3.03.00 or 3.01.01 driver set and see what happens.

If you have used different drivers in the past it would pay you to do a file search on your system to make sure that the only one the games are going to find is in your Windows\System directory.  Delete all others.

Post to say how it goes.

Ya' my twin Voodoo 2 setup works fine under windows (cept' maybe the weird colours in OGL for quake 2, as mentioned in another thread...only affects quake 2 though? weird?) ???

Regardless, GLiDE works fine... :D

Yup, I've got the 3Dfx Tombraider patch (Tombraider Gold Ed.) so that's O.K. :)

Could be the 'not running it in DOS mode and being a moron NOT to realise this' problem...I saw this somewhere else on another thread and haven't had the chance to try it yet... :-[

Oh, and thanx for the batch file! I'll copy an' paste it and give it a whirl... ;D

Guess I should have tried them in REAL DOS mode first huh? :P

I'll get back to y'all on how it goes! ;)

L8R DUDES! 8)

GRR...Well I tried Tombraider and GTA in DOS and they STILL go 'black-screen'. >:(

Guess I wasn't being as daft as I thought! ::)

Anyway, here's the full list of my GLiDE file specs...

3dfx16v2.dll - 4.11.1.1151
3dfx32v2.dll - 4.11.1.1151
3dfxspl2.dll - 1.0.0.4
3dfxspl3.dll - 1.0.0.4
3dfxv2.drv - 4.1.11.1151
3dfxv2ps.dll - 4.11.1.81
3dfxvgl.dll - 1.0.0.761
fxmemmap.vxd - 4.11.1.15
fxoem2x.dll - 4.1.0.2105
glide2x.dll - 2.56.0.2105
glide3x.dll - 3.3.0.670
glide2x.ovl - dated 16/12/99 @5:10AM

If you know of any newer file versions, let me know! ;D

Cheers again...

Paul.

Hmm.  Are those manufacturer branded drivers (Creative or Diamond or something)?

I would really recommend downloading and installing the 3.02.02 reference driver from FalconFly's archive-
http://www.falconfly.de/voodoo2.htm

It's the final Voodoo2 driver set from 3dfx and it's the most stable, compatible and predictable driver and would give us a good base to start off from.

Does the game sound continue even though the screen is black?  Have you tried moving the connectors over to the second Voodoo2 card?

I'm actually using the Voodoo 2 3.02.02 Athlon compatible release from Falcon's archive of drivers (found at bottom of Voodoo 2 page). :D

Only difference is that I've replaced the 3dfxvgl.dll with the most recent version. ;D

As for your other question, the games don't actually start, they just go straight to a 'black screen'. :'(

Whatcha' mean 'move the connectors? ???

1. Swap card 1 and 2 around...
2. Use one card only...
3. Sumthin' else...

Any other ideas? ???

Cheers again...

Paul.

Paul asked:

Quote:

Whatcha' mean 'move the connectors?

Go and look at the second picture on this page (ignore the text- it's a Mac site)-
http://www.mac3dfx.com/voodoo2.html

What I mean is that you should swap the monitor cable and the SLI passthrough cable over to the other Voodoo2 card and see if that helps.

In SLI one card has nothing connected to it except the internal ribbon cable (first pic) whilst the other has the monitor and, via the passthrough cable, the machine's main video card connected to it.  Unless you're running a MegaMonster (which I understand doesn't have external connectors on one of the two cards) you should try swapping the external connectors to the other card.

If you are running a MegaMonster then I'd suggest swapping the cards around in their PCI slots.

Hope this is clear.  Sorry not to recognise the Athlon compatible drivers  ::)  They should be fine which is why I'm looking at hardware.  I've certainly never heard that glide2x.ovl needs to be tweaked for Athlon compatibility.  If it did then someone would have done it by now!

Ya', I might just give that a try, as this may also be related to the GFX glitches I'm getting in Quake 2. ;)

I 'was' going to send some shots to Falcon to show the GFX errors (brown lines). :'(

But upon TAKING the screenshots I saw that the TGA files created were totally glitch free! ???

The ONLY thing that this suggests is that the frame buffer is somehow getting corrupted before it reaches the screen. (affects Quake 2 only!):P

Explains the totally weird alternate lines of glitchy colour... ::)

Maybe switching primary and secondary cards for SLI would fix this... ???

Guess I'll just have to give it a shot. :P

L8R! 8)

Nope, STILL hasn't fixed it! :(

I tried swapping the pass-through cable to the other card, but it just does the same (glitches in quake 2 and DOS games go black-screen) :P

I even tried using my spare passthrough cable and it STILL didn't fix it! :'(

The only thing I can think of that 'might' (and it's a very slim 'might') be causing this is that although both of my cards are Creative Voodoo 2 12MB.

The first card has 'Silicon Magic' memory chips and the other one has 'Entron-Tech' memory chips. Although this shouldn't matter since they are the same reference board design? ???

Whatever! :P

Lemme' know if anyone thinks of anything! ;D

L8R! 8)

I can't believe that two Creative Blasters wouldn't match.  But... since we're tried everything else...

Why not give the mismatched SLI drivers a try.  It might fix the Quake II thing anyway (although I don't think the ovl file is altered for mismatched SLI so it won't help the DOS issue).

Sorry.  Otherwise I'm stumped.  :-[

Well, it seems that I 'might' have found a partial solution at least... :P

The Quake 2 problem seems to be related to the fact that I'm using the reference drivers... :o

But HOW you all ask! ???

Well, I tried the Creative Hi-Res Mini-GL with Quake 2 and it solved at least half of the GFX glitches! :o

I still get some 'cyan lines' on the explosion effects and the lava is red and white (instead of red and black). ::)

The only way to describe the fault is that some of the textures seem to be partially solarised. :-/

I'm gonna try the Glide2x.ovl from the Creative blaster drivers to see if it will work! :P

There's hope yet! Keep the faith 3Dfx fans! ;D

Peace! 8)

Nope, nuthin' doin'! :(

DOS games STILL go 'black screen'! :'(

At least I half fixed the Quake 2 problems, well sorta... :P

If only DOS games worked, <sigh>! :'(

I might try and see If I can get an EXACT match for one of the cards, so that the memory is the same on both. :-/

But I'll probably be waiting till after Christmas... :(

All I can think of is that it 'must' be a mismatch problem, even though GLiDE works fine with the mismatch drivers... :P

Whatever! :o

L8R! 8)

Just to verify that the problems with Quake 2 and the two Creative Voodoo 2's in SLI is DEFINATELY fixed by using the Creative Mini-GL drivers... ;D

I now use the standard Creative mini-GL set to the 3dfxgl.dll for Quake 2 and the hi-res Mini-GL set to the 3dfxglam.dll for Quake 2. :D

Both work with VERY minor GFX glitches (lava is red and white instead of red and black and you get funky cyan lines on explosions) :P

By the way, does anyone know where I can get my mitts on some Athlon-hacked Creative voodoo 2 drivers? (the most recent version from the creative site, NOT the older ones from before the days of glide3x.dll)???

If not, does anyone know the HEX editing process to make drivers Athlon compatible (i.e., what HEX strings must be changed in the glide2x.dll, glide3x.dll and 3dfx32v2.dll?) ???

Oh and is anyone still reading this thread? ???

Cheers again!

Paul.

I'm still with you Paul.  I just can't think of any way to help.  :(

I've found a page about hex-editing Voodoo2 drivers for mismatched SLI but nothing about the Athlon conversion.

Perhaps a real geek could spot the changes between Athlon and non-Athlon files in a hex editor but its generalising the rule to other files that would be the problem, I expect.

I'm completely stumped by the DOS problem.  ???

Cheers Procerus, glad to know someone is still listening! ;D

Hmm...I guess I'll either have to contact [XCL]TempesT who did the original 'Athlon conversion' or just HEX the files myself (it'll be a B*TCH, but someone has to do it!) :P

Hmm...time for some funky HEXin' methinks... 8)

L8R! ;)