Answer Guide
Diamond Products
and
OS/2 Warp
General Questions about Diamond video cards and Warp	
Which Diamond video cards have drivers for OS/2 Warp?	
I have gotten on the Diamond BBS and FTP site.  I have only found OS/2 2.1 drivers.  Do you have any drivers specifically for OS/2 Warp?	
Do you have any video cards that are DIVE or EnDive compliant?	
What is the reason for manually expanding certain files for the Stealth video cards?	
When I look in the DISPLAY.LOG, there are several errors about unable to patch the kernel and VWIN, how can I fix this?	
Why does SVGADATA.ERR keep growing in size every time I boot Warp?	
Everytime I set my setup back to VGA, I am unable to switch back to VGA.  I just get a flashing cursor after bootup.  What can I do to correct this problem?	
Stealth	
VGA-Setting OS/2 Warp back to VGA	
Alt-F1 does not work.	
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?	
I have your Stealth 64 Grapics 2xxx 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.
How do I work around the error?	
When will the above errors above be fixed for the Stealth 64 Graphics 2xxx?	
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?	
When I am installing your OS/2 Warp drivers, I click on 32 bit S3 Display Driver ver. x.xx from the Primary Display Driver List:
“Display driver selected is not supported by this adapter.”
How can this be fixed?	
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?	
During Display Driver Install,  the files begin be copied but there is an unpacking error.  How can I do this manually?	
When I try to unpack files manually an error message appears, “Data invalid” and nothing happens?	
When Display Driver Install is unpacking files, I get a SYS3175 error and the installation stops.  What can I do to fix this?	
I can’t find the Display Driver Icon.  Where is it?	
Disk 1 is not accepted during the installation.  What can I do about it?	
Disk 1 is STILL NOT ACCEPTED!	
When I try to install the drivers, the installation  starts copying files and says it cannot replace the VGA.DRV driver?	
GO95 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 regiter values}  How do I correct this error?
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	
Supported Resolutions and Color Depths for Stealth cards (S3)	
What are the supported resolutions and color depths for the S3 based Stealth cards?	
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?	
Lockups When Using Stealth drivers	
I have your Stealth 64 Video 3xxx 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?	
Why does the video BIOS for the Stealth 64 Video 3xxx need to be downgraded to version 1.04 to work with Warp?	
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?	
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?	
I have your Stealth 64 Graphics 2xxx.  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?	
After installing the correct version of VSVGA.SYS, I still have a problem switching back to the DOS full screen session?	
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.  What can I do to correct this?	
After loading the Stealth drivers, my computer begins to boot, I see the OS/2 logo, then my system locks?	
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?	
How can I get rid of the InControl Tools icon from loading when I load a Seamless Windows session?	
Seamless Win-OS/2	
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?	
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.  What can be done to correct this problem?	
I have a Stealth 64 VRAM (964/968) card.  Everytime I open a seamless  Win-OS2 session the colors on my desktop shift to wild colors (wild berry, pink and radioactive green)?  How do I correct this problem?	
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?	
Benchmark Questions	
During a benchmark test under Win-OS/2 Full Screen, this Diamond video card scores as high as a simple VGA card?	
Mouse Questions	
I have your Stealth 64 Graphics 2xxx.  I open a DOS Full Screen Session, switch back to the OS/2 Desktop and then back to the DOS Full Screen session the moue dissappers.  What can I do to fix the problem?	
Under Win-OS/2 Full Screen, when the mouse moves it seems "jerky" and "jumpy?"	
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?	
Font Problems	
When I am running with Stealth drivers, my text appears corrupted and my screens do not refresh properly?	
I have a Stealth 64 VRAM (964).  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?	
Every where in Warp my fonts are corrupted.  How can I correct this?	
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?	
Monitor Questions	
How can I get a flicker-free higher resolutions when using my Stealth card?	
What is the reason for not being able to use Custom for configuring the Stealth driver under Warp?	
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?	
Color Palette Questions	
I have a Stealth 64 VRAM (964/968) card.  Everytime I open a seamless  Win-OS2 session the colors on my desktop shift to wild colors (wild berry, pink and radioactive green)?  How do I correct this problem?	
Why do certain Seamless Win-OS/2 application change the color palette when I am running in 256 colors?	
Stealth 64 Graphics 2001 (ARK 2000)	
Disk 1 is not acceped, when I install the drivers for the Stealth 64 Graphics 2001.	
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?	
Do you have driver that supports OS/2 2.1x for the Stealth64 Graphics 2001?	
Stealth 32(Tseng)	
How do I set refresh rate on the Stealth 32?	
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?	
Viper	
Corrupted Icons	
When I go into a Win-OS/2 Full screen session, my icons are corrupted and scrambled?	
Viper SE/PRO:  Win-OS/2 Freezes when loading	
How do I set a higher refresh rate with the Warp P9100 drivers?	
I am currently running Warp for Windows.  Why does the following occur when I use the Viper SE/PRO 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?	
Viper PCI	
“I get the following error when I boot my machine in OS/2 with the Viper PCI:	
OS/2:  TRAP 00000D error”	
SpeedStar	
What Warp drivers do I use for my SpeedStar video card?	
3D Edge	
Do you have OS/2 Warp video and audio drivers for your 3D Edge?	
Multimedia Kits	
What Multimedia Kits are supported under OS/2 Warp?	
TeleCommanders	
What TeleCommander products are supported under OS/2 Warp?	

