JPH07191835A - Computer system - Google Patents

Abstract

PURPOSE:To automatically install a driver corresponding to the plug-in operation of an option device. CONSTITUTION:Concerning the computer system provided with the plug-in/plug- out mechanism of the option device, an option device 60 is provided with a non-volatile memory 70 storing a driver program, an operating system at the main body of the system is provided with a means (load program 22) for loading the device driver stored in the non-volatile memory 70 and when the option device 60 is plugged in an extended connector 30, the device driver of the plugged-in option device 60 is automatically loaded to a main memory 20.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer system having an optional device plug-in / plug-out mechanism.

[0002]

2. Description of the Related Art Generally, a personal computer has
A connector for function expansion for connecting an optional device (referred to as an expansion connector) is provided, and by connecting, for example, a communication card as an optional device to the expansion connector, an external device can be connected via the communication card. Communication becomes possible between them. Further, by connecting the HDD card, a plurality of hard disk devices can be connected via the HDD card.

In this kind of personal computer, when a function is expanded by an optional device by using various expansion connectors, a driver of an optional device plugged in the expansion connector (the optional device is operated properly). For operating system) in the computer body
Must be installed in advance.

At this time, conventionally, a driver of an optional device (device driver) is provided from a maker by a recording medium such as a floppy disk, and a user installs the device driver in an OS in a computer according to a predetermined procedure. For the first time, the optional device corresponding to the driver can be used.

As described above, conventionally, when the optional device is used, it is necessary to previously incorporate the driver of the optional device to be used into the OS in the computer body by the user's operation. Therefore, conventionally, there has been a problem that the use of the optional device imposes a heavy operational burden on the user and the optional device cannot be used easily and easily.

Further, when an optional device is required during the work of a certain process, the work is temporarily interrupted, the driver of the required optional device is incorporated, and then the interrupted work is restarted. Since it is necessary to use the optional device during operation, it is not possible to realize the operation function considering the usability such as using the optional device, and it is possible to construct the system considering the responsiveness and expandability. There was a problem that it was difficult.

Further, in the past, since the driver storage address and storage area of the optional device in the main memory are fixed in advance, it is not possible to easily deal with system changes, function upgrades, etc. However, there was a problem in constructing a system environment considering flexibility.

[0008]

As described above, in the prior art, when the optional device is used, it is necessary to previously incorporate the driver of the optional device to be used into the OS in the computer body by the operation of the user. However, when using the optional device, there is a problem that the operation load on the user is heavy and the optional device cannot be used easily and easily. Also, when an optional device is needed during work, the work must be interrupted once, and the interrupted work must be restarted after the driver installation work for the required optional device is performed. In addition, if necessary, it is not possible to use the optional device each time, and it is not possible to realize the operating function considering the usability such as proper use, and the system considering the operability and expandability when using the optional device. There was a problem that it was difficult to build. Also, because the storage address and storage area of the optional device driver in the main memory are fixed in advance, it is not possible to easily deal with system changes and functional upgrades, and consider the system's expandability and flexibility. There was a problem in building the system environment.

The present invention has been made in view of the above circumstances,
An object of the present invention is to provide a computer system that realizes an automatic device driver installation mechanism associated with an option device plug-in operation and significantly reduces a user's operation load when using the option device.

Further, according to the present invention, a device driver loading / unloading mechanism associated with a plug-in / plug-out operation of an option device is realized for a plurality of types of option devices, and an optional option in the middle of work is realized. It enables the use of devices, improves the usability of extended functions by optional devices, and selectively replaces the drivers of the optional devices to be used.
An object of the present invention is to provide a computer system that can be incorporated in S and can save the main storage area.

Further, the present invention realizes an OS-based dynamic environment setting mechanism for dynamically loading a corresponding device driver into a free space at that point in time in a plug-in operation of an optional device, thereby implementing the optional device. The purpose of the present invention is to provide a computer system that can improve the operability when expanding the functions by using it and can easily deal with system changes and function upgrades, and that can build a system environment considering system flexibility and expandability. To do.

[0012]

