"Generic" 800x600 16-color 32-bit OS/2 2.x SuperVGA Display Driver Alpha Release: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 1: Line 1:
<PRE>
''February 15, 1993''
"Generic" 800x600 16-color 32-bit OS/2 2.x SuperVGA Display Driver
                          Alpha Release
                        February 15, 1993


This package contains an alpha level driver for 32-bit "generic"
This package contains an alpha level driver for 32-bit "generic" 800x600/16 Presentation Manager support. There is NO "SEAMLESS" WINDOWS (WIN-OS/2) SUPPORT in this driver. "Seamless" support will appear in a subsequent release.
800x600/16 Presentation Manager support. There is NO "SEAMLESS"
WINDOWS (WIN-OS/2) SUPPORT in this driver. "Seamless" support will
appear in a subsequent release.


Before installing the driver files:
Before installing the driver files:
 
#Make sure that you have the 32-bit graphics engine installed (OS/2 2.0 with Service Pak or OS/2 2.1 Beta or later). To determine your OS/2 release level, issue the command: <tt>SYSLEVEL</tt><br/>from any OS/2 command line prompt. OS/2 2.0 release levels prior to 06055 cannot use this driver.
        1. Make sure that you have the 32-bit graphics engine installed
#Make sure that your OS2.INI is set up for 32-bit IBMVGA32. (If you are currently running any 32-bit PM driver, you're fine.)
          (OS/2 2.0 with Service Pak or OS/2 2.1 Beta or later). To