General Questions about Diamond video cards and Warp

Which Diamond video cards have drivers for OS/2 Warp?
Most Diamond cards can be found in the Primary Display Driver List that is shipped with Warp.  The following cards are compatible with the drivers supplied with Warp.

Video Card  	IBM supplied Warp Driver	
Viper Pro	Weitek Power 9100	
Viper SE 	Weitek Power 9100	
Viper VLB  	Weitek Power 9000	
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 (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	

The following list shows the cards that are supported using a driver on  the Diamond BBS at 408-325-7175 or by calling Customer Service 408-325-7000.

Stealth 64 VRAM
Stealth 64 DRAM
Stealth 64 Video VRAM 
Stealth Video
Stealth VRAM (only Win-OS/2 Full Screen support)
Stealth SE

I have gotten on the Diamond BBS and FTP site.  I have only found OS/2 2.1 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.

When I look in the DISPLAY.LOG, there are several errors about unable to patch the kernel and VWIN, how can I fix this?
This errors are used for diagnostic purposes.  They have no effect on the performance of the OS/2 Stealth drivers.

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 am unable to switch back to VGA.  I just get a flashing cursor after bootup.  What can I do to correct this 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.  
	
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.  If you have a disk version of Warp, BUNDLE will be found on Disk 4 of the installation disks.
9. 	COPY A:\BUNDLE Y:\TEMP where Y is the boot drive.
10. 	From the TEMP directory, type UNPACK BUNDLE where y is the OS/2 boot drive.  The files will be copied to the proper directories automatically.  
11. 	Restart the computer, when the OS/2 white block appears, press Alt-F1, to select ‘V’ to restore VGA.
Stealth
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.  

Alt-F1 does not work.
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.   You can continue with the rest of the installation.

If the files have been replaced are older than 1/12/95  you can get the new version back by doing the following: 

1.	Open an OS/2 Full Screen session using the Command Prompts folder.
2.	Make a temp directory on the C drive.  MD TEMP
3.	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.
4.	COPY X:\OS2IMAGE\DISK_4\BUNDLE C:\TEMP 
5.	where x is the CD-ROM drive.  
6.	If you have a disk version of Warp, BUNDLE will be found on Disk 4 of the installation disks.
7.	COPY A:\BUNDLE C:\TEMP
8.	Change to the TEMP directory.
9.	Type UNPACK BUNDLE.   The files will be copied to the appropriate directories automatically.

This should replace the older file in the OS2 directory and the installation can continue.

I have your Stealth 64 Grapics 2xxx 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.

How do I work around the error?

In the following, we are tricking the installation into thinking it found the files so it will not complain.

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 the following at the beginning of the file:
	ABC
	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

These errors will not have an effect on the installation.  The installation can continue.  

When will the above errors above be fixed for the Stealth 64 Graphics 2xxx?
The Stealth 64 DRAM 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. x.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.
1. 	S3INST.CMD must be executed from the floppy drive in the following manner:  
	
	A:\S3INST A: C:  
	
	NOT in the following manner:  
	
2. 	C:\>A:S3INST A: C:   
	
3. 	Reinstall DOS support to ensure all files are properly installed.
4. 	Check to make sure there is an S3 adapter in the computer.
5. 	Remove the AUTOEXEC.BAT for any video card TSR BIOS programs from a previous video adapter.

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.

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 go 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:
	
a)	Open "OS/2 System".
b)	Open "System Setup".
c)	Open the "System" object.  The Screen page of the Settings notebook lists all the supported resolutions for your configuration.
d)	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,

1.	Open an OS/2 full screen session.  There is no need to close the DSPINSTL.EXE program.
2.	Place the first Stealth disk in the floppy drive.
3.	Type A: to move to the A drive.
4.	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.
5.	Place the 2nd OS/2 Stealth disk in the drive.
6.	At the prompt type:  LABEL S3 DRV2
7.	Close the session and continue with the installation.  There is not need to restart.

