Voodoo driver bugs

Here's a list of known (to me) bugs within 3DFX Win2000 drivers, due to the fact that I'm asked about them (because of the Voodoo Frequency Selector).

   Voodoo4 / Voodoo5 driver v1.01.01:

• There is no 3d mode available after starting from the hibernate mode, the screen remains black after switching to the new (and correct) resolution and frequency.
  Bugfix: none known
• Force Commander doesn't run (stable). It quits without an error message soon after the start of a mission.
  Bugfix: none known
• Low performance, compared to the Win9x drivers.

Voodoo4 / Voodoo5 driver v1.03.00:

• Still no hibernate mode available.
  Bugfix: none known
• Force Commander still doesn't run stable.
  Bugfix: none known
• Some D3D games (e.g. Grand Prix 3) are unplayable due to heavy texture corruptions.
  Bugfix: none known
• Still low performance, compared to the Win9x drivers, but better than the former version

Voodoo4 / Voodoo5 driver v1.04.00:

• Still no hibernate mode available.
  Bugfix: none known
• Some D3D games (e.g. Grand Prix 3) are unplayable due to heavy texture corruptions.
  Bugfix: none known
• Quake 3 "slipped" to the lower left corner of the screen and the frequency is still as low as 60 Hz, although set to a higher value with the VFS. This occurs mostly only with modified frequency settings.
  Bugfix: copy the files "3dfxOGL.dll" and "glide3x.dll" from an older driver Version (preferably 1.03) to the Q3 directory and rename "3dfxOGL.dll" to "opengl32.dll".
• Battle Isle IV: The Andosia War shows in its setup only low frequencies for the selected resolution, although there has a higher one been set with the VFS. If a lower value is selected, the game doesn't start.
  Bugfix: start the VFS, set the values to their standard, apply and restart. Run the BI setup and set the resolution and frequency (the higher one should now be available again). Now Battle Isle will start and even have the right frequency. Afterwards, the general values can be set again with the VFS, but note that you shouldn't set the value for the BI resolution higher than within BI's setup (equal is possible).