Windows 3.1 Device Drivers (ddag31qh.hlp) (Table of Contents; Topic list)
Important Notice
The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.
Initializing the Driver
                                                     Up Next Previous
────────────────────────────────────────────────────────────────────────────
 
Windows initializes the keyboard driver by calling the driver's
initialization routine when it first loads the driver. Windows also calls
the driver's Inquire function to retrieve information about the driver in
the KBINFO structure.
 
The initialization routine typically retrieves the computer-type identifier
from ROM BIOS and determines whether the Windows is running with MS-DOS or
another environment, such as the MS-DOS compatibility box with IBM OS/2. The
driver uses the computer-type identifier to determine which translation
tables to use when translating scan codes. The driver adapts its processing
of keystrokes. For example, if running with OS/2, it passes CTRL+ESC key
combinations to OS/2 rather than Windows.
 
The Inquire function fills the KBINFO structure. The function also specifies
the size of the state array Windows must support. Windows calls the ToAscii
function to translate scan codes to ANSI character codes.
 
For more information about your keyboard and ROM BIOS, see the documentation
from your computer manufacturer.
 
 
                                      ♦