Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method for Preloading Multiple Device Drivers

IP.com Disclosure Number: IPCOM000114818D
Original Publication Date: 1995-Feb-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 56K

Publishing Venue

IBM

Related People

Ingenoso, T: AUTHOR [+2]

Abstract

Disclosed is a method for preloading a number of device drivers in the DOS environment. Without this method, only the disk compression driver, DBLSPACE.BIN, can be preloaded. During a conventional preloading operation, the keyboard is disabled, so that the loading of a driver cannot be interrupted or completely avoided through the use of the function keys. After the first half of the preload, the keyboard is enabled, so the loading of device drivers can be interrupted and avoided.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 67% of the total text.

Method for Preloading Multiple Device Drivers

      Disclosed is a method for preloading a number of device drivers
in the DOS environment.  Without this method, only the disk
compression driver, DBLSPACE.BIN, can be preloaded.  During a
conventional preloading operation, the keyboard is disabled, so that
the loading of a driver cannot be interrupted or completely avoided
through the use of the function keys.  After the first half of the
preload, the keyboard is enabled, so the loading of device drivers
can be interrupted and avoided.

      The Figure is a block diagram of the operation of the process,
which provides for loading device drivers from the CONFIG.INI file.
Drivers which are to be preloaded are indicated by a parameter
assigned for this function being "on."  The process is initiated by
BIOS in block 10.  If there is no CONFIG.INI file, as indicated in
block 12, the normal initialization process is continued in block 14;
otherwise the CONFIG.INI file is parsed in block 16; and, until an
End of File condition is determined in block 18, the name of each
device driver is loaded in block 20, while parameters which may be
attached to the name are loaded in block 22.  The parameter assigned
to trigger the preload function, indicated as PARAM, is tested in
block 24.  If this parameter is "on" SKIP_FLAG is set, and the driver
is preloaded in block 30.  If this parameter is "off" a Device Number
Flag is set in block 28 to allow the subsequent identificati...