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

Dual Use of CONFIG. SYS Device Driver Installation Line

IP.com Disclosure Number: IPCOM000108143D
Original Publication Date: 1992-Apr-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 1 page(s) / 52K

Publishing Venue

IBM

Related People

Brewer, JA: AUTHOR [+4]

Abstract

Disclosed is a method to store small amounts of information required by a personal computer device driver setup program. This information will never be directly used by the device driver. Basically, minimal setup required program parameters are saved in the driver installation line of the CONFIG.SYS file. When the device driver installs at boot time, it will ignore these "extra" parameters. This is unusual since parameters on a device driver installation line normally relate directly to the device driver installation. Thus, not only is the driver install line (in the CONFIG.SYS file) used to initialize or start the device driver, it also holds information needed only by the device driver setup program.

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

Dual Use of CONFIG. SYS Device Driver Installation Line

      Disclosed is a method to store small amounts of information
required by a personal computer device driver setup program. This
information will never be directly used by the device driver.
Basically, minimal setup required program parameters are saved in the
driver installation line of the CONFIG.SYS file.  When the device
driver installs at boot time, it will ignore these "extra"
parameters.  This is unusual since parameters on a device driver
installation line normally relate directly to the device driver
installation.  Thus, not only is the driver install line (in the
CONFIG.SYS file) used to initialize or start the device driver, it
also holds information needed only by the device driver setup
program.

      In the case of an Expanded Memory Manager (EMM) device driver,
it is helpful for the device driver setup program to remember when a
16 K- Byte memory page is unusable for EMM purposes, even though an
EMM setup program memory check may have indicated a particular memory
page to be available.  A memory page is available to the EMM device
driver only when no other device responds in that page's address
range.

      Some memory mapped devices use addresses in the system memory
space and these addresses may be hidden from the system until being
activated by an application or by their own device driver.  Whether a
seemingly unused 16 K-Byte memory page is really unusable to the EMM
device driv...