Just thought I'd mention the facts on the whole lindows/windows thing.  Microsoft sued for trademark violation.  Lindows sued stating, truthfully, that it was illegal to trademark a generic english word. Microsoft realized that they didn't want everyone and their brother to start stomping all over their trademark(after it was rightly declared void) and made a few quiet proposals to the Lindows people.  They both dropped their cases, Lindows changed their name voluntarily, Microsoft "bought" the Lindows domains, and a few other lindows related domains for big money.  Lindows gets a better name and the company gets a large cash injection, Microsoft doesn't have to try and defend their illegal trademark in court.

How ironic, the program he used to get it running is the same .dll stub that I found and posted to a couple of boards about.  It's what got the game working on my old, now my brothers, kyro 2.  I imagine the stub combined with mesafx would probably get any voodoo card to load it up.

Is it a hardware issue, or a software issue?  Just curious, could a properly written driver get them to share texture memory?  Anyway, I don't think texture memory would stop you from running doom 3, since you can set it to resize the textures, it defaults to 512x512, or 256x256, but if you dropped it down to 64x64, or 32x32 it shouldn't be a problem, and that's before you look to mesafx to resize textures.  In the end, it comes down to why RtCW: ET won't run on my voodoo 1, and day of defeat won't run on a voodoo 3, no 32 bit color support.  MesaFX can only do so much.  Unless their's some way to force downsampling, and I have no idea if that's possible, then we're stuck.

I apologize for going off topic, I just erased a long post when I realize I was cluttering up the MesaFX thread.  MesaFX, Woooot! It, like, makes games run, and stuff.

Voodoo 2 is either an 8 meg or 12 meg card.  In SLI that's either 16 or 24.  A Rage 128 came in 8, 16, and 32.  Don't know which one was used, but see the above link.  Actually, the reason I don't believe it will work now that I think about it is that doom 3 is in 32 bit color.  Not sure how to get around that.

I wouldnt' be sure about impossible, I found this http://blogs.lns.kicks-ass.net/moonjihad/archives/cat_programming.html while desperately searching for a way to make doom 3 run on my brothers computer, which has my old kyro 2 in it.  This worked, but if you go the page, he made the little stub dll to make doom 3 load on his rage 128, and has screenshots of it doing so, at 1 fps.  So getting retail to load on old hardware is possible, doing anything with it after that probably isn't.

Figured someone might be interested in this too, and since this thread is already about doom 3 on a non 3dfx card...

http://www.mitrax.net/phpBB2/viewtopic.php?p=36914#36914

Just scroll down to the last couple of posts, shots of doom 3 on the Kyro 2.

For the voodoo 1, there aren't alot of choices.  I honestly just use which ever one comes with the drivers I'm using, and I haven't found anything better than Iceman's drivers at the moment.  The development of 3rd party drivers for the voodoo 1 doesn't seem to be a huge priority for anyone, I wonder why...

It's just a shame that it's, you know, the worst game ever.

Angel, as a person who does the same thing myself, that is tries to get new games to run on my voodoo 1, for me it's really not about playing the game.  I just like seeing if I can get it to do it because I find it amusing when it actually works.  Although, I remember being kind of impressed with how well RtCW ran on my P2-333 witht he voodoo 1 in it.  I even tried to get it to run Enemy Territory so we would have an extra game terminal on the LAN if a friend didn't bring his own computer over, but where RtCW was gold, I never did get Enemy Territory to work.

You won't get direct anything out of a voodoo 1 in windows XP, the drivers will give you OpenGL and Glide acceleration though.  If you're regular card supports acceleration of any kind, directx will still use it.  If you need directx acceleration with the voodoo 1, you have to run windows 98.

Actually, the I believe he added windows mode support two revisions ago, as long as you have a card that supports it.

I don't believe that the leaked drivers were "new".  And by leaked they mean that not just the drivers were out there, but that the source code was given out by someone.  With the source code available, skilled programmers were able to continue the same work as 3dfx would have been doing were they still around, like fixing bugs, optimizing the code, adding new features, etc.  I think they actually started with source code older than the last official driver release, so they would have had to modify it even to bring it up to the same level, but it atleast gave them something to work with.

You can, but not every program is going to like it.  Programs detect and use it because if someone programs it to use an external resource, in this case opengl32.dll, the first place it looks for it is in it's own directory, then it looks in the system directory.  So if you put a different one where the program is it will stop looking as soon as it finds that one.

Well, if money's not a real consideration I would definitely go with one of the Athlon 64s, they have great support for 32 bit applications, unlike a certain other companies 64 bit processors, so windows 98 SE shouldn't be a problem for them. Plus, when games that support 64 bit processing start coming out, you'll actually be able to upgrade to a 64 bit OS and run them, with out having to run out and upgrade.  And I really like my nforce2 board and wouldn't hesitate to reccomend nforce2 or nforce3 boards to any of my friends, but to everyone their own.