I downloaded FastVoodoo2 last night and installed in one of my Voodoo2's.

I ran the FastVoodoo2 setup (then the XP fix that comes with it) then downloaded one of the Orchid Righteous Glide Demo's from FalconFly's site.  I downloaded the Race demo and the engine files to run it as a simple Glide test to see if the Voodoo2 was working properly.

However, as it goes in to launch the program, a Windows error crashes the program and identifies a problem in the glide3x.dll file.  So I got both the "Donut" and "Borg" demos, and they do exactly the same thing.  :'(  Anyone else have this problem on XP?  ???

Beware that you should only install this Fix if you receive Errors with the default installation.

Thus, it might be worth a shot to try it without Fix first.

Otherwise, the mentioned Glide Demos are extremely old, and I can imagine this could cause errors under WinXP not related to the Driver itself (tried the various compatibility options ?).

I've tried the drivers without the fix first.  Brought up some error about a window handle  ???

So I put the fix on, now Windows just crashes with the 'Send, Don't Send' kinda dialogue box, saying that glide3x.dll is at fault.

The old glide demos work fine in XP, with a Orchid Righteous 3D Voodoo1, Macronix Rush, Voodoo3 2000, Voodoo5 5500 PCI.

To me, it looks like the FastVoodoo2 drivers are to blame.  Even the demos that come with FastVoodoo2 bring up the same crash problem when run.

After testing two different Voodoo2 cards, I've come to the conclusion that one of the Voodoo2's is either faulty, or requires some exclusive different Voodoo2 drivers.  >:(

I have tested on WinXP with 3 different set's of V2 drivers from Falconfly's resources.

The first card I have is a Creative 3D Blaster Voodoo2, which works fine.  The second, I do not know what it is, but it has certain distinguishing marks (seen in the photos).  It's memory chips are 110 MHz !!!  :o
The PCB board is also more "blue tinted" than normal V2 boards.
The error I get when I try to run this board is:

"Mapmem driver initilization failure".

As soon as I switch the cables over, to the Creative board, the 3D application's run normally.  Switch the cables back again and the 3d application quits and gives the error again.  :'(

Putting the cards in SLI mode is even weirder.  Run the 3d application, you hear the hardware 'click' kicking in, then the monitor turns off.  End the application blindly, and the monitor kicks back in!  :-/

I'm lost on this one! Don't know where to start!  ???
Can anyone help out on this issue?

Hmm...sounds like an SLI conflict to me... :'(

Especially since it's complaining about a 'memory type conflict' (two different cards with different memory types = NOT GOOD!) :'(

If you run Voodoo 2's in SLI, BOTH cards must be EXACTLY the same. :o

e.g. 2x Creative Voodoo 2, or 2x DIAMOND Voodoo 2, etc... ::)

This is most likely your problem! :(

So go and get another Creative Voodoo 2! ;)

The mapmem error does not come from running an SLI! It comes from running the card on it's own a single Voodoo2.  :P

Hm, you could always join the respective Bug Report / support Forum over at 3dfxzone.it...

http://www.3dfxzone.it/enboard/forum.asp?FORUM_ID=6

wrote on 17.01.04 at 20:29:58:

About the card : perhaps a Jazz Multimedia Renegade 3D, but really not sure. I know that Jazz used always a blue pcb. But since this company has gone out of business...

Does anyone know if there are any specific Jazz drivers available, that I could possibly try out on this card??

Is their any chance that this problem could be Windows XP specific??  Could it be that this card will just not run with WinXP drivers??  Could it be something that small, that makes the difference?

Do you think it's worth my while formatting my 3dfx test machine and installing Win98 or Win2000, and maybe trying it out on one of those??  Which one should I use??

And if so, what drivers would you recommend, as the most generic stable drivers that would surely run with this card?? 3dfx's official latest drivers??  ???

I think patience is right about the manufacturer: it appears to be a similar blue to my own Jazz adrenaline  rush. Are you trying to use both V2s at once, simply not connected to each other? If you're using both, try removing the creative and putting the "jazz" into its PCI slot.

Also, your card appears to be very similar to my diamond, so it should work with the FV drivers.

EDIT: Is there an FCC ID on the card? If so, and the first three characters are LJW, it is definately Jazz.

wrote on 18.01.04 at 18:08:25:

Even if this card is a Jazz, most manufacturers used the 3dfx reference drivers (since they follow the reference design). ps : what's written on the stickers ?

I cannot tell what is written on the stickers from the crappy pictures I took, I will have a look tonight.


Quote:

Can you try your card under Win98 ?

The card was tested under WinXP only.  That may contribute to the errors I receive.  But why would would this V2 card behave differently under XP than any other V2 card??
I am going to test it under Win98 ASAP (and as soon as someone let's me know how to set up this Win98Lite  ::)).


Quote:

you put the card in what slot pci ?

The card is definetely in a PCI slot, as that is all the card will go in.  :P

wrote on 19.01.04 at 03:36:56:

I think patience is right about the manufacturer: it appears to be a similar blue to my own Jazz adrenaline  rush. Are you trying to use both V2s at once, simply not connected to each other? If you're using both, try removing the creative and putting the "jazz" into its PCI slot.

I have tried every combination.  The card does not work for everyone I tried:

- The card on it's own.
- The card sat in the machine next to an unused Voodoo2.
- The card in SLI mode.

All done under XP.


Quote:

Also, your card appears to be very similar to my diamond, so it should work with the FV drivers.

What OS are the Diamond FV drivers for?  Are they located here on FalconFly?


Quote:

EDIT: Is there an FCC ID on the card? If so, and the first three characters are LJW, it is definately Jazz.

I have never had to look for the FCC ID on any card before? Is it located on the front or the back of the Voodoo2 card?

It Works!  :D  I managed to get the 110MHz Voodoo2 to work! But it was a scenario I had tried before!  :-[

The card works on it's own in a machine, as long as another non-identical Voodoo2 (ie my Creative V2) is not present in the machine and/or not connected to a non-identical V2 SLI.  However, I had already tried that scenario on my girlfriends machine.
I tried the 110MHz V2 on it's own in her machine, which is a very new machine with an MSI 8x AGP possible KT333/400 mobo.  That's why it probably didn't work the first time round.  That is when I was receiving glide3x.dll errors.

So I took the cards back to mine and tried the Creative V2 first on it's own in my old machine, which worked fine.  I then added the 110MHz V2, but not SLI.  I swapped to that card, which did not work, but started to receive the different 'mapmem' error. So then I tried the SLI, which didn't work at all, as it kept turning my monitor off.

So I thought I had ruled out all possibilities, but I didn't try the 110MHz V2 on it's own again in my machine, as I had already tried that on my girlfriends machine, which didn't work. So I was confident it wouldn't work again.

However, I tried it last night, and the card is now fine.  The possibilities that it could be are:

- The FastVoodoo2 4.0 drivers DO NOT work with this specific card, as I tried two different sets of drivers the second time round, NOT the FastVoodoo2 ones.  They were the ones that caused the Glide3x.dll error.

- The new PC of my girlfriends I tried  it on could not be compatible with the Voodoo2 due to it being a brand new motherboard, although it would be the first I've ever heard of this.  :-/

EDIT: Hey, I've just noticed this is my 100th post! Woohoo!  :D

I lent a couple of voodoo2 to a friend (techworks v2 12MB with nothing special) and we couldn't run the fastvoodoo2 driver (version 3.0 or 3.5 at the time)
that was on a KT400, under win98SE
but original 3dfx drivers ran w/o problem