Hello all!  :)

I would need a little assistance with my X-24 Card from Quantum3D. I installed the original 3dfx BETA Drivers now knowing that they won't work on my Obsidian2 Card in Win2000. A Guy from the x-3dfx Forums gave me this link:
http://www.falconfly.de/quantum.htm

These (modified NT4?!?) Quantum3D Drivers seem to work even without NTREMAP.SYS...  well..  sort of. Most of the time I get an Error from the Memory Mapper Service, or i get a crashed Rundll32.exe that puts my system under full load. Although i correctly uninstalled the original 3dfx BETA Drivers i suspect them to be responsible for Anthony's Obsidian2 driver not working.

I also get the crashed Rundll32 VERY often when trying to access the display control panel, 'cause those drivers run a Glide splash screen when trying to enter the CPL. Sometimes it works when killing the rundll32 Task, but those cases are rather rare...

I already tried reinstalling the drivers and i already cleaned the registry using Microsoft's Tool. No effect.  ???

I would appreciate any help in that case, thanks in advance.

Quantum3D itself did not reply to my email. I HAD contact to that company some time ago but they seem to have stopped any correspondancy with end users.

The Guy in the x-3dfx Forums said that he's got an Obsidian2 200SBi which should be quite similar to the X-24, and he tried the 3dfx reference drivers and they did not work for him.

I tried those in the first place, and i only got this Memory Mapper Error. ("Memmap returned an error when trying to map memory"). I tried different modified reference beta's and not one worked for me. I tried two systems. I even tried an original NT4 Memmap Service with the same results.

So far only those modified Q3D NT4 Driver works (with massive initialisation problems). When Glide DOES initialize, it runs smooth and stable. But i need 10-20 tries before it works....

Boo!  It's me again, Thrawn.  ;D

Have you tried disabling the glide splash screen with-
SET FX_GLIDE_NO_SPLASH=1
in a batch file?  I wonder if this could be tripping the card's initialization up in some way.

Also have you tried setting your primary card to the same colour depth and resolution as the game you're trying to run?  It's a desperate (and, on the face of it, silly) measure but it might have an effect.  If it did work then you could use PowerStrip to switch the res automatically before running any glide games.

BTW I'm still looking for a resource that mentions the values (apart from the fact that they're "clocks") of those environment variables.  ???

Hm, the Tweak compendium in the Reference Section should list all Settings there are (as far as I know, the Registry entries seem to be identical to the DOS Variables).

Of course, not all will apply to DOS, or older Cards (as many are for V3 to V5 as well), but the basic ones should work, and are fully explained.

@procerus: Hello again!  ;D  

I downloaded "3dfxtools-regtweak.zip" from falconfly, but the registry settings listed are only "SSTH3_" ones, for Banshee / v3 / v5, not for the v².

I also tried deactivating the 3dfx Splash Logo, but this did not work. I tried setting FX_GLIDE_NO_SPLASH to "1" as well as FX_GLIDE_SHAMELESS_PLUG to "0" but both had no effect. Maybe I'm placing the Variables into the wrong registry key?

The installation of the Q3D Drivers created the 3dfx Regkeys as well as Q3D ones in  "..\HKEY_LOCAL_MACHINE\SOFTWARE\", both containing those well-known Registry Settings. I entered the new Values in everywhere i thought it might take effect, but they seem not to work. I also tried setting Win2000 System Environment Variables, but this didn't work either.

A batch File would unfortunately not help me when trying to access the Video Control Panel, since this is no Command Line Executable, but a CPL. However, I tried a batch File for the 3dfx Donut Demo, and initialisation problems are not gone...  unfortunately...

@FalconFly: I do have a complete List of "SSTV2_" / "FX_GLIDE" Settings here, but most of them are not very well or unexplained, and no default values seem to be known. I did find out which variables might have to be set to correct the PCI and memory latency timings, but since i don't know the default values, i can't modify them as i would not really know which settings to apply. I would need to know the default values of the following variables:

SSTV2_FT_CLKDEL
SSTV2_MEMFIFO_ENTRIES
SSTV2_MEMINFO_LFB
SSTV2_MEMINFO_TEX
SSTV2_PCIFIFO_LWM
SSTV2_PFT_CLK_DEL
SSTV2_PFT_CLK0_DEL
SSTV2_PFT_CLK1_DEL
SSTV2_PFT_CLK2_DEL
SSTV2_SLIM_PVOUT_CLKDEL
SSTV2_SLIM_VIN_CLKDEL
SSTV2_SLIM_VOUT_CLKDEL
SSTV2_SLIS_PVOUT_CLKDEL
SSTV2_TF0_CLKDEL
SSTV2_TF1_CLKDEL
SSTV2_TF2_CLKDEL
SSTV2_TF_FIFO_THRESH
SSTV2_VFIFO_THRESH

(already set SLIS_VIN/VOUT & SLIM_VIN/VOUT SLI Clock delays to safe values)

How about these ones :

http://www.geocities.com/k_lupinsky/Voodoo_SST_FX.htm

(Hint : Site Found in the Links Section ;D )

Those should fill a few evenings of tweaking ;)

Thanks, but that is the list i already have (v1/ v2)! :)  What i would need are the default values of all of those variables (or at least the ones i posted). Just playing around with the different variables a bit had absolutely no effects (setting values like 0, 1, 2, 6 or the like).  :-/

Hm, as far as I remember, many of those advanced settings actually did not have any reasonable effect (within benchmarking tolerance), hence they never were of much interest.

Only those, that had a useful effect on performance, were kept in public discussion, so I guess the known (documented) tweaks are as good as good can get...