Graphics Display Device Driver for OS/2
Systems Supported: IBM Systems with S3 Trio64V+/64V2 video subsystems.
Driver Version: 3.03.14
IMPORTANT:
o This package contains an OS/2 graphics-accelerator device driver
that supports the Trio64V+ (765), and Trio64V2 DX/GX (775/785)
chip sets from S3 Incorporated.
o Read this entire document before beginning the device driver
installation. The installation procedure in this document must
be used to install this device driver. The OS/2 Selective
Install procedure can not be used to install this device driver.
o The two device driver installation diskettes must contain the
volume labels of "S3 DRV1" (without the quotation marks).
o Device driver features include:
- DDC monitor detection support,
- under the OS/2 Warp/Merlin "System - Settings" notebook a user can
select the monitor Refresh Rate,
- large and small font support for WIN-OS/2 sessions,
- WIN-OS/2 support is based on latest S3 Windows 3.1x drivers,
- the device driver is enabled for the Configuration
Installation Distribution (CID) method, and
- a one diskette installation package.
CONTENTS
________
1.0 Supported Features
1.1 Supported Resolutions
1.2 Supported Adapters
1.3 Technical Support
1.4 DDC Monitor Support
1.5 Selecting Large or Small Fonts for Windows
2.0 Preliminary Installation Steps
2.1 Setting OS/2 Warp/Merlin to VGA Mode
2.2 Setting OS/2 2.1x to VGA Mode
2.3 Preparation for CD-ROM or LAN Installation
3.0 Installation from Diskette
4.0 Installation in a CID Environment
5.0 Limitations
6.0 Trademarks
1.0 Supported Features
_______________________
This graphics-accelerator device driver provides seamless support
for accelerated video graphics and advanced color resolutions when
used with the minimum required video memory. It conforms to the
OS/2 32-bit, flat memory model and is designed to function as a
32-bit Presentation Manager graphics-display device driver under
the OS/2 32-bit graphics engine. This device driver supports
setting the refresh rate using the System - Settings notebook
(page 2 of the Screen tab) in the OS/2 System Setup folder, and
monitor detection using Display Data Channel (DDC) protocols.
1.1 Supported Resolutions
*===================================================*
* Mode * Resolution * Memory * Trio *
* * * Required* Family *
* * * *-------------------*
* * * * 764/765 * 775/785 *
*------*--------------*---------*---------*---------*
* 101 * 640x480x8 * 1 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 103 * 800x600x8 * 1 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 105 * 1024x768x8 * 1 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 107 * 1280x1024x8 * 2 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 111 * 640x480x16 * 1 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 114 * 800x600x16 * 2 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 116 * 1024x768x16 * 2 MB * Y * Y *
*------*--------------*---------*---------*---------*
* 212 * 640x480x24 * 1 MB * N/S * N/S *
*------*--------------*---------*---------*---------*
* 112 * 640x480x32 * 2 MB * Y * Y *
*===================================================*
NOTES:
o BPP = Bits Per Pixel (color depth); 8 = 256 colors, 16 =
65,536 colors, 24 = 16,777,216 colors & 32 = 16,777,216 colors.
o Y = Supported; N/S = Not Supported.
o 1 MB only - 640x480x24 is supported for 1 MB memory
configuration only; for 2 MB and above, 32 bits per pixel
(BPP) is supported.
o S3 BIOS supports 1600x1200x8 with 2 MB; S3 OS/2 device driver
needs 4 MB of memory.
o S3 BIOS supports 800x600x16 with 1 MB; S3 OS/2 device driver
needs 2 MB of memory.
o S3 BIOS supports 1280x1024x16 with 3 MB; S3 OS/2 device driver
needs 4 MB of memory.
o S3 BIOS supports 800x600x32 with 2 MB; S3 OS/2 device driver
needs 4 MB of memory
The 32 bpp device driver might need a large swap space on the
hard disk, for example, 15 MB.
1.2 Supported Adapters
For a comprehensive list of products that have been tested by IBM
and are OS/2 compatible, refer to the "OS/2 Hardware Compatibility
List" book. This book is available electronically in the following
locations:
http://www.austin.ibm.com/pspinfo/os2hw.html
IBM National Support Center BBS (data connection: 919-517-0001)
CompuServe (IBM OS/2 Support Forum \Library\IBMFiles\PCMTABLE.ZIP)
PRODIGY
LAN Server & OS/2 BBS - Sydney, Australia
IBM Austria BBS - Vienna, Austria
IBM BBS - Vancouver, BC, Canada
IBM PS BBS - Hong Kong
IBM OS/2 BBS & IBM AP OS/2 BBS - Singapore
IBM BBS - Belgium
IBM BBS - England
IBM BBS - Spain
OS2BBS - Denmark
Hitline BBS- Switzerland
DAP & PSP BBS - Italy
IBM BBS - Jakarta, Indonesia
IBM BBS - Thailand
NOTE: The compatibility hardware test information supplied is
provided for information purposes. IBM makes no warranty, express
or implied, with respect to the operation of OS/2 on the personal
computers listed.
1.3 Technical Support
Updates for this device driver, when available, may be obtained
from the following sources:
http://www.pc.ibm.com
IBM National Support Center (data connection: 919-517-0001)
IBM National Support Center (voice connection: 800-772-2227)
1.4 DDC Monitor Support
VESA Display Data Channel (DDC) 1 and 2B protocols are supported,
allowing similarly enabled computers and operating system software
to identify the monitor and its capabilities. This device driver
automatically detects DDC monitor capabilities and sets the monitor
to the maximum refresh rate which it supports. If, after
installing this device driver, you switch from a non-DDC monitor to
a DDC monitor or switch to a different DDC monitor, you must run
the DDC Display Setup program in the System Setup folder.
Use the following procedures when installing a DDC monitor.
1. Reset the monitor to the lowest refresh rate available. This
will prevent the system from setting a refresh rate higher
than that supported by the new monitor.
2. Shut down your computer and install the new monitor.
3. Restart your computer.
4. Select the "DDC Display Setup" icon in the OS/2 System Folder.
5. When you are instructed to do so, shut down your system and
restart it.
1.5 Selecting Small or Large Fonts for Windows
The default font sizes for Windows sessions are listed below.
Resolution Default Font Size
---------- ---------------------------
640x480 Small
800x600 Small
1024x768 Large
1280x1024 Large
1600x1200 Large
NOTE: Large fonts are not available for the 640x480 resolution.
Use the following procedures to select small or large fonts for
Windows sessions.
1. Select the "S3 Windows Font Size" object in the OS/2 System
Setup Folder.
2. Click on the radio button next to the font size you wish to
select.
3. Click on the OK button.
4. A message will display saying that the new settings will take
take effect the next time you restart your Windows session.
Currently open sessions will not be affected by the new
settings.
5. Click on the OK button.
6. Start any WIN-OS/2 window or full-screen session.
The setting you select will remain in effect until you explicitly
change it, you change your display resolution, or you install a
new display driver.
2.0 Preliminary Installation Steps
___________________________________
The following steps must be performed before you install the
graphics-accelerator device driver:
1. You must have OS/2 DOS Support installed.
2. If you previously installed SVGA support, you must reset the
resolution to VGA mode, using the procedures in the
following section.
3. The device driver installation diskette must contain the
diskette volume label of "S3 DRV1" (without the quotation
marks). The volume label may be applied using the OS/2 LABEL
command.
4. After driver installation, the OS/2 SYSLEVEL command can be
used to confirm the new driver version level. Following
execution of the SYSLEVEL command, look for SYSLEVEL.VID.
For example:
C:\OS2\INSTALLATION\SYSLEVEL.VID
Vision868/968/Trio32/64/64V+/64V2
Version 3.03 Component ID 562107701
Current CSD level: S330312
Prior CSD level: S330312
In this case the current version level is S3 3.03.14.
2.1 Setting OS/2 Warp/Merlin to VGA Mode
If you are installing this driver on OS/2 Warp/Merlin , do the following:
1. Turn on your computer. If your computer is already on,
press Ctrl+Alt+Del to restart it.
2. When a small white box appears in the upper-left corner
of your screen, press Alt+F1.
3. When the Recovery Choices screen appears, press V for Warp Version 3
or press F3 for Warp Version 4(Merlin).
Your video subsystem is now restored to work in VGA mode.
If you want to install a new video adapter refer to Chapter 16
"Video Procedures," in the User's Guide to OS/2 Warp/Merlin.
2.2 Setting OS/2 2.1x to VGA Mode
If you are installing this driver on OS/2 2.1, 2.11 or OS/2 for
Windows, and you installed from diskettes, do the following:
NOTE: If your monitor has lost synchronization, start OS/2 using
the OS/2 Installation Diskette. When prompted insert
diskette 1, press F3 to display a command prompt, and then
use the following instructions to reset your display mode.
1. Under OS/2 2.1, before running RSPDSPI, delete the
following file:
*OS2 DRIVE*:\OS2\INSTALL\00S3.DSC
2. Under OS/2 2.11, before running RSPDSPI, delete the
following file:
*OS2 DRIVE*:\OS2\INSTALL\00S3.DSC
3. Be sure RSPDSPI.EXE is in the \OS2\INSTALL directory. If
it is go to step 6. If it is not, insert Diskette 8 into
into drive A and unpack RSPDSPI.EXE with the following
command:
C:\OS2\UNPACK A:\INSTAID C: /N:RSPDSPI.EXE
where A: is the drive containing Diskette 8, and C: is
the drive where OS/2 is installed.
4. Type C: and then press Enter.
5. Type CD C:\OS2\INSTALL and then press Enter.
6. Type the following:
RSPDSPI /PK:VGA /SK:NONE /S:A:\ /T:C:
In /T:C:, C: is the target drive where OS/2 is installed.
In /S:A:, A: is the source diskette drive for installing the
device driver.
Then press Enter.
7. In some cases you will get screen instructions telling you
to "Insert the diskette with the following label into drive
A: Display Driver Diskette 1. Then press Enter". Please
follow these instructions.
8. Perform a shutdown and restart your computer.
2.3 Preparation for a CD-ROM or LAN Installation
If you are installing this device driver on OS/2 2.1, 2.11 or OS/2
for Windows, and you installed from CD-ROM or a LAN, do the
following:
1. Under OS/2 2.1, before running RSPDSPI, delete the
following file:
*OS2 DRIVE*:\OS2\INSTALL\00S3.DSC
2. Under OS/2 2.11, before running RSPDSPI, delete the
following file:
*OS2 DRIVE*:\OS2\INSTALL\00S3.DSC
3. Be sure RSPDSPI.EXE is in the \OS2\INSTALL directory. If
it is go to step 6. If it is not, unpack RSPDSPI.EXE with
the following command:
C:\OS2\UNPACK E:\DISK_8\INSTAID C: /N:RSPDSPI.EXE
where C: is the drive where OS/2 is installed, and E: is
the CD-ROM or LAN drive.
4. Type C: and then press Enter.
5. Type CD C:\OS2\INSTALL and then press Enter.
6. Type the following:
RSPDSPI /PK:VGA /SK:NONE /S:E:\OS2SE21\ /T:C:
In /T:C:, C: is the target drive where OS/2 is installed.
In /S:E:, E: is the source CD-ROM or LAN drive.
Then press Enter.
7. Perform a shutdown and restart your computer.
3.0 Installing from Diskette
_______________________________
To install the graphics-accelerated device driver from diskette, do
the following:
1. If system is not in VGA mode, select VGA mode.
2. Insert the driver installation diskette into drive A (or any
other diskette drive). In the following sequence the A drive
is assumed.
3. Open an OS/2 full-screen or OS/2 window session.
4. At the OS/2 command prompt, type the following command to copy
all necessary files to the OS/2 drive:
A:SETUP
where A: is the diskette drive which contains the device driver
installation diskette.
Then press Enter.
Due to the limitations with a single pass installation. A dialog box
may come up during installation with the message, "The installed adapter
does not support the selected display driver. Do you wish to continue?".
Please continue the installation by selecting the Yes button.
5. When the Monitor Configuration/Selection Utility window appears,
the "Install Using Defaults for Monitor Type" choice is
preselected. Select OK. Do not select "Install Using Display Adapter
Utility Program" since this method of setting refresh rates is not
supported anymore.
NOTE: DSPINSTL determines the hardware configuration by
creating the \OS2\SVGADATA.PMI file. If the
\OS2\SVGADATA.PMI file has not been created, the
adapter will not be supported. This process can
take several seconds and will black-out the screen.
6. When the Source Directory pop-up window appears, insert the prompted
graphics-accelerator driver diskettes into drive A. At this
point the source directory must specify the drive containing
the installation diskette (e.g. A:). If necessary change the
source directory, then select Install.
7. When the installation is complete, shut down your system,
remove the diskette, and restart your computer.
8. When the system has restarted:
a. Open the OS/2 System folder.
b. Open the System Setup folder.
c. Open the System object.
d. When the Settings notebook appears, select the Screen tab.
If your monitor has been detected as Plug and-Play (DDC)
compatible, go to step 10.
9. On Screen page 2, select your display from the display list. If
your display does not appear in the list, select Default.
It might be necessary to restart your computer to have all
refresh rate options available.
10. When the system has restarted:
a. Open the System object and select Screen page 1, as in
step 8.
b. Select a screen resolution and a screen refresh rate.
c. Close the Settings notebook.
d. Perform a shutdown and restart your computer.
NOTES:
o If the selected vertical refresh rate is not supported by your
monitor, delete \OS2\VIDEO.CFG file and reboot. This will set
the refresh rate to the default value. A new refresh rate can
now be selected using the procedure described above.
o During the installation of this driver, DISPLAY.LOG and
DSPINSTL.LOG files are created in the OS/2\INSTALL directory.
These files identify the OS/2 system files that were updated
and indicate whether the installation was successful. The
contents of these files might be useful if you need to report
an installation problem.
o If the video memory size is changed after the device driver is
installed, the device driver must be reinstalled in order for
the system to recognize the change. Not reinstalling the driver
might result in serious system problems.
o When starting a Windows session from a DOS command line, use the
WINOS2 command rather than the WIN command. Additionally, you
must modify the C:\AUTOEXEC.BAT file. Place the following line
anywhere after the "@ECHO.OFF" line in the AUTOEXEC.BAT:
COPY C:\WINDOWS\WINOS2.COM C:\WINDOWS\WIN.COM
4.0 Installing in a CID Environment
____________________________________
NOTES:
o The server must contain a directory named S3_DRVS on the same
drive where the OS/2 diskettes reside. The S3_DRVS directory
must contain all of the files from the graphics-accelerator
device driver installation diskette.
o OS/2 must have been successfully installed on the client using
the CID (Configuration Installation Distribution) method.
To install the graphics-accelerator device driver using CID, use
the following information to modify your LCU command file.
NOTE: The following information is meant as a guide.
Your LCU command file might be different.
/*****************************************************/
/* LCU PRODUCT DATA SECTION */
/*****************************************************/
.
.
.
x.s3video = 15
x.15.name='S3 Video'
x.15.statevar = 'CAS_' ** x.15.name
x.15.instprog = 'x:\img\s3_drvs\SETUP.CMD',
' x:\img\s3_drvs ' ** bootdrive ** ' CID'
x.15.rspdir = ''
x.15.default = ''
/*---------------------------------------------------*/
/* NUMBER OF PROGRAMS SET UP IN THE */
/* PRODUCT DATA SECTION */
/*---------------------------------------------------*/
NUM_INSTALL_PROGS = 15
/*****************************************************/
/* INSTALLATION SECTION */
/*****************************************************/
.
.
.
when OVERALL_STATE = 2 then do
if RunInstall(x.s3video) == BAD_RC then exit
Call RebootAndGotoState(3)
end
when OVERALL_STATE = 3 then do
if RunInstall(x.s3dspinstl) == BAD_RC then exit
Call CheckBoot
end
.
.
.
/******************************************************/
/* ROUTINE SECTION */
/* The following information should already exist in */
/* the LCU command file. */
/******************************************************/
.
.
.
RebootAndGotoState:
parse arg new_state, other
/* Set the state to go to in OVERALL_STATE */
rc2 = SetState(new_state, 'RebootAndGotoState', 1)
Call SaveStates /* Save the environment vars */
Call Reboot /* Reboot the machine */
return
.
.
.
/*****************************************************/
END OF LCU INFORMATION TO BE ADDED
/*****************************************************/
Following is an explanation of the line that is executed in the LCU
command file:
C:\OS2\INSTALL\DSPINSTL /pd:c:\os2\install\00S3.DSC
/S:X:\img\s3_drvs /T:C: /res:640x480x256 /u
/pd:c:\os2\install\00S3.DSC
is the dsc laid down during setup phase.
/S:X:\img\s3_drvs
where X:\img\s3_drvs is the redirected source path.
/T:C:
where C: is the drive where OS/2 is installed.
/res:640x480x256
is a resolution/color depth from the list of "Supported
Resolutions" that appears earlier in this README. In this
example 256 colors is specified. Enter "64K" to specify
65,536 colors or "16M" to specify 16,777,216 colors.
/u
means Unattended installation.
NOTES:
o After a CID installation the end user should go to section 3.0
"Installing from Diskette" and continue with step 8.
o Be sure you have the stated video memory required, as listed in
"Supported Resolutions" earlier in this README. A safe choice
is 640x480x256. Any of the listed resolutions can be selected,
but your display might be damaged if you select a resolution
that your display does not support.
o To select a refresh rate, SVGA.EXE can be executed again separately
after DSPINSTL. Example, SVGA ON INIT 1024 75
This will create another \OS2\VIDEO.CFG file with 75Hz as the default
at 1024x768 resolution. The prior \OS2\VIDEO.CFG file should be
deleted first.
o After the graphics-accelerator device driver has been
successfully installed on the client machine using the CID
method and the client machine is restarted, the resolution
will be as specified by command line argument.
5.0 Liminations
_______________
1. CID install pauses due to SVGA.EXE loading in the background.
Work around: In the CID install script, do not initiate any other
processes until DISPINSTL completes execution. Ensure that no
other processes are running during CID install. This can be
accomplished by adding the following line to the CONFIGSYSLINE
keyword of the CID response file:
SET RESTARTOBJECTS=STARTUPFOLDERSONLY
2. DISPINSTL does not allow CID selection of monitor and refresh
rate.
WORK AROUND:
Requirements:
* A system with the same graphics subsystem and monitor
configured with this graphics-accelerator device driver,
the correct display type, the desired resolution and
refresh rate.
Step 1: Copy Configured Video/Display Data Files
* copy the video and display data files containing information
about the display type, resolution and refresh rate to the
CID server (\img\svgadata).
> copy \os2\svgadata.pmi x:\img\svgadata
> copy \os2\video.cfg x:\img\svgadata
Step 2: Create CID Command File
* create a command file to copy svgadata.pmi and video.cfg
to the client system's \OS2 directory via CID.
* reboot the client system.
* the client system will be configured with the correct
driver, display type, resolution and refresh rate.
Another work around is to delete \OS2\VIDEO.CFG and to execute
SVGA.EXE again after DSPINSTL completes. Example: SVGA ON INIT 1024 75
to set 75Hz as the default refresh rate at 1024x768.
3. In all modes, video corruption or out-of-sync screen is
displayed when using Alt+Esc to switch between WIN-OS/2,
OS/2, DOS window and DOS full-screen sessions started from
the Startup folder. To avoid this situation, do not start
sessions from the Startup folder or press Alt+Esc several
times to restore.
4. Some programs, such as WINBENCH95, WINBENCH96, and After Dark
3.0. were written specifically for the Windows environment.
In the Windows environment, these programs prevent any
keystrokes from interfering with their proper execution.
However, in the OS/2 environment, it is possible to switch
context away from the Windows session without notifying these
programs. General Protection Faults (GPSs) may result.
Therefore, context switching during the execution of
WINBINCH95 and WINBENCH96 tests is not recommended. Also,
context switching during the execution of the After Dark 3.0
demo is not recommended.
6.0 Trademarks
______________
The following terms are trademarks of the IBM Corporation in the
United States and/or other countries:
Aptiva
IBM
OS/2
WIN-OS/2
The following terms are trademarks of other companies:
TRADEMARK OWNER
After Dark Berkely Systems, Inc.
CorelDRAW Corel Corporation
Lotus Lotus Development
Corporation
Micrografx Micrografx Incorporated
S3 S3 Incorporated
Trio64/Trio64V+ S3 Incorporated
Trio64V2 S3 Incorporated
Ventura Publisher Ventura Software, Inc.
Vision 864/868/964 S3 Incorporated
Windows Microsoft Corporation
WordPerfect WordPerfect Corporation
1-2-3 Lotus Development
Corporation
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED,
INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY
WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY
FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY
RELATED PATENTS OR COPYRIGHTS.
THIS DRIVER IS COPYRIGHTED BY INTERNATIONAL BUSINESS
MACHINES CORPORATION. ALL APPROPRIATE RESTRICTIONS
APPLY.
(End of Document)