According to the present invention, in a computer system having an optional device plug-in / plug-out mechanism, an optional device has a device driver (driver program) having an input / output program for operating the device. ) Is stored, a means for loading the device driver stored in the nonvolatile memory is provided in the operating system of the system body, and when the option device is plugged in, the plugged-in option device It is characterized by realizing an automatic driver installation mechanism that automatically loads the device driver in the main memory in accordance with the plug-in operation of the optional device.

Further, the present invention realizes a device driver loading / unloading mechanism associated with a plurality of optional device plug-in / plug-out operations, so that an optional option in the middle of work can be realized. It enables the use of devices, improves the usability of extended functions by optional devices, and selectively replaces the drivers of the optional devices to be used.
It is characterized in that it can be incorporated in S to save the main storage area.

According to the present invention, the automatic installation mechanism further includes means for generating, managing and storing a driver management table (support table) which defines correspondence between optional devices and drivers. Realizes a dynamic environment setting mechanism of the OS system that dynamically loads the corresponding device driver to the free space at that point in time on the main memory during operation, improving operability when expanding functions with optional devices and changing the system. The feature is that the system environment can be constructed in consideration of system flexibility, expandability, etc., which can easily cope with functional upgrades.

Further, according to the present invention, at the time of loading the driver of the plug-in optional device, at the same time as securing the area, various values (for example, HDD, which are conventionally set by the user on the setup screen, dip switch, etc.). As a configuration for allocating a dynamic management information storage area under OS management in which dynamic information such as the number of connected devices, communication speed, flags, parameters, etc.) and dynamic information such as conditional expressions are set as necessary,
It is characterized by smoothing various functions by S management and enhancing functionality, and further improving the usability of the optional device.

Further, the present invention realizes an OS-based dynamic environment setting mechanism for managing a plurality of types of device drivers dynamically loaded according to a plug-in operation of an optional device on a driver management table (support table). The OS-based dynamic environment setting mechanism that can dynamically load multiple types of device drivers into the free space on the main memory at that time, and improve the operability when expanding the functions with optional devices, The feature is that the system environment can be constructed in consideration of system flexibility, expandability, etc., which can easily deal with system changes and function upgrades.

[0017]

In the above structure, when the optional device is plugged in, the OS load program is started,
The device driver of the plugged-in optional device is automatically loaded in the main memory. By automatically installing the driver accompanying the plug-in operation of the optional device, the work load on the user who uses the optional device can be significantly reduced, and the operational management of the optional device can be facilitated.

Further, in the above-described configuration of the present invention, the device driver load / unload control associated with the plug-in / plug-out operation of the option device for a plurality of types of option devices is performed during the work. It is possible to use any optional device in the device, which improves the usability of the extended function by the optional device and enables effective use of the limited area in the main memory.

Further, in the above-described configuration of the present invention, by having the driver management table (support table) which defines the correspondence between the optional device and the driver, the corresponding device driver is operated at the time of the plug-in operation of the optional device. A dynamic environment setting mechanism of the OS system that dynamically loads the OS to the free space at that time in the main memory can be realized, and the operability at the time of function expansion by the optional device is improved, and it is easy to change the system or upgrade the function. Can deal with

Further, in the above-mentioned configuration of the present invention, conventionally, the user sets up the dynamic management information storage area under the OS management which is secured at the same time when the driver of the plug-in optional device is loaded. Since various values (for example, various information such as the number of connected HDDs, communication speeds, flags, parameters, etc.) and dynamic information such as conditional expressions, which were set on the screen, DIP switch, etc., are set as necessary, Various processes can be facilitated by the OS management, high functionality can be achieved, and usability of the optional device can be further improved.

Further, in the above-mentioned configuration of the present invention, the OS system dynamics for managing a plurality of types of device drivers dynamically loaded by the plug-in operation of the optional device on the driver management table (support table) The environment setting mechanism allows multiple types of device drivers to be dynamically loaded into the free space on the main memory at that time, which improves the operability when expanding the functions with optional devices, and can be used for system changes and function upgrades. Easy to deal with.

[0022]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention.

In FIG. 1, reference numeral 10 is a CPU that controls the entire system, and an OS on the main memory (MEM) 20.
(Operation system) and executes a process according to an application program. Here, an expansion connector (EX-SLO) connected via the system bus 50 is used.
T) 30 optional device (PNP device) 6
0 Plug-in / Plug-ou
2), the optional device management process as shown in FIG. 2 is executed.

