Method and apparatus for dynamically loading a driver routine in a computer memory

Claim 3

The method as set forth in claim 1, wherein said operating system comprises a disk operating system (DOS).

Claim 4

The method as set forth in claim 1, wherein said device driver comprises a dynamic loading function, static data, at least one run time interface, and an initialization function.

Claim 5

The method as set forth in claim 3, wherein the step of retaining a minimum resident subset of the device driver using the initial copy for storage comprises the step of identifying, to said operating system said dynamic loading function and said static data as said minimum resident subset of the device driver.

Claim 6

The method as set forth in claim 1, wherein the step of initializing said device driver comprises the steps of: obtaining a path for said device driver stored in said storage device; storing said path of said device driver; determining an ending location of said minimum resident subset of the device driver of the initial copy; and communicating, to said operating system, said ending location of said minimum resident subset of the device driver of the initial copy.

Claim 7

The method as set forth in claim 1, wherein the step of loading a subsequent copy of said device driver comprises the steps of: allocating memory for said subsequent copy of said device driver when execution of said device driver is required; and reading said subsequent copy of said device driver from said storage device into said allocated memory.

Claim 8

The method as set forth in claim 1, wherein the step of executing said device driver utilizing both said minimum resident subset of the device driver of the initial copy and said dynamically loaded subset of said device driver of the subsequent copy comprises the steps of: storing a code segment into said allocated memory, said code segment being said subsequent copy of said device driver; determining an offset to a starting location of run time interfaces that are members of said dynamically loaded subset of the device driver; building a pointer with said code segment and said offset; and calling said run time interfaces residing in said allocated memory with said pointer.

Claim 9

The method as set forth in claim 1, further comprising the steps of: providing a user of the computer system with an option to either dynamically load a subsequent copy of said device driver, or to permanently store an entire copy of said device driver in said computer system memory during initialization; and permanently storing all of said device driver in said computer system memory when said user so elects.

Claim 10

A computer system comprising; a processor unit; a memory coupled to the processor unit; at least one peripheral device coupled to said processor unit; an operating system that operates said computer system; and a storage device, coupled to said processor, that stores a device driver for said at least one peripheral device, an initial copy of said device driver being loaded into said memory from said storage device during an initialization period, said initial copy of said device driver comprising: an initialization function that initializes said initial copy of the device driver in said computer system memory and specifies to said operating system a minimum resident subset of the device driver which is to be retained in said computer system memory using the initial copy, thereby reducing the amount of memory required to store said device driver in said computer system memory; and a dynamic loading function that loads a subsequent copy of said device driver from said storage device into said computer system memory in response to a call to said device driver from said processor unit, said subsequent copy of said device driver comprising at least said minimum resident subset and a dynamically loaded subset of the device driver, said processor unit utilizing both said minimum resident subset of the device driver of the initial copy and said dynamically loaded subset of said device driver of the subsequent copy to execute said device driver.

Claim 11

A computer system comprising; a processor unit; a memory coupled to the processor unit; at least one peripheral device coupled to said processor unit; an operating system that operates said computer system; and a storage device, coupled to said processor, that stores a device driver for said at least one peripheral device, an initial copy of said device driver being loaded into said memory from said storage device during an initialization period, said initial copy of said device driver comprising: an initialization function that initializes said initial copy of the device driver in said computer system memory and specifies to said operating system a minimum resident subset of the device driver which is to be retained in said computer system memory using the initial copy, thereby reducing the amount of memory required to store said device driver in said computer system memory; and a dynamic loading function that loads a subsequent copy of said device driver from said storage device into said computer system memory in response to a call to said device driver from said processor unit, said subsequent copy of said device driver comprising at least said minimum resident subset and a dynamically loaded subset of the device driver, said processor unit utilizing both said minimum resident subset of the device driver of the initial copy and said dynamically loaded subset of said device driver of the subsequent copy to execute said device driver.

Claim 12

The computer system as set forth in claim 9, wherein said operating system comprises at least a disk operating system (DOS).

Claim 13

The computer system as set forth in claim 9, wherein said device driver further comprises at least one run time interface and static data.

Claim 14

The computer system as set forth in claim 11, wherein said minimum resident subset of the device driver comprises said dynamic loading function and said static data.

Claim 15

The computer system as set forth in claim 11, wherein said dynamic loading function comprises: a pointer building function that stores a code segment for said allocated memory wherein said code segment is said subsequent copy of said device driver, that determines an offset to a starting location of said run time interfaces that are members of said dynamically loaded subset of the device driver, and that builds a pointer with said code segment and said offset; and a calling function that calls said run time interfaces residing in said allocated memory with said pointer.

Claim 16

The computer system as set forth in claim 11, wherein said dynamic loading function comprises: a driver location building function that stores an execution location for said allocated memory, that determines a starting location of said run time interfaces that are members of said dynamically loaded subset of the device driver, and that builds a run-time environment to allow execution at said starting location; and a calling function that calls said run time interface residing in said allocated memory at said starting location.

Claim 17

The computer system as set forth in claim 9, wherein said initialization function comprises: a device driver identification function that obtains a path for said device driver stored in said storage device, and that stores said path of said device driver; and a device driver size function that determines an ending location of said minimum resident subset of the device driver of the initial copy, and that communicates, to said operating system, said ending location of said minimum resident subset of the device driver of the initial copy.

Claim 18

The computer system as set forth in claim 9, wherein said dynamic loading function comprises: an allocation function that allocates memory from said memory of said computer system for said subsequent copy of said device driver when a call is made to said device driver; and a reading function that reads said subsequent copy of said device driver from said storage device into said allocated memory.

Claim 19

The computer system as set forth in claim 9, wherein said at least one peripheral device comprises a peripheral device configured in accordance with an Industry Standard Architecture (ISA) standard.

Claim 22

The method as set forth in claim 18, wherein the step of initializing said device driver comprises the steps of: obtaining a path for said device driver stored in said storage device; storing said path for said device driver; determining an ending location of said minimum resident subset of the device driver of the initial copy; and communicating, to said operating system, said ending location of said minimum resident subset of the device driver of the initial copy.

Claim 23

The method as set forth in claim 18, wherein: the step of loading said run time interfaces comprises the steps of: allocating memory for said run time interfaces when execution of said device driver is required; and reading said run time interfaces from said device driver stored on said storage device into said allocated memory; and the step of calling said run time interfaces comprises the steps of: storing a code segment for said allocated memory, said code segment being said subsequent copy of said device driver; determining an offset to a starting location of said run time interfaces that are members of said dynamically loaded subset of the device driver of the subsequent copy; building a pointer with said code segment and said offset; and calling said run time interfaces residing in said allocated memory with said pointer.