Video Driver Install v5.00: Upload information

Video Driver Install v5.00: Upload information

Post by A.A. Olowofoye » Wed, 17 Nov 1993 06:16:39



Hi all,

I have just uploaded a new version of my video driver install program
for full screen Win-OS/2 sessions to ftp-os2.cdrom.com. The file is
called videodr5.zip and is currently in the /pub/os2/incoming driectory.

This is an important update to videodr5.zip, and contains a number of
bug fixes and new features.

A fuller description of the upload is below.

          UPLOAD INFORMATION FOR VIDEO DRIVER INSTALL v5.00
          -------------------------------------------------
          videodr5.zip

While it is possible for OS/2 users to use different video display drivers
for their seamless and full screen Win-OS/2 sessions, the OS/2 installation
and DSPINSTL programs always identical drivers for both sessions. While this
may be fine for some people, many OS/2 users have optimized Windows drivers
that they would like to use for their full screen Win-OS/2 sessions. The
process of changing the video display drivers for full screen Win-OS/2
sessions has normally been tedious, involving fiddling around with INI
files.

VideoDrv is a program that greatly simplifies this process - just type in
the name of your new full screen driver, or select one from a listbox, then
click on a button, and the rest is done automatically. The whole process
takes no more than 5 seconds. In short, VIDEODRV works as a Win-OS/2
replacement for the SETUP program that comes with Windows 3.1.

************
NEW FEATURES
************

1. From version 3.00, VIDEODRV will now install your display driver directly
from your driver/distribution disk, unpacking and decompressing them (if
necessary) in the process. In this respect, it simulates the SETUP program
that comes with Windows 3.1. To use this feature, select the menu option
"INSTALL NEW DRIVER FROM DISK". You will then be prompted for the directory
in which your driver files are to be found (this will normally be a floppy
disk drive into which your driver disk has been inserted, or if you have
copied the files to the hard disk, then the subdirectory on the hard disk
where the files may be found).

VIDEODRV will then read the OEMSETUP.INF file that comes with your driver
disk and decompress the drivers to your Win-OS/2 system directory.

NOTE that if you downloaded your drivers from a bulletin board or from an
ftp site, you need to unzip the files first. VIDEODRV will NOT unzip files
that have been archived in the ZIP format.

2. When you have installed your drivers from a driver disk, VIDEODRV will
create a file in your DRIVER DIRECTORY (see below) called VIDEODRV.DBF. This
file will hold information on all the drivers that you have installed
through VIDEODRV from a driver disk. Thus, if you want to change the
drivers, you will be presented with a list of the descriptions of the
drivers (not just the file names as in early versions of VIDEODRV). When you
select from the list, the appropriate driver will be installed.

From version 4.00, VIDEODRV will optionally restart the Win-OS/2 session
after the changes have been made.

Please NEVER delete VIDEODRV.DBF, otherwise, VIDEODRV will just assume that
you have not installed any driver from a driver disk as described above, and
will only present you with a list of driver filenames.

Note that the format of the file VIDEODRV.DBF has changed in version
4.00. I have supplied a utility to convert the old file format into the
new one.

3. VIDEODRV will put a copy of each installed driver into your DRIVER
DIRECTORY. This is to facilitate future driver changes.

--
The Chief.
---------
Dr. A*la Olowofoyeku ( The African Chief )
Keele University         ( All opinions are not personal and do reflect )
England.                 ( the views of the universe )


Tel  : (0782) 621111
Fax  : (0782) 583228
----------------------------------------------------
"Love loves love, hate hates hate. Consummatum est."
----------------------------------------------------