#:a) If the file \OS2\SVGADATA.PMI does not exist, go to a full screen DOS session and issue the command: <tt>SVGA ON</tt><br/>If the \OS2\SVGADATA.PMI file is not then created, you will probably not be able to use this driver.
          determine your OS/2 release level, issue the command:
 
          SYSLEVEL
 
          from any OS/2 command line prompt. OS/2 2.0 release levels
          prior to 06055 cannot use this driver.
 
        2. Make sure that your OS2.INI is set up for 32-bit IBMVGA32.
          (If you are currently running any 32-bit PM driver,
          you're fine.)
 
        2a. If the file \OS2\SVGADATA.PMI does not exist, go to a
            full screen DOS session and issue the command:
 
            SVGA ON
 
            If the \OS2\SVGADATA.PMI file is not then created, you will
            probably not be able to use this driver.


To install IBMDEV32.DLL and IBMVGA32.DLL:
To install IBMDEV32.DLL and IBMVGA32.DLL:


        3. Create a new directory (e.g. \Display) and place the
3. Create a new directory (e.g. \Display) and place the IBMDEV32.DLL and IBMVGA32.DLL files in that directory. Edit your CONFIG.SYS to place the name of this new directory in LIBPATH, ahead of the directory containing the original IBMDEV32.DLL and IBMVGA32.DLL files. For example, if your LIBPATH line in CONFIG.SYS reads:
          IBMDEV32.DLL and IBMVGA32.DLL files in that directory.
LIBPATH=.;C:\OS2\DLL;C:\APP\DLL;C:\;
          Edit your CONFIG.SYS to place the name of this new
change it so that it reads:
          directory in LIBPATH, ahead of the directory containing
LIBPATH=.;C:\Display;C:\OS2\DLL;C:\APP\DLL;C:\;
          the original IBMDEV32.DLL and IBMVGA32.DLL files. For
(assuming that C:\Display is the directory containing the new IBMDEV32.DLL and IBMVGA32.DLL files). Keep a backup copy of the old CONFIG.SYS. Reboot.
          example, if your LIBPATH line in CONFIG.SYS reads:
 
          LIBPATH=.;C:\OS2\DLL;C:\APP\DLL;C:\;
 
          change it so that it reads:
 
          LIBPATH=.;C:\Display;C:\OS2\DLL;C:\APP\DLL;C:\;
 
          (assuming that C:\Display is the directory containing the
          new IBMDEV32.DLL and IBMVGA32.DLL files). Keep a backup
          copy of the old CONFIG.SYS. Reboot.


          Should you need to revert to the original CONFIG.SYS, simply
Should you need to revert to the original CONFIG.SYS, simply boot OS/2 from diskette. To do so, insert the OS/2 Installation Diskette in Drive A and reboot.  Insert Diskette 1 when prompted, then press ESC when prompted. You will be presented with an OS/2 command line from which you can make the necessary restoration.
          boot OS/2 from diskette. To do so, insert the OS/2
          Installation Diskette in Drive A and reboot.  Insert Diskette
          1 when prompted, then press ESC when prompted. You will be
          presented with an OS/2 command line from which you can make
          the necessary restoration.


---------------------------
----
The full source code to this driver is included in the OS/2 2.1 Device Driver Kit CD-ROM. It is simply a makefile change from the VGA32 driver!


The full source code to this driver is included in the OS/2 2.1 Device
Just change the two makefile instances of DSCAN_CNT from 480 to 600. Recompile, and you have this driver.
Driver Kit CD-ROM.  It is simply a makefile change from the VGA32 driver!
Just change the two makefile instances of DSCAN_CNT from 480 to 600.
Recompile, and you have this driver.


Please, if you are at all interested in OS/2 programming, join the
Please, if you are at all interested in OS/2 programming, join the Developer's assistance program and get this CD! Considering that most hardware companies have 0-1 people working on OS/2 devices, the online community can make a dramatic difference in the amount of OS/2 support available!
Developer's assistance program and get this CD! Considering that most
hardware companies have 0-1 people working on OS/2 devices, the online
community can make a dramatic difference in the amount of OS/2 support
available!


Please use the following information to join the DAP, or type GO OS2DAP
Please use the following information to join the DAP, or type GO OS2DAP on CompuServe:
on CompuServe:


OS/2 2.1 DEVICE DRIVER DEVELOPMENT KIT (DDK) CD-ROM AVAILABLE
OS/2 2.1 DEVICE DRIVER DEVELOPMENT KIT (DDK) CD-ROM AVAILABLE


This DDK, which replaces previously distributed Display and SCSI Device
This DDK, which replaces previously distributed Display and SCSI Device Adaptation Kits, is a release of over 50MB of full function source code, build tools, test tools, and on-line documentation for several OS/2 2.1 device drivers. It includes source code for PM display drivers, virtual video drivers, base video handlers, printer, DASD, SCSI, CD-ROM, and mouse drivers. Source code for WIN-OS/2 seamless display drivers is available separately.
Adaptation Kits, is a release of over 50MB of full function source code,
build tools, test tools, and on-line documentation for several OS/2 2.1
device drivers. It includes source code for PM display drivers, virtual
video drivers, base video handlers, printer, DASD, SCSI, CD-ROM, and
mouse drivers. Source code for WIN-OS/2 seamless display drivers is
available separately.


The information and code on this DDK will be updated and made
The information and code on this DDK will be updated and made available on a DDK in approximately three months and be available through a subscription service.
available on a DDK in approximately three months and be available
through a subscription service.


PREREQUISITES
PREREQUISITES
 
*CD-ROM Player
CD-ROM Player
*The DDK is intended for use on IBM OS/2 2.0 with the OS/2 2.0 Service Pack (XR06055) or later releases. Use of this DDK and its associated utilities on a system earlier than OS/2 2.0 and the Service Pack may produce unpredictable results.
 
*It is recommended that developers have the OS/2 2.0 Toolkit installed on their system so the 2.0 kernel debugger can be used.
The DDK is intended for use on IBM OS/2 2.0 with the OS/2 2.0
*If you are developing video drivers and you require the WIN-OS/2 seamless supplement, you are required to have licenses to use the Windows** 3.0 and Windows 3.1 DDK.
  Service Pack (XR06055) or later releases. Use of this DDK and
*For some drivers, Microsoft* C 6.0 is required.
  its associated utilities on a system earlier than OS/2 2.0 and
*For some drivers, Microsoft MASM 6.0 is required.
  the Service Pack may produce unpredictable results.
*Adobe Systems files included in the DDK must not be changed. Persons changing these files are subject to legal action by the Adobe Corporation.
 
It is recommended that developers have the OS/2 2.0 Toolkit
  installed on their system so the 2.0 kernel debugger can be used.
 
If you are developing video drivers and you require the WIN-OS/2
  seamless supplement, you are required to have licenses to use the
  Windows** 3.0 and Windows 3.1 DDK.
 
For some drivers, Microsoft* C 6.0 is required.
 
For some drivers, Microsoft MASM 6.0 is required.
 
Adobe Systems files included in the DDK must not be changed.
  Persons changing these files are subject to legal action by
  the Adobe Corporation.


INSTALLATION
INSTALLATION


The DDK includes an installation program that permits you to selectively
The DDK includes an installation program that permits you to selectively install device drivers. After selecting one, more, or all device drivers, the program informs you of the disk space required and how much available space you have. The program will not copy drivers onto your system unless it detects you have enough room for everything you selected. Regardless of your selections, the installation program will NOT update your CONFIG.SYS file. Please ignore any messages to the contrary that may be displayed in this release.
install device drivers. After selecting one, more, or all device
drivers, the program informs you of the disk space required and how much
available space you have. The program will not copy drivers onto your
system unless it detects you have enough room for everything you
selected. Regardless of your selections, the installation program will
NOT update your CONFIG.SYS file. Please ignore any messages to the
contrary that may be displayed in this release.


A README.DDK file provides installation information as well as
A README.DDK file provides installation information as well as a detailed description of the DDK.
a detailed description of the DDK.


ORDERING A DDK
ORDERING A DDK


This DDK is available at a nominal shipping and handling charge to
This DDK is available at a nominal shipping and handling charge to developers who are currently developing or planning to develop OS/2 device drivers.
developers who are currently developing or planning to develop OS/2
device drivers.  To obtain a DDK, contact the IBM DDK coordinator or
Ordering Number for your country or geography as listed below.
 
Country or Geography                  Ordering Number
--------------------                  ---------------
 
Australia, Hong Kong including        Telephone: 61-2-354-7684
People's Republic of China,          FAX:      61-2-354-7766
Indonesia, Malaysia, New Zealand,
Philippines, Singapore (including
offshort support of India), Sri
Lanka, Taiwan and Thailand
 
Canada
 
    NOTE: Device Driver developers in this geography will receive a
          direct communication regarding distribution and support.
 
Europe, Middle East and Africa        Telephone: 44-285-641175
                                      FAX:      44-285-640181
 
    NOTE: IBM EMEA OS/2 Developer Assistance Program members will
          receive a direct communication regarding distribution and
          support.
 
Japan                                Telephone: 81-3-5563-5897
                                      FAX:      81-3-5563-4957
 
Korea                                Telephone: 82-2-528-1548
                                      FAX:      82-2-528-1414/1415
 
Latin America                        Telephone: 011-52-627-1846
                                      FAX:      011-52-395-7812
 
United States                        Telephone: 407-982-4239
                                      FAX:      407-982-4218
 
    NOTES: When ordering a DDK, please FAX your name, company name,
          full business address, and telephone number to 407-982-4218.
          The DDK order materials will be mailed to you.
 
          If you are a member of the Boca Raton OEM (Device Driver)
          Support Bulletin Board or are a device driver developer in
          the Developer Assistance Program (DAP), you need NOT request
          a DDK unless you have not received DDK order materials by
          February 19, 1993.


TECHNICAL SUPPORT
TECHNICAL SUPPORT


Technical support for specific device driver development questions will
Technical support for specific device driver development questions will be provided. Information about obtaining support will be available through the DDK coordinator for your geography. Other OS/2 inquiries should be directed to the appropriate IBM channels.
be provided. Information about obtaining support will be available
through the DDK coordinator for your geography. Other OS/2 inquiries
should be directed to the appropriate IBM channels.
 
*
OS/2 is a registered trademark of the IBM Corporation in the
U.S. and other countries.
 
**
Microsoft is a registered trademark of the Microsoft Corporation and
Windows is a trademark of the Microsoft Corporation.


</PRE>
# OS/2 is a registered trademark of the IBM Corporation in the  U.S. and other countries.
# Microsoft is a registered trademark of the Microsoft Corporation and Windows is a trademark of the Microsoft Corporation.


[[Category:How_To]]
[[Category:How_To]]

Revision as of 22:15, 19 August 2019

February 15, 1993

This package contains an alpha level driver for 32-bit "generic" 800x600/16 Presentation Manager support. There is NO "SEAMLESS" WINDOWS (WIN-OS/2) SUPPORT in this driver. "Seamless" support will appear in a subsequent release.

Before installing the driver files:

  1. Make sure that you have the 32-bit graphics engine installed (OS/2 2.0 with Service Pak or OS/2 2.1 Beta or later). To determine your OS/2 release level, issue the command: SYSLEVEL
    from any OS/2 command line prompt. OS/2 2.0 release levels prior to 06055 cannot use this driver.
  2. Make sure that your OS2.INI is set up for 32-bit IBMVGA32. (If you are currently running any 32-bit PM driver, you're fine.)
    a) If the file \OS2\SVGADATA.PMI does not exist, go to a full screen DOS session and issue the command: SVGA ON
    If the \OS2\SVGADATA.PMI file is not then created, you will probably not be able to use this driver.

To install IBMDEV32.DLL and IBMVGA32.DLL:

3. Create a new directory (e.g. \Display) and place the IBMDEV32.DLL and IBMVGA32.DLL files in that directory. Edit your CONFIG.SYS to place the name of this new directory in LIBPATH, ahead of the directory containing the original IBMDEV32.DLL and IBMVGA32.DLL files. For example, if your LIBPATH line in CONFIG.SYS reads:

LIBPATH=.;C:\OS2\DLL;C:\APP\DLL;C:\;

change it so that it reads:

LIBPATH=.;C:\Display;C:\OS2\DLL;C:\APP\DLL;C:\;

(assuming that C:\Display is the directory containing the new IBMDEV32.DLL and IBMVGA32.DLL files). Keep a backup copy of the old CONFIG.SYS. Reboot.

Should you need to revert to the original CONFIG.SYS, simply boot OS/2 from diskette. To do so, insert the OS/2 Installation Diskette in Drive A and reboot. Insert Diskette 1 when prompted, then press ESC when prompted. You will be presented with an OS/2 command line from which you can make the necessary restoration.


The full source code to this driver is included in the OS/2 2.1 Device Driver Kit CD-ROM. It is simply a makefile change from the VGA32 driver!

Just change the two makefile instances of DSCAN_CNT from 480 to 600. Recompile, and you have this driver.

Please, if you are at all interested in OS/2 programming, join the Developer's assistance program and get this CD! Considering that most hardware companies have 0-1 people working on OS/2 devices, the online community can make a dramatic difference in the amount of OS/2 support available!

Please use the following information to join the DAP, or type GO OS2DAP on CompuServe:

OS/2 2.1 DEVICE DRIVER DEVELOPMENT KIT (DDK) CD-ROM AVAILABLE

This DDK, which replaces previously distributed Display and SCSI Device Adaptation Kits, is a release of over 50MB of full function source code, build tools, test tools, and on-line documentation for several OS/2 2.1 device drivers. It includes source code for PM display drivers, virtual video drivers, base video handlers, printer, DASD, SCSI, CD-ROM, and mouse drivers. Source code for WIN-OS/2 seamless display drivers is available separately.

The information and code on this DDK will be updated and made available on a DDK in approximately three months and be available through a subscription service.

PREREQUISITES

  • CD-ROM Player
  • The DDK is intended for use on IBM OS/2 2.0 with the OS/2 2.0 Service Pack (XR06055) or later releases. Use of this DDK and its associated utilities on a system earlier than OS/2 2.0 and the Service Pack may produce unpredictable results.
  • It is recommended that developers have the OS/2 2.0 Toolkit installed on their system so the 2.0 kernel debugger can be used.
  • If you are developing video drivers and you require the WIN-OS/2 seamless supplement, you are required to have licenses to use the Windows** 3.0 and Windows 3.1 DDK.
  • For some drivers, Microsoft* C 6.0 is required.
  • For some drivers, Microsoft MASM 6.0 is required.
  • Adobe Systems files included in the DDK must not be changed. Persons changing these files are subject to legal action by the Adobe Corporation.

INSTALLATION

The DDK includes an installation program that permits you to selectively install device drivers. After selecting one, more, or all device drivers, the program informs you of the disk space required and how much available space you have. The program will not copy drivers onto your system unless it detects you have enough room for everything you selected. Regardless of your selections, the installation program will NOT update your CONFIG.SYS file. Please ignore any messages to the contrary that may be displayed in this release.

A README.DDK file provides installation information as well as a detailed description of the DDK.

ORDERING A DDK

This DDK is available at a nominal shipping and handling charge to developers who are currently developing or planning to develop OS/2 device drivers.

TECHNICAL SUPPORT

Technical support for specific device driver development questions will be provided. Information about obtaining support will be available through the DDK coordinator for your geography. Other OS/2 inquiries should be directed to the appropriate IBM channels.

  1. OS/2 is a registered trademark of the IBM Corporation in the U.S. and other countries.
  2. Microsoft is a registered trademark of the Microsoft Corporation and Windows is a trademark of the Microsoft Corporation.