FREQUENTLY ASK QUESTIONS
Windows 3.x
________________________________________________________________________
Problem: What version(s) of Windows are currently supported?
Solutions: The Viper PCI supports Windows 3.x. We have a final release of 3.06 available. We have also have a beta driver, release 3.10. Please reference the README.TXT file, of this drivers to identify issues we have corrected.
________________________________________________________________________
Problem: Corruption of icons and title bars in Windows3.x with motherboaords using Aires, Triton, and SIS chipsets.* Also, the wrong colors in DOS through Windows.
Solutions: Disable CPU to PCI Burst Memory Write in the CMOS setup utility.
(Please note: If you are experiencing this issue and have a chipset manufactures that is not listed above, please download the file "BURST.EXE, from our on-line information services. To determine the chipset manufacturer, you can locate two or three approximately one inch square chips on the motherboard with a manufacture name printed on them.)
Problem: Get an error message, "Not Enough Memory to Convert All Icons..." and some icons turn black when using a driver with greater than 256 colors.
Solution: This is a Microsoft Windows limitation. It happens with any video card when using drivers with greater than 256 colors. To correct this problem, either lower the color depth or create new groups and move some icons to the new groups so that each group contains 10 icons or less.
Problem: No matter what resolution is selected, Windows always defaults to 640x480 resolution.
Solution: This problem occurs most frequently on a DEC system. To resolve this issue, move the statement SET VIPERPATH=C:\VIPER to the top of the AUTOEXEC.BAT file.
Problem: No video when system is turned on, or blank screen during Windows 3.x startup.
Solution: Check for a Weitek P9000 jumper on the motherboard, and be sure it is jumpered for the presence of a P9000 based add-in card in the system.
Windows95
_____________________________________________________________
Problem: Setup utility aborts during installation, and the user cannot change modes from 640x480.
Solutions: Be sure to have the latest release of BIOS (V.3.13) also be sure to have the "SET VIPERPATH=X" statement in your autoexec.bat for Windows 95, the "X" denotes the proper path for the VIPER.INI file.
(Please note that that this is the ONLY statement needed in the autoexec.bat file. If you have additional statements regarding the Viper and/or VPRBIOS they should be removed or remarked out)
_____________________________________________________________
CAD Applications
Problem: Using 3D Studio release 3.0.
Solution: Vibrant has drivers for 3D Studio release 3.0. If your Viper card is A4, A7, B1, B3, and D3 revision, you can use the Vibrant drivers that are included with 3D Studio. Their BBS number is (512)918-3411 and the file to download is ID124103.ZIP.
* If you have any difficulties with the installation, contact Autodesk or consult your 3D Studio Installation Guide.
Problem: Get an error message, "1805: P9000 INI file has invalid memory statement!" when loading your CAD application with our Soft Engine drivers.
Solution: To resolve this problem, get an updated VPRMODE.EXE version 2.04. This file is available on our BBS, AOL, CompuServe, or FTP under the name VPRMOD.EXE.
Problem: Get an error message, "1800: Unable to locate P9000RES.INI" when loading your CAD application with our Soft Engine drivers.
Solution: Add SET VIPERPATH=C:\VIPER to AUTOEXEC.BAT and run VPRMODE to setup your monitor.
Problem: Get an error message, "System Fault: Bad memory access. MDL abort in panastn.mc at 303" when starting Microstation with our drivers.
Solution: To resolve this problem, remove EMM386 memory manager from the CONFIG.SYS file. Our drivers are not compatible with this memory manager.
* If you have not run VPRMODE and set up the monitor, please do so. Make sure the line SET VIPERPATH=C:\VIPER is in the AUTOEXEC.BAT.
Windows NT
Problem: What revisions of Windows NT are supported?
Solution: The current drivers available are revision 1.02b, which support Windows NT 3.5x.
________________________________________________________________________
Problem: With a Gateway system using an Intel Mercury motherboard, and BIOS 1003AFI, you get a Kernal Error after installation of the Viper PCI drivers.
Solution: The BIOS is not PCI 2.0 compliant. You need to upgrade to BIOS 1004AFI through Gateway.
Problem: No matter what resolution is selected, Windows NT always defaults to 640x480 resolution.
Solution: If your system is a Zeos Pantera, contact Zeos and get the upgraded BIOS, version 453-0026-07, for your system. If your system is not a Zeos, contact your motherboard manufacture for the latest BIOS.
________________________________________________________________________
Problem: What frequencies are available for which resolutions?
Solution: See chart below:
Mode/Freq 55 60 70 72 74 75
640x480 X X
800x600 X X
1024x768 X X
1280x1024 X X X X
1600x1200 X
Problem: After installing the Viper NT drivers and then rebooting NT, a HEX dump error is displayed, and the boot does not complete.
Solution: Your system's BIOS is not PCI 2.0g complaint. Contact your motherboard manufacture to get the latest BIOS for your system.
Problem: Get a General Protection Fault error in PowerPoint with our drivers installed.
Solution: We currently have a set of BETA drivers, version 1.02, that resolve this problem. You can obtain these from our BBS, AOL, CompuServe, or FTP.
Problem: Get tremendous flicker when using 1280x1024 with refresh rates higher than 60Hz.
Solution: We currently have a set of BETA drivers, version 1.02, that resolve this problem. You can obtain these from our BBS, AOL, or CompuServe.
OS/2 2.x, 3.x, Warp and Warp Connect
Problem: After installing the Viper OS/2 drivers and then rebooting OS/2, a TRAP error is displayed, and the boot does not complete.
Solution: Your system's BIOS is not PCI 2.0g complaint. Contact your motherboard manufacture to get the latest BIOS for your system.
Problem: The mouse is locking up right after the Viper drivers have been loaded.
Solution: To resolve this problem, simply move the line:
DEVICE=\OS2\POWER_9K\P9000.SYS to the second line in CONFIG.SYS file.
Problem: When using OS/2 for Windows, the Win/OS2 full screen displays in standard VGA 640x480.
Solution: The Viper OS/2 drivers, were designed for OS/2 standard edition. To correctly install these drivers in OS/2 for Windows, there are additional steps to follow. The instructions for installing the Viper OS/2 drivers into OS/2 for Windows are available on our BBS, AOL, FTP, and CompuServe.
Problem: The monitor does not synchronize or is off center, under OS/2.
Solution: There is currently no monitor centering utility that will effect the synchronization or screen centering of the Viper board under OS/2. Try to lower the resolution and refresh rate.
Problem: The DOS prompt scrolls when opening a DOS session.
Solution: To resolve this problem, simply move the line:
DEVICE=\OS2\POWER_9K\P9000.SYS to the second line in CONFIG.SYS file.
Problem: Ultimedia Builder/2 runs very slow.
Solution: This is a known issue. Currently there is no correction.
Problem: Multimedia Presentation Manager/2, does not work correctly in 65k or 16.7 million colors.
Solution: Get the Multimedia Corrective Services disks from IBM to correct this problem in 65K colors mode. The Multimedia Presentation Manager/2 currently does not support *any* 32 bpp (bits per pixel) modes. The 16.7 million colors driver for the Viper is a 32bpp driver; therefore, will not work.
Problem: An error message, "386 Enhanced Mode is required When running Win/OS2" occurs when running WinOS/2.
Solution: The Viper OS/2 drivers are not compatible with Win/OS2 when running in Standard mode. You must configure your Win/OS2 to run in 386 Enhanced Mode.
DOS/VESA Applications
Problem: Inverted colors when running a DOS application in standard VGA.
Solution: Obtain Bios version 3.13 or later from us.
Problem: Problems starting the game, "The Seven Guest."
Solution: Contact Virgin and request T7GFIX.ZIP to update your game. Also, you must run VPRMODE VESA from the VIPER directory before loading the game.
Problem: Difficulties configuring Flight Simulator 5.0 to run in super VGA mode.
Solution: Obtain the latest VPRMODE version 2.05b from us. Due to a limitation, this will only work with the Viper 2Mb.
Problem: Get VLB instead PCI when running VIP or when the system starts.
Solution: Get the updated VPRMODE.EXE, version 2.04 which is included in the VPR PCI disk set 3.06 or later. This file is available on our BBS, AOL, FTP, and CompuServe under the name VPRMOD.EXE.
________________________________________________________________________
Problem: No Video during system boot , after installing the Viper PCI card
Solution: Upgrade to the 3.14 BIOS version. This BIOS was implemented to turn off VIDEO PALETTE SNOOPING.
________________________________________________________________________