Reference numeral 20 denotes a main memory (MEM), which is a CPU 1
It is used as a storage area for various programs including the OS executed by 0, a work area used by the CPU 10, and the like. Here, at the time of system startup, a kernel 21 having a driver load / unload control function associated with plug-in / plug-out of an optional device 60 as shown in FIG. Kernel 21
Is started by the load program 22 for loading the device driver of the optional device into the free space in the main memory, and the driver management table (hereinafter referred to as the support table) that defines the correspondence between the optional device and the driver used by this OS. ) 23 and a predetermined program and database are loaded. At this time, in the support table 23, the O
Identification information (device ID) of each PNP device 60 supported by S, storage capacity of driver program, I
/ O port address, base address, interrupt level,
Built-in / initialized flags and the like are stored in association with each device. In addition, after the system is started up, in accordance with the plug-in operation of the optional device, under the control of the load program 22, a device driver (driver) in the non-volatile memory mounted on the plugged-in optional device is provided in the empty area. Program) 24
The dynamic management table 2 that is loaded and is used only when the processing using the plug-in device is executed
5 storage areas (dynamic management information storage areas) are secured.

Reference numeral 30 denotes an expansion connector (EX-SLOT) to which an optional device (PNP device) 60 for expanding the system function is connected. Here, for example, a communication card or the like that enables communication with an external device, Various option cards such as HDD cards that enable the addition of hard disks are the targets of Plug-in / Plug-out. The connection port of the optional device targeted by the present invention includes an expansion connector (E
Not only the X-SLOT) 30 but also a PCMCIA port or the like is included, but here, for simplification of description,
Only the extension connector (EX-SLOT) is given a reference numeral.

Reference numeral 40 denotes an external storage (HDD) realized by, for example, a magnetic disk, which stores various programs including an OS and application programs, files, etc. Here, an expansion connector (EX-SL) is used.
The utilization program (application program) of each optional device plugged in the OT) 30 is stored.

Reference numeral 50 denotes a system bus used for exchanging information between the CPU 10 and various input / output devices. Here, the main memory (MEM) 20 is connected together with the memory bus and an expansion connector (EX-). SLOT) 30, PCM
The CIA connector, the external storage 40, etc. are connected.

Reference numeral 60 denotes an expansion connector (EX-SLOT) 3
It is an optional device that is plugged in 0 for system function expansion, and here, an optional card such as a communication card and an HDD card is shown as a PNP device. The PNP device 60 has an ID (device ID) for identifying the type of each device, and is equipped with a non-volatile memory 70 storing a device driver of the device. As for the device driver in the non-volatile memory 70 mounted on the PNP device 60, the PNP device 60 has an expansion connector (EX
When it is plugged in to the (-SLOT) 30, it is dynamically loaded into an empty area on the main memory (MEM) 20 by the load program 22 of the OS on the main memory (MEM) 20.

FIG. 2 is a flow chart showing a processing procedure of device driver incorporation control under OS management in the above embodiment, which is a driver autoloading process associated with the plug-in of the PNP device 60 and a plug-out of the PNP device 60. The unload process associated with is shown.

Now, the operation of the embodiment of the present invention will be described with reference to the drawings.

At system startup, the OS stored in the external storage (HDD) 40 is stored in the main storage (ME).
M) It is loaded in a predetermined area on 20. At this time, the OS
The load itself is the same as before, but here, O
A kernel 21 having a device driver loading / unloading control means as shown in FIG. 2 is started in S, and the device driver of the plugged-in optional device is activated in the free space in the main memory by the kernel 21. A load program 22 for loading is included.

When the PNP device 60 is plugged in to the expansion connector (EX-SLOT) 30 after system startup (step S1 (YES) in FIG. 2), the plugged-in PNP is controlled under the control of the OS. The load control of the driver of the device 60 is executed.

The load control of the driver at this time is as follows.
The support check routine in S determines whether or not the plugged-in PNP device 60 is supported by the OS of the system, and if it is supported by the OS of the system, the support table 23 is referred to, Whether or not the plugged-in PNP device 60 is the first (newly) plugged-in after the system is started up, that is, the nonvolatile memory 70 mounted in the plugged-in PNP device 60. It is determined whether or not the device driver stored in the main memory (MEM) 20 has already been loaded (step S2 in FIG. 2).
), If it is already loaded in the main memory (MEM) 20, the loading process of the device program is terminated (step S2 (NO) in FIG. 2).