Disk 1 is STILL NOT ACCEPTED!
Make sure that the labels have the following…
Confirm that there is a SPACE and not an UNDERSCORE.
Confirm that the number ‘3’ is instead of the word, “three”

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.

GO95 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 regiter values}  How do I correct this error?

There are three possible scenarios to rebuild the monitor configuration file (SVGADATA.PMI):

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.
4.  Save the configuration.  Test the new monitor selection by typing DMS.EXE MONITOR.  This will echo back the monitor chosen.
5.  Go into the OS2 directory.
6.  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.
7.  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
8.  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:
5. 	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 one 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.
5.  Go into the OS2 directory.
6.  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.
7.  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
8.  Restart Warp to have the new resolutions recognized.

The second method is:

1.	Make a bootable PC-DOS or MS-DOS boot disk.
2.	Make a blank floppy and place it in A: drive.
3.	Go to the GO95 directory by tying  CD GO95.
4.	Copy the following files to this blank floppy by typing:
	COPY Y:\GO95\*.EXE A:\
	COPY Y:\GO95\*.DAT A:\
	COPY Y:\GO95\*.DLL A:\
	COPY Y:\GO95\*.INI  A:\
	COPY Y:\GO95\*.DMS A:\
	COPY X:\OS2\SVGA.EXE A:\
	where Y is the drive where GO95 program is installed and X is the drive OS/2 is installed.
5.	Boot up with the PC-DOS or MS-DOS boot disk.
6.	Insert the GO95 disk and type GO95.  This will take about a minute or two to read these files from the floppy drive.
7.	Select the correct 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.	Change to the floppy drive and 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.  The monitor might click several times for 30 seconds to create this file.
10.	Reboot the computer to get back into OS/2.
11.	Open an OS/2 full screen and type the following:
12.	ren Y:\OS2\SVGADATA.PMI   X:\OS2\SVGADATA.OLD
13.	Place the GO95 disk back in the drive.  Type
	COPY A:SVGADATA.DOS Y:\OS2\SVGADATA.PMI
14.	Restart Warp to have the new settings recognized.

Supported Resolutions and Color Depths for Stealth cards (S3)
What are the supported resolutions and color depths for the S3 based Stealth cards?

Resolution	Memory
Required	Stealth Video
Stealth 64 DRAM
Stealth SE
(868/864/764/732)	Stealth 64 VRAM 
Stealth 64 Video VRAM 3000
(964/968)	
640x480x8	1M	Ö	Ö	
800x600x8	1M	Ö	Ö	
1024x768x8	1M	Ö	Ö	
1280x1024x8	2M	Ö	Ö	
1152x864x8	   2M 1	Ö	Ö	
1600x1200x8	   4M 2	Ö	Ö	
640x480x16	1M	Ö	Ö	
800x600x16	   2M 3	Ö	Ö	
1024x768x16	2M	Ö	Ö	
1280x1024x16	   4M 4	Ö	Ö	
640x480x24	1M 	N/S	N/S	
640x480x32	2M	Ö	Ö	
800x600x32	   4M 5	N/S	Ö	
1024x768x32	4M	Ö	Ö	

Notes:  

N/S -Not Supported.

1M only - 640x480x24 is not supported for 1M memory configuration only, for 2M and above 32bpp will be supported.  

11152x864x8 with 1M, S3 OS/2 driver needs 2M of memory
21600x1200x8 with 2M, S3 OS/2 driver needs 4M of memory.  Stealth 64 VRAM does not have a RAMDAC to support this resolution and color depth.
3800x600x16 with 1M, S3 OS/2 driver need 2M of memory.
41280x1024x16, S3 OS/2 driver needs 4M of memory.
5800x600x32 with 2M, S3 OS/2 driver needs 4M of memory

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 your Stealth 64 Video 3xxx 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 Stealth 64 Video.  The problem only occurs with 1.06 version of the video BIOS for this Stealth card. 

Why does the video BIOS for the Stealth 64 Video 3xxx 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?

Do the following to correct the message: 

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 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?
Do the following to correct the message: 

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 over during the installation.
8.	Restart Warp normally without the diskettes.

I have your Stealth 64 Graphics 2xxx.  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.
	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.
	
After 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.

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.  What can I do to correct this?
There is a possibility that the video card is using the wrong driver.  To check what kind of video card you can do 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 call our BBS at 408-325-7175 and download them from the appropriate library or call Customer Service at 408-325-7000.

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 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 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?
You can edit the WIN.INI file.  You can search for the following string, “dcshkey.exe.”  Once you find this file you can delete it.  This should disable this icon.

