home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 33 VDrivers
/
33-VDrivers.zip
/
01k7513.txt
< prev
next >
Wrap
Text File
|
1998-09-04
|
19KB
|
515 lines
----------------------------------------------------------------------
OS/2 Video Device Driver for S3 Trio3D
V4.00.25
----------------------------------------------------------------------
This package contains an OS/2 graphics-accelerator device driver that
supports the Trio3D chip set from S3 Incorporated.
This README file contains procedures for installing the S3 Trio3D video
device driver for OS/2 Warp 3.0 and 4.0.
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.
The following topics are included in the file:
1.0 Supported Features
2.0 DDC Monitor Support
3.0 Preliminary Steps
4.0 Setting Your Monitor to VGA Mode
5.0 Installing the S3 Video Device Driver
6.0 Installing the S3 Video Device Driver in a CID Environment
7.0 Selecting Small or Large Fonts for Windows
8.0 Features and Fixes Included in This Device Driver
9.0 Limitations
10.0 Trademarks
+--- Important ------------------------------------------------------+
│ │
│ If you are installing from diskette the label "S3 DRV1" │
│ must be the label on the installation diskette. │
│ This label can be applied using the DOS or OS/2 LABEL command. │
│ The video driver installation will fail without this step. │
│ │
+--------------------------------------------------------------------+
1.0 Supported Features
_______________________
This Trio3D graphics-accelerator device driver provides seamless
support for accelerated display 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.
2.0 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 S3 video device
driver automatically detects DDC monitor capabilities and sets the
display to the maximum refresh rate supported by the monitor. 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 attempting to display at 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. Double-click on the DDC DISPLAY SETUP icon in the OS/2 System
folder.
5. When you are instructed to do so, shut down your computer and
restart it.
3.0 Preliminary Steps
______________________
The following steps must be performed before you install the
Trio3D graphics-accelerator video 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 procedure under "Setting Your
Monitor to VGA Mode" (section 5.0 in this README).
4.0 Setting Your Monitor to VGA Mode
_____________________________________
To switch to VGA mode:
1. Start OS/2 Warp.
2. When the small white (OS/2) box appears in the upper-left
corner of the screen, press Alt+F1; when the list of choices
appears, press F3 (or V for OS/2 3.0).
5.0 Installing the S3 Video Device Driver
___________________________________________
To install the Trio3D device driver, do the following:
1. If your system is not in VGA mode, use the steps under section
5.0 to switch to VGA mode.
2. If installing from diskette, insert the Trio3D diskette into drive A.
3. Open an OS/2 full-screen or OS/2 window session.
4. At the OS/2 command prompt, execute X:\PATH\SETUP, where X:\PATH
is the full path to the diskette drive or sub-directory to copy
all driver files to the OS/2 drive.
5. Setup will then identify your chip set. When prompted to do
so, press Enter to continue. Setup will then copy files.
6. When the Monitor Configuration/Selection Utility window
appears, the "Install Using Defaults for Monitor Type" choice
is preselected. Accept this choice by clicking OK.
7. When prompted to do so, select OK to perform a shutdown. Remove
any diskettes from the floppy drive before restarting your computer.
8. Open the OS/2 System folder.
9. Open the System Setup folder.
10. Open the Display Driver Install object or type DSPINSTL
at an OS/2 command prompt. When the Display Driver Install
window appears, select PRIMARY DISPLAY DRIVER and then
select OK.
NOTE: If a message appears stating that the "Installed adapter
does not match the driver", select OK to continue.
11. When the Primary Display Driver List window appears, select
"S3 Trio3D [32 Bit] Version ...." then select
OK to install the video driver.
12. When the Monitor Configuration/Selection Utility window
appears, the "Install Using Defaults for Monitor Type" choice
is preselected. Accept this choice by clicking OK.
13. When the Source Directory pop-up window appears, CHANGE the
path statement to point to the driver files (same as in step 4.)
If installing from diskette, insert the install diskette into
the drive. Then select INSTALL.
14. When the installation is complete, remove any diskettes,
shut down your system, and restart your computer.
15. 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 17.
16. On Screen page 2, select your monitor from the list. If your
monitor does not appear in the list, select DEFAULT.
It might be necessary to restart your computer to have all
refresh rate options available.
17. When the system has restarted:
a. Open the System object and select Screen page 1, as in step
15.
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 During the installation of this device 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 to IBM.
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
device driver might result in serious system problems.
o To start a WIN-OS/2 session, double-click on one of the WIN-OS/2
icons located in the "Command Prompts" folder within the "OS/2
System" icon. For additional information, see section 10.0
"Limitations."
6.0 Installing the S3 Video Device Driver in a CID Environment
_______________________________________________________________
Notes:
o OS/2 must have been successfully installed on the client using
the CID (Configuration Installation Distribution) method.
To install the Trio3D 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',
' /u /s:x:\img\s3_drvs'
x.15.rspdir = ''
x.15.default = ''
x.s3dspinstl = 16
x.16.name='S3 CID Dspinstl'
x.16.statevar = 'CAS_' || x.16.name
x.16.instprog = bootdrive || '\os2\install\DSPINSTL.EXE',
' /pd:' || bootdrive || '\os2\install\00S3.dsc',
' /s:x:\img\s3_drvs',
' /t:' || bootdrive,
' /res:640x480x256',
' /u'
x.16.rspdir = ''
x.16.default = ''
/*---------------------------------------------------*/
/* NUMBER OF PROGRAMS SET UP IN THE */
/* PRODUCT DATA SECTION */
/*---------------------------------------------------*/
NUM_INSTALL_PROGS = 16
/*****************************************************/
/* 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.
/u
means Unattended installation.
Notes:
o Be sure you have the stated video memory required, as listed
under section 2.0 "Supported Resolutions." A safe choice is
640x480x256. Any of the listed resolutions can be selected, but
your monitor might be damaged if you select a resolution that
your monitor does not support.
o After the Trio3D 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.
o After the CID installation, refer to section 6.0 "Installing the
S3 Video Device Driver from Diskette," step 12.
7.0 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 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.
A message will be displayed indicating that the new settings will
take effect the next time you restart your Windows session.
4. Click on the OK button.
5. 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 monitor resolution, or you install a new
video device driver.
8.0 Features and Fixes Included in This Device Driver
______________________________________________________
These are the features and fixes included in this device driver:
o "System - Settings" notebook support for setting refresh rate
o DDC monitor detection support
o Windows "Large font" and "Small font" support in high
resolutions
o WIN-OS/2 based on latest S3 Windows 3.1 drivers
o One-diskette package
9.0 Limitations
_________________
These are some known limitations:
1. CID install pauses due to SVGA.EXE loading in the background.
Workaround: In the CID installation 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. During CID install of IBM AntiVirus when using NetView DM/2,
the OS/2 full screen is displayed as a black screen.
Workaround: Perform CID install under VGA.
3. DISPINSTL does not allow CID selection of monitor and refresh
rate. The workaround is as follows:
Requirements:
* A system with the same graphics card and monitor
configured with the S3 driver version 2.81.05, the
correct display type, the desired resolution, and the
desired 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 using CID.
* Restart the client system.
* The client system will be configured with the correct
device driver, display type, resolution and refresh rate.
4. In all modes, video corruption or an out-of-sync screen is
displayed when using Alt+Esc to switch between WIN-OS/2, OS/2,
and DOS window and 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.
5. 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 (GPFs)
may result. Therefore, do not perform context switching during
the execution of WINBENCH95 and WINBENCH96 tests. Also, do not
perform context switching during the execution of the After Dark
3.0 demo.
6. If you attempt to start a WIN-OS/2 session from an OS/2 Full
Screen session by typing "WIN" or "WINOS2" at the command
prompt, it will not execute with the settings needed to
support WIN-OS/2, and will result in video corruption or a
system lockup. Therefore, whenever you want to launch a
Windows session, use one of the WIN-OS/2 icons located in the
"Command Prompts" folder within the "OS/2 System" icon.
7. When attempting to start a WIN-OS/2 session from a DOS Full
screen or DOS Window by typing the "WIN" or WINOS2" command,
you must first be sure that the video settings of the session
are changed to enable this feature. These settings can be
changed using the following procedure:
a. Place the mouse pointer over the DOS Full Screen icon
(or any DOS session icon you want to alter). Press
mouse button 2 (the right button) to bring up a
context-sensitive menu.
b. Click on SETTING; then click on the SESSION tab.
c. Click on the DOS SETTING button.
d. Click on DOS VIDEO SETTINGS; then click on OK.
e. From the list of settings that appear, ensure that
"VIDEO_8514A_XGA_IOTRAP" is set to OFF, and
"VIDEO_SWITCH_NOTIFICATION" is set to ON; then save
these settings by clicking on SAVE.
8.0 At 32 bpp color depth, the device driver might need a large swap
space on the hard disk, for example, 15 MB.
10.0 Trademarks
________________
The following terms are trademarks of the IBM Corporation in the
United States or other countries or both:
IBM Presentation Manager
NetView WIN-OS/2
OS/2
The following terms are trademarks of other companies:
After Dark Berkely Systems, Inc.
S3 S3 Incorporated
VESA Video Electronics Standards Association
Microsoft and Windows are trademarks or registered trademarks of
Microsoft Corporation.
Other company, product, and service names may be trademarks or
service marks of others.
(End of Document)