Some VESA/DMT timings have been adjusted to more closely match the VESA specification.
System now recovers after sleep with FoxBear running.
The system no longer hangs at MFC42.DLL when installing from floppy.
Corruption of text when windowing a VESA mode that is not supported as windowed and then returning to full screen has been addressed.
Known Limitations ------------------
The NVidia Riva 128 chip used on the Diamond Viper V330 requires an IRQ to function correctly. If no IRQ has been assigned to the card by the motherboard BIOS you may experience symptoms such as windows not booting, or extremely poor performance. The symptoms mostly involve error messages such as "While initializing device, VDD. Windows Protection Error. You must restart your computer." and "While initializing device, NVRM. Windows Protection Error. You must restart your computer." Some motherboard BIOS' allow for an option to "Assign IRQ for VGA". Often times the latest BIOS will also resolve this problem. To correct the problem: Boot into the BIOS setup; Look for an option to enable IRQ for VGA (may be in chipset features or PnP configuration) and set it to enabled or on; Reboot the system and it should bypass the error. For further information please contact your motherboard manufacturer
When running the DXSETUP.EXE program (which comes with Microsoft's DirectX application), the version of the Primary Display Driver will incorrectly be displayed as: 0.00.00.0000. This is an issue with the DXSETUP program. To get the correct driver information, run the DXINFO.EXE program from within the same directory that DXSETUP.EXE is found (on our CD the directory is DirectX\DirectX5\DirectX).
Simultaneous output to a TV and a computer monitor is not supported. To enable output to a TV, disconnect the monitor cable from the Viper card, attach a TV cable and restart your system.
Under some conditions of BIOS, APM, and cursor themes, when a DirectDraw surface is active, and the systems asks the graphics card to enter a low power S1 state, the DirectDraw surface remains active, even if the application is minimized. The Viper will not sleep the monitor in this condition. Upon return to full power-up condition, Windows and/or the application may reset the cursor. When this happens, a cursor previously hidden by the application may become visible again. The cursor will promptly disappear as soon as the mouse is moved. While a workaround could potentially be implemented in the driver, this could introduce many other severe system problems in applications or other undesired behavior.
Duke Nukem fails to enumerate available VESA 2.0 modes. This allows you to select modes which are unsupported, such as 320x400.
Shiny Entertainment's game MDK doesn't handle [CTRL-ESC] task switching to the desktop properly when in D3D mode. This can cause application or illegal operation errors when attempting to do this.