OS/2 Warp FAQ --------------------------------------------------------------------------- General Information Viper cards * Information about Diamond video * Corrupted Icons cards and Warp * Viper SE / Viper Pro Video lock with Win-OS/2 Stealth cards * Viper PCI and OS/2 Trap 0000D Error * Setting OS/2 Warp back to VGA * Installation Questions SpeedStar cards * Go'95 Problems * Supported Reolutions * Installing the correct driver * Lockups When Using Stealth drivers Edge 3D cards * Seamless Win-OS/2 Questions * Benchmark Questions * Driver availability * Mouse Questions * Font Questions Diamond Multimedia Kits * Monitor Questions * Color Palette Questions * Driver availability * Stealth64 Graphics 2001 (Ark 2000PV) TeleCommanders * Stealth 32 * Driver availability --------------------------------------------------------------------------- General Questions about Diamond video cards and Warp Which Diamond video cards have drivers for OS/2 Warp? Most Diamond cards have driver support listed in the Primary Display Driver List that is shipped with Warp. The following cards are compatible with the drivers supplied with Warp. Diamond Product OS/2 Warp Driver Viper Pro Video & Viper SE Weitek Power 9100 Viper VLB & Viper PCI Weitek Power 9000 Stealth 32 Tseng Laboratories ET4000/W32, /W32i, /W32p Stealth 24 S3 86C801, 86C805, 86C928 Stealth Pro S3 86C801, 86C805, 86C928 SpeedStar 24x Western Digital 90C31 / Western Digital 90C33 This depends on the chipset used. SpeedStar Pro Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar Pro SE Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar 64 Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar VGA Tseng Laboratories ET4000 SpeedStar Plus Tseng Laboratories ET4000 SpeedStar 24 Tseng Laboratories ET4000 SpeedStar Hi-Color Tseng Laboratories ET4000 The following list shows the cards that are supported using Diamond supplied driver: Diamond Product Drivers on FTP Installation Guide Stealth 64 VRAM Drivers st64v.html Stealth64 Graphics 2000 series formerly the Stealth 64 DRAM Drivers s64g2000.html Stealth64 Video 3000 series formerly the Stealth 64 Video VRAM Drivers s64v3000.html Stealth64 Video 2000 series formerly the Stealth Video DRAM Drivers s64v2000.html Stealth VRAM Drivers stvram.html Stealth SE Drivers stlse.html --------------------------------------------------------------------------- I have gotten on the Diamond BBS and FTP site. I have only found OS/2 2.1x drivers. Do you have any drivers specifically for OS/2 Warp? At the moment, the OS/2 2.1 drivers are compatible with Warp. Currently, we have reported the need for Warp specific drivers to engineering. --------------------------------------------------------------------------- Do you have any video cards that are DIVE or EnDive compliant? Currently, we do not have video card drivers that are DIVE or EnDive compliant. However, the need for support has been reported to engineering. You may also write a letter to the Product Manager of the of the specific card that you have. To address the letter do so in the following fashion: Product Manager of [i.e. Stealth 64 VRAM] Diamond Multimedia Systems 2880 Junction Ave. San Jose, CA 95134-1922 --------------------------------------------------------------------------- What is the reason for manually expanding certain files for the Stealth video cards? On some systems, the installation program is unable to do this during the installation. Currently, Diamond is working to correct this program. --------------------------------------------------------------------------- Why does SVGADATA.ERR keep growing in size every time I boot Warp? This is a known issue and has been reported to engineering. This file does not have an effect on the drivers so the file can be deleted whenever the files gets too big. --------------------------------------------------------------------------- Everytime I set my setup back to VGA, I just get a flashing cursor after bootup. What can I do to correct this problem? Please see the next section titled "Setting OS/2 Warp back to VGA" --------------------------------------------------------------------------- Setting OS/2 Warp back to VGA The best way to restore Warp back to the VGA driver is to do the following: 1. Restart the computer. 2. When the computer begins to boot, an OS/2 small white block will appear in the right upper corner of the screen. At this point, press the Alt-F1 keys. 3. This will bring up a blue screen with several options. Press ‘V’ to restore VGA. 4. This should restore VGA. If you are unable to start up in VGA mode, please see below. 1. Boot up with the two floppies supplied for the installation of Warp. After the second disk, you will have an option to get to the Command Line, by pressing F3. 2. NOTE: Please do not use Alt-F1 to get to the Command Line. The files to be replaced are still in use. 3. At the root of the drive where OS/2 is installed, make a temporary directory. Type: MD TEMP 4. Type: CD TEMP. This will get you into the TEMP directory. 5. Make a temporary directory on the boot drive (where the OS2 directory is stored): MD TEMP 6. Place the OS/2 CD into the CD-ROM drive. If you have the disk version of Warp, insert Disk 4 of the installation disks. 7. COPY X:\OS2IMAGE\DISK_4\BUNDLE Y:\TEMP 8. where x is the CD-ROM drive and Y is the boot drive where the OS2 directory is stored. 9. If you have a disk version of Warp, BUNDLE will be found on Disk 4 of the installation disks. 10. COPY A:\BUNDLE Y:\TEMP where Y is the boot drive. 11. From the TEMP directory, type UNPACK BUNDLE where y is the OS/2 boot drive. The files will be copied to the proper directories. 12. Restart the computer, when the OS/2 white block appears, press Alt-F1, to select ‘V’ to restore VGA. This should replace the older files in the OS2 directory and the installation can continue. --------------------------------------------------------------------------- Installation Questions When I double-click on Display Driver Install, I get the following error: "Display driver installation detected an invalid argument count in a configuration file (.DSC). Check the configuration file(s)." How do I fix this error? To correct the error do the following: Open a Seamless or Full Screen OS/2 session. Type: CD OS2\INSTALL[Enter] REN WP9100.DSC WP9100.ERR[Enter] REN WP9000.DSC WP9000.ERR[Enter] And also type the following: COPY DSPINSTL.SAV DSPINSTL.EXE[Enter] COPY RSPDSPI.SAV RSPDSPI.EXE[Enter] These two files with the SAV extension should be dated 1/12/95 instead of an older date. These files are the correct versions for the installation. These files should also prevent further error messages. --------------------------------------------------------------------------- Sometimes when I switch to the VGA driver for OS/2 Warp using Alt-F1 setup screen, the VGA files are copied, and OS/2 Desktop appears corrupted which several blocks of colors. What can I do to correct this? This usually occurs with PCI based Stealth cards. You need to shut down the system completely wait 30 seconds and let the computer boot up into OS/2. There is no need to use Alt-F1 to copy the files over again. The computer will boot up using VGA. --------------------------------------------------------------------------- When I run S3INST from the OS/2 prompt, I get the following error, "An error occurred while starting an new session (DSPINSTL.EXE) %1 %2 %3 %4 %5 %6 %7 void." What can I do to fix this problem? You might be running Selective Install in the background while DSPINSTL.EXE runs in the foreground. Make sure you close Selective Install, DOS session and any Win-OS/2 sessions while installing the driver. --------------------------------------------------------------------------- When I try to install the drivers, the installation starts copying files and says it cannot replace the VGA.DRV driver? You might be running a Win-OS/2 session in the background. Close all WIN-OS/2 session that are running in the background. Please refer to the OS/2 manual for instructions. --------------------------------------------------------------------------- When I try to unpack files manually an error message appears, "Data invalid" and nothing happens. You need unpack the files from an OS/2 session rather than DOS session. --------------------------------------------------------------------------- I have a Stealth 64 Grapics 2000 series card (formerly the Stealth 64 DRAM) and I get the following errors when running S3INST.CMD: Error sys0002: file not found Error sys0003: path not found Error sys0002: file not found Error sys0003: path not found Installation then stops. The following will trick the installation into thinking it found the files so it will not produce errors: 1. Open a DOS full screen session. 2. Change to the A: drive. 3. Since the TESTVER file is not found on the disk. There will be a dummy TESTVER file made. EDIT TESTVER [there is no extension on this file] 4. You will get an empty file. Type in "ABC" at the beginning of the file. This will create some contents in the file. 5. Save and exit. 6. Rerun the S3INST.CMD according to the installation instructions. 7. During the installation of S3INST.CMD, you will only now get two errors. Error sys0002: file not found Error sys0003: path not found However, these errors will not effect the proper installation. The Stealth64 Graphics 2000 series OS/2 Drivers version 2.01 fix the above errors. --------------------------------------------------------------------------- Sometimes when I switch to the VGA driver for OS/2 Warp using Alt-F1 setup screen, the VGA files are copied, and OS/2 Desktop appears corrupted which several blocks of colors. What can I do to correct this? This usually occurs with PCI based Stealth cards. You need to shut down the system completely wait 30 seconds and let the computer boot up into OS/2. There is no need to use Alt-F1 to copy the files over again. The computer will boot up using VGA. --------------------------------------------------------------------------- When I am installing your OS/2 Warp drivers, I click on 32 bit S3 Display Driver ver. 2.xx from the Primary Display Driver List: Display driver selected is not supported by this adapter. How can this be fixed? There are several causes of this error. Bellow are suggestions to correct the problem: 1. S3INST.CMD must be executed from the floppy drive in the following manner: A:\S3INST A: C: NOT in the following manner: C:\>A:S3INST A: C: 2. Reinstall DOS support to ensure all files are properly installed. 3. Check to make sure there is an S3 adapter in the computer. 4. Remove the AUTOEXEC.BAT for any video card TSR BIOS programs from a previous video adapter. --------------------------------------------------------------------------- During Display Driver Install, the files begin be copied but there is an unpacking error. How can I do this manually? This sometimes occurs on some systems. To work around this, do the following: 1. After allowing DSPINSTL.EXE to go as far as possible unpacking only some of the files. Cancel the Install program by pressing Cntrl-Esc to get the tasklist. Select the Install program. Then choose CLOSE. 2. Bring up an OS/2 Full Screen. Go to the root of the directory by typing CD\. 3. Later in the installation we will need the destination of the files for the Win-OS2 drivers, to find out where windows resides type: dir win.com /s. Take note of which directory Windows resides. 4. Once at the root of the OS/2 boot drive, type: MD TEMP. This will a create a temporary directory to keep the compressed files. 5. Move to the TEMP directory by typing: CD TEMP 6. Place the Stealth OS/2 Disk 1. Type: COPY A:*.* and press Enter. This will copy all the files found on the DISK 1. 7. Place the Stealth 64 DRAM OS/2 Disk 2. Type: COPY A:*.* and press Enter. This will copy the rest of the files from floppy drive A. 8. To uncompress the files, type: UNPACK2 S3VIDEO [The files will be unpacked in the correct directories.] UNPACK2 S3WIN [The files will be unpacked in the correct directories.] Note: These files will be placed in the appropriate subdirectories depending on where OS2 is booted from and Windows resides. Make any changes to the destination needed to place them in the correct subdirectories. 9. After uncompressing the files, we make sure that the OS/2 will be booted using the S3 drivers. To do this, type from the root directory for the OS/2 boot drive: edit config.sys 10. Check for the following lines, DEVINFO=SCR,VGA,D:\OS2\BOOT\VIOTBL.DCP SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=d:\OS2\MDOS\VSVGA.SYS where D: is the OS/2 boot drive. 11. Once the above lines are verified, restart OS/2. 12. When the installation is complete, do the following: o Open "OS/2 System". o Open "System Setup". o Open the "System" object. The Screen page of the Settings notebook lists all the supported resolutions for your configuration. o Select a resolution; then, close the notebook. Shutdown to have the new settings take effect. --------------------------------------------------------------------------- When I try to unpack files manually an error message appears, "Data invalid" and nothing happens? Unpacking files must be done in an OS/2 session instead of a DOS session. --------------------------------------------------------------------------- When Display Driver Install is unpacking files, I get a SYS3175 error and the installation stops. What can I do to fix this? On some systems, unpacks that come with the Stealth card will produce this error. To go around this problem, do the following: 1. Place the OS/2 Installation CD in the CD-ROM drive. 2. Open an OS/2 Full Screen session. 3. Change CD driver letter and change to the following directory: CD\OS2IMAGE\DISK_2 4. Copy the original unpack files by doing the following: COPY UNPACK*.* C:\OS2 These files should be dated 12/12/95. 5. Close the OS/2 session. 6. Double click on Display Driver Install icon to continue with the rest of the installation. --------------------------------------------------------------------------- I can’t find the Display Driver Icon. Where is it? Scroll to the bottom of the window to find the Display Driver Install icon. If the icon did not get installed, open an OS/2 full screen session, and type DSPINSTL.EXE [enter]. This will load the program on the OS/2 desktop. --------------------------------------------------------------------------- Disk 1 is not accepted during the installation. What can I do about it? The label on the disks are incorrect. The installation needs to have these labels spelled correctly. To correct it, perform the following: * Open an OS/2 full screen session. There is no need to close the DSPINSTL.EXE program. * Place the first Stealth disk in the floppy drive. * Type A: to move to the A drive. * At the prompt type: Label S3 DRV1 Make sure that the customer does not type the word three instead of the numeral 3. Also make sure that there is a space between 3 and D and not an underscore. * Place the 2nd OS/2 Stealth disk in the drive. * At the prompt type: LABEL S3 DRV2 * Close the session and continue with the installation. There is no need to restart. --------------------------------------------------------------------------- Disk 1 is STILL NOT ACCEPTED! Confirm that there is a SPACE and not an UNDERSCORE. Confirm that the number ‘3’ is instead of the word, "three" --------------------------------------------------------------------------- Go'95 Problems --------------------------------------------------------------------------- When I try to run GO95 from a DOS full screen session, I get the following error: Fatal error 286.3330: Single-Step interrupt detected. AX=0000 BX=06AE CX=0000 DX=0057 SI=001F DI=0B49 BP=07AE {other register values} How do I correct this error? This problem occurs because the Phar Lap DOS extender cannot setup the running mode that GO95 requires. Running Go'95 is necessary to load the monitor timings into memory in order to build the monitor configuration file for OS/2, called SVGADATA.PMI. There are three possible OS/2 installation configurations that have slightly different methods for working around this problem: OS/2 (FAT) formatted and PC-DOS or MS-DOS installed on the hard drive OS/2 (HPFS) formatted and PC-DOS or MS-DOS installed on the hard drive OS/2 (HPFS) formatted is the only one installed on the hard drive OS/2 (FAT) formatted and PC-DOS or MS-DOS installed on the hard drive 1. Boot the computer into PC-DOS or Microsoft DOS. 2. Run the GO95 mode utility for the Stealth card. Select the correct flicker-free predefinded monitor (This monitor should be within the specifications stated in the monitor manual.) Note: Custom monitor is not supported under OS/2. 3. Save the configuration. Test the new monitor selection by typing DMS.EXE MONITOR. This will echo back the monitor chosen. 4. Go into the OS2 directory. 5. Type at the C:\OS2> prompt (or the D:\OS2>, "SVGA ON DOS" This creates the configuration file to send the appropriate frequencies to the monitor. SVGA ON DOS will create a file called SVGADATA.DOS. 6. In order to have the new frequencies take effect, you must disable the old configuration file by typing: REN SVGADATA.PMI SVGADATA.OLD And to enable the new configuration file, rename the SVGADATA.DOS by typing REN SVGADATA.DOS SVGADATA.PMI 7. Restart Warp to have the new settings recognized. OS/2 (HPFS) formatted and PC-DOS or MS-DOS installed on the hard drive 1. After the installation has completed, open an OS/2 full screen. 2. Change to the OS2 directory by typing CD\OS2 3. Move to the PC-DOS or MS-DOS partition and install the GO95 utility on this drive. Refer to the video manual regarding the GO95 installation. 4. Copy the SVGA.EXE file to the GO95 directory. To do this type: COPY Y:\OS2\SVGA.EXE X:\GO95\SVGA.EXE. 5. Boot the computer into PC-DOS or Microsoft DOS. 6. Run the GO95 mode utility for the Stealth card. If needed, you can reference the Stealth manual for instructions regarding the GO95 utility. 7. Select the correct flicker-free predefinded monitor (This monitor should be within the specifications stated in the monitor manual.) Note: Custom monitor is not supported under OS/2. 8. Save the configuration. Test the new monitor selection by typing DMS.EXE MONITOR. This will echo back the monitor chosen. 9. Type SVGA ON DOS This creates the configuration file to setup the video card for the monitor chosen. The name of this file is SVGADATA.DOS. 10. Open an OS/2 full screen and type the following: REN Y:\OS2\SVGADATA.PMI Y:\OS2\SVGADATA.OLD 11. And to enable the new configuration file, by typing COPY X:\GO95\SVGADATA.DOS Y:\OS2\SVGADATA.PMI 12. Restart Warp to have the new settings recognized. OS/2 (HPFS) formatted is the only OS installed on the hard drive There are two ways to go around this situation. Download S3REFRSH.EXE file from the S3 BBS at 408-654-5676. The first method is as follows: 1. Open a DOS Full Screen Session. 2. Run the S3REFRSH.EXE utility for the Stealth card. 3. Select the appropriate frequencies for each resolution. Note: Theses settings should be supported by your monitor. Please refer to your monitor manual for the appropriate settings. Save the configuration. Say NO to modifying the AUTOEXEC.BAT. 4. Go into the OS2 directory. 5. Type at the C:\OS2> prompt (or the D:\OS2>, "SVGA ON DOS" This creates the configuration file to send the appropriate frequencies to the monitor. SVGA ON DOS will create a file called SVGADATA.DOS. 6. In order to have the new frequencies take effect, you must disable the old configuration file by typing: REN SVGADATA.PMI SVGADATA.OLD And to enable the new configuration file, rename the SVGADATA.DOS by typing REN SVGADATA.DOS SVGADATA.PMI 7. Restart Warp to have the new resolutions recognized. The second method is: 1. Boot OS/2 and open a full-screen DOS session. 2. Make a blank floppy disk. 3. Run INSTALL.EXE from the DOS/Utils disk that came with the card. 4. Choose to install to the C:\TEMP directory. 5. Files will be copied, and GO95 will attempt to load. It may, or may not, load properly. After the files are copied, abort any further action, and return to the DOS prompt. 6. Copy the following to the blank floppy: COPY C:\TEMP\*.EXE A:\ COPY C:\TEMP\*.DLL A:\ COPY C:\TEMP\*.DAT A:\ COPY C:\TEMP\*.INI A:\ COPY C:\TEMP\*.DMS A:\ COPY {OS/2}:\OS2\SVGA.EXE A:\ 7. Shutdown OS/2 and boot with a PC-DOS or MS-DOS disk. 8. Run GO95 from the new floppy and select a compatible monitor from the list (do not use "User Defined"). 9. Save and exit. 10. Type DMS MONITOR. 11. Type SVGA ON DOS to create SVGADATA.DOS on the new floppy disk. 12. Reboot the computer to get back into OS/2. 13. Open an OS/2 full screen and type the following: REN {OS/2}:\OS2\SVGADATA.PMI SVGADATA.OLD 14. Copy the new SVGADATA.DOS to the OS/2 drive: COPY A:SVGADATA.DOS {OS/2}:\OS2\SVGADATA.PMI 15. Restart Warp to have the new settings recognized. --------------------------------------------------------------------------- Supported Resolutions --------------------------------------------------------------------------- What are the supported resolutions and color depths for the S3 based Stealth cards? The following table shows which modes are supported with the S3 OS/2 drivers for the Stealths: Stealth64 Video 2000 Stealth64 Video 3000 Resolution Memory Stealth 64 DRAM Stealth 64 VRAM Required Stealth SE (868/864/764/732) (964/968) 640x480x8 1Mb YES YES 800x600x8 1Mb YES YES 1024x768x8 1Mb YES YES 1152x864x8 2Mb YES YES 1280x1024x8 2Mb¹ YES YES 1600x1200x8 4Mb¹ YES YES 640x480x16 1Mb YES YES 800x600x16 2Mb¹ YES YES 1024x768x16 2Mb YES YES 1280x1024x16 4Mb¹ YES YES 640x480x24 1Mb² not supported not supported 640x480x32 2Mb YES YES 800x600x32 4Mb¹ not supported YES 1024x768x32 4Mb YES YES ¹ Although the card is capable of these modes, the S3 OS/2 driver requires more memory to display these modes. ² 640x480x24 is not supported for 1Mb memory configuration, however 640x480x32bpp with 2Mb is supported. --------------------------------------------------------------------------- Why are certain resolutions and color depths not supported under OS/2 Warp as they are supported in Windows 3.1x with the same amount of display memory? In order to give OS/2 the ability to multitask graphics intensive programs in DOS sessions, the OS/2 driver needs to have a section of off-screen display memory to let the DOS session believe it is still writing to display memory and therefore the DOS application remains actively working. Since the OS/2 driver needs an extra section of off-screen display memory certain color depths and resolutions to properly run DOS sessions, that is the reason the driver does not support the same resolutions and color depths supported under Windows 3.1x. --------------------------------------------------------------------------- Lockups When Using Stealth drivers --------------------------------------------------------------------------- I have a Stealth64 Video 3000 series card. After I finish installing the drivers, the following error occurs: This program encountered a problem in this session and cannot continue. c0000005 and lots of other CPU register values. Boot stops completely and I must go back to VGA to load Warp. How do I workaround this error? Call Diamond Customer Service for a 1.04 BIOS for the Stealth64 Video 3000 series. This problem only occurs with 1.06 version of the video BIOS for this Stealth card. --------------------------------------------------------------------------- Why does the video BIOS for the Stealth64 Video 3000 series need to be downgraded to version 1.04 to work with Warp? There were some changes made to support DDC compliant monitors in the 1.06 BIOS. These changes prevent the OS/2 driver from loading. Since the OS/2 driver does not support DDC compliant monitors, there is no loss in performance. --------------------------------------------------------------------------- I get the following error when I install the Stealth card on my system, A program in this session encountered a problem and cannot continue. VIDEOPMI.DLL [register values after this] and the computer is unable to boot into Warp. How do I correct his problem? Perform the following to correct the problem: 1. Boot up with the two floppies supplied for the installation of Warp. After the second disk, you will have an option to get to the Command Line, by pressing F3. NOTE: Please do not use Alt-F1 to get to the Command Line. The files to be replaced are still in use. 2. At the root of the drive where OS/2 is installed, make a temporary directory. Type: MD TEMP 3. Type: CD TEMP. This will get you into the TEMP directory. 4. Insert the Stealth OS/2 driver disk 1 into the floppy drive. 5. Type: COPY A:S3VIDEO. This will copy the S3VIDEO file to the TEMP directory. 6. Once the file is copied, to uncompress the files type: UNPACK S3VIDEO C:\TEMP 7. Since in the computer is in the TEMP directory type: COPY *.DLL D:\OS2\DLL COPY *.SYS D:\OS2\MDOS Where D:\ is the bootdrive where OS/2 is installed. This will copy the correct files that were not copied over during the installation. 8. Restart Warp normally without the diskettes. --------------------------------------------------------------------------- I get the following error when I install the Stealth card on my system, A program in this session encountered a problem and cannot continue. BVHSVGA.DLL [register values after this] and the computer is unable to boot into Warp. How do I correct his problem? Perform the following to correct the problem: 1. Boot up with the two floppies supplied for the installation of Warp. After the second disk, you will have an option to get to the Command Line, by pressing F3. NOTE: Please do not use Alt-F1 to get to the Command Line. The files to be replaced are still in use. 2. At the root of the drive where OS/2 is installed, make a temporary directory. Type: MD TEMP 3. Type: CD TEMP. This will get you into the TEMP directory. 4. Insert the Stealth OS/2 driver disk 1 into the floppy drive. 5. Type: COPY A:S3VIDEO. This will copy the S3VIDEO file to the TEMP directory. 6. Once the file is copied, to uncompress the files type: UNPACK S3VIDEO C:\TEMP 7. Since in the computer is in the TEMP directory type: COPY *.DLL D:\OS2\DLL COPY *.SYS D:\OS2\MDOS Where D:\ is the bootdrive where OS/2 is installed. This will copy the correct files that were not copied over during the installation. 8. Restart Warp normally without the diskettes. --------------------------------------------------------------------------- I have a Stealth64 Graphics 2000 series card. I open a DOS Full Screen Session, switch back to the OS/2 Desktop and then back to the DOS Full Screen session and my session locks. What can I do to fix the problem? On some systems, the VSVGA.SYS file that controls this switching does not get replaced by the correct file. To replace it with the correct version of VSVGA.SYS, the following can be done: 1. Open a OS/2 Full Screen Session. 2. On the boot drive (where the OS2 directory is stored), make a temporary directory. 3. Insert the OS/2 Installation CD-ROM into the drive. 4. Copy the VGADOS file to the temporary directory. COPY X:\OS2IMAGE\DISP_1\VGADOS Y:\TEMP where X is the drive letter of the CD-ROM drive and Y is the boot drive where the TEMP directory was made. 5. Change to the TEMP directory and type the following: UNPACK VGADOS Y:\TEMP This should unpack all the files stored in VGADOS to the TEMP directory. 6. Copy the VSVGA.SYS file to the proper directory. COPY VSVGA.SYS Y:\OS2\MDOS\VSVGA.SYS 7. Restart Warp to have the changes take effect. --------------------------------------------------------------------------- After manually installing the correct version of VSVGA.SYS, I still have a problem switching back to the DOS full screen session? This might be due to the incorrect DOS settings. Try the following: 1. Right mouse click on the DOS icon that is opening the DOS full screen session. 2. Click on the Settings Tab. 3. Click on the "DOS Settings" button. A long list of settings will appear. 4. Scroll to towards the bottom of the list to find VIDEO_SWITCH_NOTIFICATION. 5. If the setting is OFF, check it ON. If the settings is ON, check it ON. 6. Save the settings and exit. 7. Restart the DOS full screen session to test if the problem still occurs. --------------------------------------------------------------------------- My system slows down when I switch between applications while in OS/2 Warp. What can I do to improve the time it takes to switch between applications? You can modify the following settings by trial and error to see how they improve or degrade performance: CAUTION: These settings can cause a corrupted screen and certain DOS applications to close unexpectedly because they do not support the screen switching protocol. Be careful when modifying these settings. VIDEO_8514A_XGA_IOTRAP VIDEO_SWITCH_NOTIFICATION VIDEO_MODE_RESTRICTION --------------------------------------------------------------------------- After loading the Stealth drivers, my computer begins to boot, I see the OS/2 logo, then my system locks? On some systems, the installation program has not copied all the files this cause the system to lock while booting. To correct this perform the following: 1. Boot up with the two floppies supplied for the installation of Warp. After the second disk, you will have an option to get to the Command Line, by pressing F3. NOTE: Please do not use Alt-F1 to get to the Command Line. The files to be replaced are still in use. 2. At the root of the drive where OS/2 is installed, make a temporary directory. Type: MD TEMP 3. Type: CD TEMP. This will get you into the TEMP directory. 4. Insert the Stealth OS/2 driver disk 1 into the floppy drive. 5. Type: COPY A:S3VIDEO. This will copy the S3VIDEO file to the TEMP directory. 6. Once the file is copied, to uncompress the files type: UNPACK S3VIDEO C:\TEMP 7. Since in the computer is in the TEMP directory type: COPY *.DLL D:\OS2\DLL COPY *.SYS D:\OS2\MDOS Where D:\ is the bootdrive where OS/2 is installed. This will copy the correct files that were not copied over during the installation. 8. Restart Warp normally without the diskettes. --------------------------------------------------------------------------- Whenever I load a Seamless or Full Screen Win-OS/2 Full session, my computer locks up after 2 minutes. What can I do to correct the problem? This problem occurs because the Display Power Management for the video card is loaded. To prevent this from locking the computer Display Power Management needs to be disabled. To do this, check Win-OS/2 object DOS Settings. Take note of the path of the DOS_AUTOEXEC. Edit this AUTOEXEC.BAT. Delete the line that loads DMPS.EXE into memory. Make sure that both sessions, Win-OS/2 Seamless and Full Screen, are not loading a different version of the AUTOEXEC.BAT. --------------------------------------------------------------------------- How can I get rid of the InControl Tools icon from loading when I load a Seamless Windows session? Edit the WIN.INI file. Search for DCSHKEY.EXE, and remove this filename from the "load=" line. --------------------------------------------------------------------------- Seamless Win-OS/2 Questions --------------------------------------------------------------------------- I have a Stealth 64 VRAM (S3 964). Whenever I try to open a Seamless Win-OS2 session, a clock appears to show it is about to load the session, the arrow reappears, and the nothing happens. How can I correct this problem? Seamless Win-OS2 does not load because the installation was unable to copy 3 files. To correct this you can do the following: 1. Boot up with the two floppies supplied for the installation of Warp. After the second disk, you will have an option to get to the Command Line, by pressing F3. NOTE: Please do not use Alt-F1 to get to the Command Line. The files to be replaced are still in use. 2. At the root of the drive where OS/2 is installed, make a temporary directory. Type: MD TEMP 3. Type: CD TEMP. This will get you into the TEMP directory. 4. Insert the Stealth OS/2 driver disk 1 into the floppy drive. 5. Type: COPY A:S3VIDEO. This will copy the S3VIDEO file to the TEMP directory. 6. Once the file is copied, to uncompress the files by typing: UNPACK S3VIDEO C:\TEMP 7. Now to copy the files to the appropriate directories: COPY *.DLL D:\OS2\DLL COPY *.SYS D:\OS2\MDOS Where D:\ is the boot drive where OS/2 is installed. This will copy the correct files that were not copied during the installation. 8. Restart Warp normally without the diskettes. --------------------------------------------------------------------------- When I run in certain resolutions with your Stealth drivers, I double click on a Seamless Win-OS/2 program and the entire system locks. It is likely that the video card is using the wrong driver. To verify which video card you have, perform one of the following: * If you have Microsoft DOS, you can use MSD.EXE. Once you are in MSD, type V for more information about the video card. The information will state the video BIOS version and the type of video card installed on your system. * If you do not have Microsoft DOS, you may be able to see a blue banner at the beginning of the boot up process. In the blue banner, it states which video card and video BIOS version. * If you are unable to see this banner, which happens on fast computers, you can also look at the card itself. The video BIOS chip will be labeled with a paper label. * After finding out which video card is on the system, you can compare this with the OS/2 drivers that were packaged with the video card. If you need new drivers you can use one of the following options: o Diamond BBS at (408) 325-7175 o Diamond's anonymous FTP server at ftp.diamondmm.com o Customer Service at (408) 325-7100 will mail a disk set --------------------------------------------------------------------------- I have a Stealth 64 VRAM or Stealth64 Video 3000 series (964/968) card. Everytime I open a seamless Win-OS/2 session the colors on my desktop shift to odd colors (wild berry, hot pink and radioactive green)? How do I correct this problem? Do the following to correct color palette shift: 1. Boot up with the two floppies supplied for the installation of Warp. After the second disk, you will have an option to get to the Command Line, by pressing F3. NOTE: Please do not use Alt-F1 to get to the Command Line. The files to be replaced are still in use. 2. At the root of the drive where OS/2 is installed, make a temporary directory. Type: MD TEMP 3. Type: CD TEMP. This will get you into the TEMP directory. 4. Insert the Stealth OS/2 driver disk 1 into the floppy drive. 5. Type: COPY A:S3VIDEO. This will copy the S3VIDEO file to the TEMP directory. 6. Once the file is copied, to uncompress the files by typing: UNPACK S3VIDEO C:\TEMP 7. Now to copy the files to the appropriate directories: COPY *.DLL D:\OS2\DLL COPY *.SYS D:\OS2\MDOS Where D:\ is the boot drive where OS/2 is installed. This will copy the correct files that were not copied during the installation. 8. Restart Warp normally without the diskettes. --------------------------------------------------------------------------- Color Palette Questions --------------------------------------------------------------------------- Why do certain Seamless Win-OS/2 application change the color palette when I am running in 256 colors? The color palette changes because certain Seamless Win-OS/2 applications reassign some of the definitions in the color lookup table while they are loading. Depending on the application, the palette resets back to normal when the application is closed or when it is brought to the foreground. Sometimes the color palette can be preserved if the "Workplace shell palette aware" is turned off. This option can be found in the System object properties. --------------------------------------------------------------------------- I have 4MB of video RAM on my Stealth card, why can I not get 16 million color depth Warp but I'm able to get this color depth in Windows? To get 16 million colors in Warp a driver must be specifically be written and tested for the 4MB Stealth card. We are currently working on a driver for the Stealth cards so they can take advantage of all the color depths. --------------------------------------------------------------------------- Benchmark Questions --------------------------------------------------------------------------- During a benchmark test under Win-OS/2 Full Screen, this Diamond video card scores as high as a simple VGA card? Since OS/2 is a true multitasking operating system, Win-OS/2 Full Screen is just one application that is running. To get the maximum speed when running the benchmark, you need to let the benchmark take priority over other applications. You can change the priority by modifying the Win-OS/2 Full Screen object DOS settings (please refer to you OS/2 Warp Manual). The setting to increase is "Session Priority." The maximum priority that you can assign is 32. --------------------------------------------------------------------------- Mouse Questions --------------------------------------------------------------------------- I have a Stealth64 Graphics 2000 series card. When I open a DOS Full Screen Session, switch back to the OS/2 Desktop and then back to the DOS Full Screen session the mouse dissappers. What can I do to fix the problem? On some systems, the VSVGA.SYS file that controls this switching does not get replaced by the correct file. To replace it with the correct version of VSVGA.SYS, the following can be done: 1. Open a OS/2 Full Screen Session. 2. On the boot drive (where the OS2 directory is stored), make a temporary directory by typing MD TEMP 3. Insert the OS/2 Installation CD-ROM into the drive. 4. Copy the VGADOS file to the temporary directory: COPY X:\OS2IMAGE\DISP_1\VGADOS Y:\TEMP Where X is the drive letter of the CD-ROM drive and Y is the boot drive where the TEMP directory was made. 5. Change to the TEMP directory and type the following: UNPACK VGADOS Y:\TEMP This should unpack all the files stored in VGADOS to the TEMP directory. 6. Copy the VSVGA.SYS file to the proper directory: COPY VSVGA.SYS Y:\OS2\MDOS\VSVGA.SYS 7. Restart Warp to have the changes take effect. --------------------------------------------------------------------------- Under Win-OS/2 Full Screen, when the mouse moves it seems "jerky" and "jumpy?" This can be alleviated by editing the DOS Settings for the Win-OS/2 object. Set the following three items: IDLE_SECONDS to 20 IDLE_SENSITIVITY to 100 MOUSE_EXCLUSIVE_ACCESS to ON --------------------------------------------------------------------------- When I boot up into OS/2, my mouse cursor is invisible, however, when I bring up a Win-OS/2 full screen, the mouse appears in the session. What can be done to correct this? It is likely that the video card is using the wrong driver. To verify which video card you have, perform one of the following: * If you have Microsoft DOS, you can use MSD.EXE. Once you are in MSD, type V for more information about the video card. The information will state the video BIOS version and the type of video card installed on your system. * If you do not have Microsoft DOS, you may be able to see a blue banner at the beginning of the boot up process. In the blue banner, it states which video card and video BIOS version. * If you are unable to see this banner, which happens on fast computers, you can also look at the card itself. The video BIOS chip will be labeled with a paper label. * After finding out which video card is on the system, you can compare this with the OS/2 drivers that were packaged with the video card. If you need new drivers you can use one of the following options: o Diamond BBS at (408) 325-7175 o Diamond's anonymous FTP server at ftp.diamondmm.com o Customer Service at (408) 325-7100 will mail a disk set If you have the correct drivers you will need to rebuild the SVGA.EXE file for the card. Please refer the OS/2 Warp Manual for instructions. --------------------------------------------------------------------------- Font Problems --------------------------------------------------------------------------- When I am running with Stealth drivers, my text appears corrupted and my screens do not refresh properly? This could be due to a hardware conflict with COM4. IBM originally defined the address space 02E8h-02EFh as reserved. For this reason, S3 based video cards, such as the Stealth series, were designed to use this address space. Since the S3 based video cards are 16-bit devices, they can see all of the 16 bits when they are being addressed by the driver. However, an 8-bit device cannot see the other 8-bits when the 16-bit devices are being addressed. This hardware conflict causes the text to be corrupted or the screen not to refresh. To resolve the conflict, the 8-bit device usually a modem, serial card, or network card needs to be moved to a different COM port. Most of the time COM 4 is usually the port that occupies the above address range. NOTE: The video card address range cannot be moved. This is inherit in the S3 chip. --------------------------------------------------------------------------- I have a Stealth 64 VRAM. Whenever I bring up a Win-OS/2 Full screen, the icon text appears corrupted, then I switch back to the OS/2 desktop and back to the Win-OS/2 full screen session and the text is back to normal. What can I do to correct the problem? This only happens with icon text other than the system default for Windows. To set Windows back to the default, you can do the following: 1. Edit the win.ini that is being used by Win-OS/2 session. 2. Move down to the [Desktop] section. Find the following line: IconTitleFaceName={any font may appear here} 3. Place a semi-colon (;) in front of the line to have Windowsignore the line. By doing this, Windows will use the default system font. Diamond is currently working to correct this problem. --------------------------------------------------------------------------- Every where in Warp my fonts are corrupted. How can I correct this? It is likely that the video card is using the wrong driver. To verify which video card you have, perform one of the following: * If you have Microsoft DOS, you can use MSD.EXE. Once you are in MSD, type V for more information about the video card. The information will state the video BIOS version and the type of video card installed on your system. * If you do not have Microsoft DOS, you may be able to see a blue banner at the beginning of the boot up process. In the blue banner, it states which video card and video BIOS version. * If you are unable to see this banner, which happens on fast computers, you can also look at the card itself. The video BIOS chip will be labeled with a paper label. * After finding out which video card is on the system, you can compare this with the OS/2 drivers that were packaged with the video card. If you need new drivers you can use one of the following options: o Diamond BBS at (408) 325-7175 o Diamond's anonymous FTP server at ftp.diamondmm.com o Customer Service at (408) 325-7100 will mail a disk set --------------------------------------------------------------------------- When I open a Seamless or a Full Screen Win-OS/2 session, the fonts naming windows and my menus are larger than normal. What lines do I need to change to get a smaller font? Unfortunately, there are only two font sizes (XGA and VGA) that Windows can use in Warp and regular Windows running under DOS. However, if you are currently using XGA fonts, you can change the following lines in the SYSTEM.INI to the smaller VGA font: fonts.fon=xgasys.fon to fonts.fon=vgasys.fon fixedfon.fon=xgafix.fon to fixedfon.fon=vgafix.fon oemfonts.fon=xgaoem.fon to oemfonts.fon=vgaoem.fon Reopen the Session for the changes to take effect. --------------------------------------------------------------------------- Monitor Questions --------------------------------------------------------------------------- How can I get a flicker-free higher resolutions when using my Stealth card? You may need to choose a different pre-defined monitor for the mode utility that accompanies the video card. After doing this, it will be necessary to rebuild the monitor configuration file called SVGADATA.PMI. The following explains building the SVGADATA.PMI given three possible types of OS/2 installations: OS/2 (FAT) formatted and PC-DOS or MS-DOS installed on the hard drive OS/2 (HPFS) formatted and PC-DOS or MS-DOS installed on the hard drive OS/2 (HPFS) formatted is the only one installed on the hard drive OS/2 (FAT) formatted and PC-DOS or MS-DOS installed on the hard drive 1. Boot the computer into PC-DOS or Microsoft DOS. 2. Run the DOS monitor utility for your Stealth card (ex: S64DMODE.EXE, S64MODE.EXE, or GO95.EXE). Select the correct flicker-free predefinded monitor (This monitor should be within the specifications stated in the monitor manual.) Note: Custom monitor is not supported under OS/2. 3. Save the configuration. Load the new monitor selection by running the "MONITOR" parameter of the DOS monitor program (ex: S64DMODE MONITOR, S64MODE MONITOR, or DMS MONITOR). This will echo back the monitor chosen. 4. Go into the OS2 directory. 5. Type at the C:\OS2> prompt (or the D:\OS2>, "SVGA ON DOS" This creates the configuration file to send the appropriate frequencies to the monitor. SVGA ON DOS will create a file called SVGADATA.DOS. 6. In order to have the new frequencies take effect, you must disable the old configuration file by typing: REN SVGADATA.PMI SVGADATA.OLD And to enable the new configuration file, rename the SVGADATA.DOS by typing REN SVGADATA.DOS SVGADATA.PMI 7. Restart Warp to have the new settings recognized. OS/2 (HPFS) formatted and PC-DOS or MS-DOS installed on the hard drive 1. After the installation has completed, open an OS/2 full screen. 2. Change to the OS2 directory by typing CD\OS2 3. Move to the PC-DOS or MS-DOS partition and install the DOS monitor utility on this drive. Refer to the your manual regarding this installation. 4. Copy the SVGA.EXE file to the GO95 directory. To do this type: COPY Y:\OS2\SVGA.EXE X:\{DOS util dir}\SVGA.EXE. 5. Boot the computer into PC-DOS or Microsoft DOS. 6. Run the DOS monitor utility for your Stealth card (ex: S64DMODE.EXE, S64MODE.EXE, or GO95.EXE). Select the correct flicker-free predefinded monitor (This monitor should be within the specifications stated in the monitor manual.) Note: Custom monitor is not supported under OS/2. 7. Save the configuration. Load the new monitor selection by running the "MONITOR" parameter of the DOS monitor program (ex: S64DMODE MONITOR, S64MODE MONITOR, or DMS MONITOR). This will echo back the monitor chosen. 8. Type SVGA ON DOS This creates the configuration file to setup the video card for the monitor chosen. The name of this file is SVGADATA.DOS. 9. Open an OS/2 full screen and type the following: REN Y:\OS2\SVGADATA.PMI Y:\OS2\SVGADATA.OLD 10. And to enable the new configuration file, by typing COPY X:\GO95\SVGADATA.DOS Y:\OS2\SVGADATA.PMI 11. Restart Warp to have the new settings recognized. OS/2 (HPFS) formatted is the only OS installed on the hard drive There are two ways to go around this situation. Download S3REFRSH.EXE file from the S3 BBS at 408-654-5676. The first method is as follows: 1. Open a DOS Full Screen Session. 2. Run the S3REFRSH.EXE utility for the Stealth card. 3. Select the appropriate frequencies for each resolution. Note: Theses settings should be supported by your monitor. Please refer to your monitor manual for the appropriate settings. Save the configuration. Say NO to modifying the AUTOEXEC.BAT. 4. Go into the OS2 directory. 5. Type at the C:\OS2> prompt (or the D:\OS2>, "SVGA ON DOS" This creates the configuration file to send the appropriate frequencies to the monitor. SVGA ON DOS will create a file called SVGADATA.DOS. 6. In order to have the new frequencies take effect, you must disable the old configuration file by typing: REN SVGADATA.PMI SVGADATA.OLD And to enable the new configuration file, rename the SVGADATA.DOS by typing REN SVGADATA.DOS SVGADATA.PMI 7. Restart Warp to have the new resolutions recognized. The second method is: 1. Boot OS/2 and open a full-screen DOS session. 2. Make a blank floppy disk. 3. Choose the installation path for your card from the following two routes: For Stealth64 Graphics 2000 series For Stealth64 Video family and Stealth 64 VRAM and Stealth SE a. Copy S64DMODE.EXE or S64MODE.EXE from the a. Run INSTALL.EXE from the DOS/Utils first OS/2 install disk to the blank floppy. disk that came with the card. b. Copy SVGA.EXE (from the S3INST routine) from b. Choose to install to the C:\TEMP directory. the \OS2 directory to the blank floppy. c. Files will be copied, and GO95 will attempt c. Shutdown OS/2 and boot with a PC-DOS or MS-DOSto load. It may, or may not, load properly. disk. After the files are copied, abort any further d. Run S64DMODE or S64MODE and select a action, and return to the DOS prompt. compatible monitor from the list of choices (do d. Copy the following to the blank floppy: not use "Custom"). COPY C:\TEMP\*.EXE A:\ e. Save and exit. COPY C:\TEMP\*.DLL A:\ f. Type S64DMODE MONITOR or S64MODE MONITOR COPY C:\TEMP\*.DAT A:\ g. Type SVGA ON DOS to create SVGADATA.DOS COPY C:\TEMP\*.INI A:\ on the new floppy disk. COPY C:\TEMP\*.DMS A:\ COPY {OS/2}:\OS2\SVGA.EXE A:\ e. Shutdown OS/2 and boot with a PC-DOS or MS-DOS disk. f. Run GO95 from the new floppy and select a compatible monitor from the list (do not use "User Defined"). g. Save and exit. h. Type DMS MONITOR. i. Type SVGA ON DOS to create SVGADATA.DOS on the new floppy disk. From here on out, the procedure is the same for both: 4. Reboot the computer to get back into OS/2. 5. Open an OS/2 full screen and type the following: REN {OS/2}:\OS2\SVGADATA.PMI SVGADATA.OLD 6. Copy the new SVGADATA.DOS to the OS/2 drive: COPY A:SVGADATA.DOS {OS/2}:\OS2\SVGADATA.PMI 7. Restart Warp to have the new settings recognized. --------------------------------------------------------------------------- What is the reason for not being able to use Custom for configuring the Stealth driver under Warp? When SVGA.EXE creates the configuration file, SVGADATA.PMI, SVGA.EXE can only capture a certain amount of bytes in each register on the video card and other components of the computer. These register settings are saved and used when OS/2 changes resolution and color depth. When Custom is used there are more bytes than SVGA.EXE can capture. To work around this problem, a new version of SVGA.EXE and other files need to be developed. --------------------------------------------------------------------------- When I center my screen while in the Presentation Manager, my screen in DOS is off by an inch from the right side. What can I do to correct this since Custom is not supported? Most new monitors will automatically reset themselves properly to accommodate switching between a text mode and a graphics mode. Moreover, other monitors are programmable so the monitor can automatically reset themselves properly when switching modes. If you do not have this type of monitor, you can change the monitor type and rebuild the SVGADATA.PMI. Please refer to the previous section explaining the methods for rebuilding the SVGADATA.PMI. --------------------------------------------------------------------------- Stealth64 Graphics 2001 series --------------------------------------------------------------------------- Disk 1 is not accepted, when I install the drivers for the Stealth 64 Graphics 2001. 1. Open an OS/2 full screen session. There is no need to close the DSPINSTL.EXE program. 2. Place the Stealth64 Graphics 2001 disk in the floppy drive. 3. Type A: to move to the A drive. 4. At the prompt type: LABEL ARK_OSWARP Make sure that there is an UNDERSCORE between "ARK" and "OSWARP," and not a SPACE. --------------------------------------------------------------------------- Whenever I open a DOS full screen session, switch to the OS/2 Desktop and back to the DOS full screen session, the DOS session locks. What can I do to fix it? This may be due to the incorrect DOS settings. Try the following: 1. Right mouse click on the DOS icon that is opening the DOS full screen session. 2. Click on the Settings Tab. 3. Click on the "DOS Settings" button. A long list of settings will appear. 4. Scroll to towards the bottom of the list to find VIDEO_SWITCH_NOTIFICATION. 5. If the setting is OFF, check it ON. If the settings is ON, check it ON. 6. Save the settings and exit. 7. Restart the DOS full screen session to test if the problem still occurs. --------------------------------------------------------------------------- Do you have driver that supports OS/2 2.1x for the Stealth64 Graphics 2001? Currently, we do not have video drivers for the Stealth 64 Graphics 2001 for OS/2 2.1x. However, the need for support has been reported to engineering. You may write a letter to the Product Manager of the Stealth64 Graphics 2001. To address the letter, do so in the following fashion: Product Manager of Stealth64 Graphics 2001 Diamond Multimedia Systems 2880 Junction Ave. San Jose, CA 95134-1922 --------------------------------------------------------------------------- Stealth 32 (Tseng Labs ET4000/W32) --------------------------------------------------------------------------- How do I set refresh rate on the Stealth 32? 1. Open an OS/2 full screen session. 2. Change to the OS2 directory. Type CD OS2 3. Type the following: SVGA ON INIT 4. This will bring up the list of monitors. Select a compatible monitor type depending on the monitor specifications found in your monitor manual. 5. Restart OS/2 for the changes to take effect. --------------------------------------------------------------------------- Whenever I open a DOS full screen session, switch to the OS/2 Desktop and back to the DOS full screen session, the DOS session locks. What can I do to fix it? This may be due to the incorrect DOS settings. Try the following: 1. Right mouse click on the DOS icon that is opening the DOS full screen session. 2. Click on the Settings Tab. 3. Click on the "DOS Settings" button. A long list of settings will appear. 4. Scroll to towards the bottom of the list to find VIDEO_SWITCH_NOTIFICATION. 5. If the setting is OFF, check it ON. If the settings is ON, check it ON. 6. Save the settings and exit. 7. Restart the DOS full screen session to test if the problem still occurs. --------------------------------------------------------------------------- Corrupted Icons --------------------------------------------------------------------------- When I go into a Win-OS/2 Full screen session when using the Viper SE or Viper Pro Video, my icons are corrupted and scrambled? 1. Reboot the computer. 2. Go into the motherboard CMOS setup. Please refer to your motherboard manual for further instructions on how to configure the CMOS setup. 3. Usually under Advanced Chipset, find the following (not all may apply) and DISABLE them: PCI Burst VGA Frame Buffering 4. Save the setup and restart the computer to have the changes take effect. If you are unable to find PCI burst or VGA Frame Buffering, contact your motherboard manufacturer for an updated BIOS. --------------------------------------------------------------------------- Win-OS/2 Freezes when loading with the Viper SE or Viper Pro Video --------------------------------------------------------------------------- I am currently running Warp for Windows, and the following occurs when I use the Viper SE and Viper Pro Video drivers only: Double click on Win-OS/2 Full Screen | Usually a blank screen with flashing cursor and the session locks. OR Boot into MS DOS | Type "win" to load Windows running | Usually a blank screen with a flashing cursor and a lock? What can I do to resolve this? Either symptom can happen depending on which driver was installed last. Problem: There is a conflicting file named p91init.dll. Win OS/2 p91init.dll 19,616 10-31-94 Win 3.11 p91init.dll 31,923 10-26-94 Since both Win-OS/2 and Win 3.11 use the same filename, not the same file, you get a blank screen depending of which driver was last installed. Workarround: 1. Using SETUP, switch back to the VGA driver. Then install the Diamond Windows driver under MS DOS. Make sure you are able to load Windows. 2. At the command prompt, type CD WINDOWS\SYSTEM. 3. Then make a copy of the this version of the p91init.dll for running Windows 3.11. COPY p91init.dll p91init.win This p91init.dll is dated 10-26-94. 4. Boot into OS/2. 5. Switch back to the VGA driver using Selective Install. For additional information, please refer to the OS/2 Warp manual. 6. After rebooting, we need to make a copy of the Win-OS/2 version of p91init.dll. Reinstall the Weitek Power 9100 driver using Selective Install. 7. After rebooting OS/2, open a OS/2 Full Screen. 8. At the OS/2 command prompt, type CD WINDOWS\SYSTEM 9. Now we can make a back up of the Win-OS/2 version of the file: COPY p91init.dll p9init.os2 This p91init.dll is dated 10-31-94. 10. You can now copy the correct file depending of which version of the Windows you will be running. Batch Files: Below are two batch files to restore the correct file: Win-OS/2 Name of file WINOS.BAT: REM This file is used under Win-OS/2 REM This batch file restores the Win-OS/2 file p91init.dll dated REM Win OS/2 p91init.dll 19,616 10-31-94 COPY c:\windows\system\p91init.os2 c:\windows\system\p91init.dll winos2.com copy c:\windows\system\p91init.win c:\windows\system\p91init.dll REM end MS Windows Name of file is WINMS.BAT REM This file is used under MS Windows REM This batch file restores the MS Windows p91init.dll dated REM Win 3.11 p91init.dll 31,923 10-26-94 COPY c:\windows\system\p91init.win c:\windows\system\p91init.dll C:\windows\win.com COPY c:\windows\system\p9init.os2 c:\windows\system\p91init.dll REM end --------------------------------------------------------------------------- Viper PCI and OS/2 Trap 0000D Error --------------------------------------------------------------------------- I get the following error when I boot my machine in OS/2 with the Viper PCI: OS/2: TRAP 00000D error" The motherboard BIOS level is not fully PCI 2.0 spec compliant. Call your motherboard manufacturer for an upgrade to a PCI 2.0 compliant BIOS. --------------------------------------------------------------------------- Installing the correct SpeedStar driver --------------------------------------------------------------------------- What Warp drivers do I use for my SpeedStar video card? The following table shows the respective driver that can be chosen through Selective Install icon: Video Card IBM supplied Warp Driver SpeedStar 24x Western Digital 90C31 (This depends on the chip found on the board.) Western Digital 90C33 SpeedStar Pro Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar Pro SE Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar 64 Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar VGA Tseng Laboratories ET4000 SpeedStar Plus Tseng Laboratories ET4000 SpeedStar Hi-Color Tseng Laboratories ET4000 SpeedStar 24 Tseng Laboratories ET4000 Diamond Product OS/2 Warp Driver SpeedStar 24x Western Digital 90C31 / Western Digital 90C33 This depends on the chipset used. SpeedStar Pro Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar Pro SE Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar 64 Cirrus Logic, 5426, 5428, 5430, 5434 SpeedStar VGA Tseng Laboratories ET4000 SpeedStar Plus Tseng Laboratories ET4000 SpeedStar 24 Tseng Laboratories ET4000 SpeedStar Hi-Color Tseng Laboratories ET4000 --------------------------------------------------------------------------- Driver availability for the Edge 3D --------------------------------------------------------------------------- Do you have OS/2 Warp video and audio drivers for your 3D Edge? Currently, the 3D Edge is only designed for Windows 95. You may write a letter to the Product Manager of the Edge 3D. To address the letter do so in the following fashion: Product Manager of Edge 3D Diamond Multimedia Systems 2880 Junction Ave. San Jose, CA 95134-1922 --------------------------------------------------------------------------- Driver availability for the Diamond Multimedia Kits --------------------------------------------------------------------------- What Multimedia Kits are supported under OS/2 Warp? The following Multimedia Kits have a beta driver posted in the file MMKOSB.EXE on our FTP server. Multimedia Kit Wave Sound CD-ROM support Multimedia Kit 1000 Yes No Multimedia Kit 2000 Yes Yes* Multimedia Kit 3000 Yes Yes* Multimedia Kit 4000 Yes Yes1 Multimedia Kit 4400 No No Multimedia Kit 5000 Yes Yes* Multimedia Kit 6000 Yes Yes* Multimedia Kit 7000 No Yes* Multimedia Kit 8000 No No 1 No support for Teac CD-ROM * IDE driver supplied by Warp. --------------------------------------------------------------------------- Driver availability for the TeleCommander series --------------------------------------------------------------------------- What TeleCommander products are supported under OS/2 Warp? Currently, we do not have any support for the TeleCommander product line under OS/2. You may write a letter to the Product Manager of TeleCommander series. To address the letter, do so in the following fashion: Product Manager of the TeleCommander Team Diamond Multimedia Systems 2880 Junction Ave. San Jose, CA 95134-1922