Lots of threads on this already. Have you searched for ef2000 in these forums yet?

EF2000 for DOS with 3DFX patch looks promising. (You did start the game from the .bat file, right?)

No I did not start the game from a .bat file, because I didn't see that the installer actually created a .bat file in the v2.0 3Dfx version directory (which you install from within windows) which is run within the windows environment even though it's technically a DOS game. This is not a patched version but the boxed v2.0 EF 2000.

Do you have the ef2000 version with 3dfx support ?
do you have the Graphics+ Patch

Yes, the v2.0 box supposedly has the graphics+ patch already included in it if you install the 3Dfx version during the initial install. Did that and I can run the game and get into the menus, but I can't fly. Crashes with the error I stated above. Tried this on two different old school machines, windows 98 and 95, same error. Very frustrating.

I have an original 3Dfx Voodoo (Monster 3D, 4MB) and would love to see this game run on it.

photios wrote:

windows 98 and 95, same error.

Its a dos game, run it in dos

Well the manual says that although the 3Dfx v2.0 is a DOS game you are supposed to run it in a Windows environment, something to do with the way Windows can allocate the memory properly, but I dunno.

I tried booting up with a floppy boot into DOS and I get the same error, can get into the menus but can't fly crashes back to the command prompt with that qrssthardwarequerry error.

I have an original Voodoo 1 here so either a) it isn't finding the card or b) the game isn't patched write from the installer. 3dfxdiag finds the card no problem so it must be the game and the card works in other games that require the .ovl driver.

I might just go a different route and get a hold of EF 2000 1.0 DOS, add the Tactcom edition, and then patch it up with the G+ patch manually and see if I obtain the same result. If that is the case, then there is a problem with the way my v 2.0 is installing the game.

If anyone has the retail v2.0 box game and can run it correctly with the 3dfx install option, please let me know though.

photios wrote:

No I did not start the game from a .bat file, because I didn't see that the installer actually created a .bat file in the v2.0 3Dfx version directory (which you install from within windows) which is run within the windows environment even though it's technically a DOS game.

So are you using the .bat file in your tests? I'm confused.

the taw wiki
http://taw.wikia.com/wiki/Running_EF2000_on_a … _and_Windows_98
you could try adding the v2 enviroment vars to your autoexec.bat

No I'm not using a .bat file, unless the shortcut that is created in the Menu by the installer IS a . bat file, which points to the EF2000.exe. Now there is another .exe in the directory called _ef2000.exe (with the underscore before the ef). I wonder if I should try that one instead and create a .bat file from that one.

What's funny is that the manual says to create a shortcut on your desktop to edit the environment variables that is supposed to point to the .bat file but there is no .bat file created by the Installer. Odd.

As far as the Voodoo2 SST variables are concerned, I don't have a voodoo2 card currently installed, so I shouldn't need them,plus I tried it anways a few days ago just to see and it still gave me the same error.

This whole thing is incredibly bizarre, especially since this isn't a bootleg copy, but the real deal, box, manuals, disc and all of EF 2000 v2.0

If there's a .pif file, environment variables might also be created in there. (.pif files may appear as shortcuts in Windows Explorer. They're not quite the same thing.)

whats your 2d card ?
can you run any other dos 3dfx games

found the voodoo 1 enviroment variables

SET SST_FASTMEM=1
SET SST_FASTPCIRD=0
SET SST_VIDEO_24BPP=1
SET FX_GLIDE_SWAPINTERVAL=0
SET SST_SWAP_EN_WAIT_ON_VSYNC=0
SET SST_SCREENREFRESH=85
SET SST_RGAMMA=1.2
SET SST_GGAMMA=1.2
SET SST_BGAMMA=1.2
SET SST_GRXCLK=60

beware of SET SST_SCREENREFRESH=85
change it to the right refresh for your monitor

Edit: just installed ef2000 (ver 1.0 not 2.0) and it created 2 bat files
config.bat and ef2000.bat

config.bat:
set DID=.
set quick_flag=1
conf.exe

ef2000.bat
set DID=.
set quick_flag=1
_ef2000.exe gui

My 2D card is an Nvidia Geforce 6800 Ultra AGP. Not really much of a 2D card, more like a powerhouse for this machine.

I have two Windows 98 SE machines, one with the 6800 Ultra and the other with a 3Dfx Voodoo 5 5500 agp. Both resulted in the same error.

The Voodoo 1 works fine in both machines in Windows games (and I can confirm these games are using the Voodoo1 and not the 6800 Ultra or the Voodoo5).

I have just about all the DOS glide games. Which one should would you recommend I use to troubleshoot this issue (since I know the card works in Windows glide only games)?

games try fatal racing, carmagedon or tomb raider

ps: with ef2000 you must run config first

It'll remove your ef2000.bat file and create a ef2000.exe file (keeping your _ef2000.exe file) when you upgrade to 2.0 and 3dfx G+.

I dont think there is a v1.0 to v2.0 patch

If you don't have v2.0, Tactcom upgrades EF 2000 to 2.0.

I dont own tactcom though
only
ef 2000 v.10
super ef 2000
ef 2000 bt wireplay edition

Well I've tried upgrading from Ef2000 1.0 DOS ---> Tactcom ---> Graphics+ the slow manual way to see if there is any difference same thing:

Error: grssthardwarequerry<> failed

It looks like it is trying to find the hardware. In other games, it seems to have a tough time finding the voodoo as well in DOS (windows is fine), I wonder if this has to do with this comp being a Pentium 4 Northwood 3.06 Ghz? Could it be that my comp is running too fast and not allowing the program to detect the hardware?

Any additional thoughts? Does anyone play EF2000 2.0 3Dfx successfully?

Thanks.

photios wrote:

I wonder if this has to do with this comp being a Pentium 4 Northwood 3.06 Ghz? Could it be that my comp is running too fast and not allowing the program to detect the hardware?

Didn't you say you tried it on some other machines as well? Were they of similar specs?