When the PNP device 60 is (newly) plugged in for the first time after system startup (step S2 (YES) in FIG. 2), the plugged-in PN is used.
The P device 60 is initialized, and information such as the device ID and the storage capacity of the device driver is read from the PNP device 60, and the device driver is stored in the nonvolatile memory 70 mounted on the plugged-in PNP device 60. By recognizing the capacity, a free area on the main memory (MEM) 20 is searched, and an area for storing the device driver and a storage area for the dynamic management table 25 are secured (steps S3, S4a, S4b in FIG. 2).

Then, the load program 22 is started,
The device driver in the non-volatile memory 70 mounted in the plugged-in PNP device 60 is loaded into the secured area on the main memory (MEM) 20 (FIG. 2).
Steps S5 and S6).

With the incorporation of this driver, the management information of the newly incorporated device driver is set on the support table 23. That is, here, the device ID read from the plug-in PNP device 60,
Also, the storage capacity of the device driver, the I / O port address, the base address, the interrupt level, the incorporated / initialized flag, and the like are set.

At this time, in the dynamic management table 25 which has been secured at the same time, various values (for example, H
Dynamic information such as the number of connected DD's mounted, parameters, etc.), conditional expressions, etc. are set as necessary and referred to in various processes under OS management.

Also, the plug-in PNP device 60
Is not supported by the OS of the system, or when the area for storing the device driver cannot be secured in the main memory (MEM) 20, a message to that effect is output and the device driver loading process ends. (FIG. 2 Steps S4a (NO) or S4b (NO), S7).

Further, the expansion connector (EX-SLOT) 30
When the PNP device 60 plugged in is plugged out, that is, the expansion connector (EX-SLOT) 3
When it is removed from 0 (step S11 (YES) in FIG. 2), whether or not to unload the device driver of the plugged-out PNP device 60 is recognized by the operation instruction or the device type intervening the operation screen, Either the plugged-out PNP device 60 is used again, or P
Except when there is an instruction input not to unload the device driver, such as when the same type of device driver is used again by replacing the NP device 60, the unload process is executed and the device driver 24 and the dynamic Free the storage area of the management table 25 (see FIG. 2).
Steps S12 and S13).

As described above, when the PNP device 60 is plugged in the expansion connector (EX-SLOT) 30, the OS load program 22 is activated and the device driver of the plugged-in PNP device 60 is stored in the main memory. Since the (MEM) 20 is automatically loaded, the work load on the user who uses the optional device can be significantly reduced, and the operational management of the optional device is facilitated.

Also, a plurality of types of optional devices (PNP
By controlling the loading / unloading of the device driver associated with the plug-in / plug-out operation for the device 60), it is possible to use any optional device during the work, which makes it easier to use the extended functions by the optional device. It is improved and the main memory can be effectively used.

Further, by having a support table that defines the correspondence between the option device (PNP device 60) and the device driver 24, the corresponding device driver is stored in the main memory (MEM) 20 when the option device is plugged in. Since an OS-based dynamic environment setting mechanism for dynamically loading in an empty area at that time can be realized, operability at the time of function expansion by an optional device is improved, and system change and function improvement can be easily dealt with.

Further, by the OS-based dynamic environment setting mechanism for managing on the support table 23 a plurality of types of device drivers 24, ... Dynamically loaded in accordance with the plug-in operation of the optional device (PNP device 60),
Main memory (MEM) for multiple types of device drivers 24, ...
20 can be dynamically loaded into the empty area at that time, which improves the operability when the function is expanded by the optional device, and can easily deal with the system change and the function upgrade.

In the above-described embodiment, the PNP device 60 plugged into the expansion connector (EX-SLOT) 30 is targeted, but the present invention is not limited to this.
It can also be applied to option boards, option cards, etc. that are plugged into various connectors such as CIA ports and PC card connectors.