Seamless Win-OS/2
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 over 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.  What can be done to correct this problem?
There is a possibility that the video card is using the wrong driver.  To check what kind of video card you can do 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 download them from the Diamond BBS at 408-325-7175 and download them from the appropriate library or call Customer Service at 408-325-7000.

I have a Stealth 64 VRAM (964/968) card.  Everytime I open a seamless  Win-OS2 session the colors on my desktop shift to wild colors (wild berry, 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 over during the installation.
8.	Restart Warp normally without the diskettes.

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

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 your Stealth 64 Graphics 2xxx.  I open a DOS Full Screen Session, switch back to the OS/2 Desktop and then back to the DOS Full Screen session the moue 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.
	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?
There is a possibility that the video card is using the wrong driver.  To check what kind of video card you can do 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 call our BBS at 408-325-7175 and download them from the appropriate library or call Customer Service at 408-325-7000.

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 (964).  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 ";" in front of the line to have Windows ignore the line.  By doing this, Windows will use the default system font.

Every where in Warp my fonts are corrupted.  How can I correct this?
You may have the wrong drivers for your video card.  To check what kind of video card you can do 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 call our BBS at 408-325-7175 and download them from the appropriate library or call Customer Service at 408-325-7000.

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	fonts.fon=vgasys.fon	
fixedfon.fon=xgafix.fon	fixedfon.fon=vgafix.fon	
oemfonts.fon=xgaoem.fon	oemfonts.fon=vgaoem.fon	

You can then 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.

The best way to do this,  is to do the following:

1.  Boot the computer into Microsoft DOS.
2.  Run the  mode utility for the Stealth card.
3.  Select the correct flicker-free predefinded monitor (This monitor should be within the specifications stated in the monitor manual.)  Note:  Custom monitor does not work correctly when the settings are used under Warp.
4.  Save the configuration.  Test the new monitor selection by typing the name of the utility and the monitor switch (i.e. s64mode.exe monitor).  This will echo back the monitor chosen.
5.  Go into the OS2 directory.
6.  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.
7.  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
8.  Restart Warp to have the new resolutions 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 go 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.  The best way to do this is to do the following:

1.  Boot the computer into Microsoft DOS.
2.  Run the  mode utility for the Stealth card.
3.  Select the correct flicker-free predefinded monitor (This monitor should be within the specifications stated in the monitor manual.)  Note:  Custom monitor does not work correctly when the settings are used under Warp.
4.  Save the configuration.  Test the new monitor selection by typing the name of the utility and the monitor switch (i.e. s64mode.exe monitor).  This will echo back the monitor chosen.
5.  Go into the OS2 directory.
6.  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.
7.  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
8.  Restart Warp to have the new resolutions recognized.

Color Palette Questions
I have a Stealth 64 VRAM (964/968) card.  Everytime I open a seamless  Win-OS2 session the colors on my desktop shift to wild colors (wild berry, 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 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 boot drive 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.

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 icon.

Stealth 64 Graphics 2001 (ARK 2000)

Disk 1 is not acceped, 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 the customer does not use a SPACE instead of an underscore. 

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 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.

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 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

Stealth 32(Tseng)
How do I set refresh rate on the Stealth 32?
1. 	Open an OS/2 full screen session.
2. 	Change to the OS2 directory.
	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 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.

Viper
Corrupted Icons
When I go into a Win-OS/2 Full screen session, 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. 

Viper SE/PRO:  Win-OS/2 Freezes when loading
How do I set a higher refresh rate with the Warp P9100 drivers?

1. 	Open an OS/2 full screen session.
2. 	Change to the OS2\POWER_9K directory found on the OS/2 boot drive.
3. 	From this directory, type P9CFG.EXE [Enter]
4. 	This will return you back to the Desktop with the monitor utility.  Select the correct monitor according to the monitor manufacturer specification found in the manual.
5. 	Restart to have the changes take effect.

I am currently running Warp for Windows.  Why does the following occur when I use the Viper SE/PRO 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?

Either symptom can happen depending on which driver they installed last.

Workaround:
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.

Below is a possible fix to help customers using Warp for Windows and the Viper SE/Pro:

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:
1)  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

2) 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

“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. 

SpeedStar

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	

3D Edge

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 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

Multimedia Kits

What Multimedia Kits are supported under OS/2 Warp?

The following Multimedia Kits have the sound card driver MMOS2B.EXE driver found on the Diamond BBS.

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.
TeleCommanders

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 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 the TeleCommander Team
Diamond Multimedia Systems
2880 Junction Ave.
San Jose, CA 95134-1922