In the above embodiment, the support table 23 stores the identifier (device ID) of the PNP device 60 that can be supported by the OS, the program capacity of the device driver in the non-volatile memory 70 mounted on the PNP device 60, The I / O port address, the base address, and the driver built-in / initialized flag information are defined, and this support table 23 is used.
In addition, although the above information is set each time the device driver is incorporated, the present invention is not limited to this. For example, the ID of a PNP device that can be supported by the OS and its PNP.
The device driver capacity of the device may be set in advance in a table.

[0047]

As described above in detail, according to the present invention, the automatic installation mechanism of the device driver accompanying the plug-in operation of the optional device is realized, so that the operation load on the user when using the optional device is significantly increased. Can be reduced to

Further, by implementing a device driver loading / unloading mechanism associated with the option device plug-in / plug-out operations for a plurality of types of option devices, the use of any option device during the work It is possible to improve the usability of the extended function by the optional device, and it is possible to selectively replace the driver of the optional device to be used and incorporate it into the OS to save the main storage area.

Further, when the driver of the plugged-in option device is loaded, at the same time, a dynamic management information storage area managed by the OS is secured, and the user has conventionally set up the dynamic management information storage area. Various values set on the screen, DIP switch, etc. (eg HDD
Since various information such as the number of connected devices, communication speed, parameters, etc.) and dynamic information such as conditional expressions can be set as necessary,
Various processes can be made smoother and more sophisticated by S management, and the usability of the optional device is further improved.

Further, by implementing an OS-based dynamic environment setting mechanism for dynamically loading a corresponding device driver into a free space at that point in time in the plug-in operation of an optional device, the function expansion by the optional device is realized. It is possible to improve the operability in the case of, and easily deal with system changes, function upgrades, etc., and construct a system environment in consideration of system flexibility, developability, and the like.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention.

FIG. 2 is a timing chart for explaining the operation of the embodiment.

[Explanation of Codes] 10 ... CPU, 20 ... Main memory (MEM), 21 ... Kernel, 22 ... Load program, 23 ... Driver management table (support table), 24 ... Device driver (driver program), 25 ... Dynamic management Table (dynamic management information storage area), 30 ... Expansion connector (EX-S
LOT), 40 ... External storage (HDD), 50 ... System bus, 60 ... PNP device (optional device),
70 ... Non-volatile memory.

Claims (7)

[Claims] 1. In a computer system having a plug-in / plug-out mechanism for an optional device, the optional device is provided with a non-volatile memory storing a device driver having an input / output program for operating the device, and the system main body is provided. The operating system is provided with means for loading the device driver stored in the non-volatile memory, and when the optional device is plugged in, the device driver of the plugged-in optional device is automatically loaded into the main memory. Characteristic computer system. 2. In a computer system having a plug-in / plug-out mechanism for an optional device, the optional device is provided with a non-volatile memory storing a device driver having an input / output program for operating the device, and the system main body is provided. In the operating system, check the free area of the main memory, secure the storage area of the device driver stored in the non-volatile memory,
A means for loading the device driver stored in the non-volatile memory and a means for unloading the device driver are provided in the area, and when the option device is plugged in, the driver of the plugged-in option device is provided. A computer system characterized by loading and unloading a driver of a plugged-out optional device when the optional device is plugged out. 3. In a computer system having a plug-in / plug-out mechanism for an optional device, the optional device is provided with an identification information storage section for the device,
And a non-volatile memory storing a device driver having an input / output program for operating the device,
When an optional device is plugged in, the operating system of the system main body is provided with means for reading the identification information in the identification information storage section and means for loading the device driver stored in the non-volatile memory. The device driver of the plugged-in optional device is automatically loaded to the main memory by determining whether the device can be used by the system by reading the identification information of the device. And computer system. 4. A means for generating, managing and storing a driver management table that defines correspondence between an optional device and a device driver, and referring to the table, embedding control of the device driver and after embedding the driver. The computer system according to claim 1, 2 or 3, wherein a device operation is executed. 5. The computer system according to claim 1, 2 or 3, wherein a dynamic data area is secured in the main memory in association with the loaded device driver. 6. The computer system according to claim 1, 2 or 3, wherein an address on a main memory for loading the device driver is determined at the time of loading. 7. A driver management table defining correspondence between an optional device and a driver, an identifier of an optional device that can be supported by an operating system, a driver program capacity in a nonvolatile memory mounted on the optional device, and I / O. The computer system according to claim 4, wherein information including an O port address and a base address is provided.