JPH10198553A - Boot method of computer system for detecting kind of cd-rom drive and method for mounting device driver driver - Google Patents

Abstract

PROBLEM TO BE SOLVED: To unnecessitate the production of a disk suitable for the kind of a CD-ROM drive by grasping the kind of the arranged CD-ROM drive and permitting a device driver being suitable for it to be resident in a memory. SOLUTION: After a port where the CD-ROM drive is arranged is detected through CMOS set-up information (S0), an ATAPI identifying drive command is transmitted to an IDE controller (S1). The IDE controller reads information stored in the memory in the CD-ROM drive(S2). The information is compared with previously decided information so as to discriminate the kind of the arranged CD-ROM drive (S3) and the information is reported to a user through a monitor, etc., (S4). Then, the device driver being suitable for the discriminated kind is selected (S5). The selected driver is used in a computer system booting, etc., by permitting it to be resident in the memory (S6).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a method for booting a computer system having a CD-ROM drive.

[0002]

2. Description of the Related Art A demand for a CD-ROM drive has rapidly increased due to expansion of multimedia functions, and supply has not been able to keep up.
Currently, there are many types of drives.
If the CD-ROM drive is different, the drive program (device driver) capable of driving the CD-ROM drive is also changed, so the drive file of the CD-ROM drive must be exchanged in the computer booting process for each CD-ROM drive used. This is disadvantageous in terms of cost.

Further, under the present situation where the OS is provided on a CD-ROM, the CD-ROM provided in the computer is provided.
If the type of the ROM drive is different, an FD containing a device driver suitable for the different type must be provided together, which is inconvenient. In the case of a hard disk that has been damaged, recovery measures include not only restoring general data on the hard disk, but also determining the type of CD-ROM drive installed in the computer and using a device driver adapted to this. Must be selected to make the driving program resident in memory during booting of the computer system. However, it is not easy for general users to grasp and select the type of CD-ROM drive and its device driver, which is a factor that makes system restoration difficult.

A device driver has a file extension of "SYS". However, a file having such a "SYS" extension cannot be executed by command input in a DOS prompt state, and must be read before a computer boots. CONFIG. This must be done in the SYS file. At this time, CO
NFIG. In the SYS file, a device driver is specified together with “DEVICE =”. For example, if the name of the device driver of the CD-ROM drive is CDROMDRV. SYS, this file exists in the directory C: \ DRIVE,
Assuming that the command / D: MSCD001 must be specified as an option, CONFI
G. FIG. If the following command does not exist in the SYS file, no device driver is set. DEVI
CE = C: {DRIVER} CDROMDRV. SYS
/ D: MSCD001

[0005] Such a command is called CONFIG. SY
S file, the system reads CDROMDRV.
A device driver SYS is resident in the RAM of the computer system to enable driving of the CD-ROM drive. However, if there are two or more types of hardware that can be used and their device drivers are different,
Even after automatically recognizing the type of hardware, there is no way to install a device driver according to this after booting the computer.

This is a DOS restriction that cannot be modified by the application program creator, for the following reasons. When a normal program recognizes hardware, an end code must be used to pass the recognition result to DOS. The number (integer from 0 to 255) set in the end code is transmitted to a variable that is recognized by DOS as an error level. At this time, a command for distinguishing this is “if errorlevel x gotol”.
abel # x ”is not used in the CONFIG.SYS file. Therefore, the method of recognizing the hardware and mounting the device driver corresponding to the recognized hardware using an if statement according to the end code is as follows.
CONFIG. It cannot be embodied in a SYS file.

As described above, CONFIG. In the SYS file, if errorlevel statement cannot be used, and after booting the computer, autoexec.b
Device driver (extension s) in at file
ys file), but this is a problem of DOS itself, so DO
Only the designer of S can make corrections. for that reason,
After the DOS has been booted once, CONFIG.
Unless the SYS is recreated and the computer system is booted again, it is no longer possible to load new device drivers into memory at the DOS prompt.

[0008]

SUMMARY OF THE INVENTION In view of the above-mentioned prior art, the present invention grasps the type of a CD-ROM drive provided when booting a computer system and stores a device driver suitable for the type in a memory. Provide a way to reside in It also provides a method by which a device driver can be reloaded into memory at the DOS prompt after booting the computer system.

[0009]

According to the present invention, there is provided a CD-ROM applied to a computer system having a hard disk and a CD-ROM drive.
As a boot method for detecting the type of drive, (a) A
IDE TAPI identification drive command
Transmitting to the controller, and (b) the ATAPI
A step in which the IDE controller reads information on the drive type stored in the memory of the CD-ROM drive in accordance with the identification drive command; and (c) a step of selecting a device driver for driving the CD-ROM drive in accordance with the information. (D) making the selected device driver resident in memory;
Provide a boot method including:

Before performing the step (a), the method may include a step of determining an equipment port of the CD-ROM drive based on the CMOS setup information. Also, CD-
The method may also include a step of notifying a user of information about the type of the ROM drive. And (c) process is a CD
-It can be done by the user with information on the type of ROM drive.

Further, according to the present invention, a step of changing the arrangement of a program mounted on a memory to secure a mounting area for a new device driver in the memory, a step of reading the new device driver from a storage medium, A step of obtaining a final address of a device driver mounted in the memory, a step of generating a command packet for controlling the new device driver, and a strategy routine and an interrupt routine of the new device driver. Initializing, connecting the address of the new device drive to the final address of the device driver installed during the booting,
Providing a device driver mounting method, comprising: resident the new device driver in a memory and ending the program. The size of the area for mounting the new device driver is preferably 64 kilobytes.

[0012]

Embodiments of the present invention will be described below with reference to the accompanying drawings.

FIG. 1 is a flowchart of a restoration program having a function of selectively booting a computer system through detection of the type of a CD-ROM drive, and FIG.
FIG. 3 is a flowchart of a method of selectively booting a computer system through detecting the type of a CD-ROM drive, FIG.
FIG. 4 is a flowchart of a method of mounting a device driver, and FIG. 4 is a memory configuration diagram for explaining a process of changing a program arrangement order of a memory in order to mount a device driver.

The method for booting a computer system according to the present invention can be applied to a computer system having a hard disk and a CD-ROM drive.
In such a computer system, a CD-ROM
The port equipped with the drive can be identified through CMOS setup information used during booting. Through the CMOS setup information, the hard disk is equipped as the primary master and the CD-RO
Assume that drive M has been found to be equipped as a secondary master.

After recognizing the port where the CD-ROM drive is located in this way, when the computer is booted, the restoration program embodying the computer system boot method of the present invention is operated. F if the hard disk of the computer system is damaged
D, the system must be booted through another medium. At this time, since the type of the CD-ROM drive must be known, the computer system booting method of the present invention is useful for a hard disk restoration program. is there. Preferably, a booting disc or CD for booting the computer
-AUTOEXEC. Insert the restoration program into the BAT file so that it operates when booting the computer system.

As shown in FIG. 1, the restoration program is executed by the user selecting an option / 0 or / 4.
The operation enters a CD-ROM drive detection stage. The difference between the two options is that / 4 does not display a message about the operation result of the program to the user, and / 0 displays a message about the operation result to the user.

When entering the CD-ROM drive detection stage,
As shown in FIG. 2, the CD-RO is transmitted through CMOS setup information that operates during booting of the computer.
After detecting the port equipped with the M drive (S0),
ATAPI IDENTIFY DRIVE
Drive command is used to control the CD-ROM drive.
The data is transmitted to a DE (Integrated Drive Electronics) controller (S1).

Here, in the IDE system, a memory having a drive control program built therein is installed on a printed circuit board of the drive, so that the computer system has a separate controller if it has only a controller for controlling these programs. CD-E without using any hardware
The ROM drive can be controlled. By adopting such a method, a user can drive various CD-ROM drives supporting the IDE method only with a general-purpose controller. ATA
PI is a standard for a CD-ROM interface among IDE application devices.

The command conforming to the ATAPI standard is AT
API Identify Drive Command (0A1
H), when this is input, the IDE controller reads and outputs the information stored in the memory in the CD-ROM drive (S2). 51 obtained by this
Of the two bytes of information, information on the manufacturer of the CD-ROM drive is recorded in the portion from 54 bytes to 64 bytes. If this information is compared with the information of the CD-ROM drive detection program, the information is provided. The type of the CD-ROM drive can be determined (S3). Then, information about the type of the CD-ROM drive can be notified to the user through a monitor or the like (S4).

In the determination step of S3, an information list about the model name of each CD-ROM drive is formed in the restoration program, and a drive file (device driver) name and manufacturer information according to each model name are recorded. It is performed by This information can be stored in a separate file for convenience at the time of addition. In this case, the new C
If a D-ROM drive is used, the information on the CD-ROM drive is added to the file and the relevant information is input to the restoration program.
The type of the D-ROM drive can be determined.

When the type of the CD-ROM drive is determined, a device driver suitable for the determined type of the CD-ROM drive is selected (S5). By making the selected device driver resident in the memory, it can be used for booting the computer system or making a system disk by copying to a hard disk or FD (S6).

In FIG. 1, the user selects option / 5.
Is selected, the ROMBIO of the computer system
Recognizing the information about the system manufacturer recorded in the specific position of S, the computer manufacturer currently operating the program is determined. This option is for determining the stored value of the ROM so that the program operates only in a specific computer system. Option / 1 is used when restoring the hard disk according to the method of the present invention, and when the user selects this option, the contents of the damaged hard disk can be erased and the program can be reinstalled or a boot disk can be created. It has become. The option / 2 is for outputting a message for determining re-booting of the system after restoring the hard disk, and the option / 3 is for outputting a message notifying the end of the program.

By appropriately setting the options of such a program according to the frequency of use of the program and creating the options in an arrangement file or by setting this, the results of the CD-ROM drive type detection of the present invention can be varied. It can be applied to

That is, the restoration program is operated at the time of booting the computer system together with the option of / 0 or / 4, and the device driver suitable for the type of the detected CD-ROM drive is loaded into the RAM at the time of booting. Then, CD-ROM
A computer system can be booted regardless of the type of drive, and a system disk can be easily created using a device driver. Also,
The user can confirm the program operation using other options, or use the / 1 option to use the restoration program for restoring a damaged hard disk. In other words, if the option / 1 and the option / 0 or / 4 are used in an appropriate order, after the current file in the damaged hard disk is completely deleted, the CD-equipped
The type of the ROM drive can be automatically recognized, and a device driver suitable for the type can be copied to the hard disk and reproduced.

In the above, the method of recognizing the type of the CD-ROM drive and mounting the corresponding device driver in the memory when booting the computer system has been described. Next, a method of mounting the device drive in the memory while the computer is booted will be described below. First, assuming that a program embodying the method of the present invention is a launcher, the method of the present invention can be realized by inputting the following command at a DOS prompt. A> launcher d: \ path \ filename.sys / opti
on …… d: \ path is the path name where filename.sys is located.
filename.sys is the file name of the device driver.

When this command is input, as shown in FIG. 3, the launcher program is mounted on the memory, and the process of rearranging the launcher program mounted on the memory is performed (S11). As shown in FIG. 4A, when the command is input at the DOS prompt, the launcher program is first mounted at the position next to the program currently mounted on the memory. In FIG. 4, part a is a mounting area for a DOS and a device driver mounted at the time of booting, part b is a mounting area for a launcher program, and part c is a non-program mounting area. The launcher program once installed in this way is shown in FIG.
As shown in B, it is relocated to a position leaving a space d of 64 kilobytes. This process involves copying the launcher program to a location approximately 64 kilobytes away from the initial location, and copying the code segment (Code Segm
ent: CS) is moved to a position where 64 kilobytes have been added. The space d of 64 kilobytes is
This is the space where the device driver mounted by the launcher program is located. Since the size of a typical device driver is smaller than 64 kilobytes, space d is sufficient.

As described above, after allocating the launcher program while securing a space of 64 Kbytes on the memory, the device driver specified on the command line is read into the space (S12). Next, the address of the last device driver loaded in the memory at the time of booting is determined (S13).

Subsequently, since the device driver always has a strategy routine and an interrupt routine, which must be initialized, a command packet necessary for the execution is created (S14). The DOS has a command packet for initializing a device driver or generating an interrupt for the device driver. Command packets for driving a normal device driver are mounted in the DOS, and the device driver mounted in the memory during the booting process can use the DOS command packet.
In this example, since the device driver is separately mounted in the memory after the DOS booting, the command packet inside the DOS cannot be used. Therefore, a command packet having a similar function must be installed in the memory for the device driver. The command packet is created so as to conform to the attributes of the device driver file. The structure of a command packet for initializing a device driver is as follows.

[Table 1] +0: Stores the size (number of bytes) of the entire packet: 24. +1: Unit name: Specify zero. +2: Command code: Zero indicates an initialization instruction. +3: Status flag: 8000H is an error, 00
00H indicates normal. +5: Unused 8-byte information: Packed to zero. +13: Number of units: Specify zero. +14: Address to return to when braking (segment:
Offset) +18: The first address where the input parameter is located (segment offset) and the first address where the option is read and stored are set. +22: Specify the next driver number: zero. +23: Specify zero to fill even numbers.

After the command packet is created in this way, six addresses of the device driver in which the address of the strategy routine is set are called in order to allow the device driver to recognize the first address of the command packet (S15). . Next, since the address of the interrupt routine is set in the eight addresses of the device driver, this is called (S16). Calling this routine returns the size for the resident portion of the device driver to the ax register. As a result, the device driver to be resident in the memory through the launcher program is initialized.

Next, in order for the computer system to recognize the new device driver, the address of the device driver installed in the memory must be changed before the currently loaded device driver (S17). The address changing process of the device driver will be described.

In general, an address value designating the next device driver is recorded in 4 bytes from the zero address of the device driver. By doing so, when the DOS detects the first device driver, the DOS knows the position where the next device driver is located from the address recorded in 4 bytes from the zero address of the device driver, and determines the zero address of the next device driver. By continuing to refer to 4 bytes from, another device driver can be found. Also, CONFIG. S
4 bytes from the zero address of the last device driver mounted on the memory by YS are set to 0FFFF to indicate that the device driver is the last mounted device driver.
An identification mark of H, 0FFFFH (4 bytes) is recorded. The launcher program links the last address of the device driver with the address of the device driver already installed in the memory by booting. Also,
In the 4 bytes from the first zero address of the currently read device driver, a -1 value is recorded to indicate that this device driver is the last device driver.
Through this process, the last device driver installed in the memory at the time of booting is connected to the new device driver installed in the memory by the launcher program.

If the new device driver is resident in the memory, the program ends (S18). The device drivers that can be mounted by this method include various device drivers such as a hard disk device driver in addition to a CD-ROM device driver.

By the above method, CONFIG. SYS
, One or more device drivers can be resident in the memory in addition to the device drivers installed in the memory device. That is, when the name of a device driver desired to be mounted on the memory is specified in the launcher program in an optional form, the launcher program mounts the desired device driver on the memory at the DOS prompt. The form in which the device driver is specified in the launcher program is as follows. launcherd: \ path \ filename.sys /
option

Such a command can be made processable by placing it in the autoexec.bat file.
User input is possible on the DOS prompt, and if the type of hardware installed in the computer is known, a device driver suitable for the installed hardware device is automatically stored in the memory using if and goto instructions. It can be mounted on.

For example, if a program (hereinafter referred to as “detected.exe” for convenience) that can recognize the CD-ROM drive to be driven is operated and the result of the recognition is a product of Company A,
If you create a program that returns 2 if it is a company B product, you can selectively load the A.sys and B.sys files, which are device drivers suitable for each company product, into the memory as follows: it can.

[Table 2] detected.exe if errorlevel 1 goto company # A if errorlevel 2 goto company # B goto finish: company # A launcher c: ＼A.sys / option goto finish: company # B launcher c: ＼B.sys / option goto finish: finish

In this case, the booting disks (FD, C) containing the device drivers of the companies A and B are provided.
(D-ROM, hard disk) can be automatically recognized and mounted on the memory in one boot disk without having to create a D-ROM and a hard disk, respectively. This prevents duplication of booting disks and reduces costs. This has the advantage that the computer system has to be re-booted in order to install a new device driver.

Further, when the above-mentioned program is mounted on a booming disk, the type of the CD-ROM drive can be easily grasped by the user, and a device driver suitable for this can be selected and mounted on the memory of the computer system. be able to. Therefore, CD-ROM
Regardless of the type of drive, if you have one disc,
Various CD-ROM drives are automatically recognized and can be driven.

[0038]

According to the present invention, it is not necessary to manufacture a device driver disk suitable for each type of CD-ROM drive, and the cost can be significantly reduced. In addition, C
By automatically recognizing the type of the D-ROM drive, correct driving of the CD-ROM drive can always be easily performed. Further, since the program can be loaded in the CD-ROM, various CD-ROM drives can be driven with one CD-ROM, and this can be easily restored when the hard disk is damaged. A CD-ROM for restoring a hard disk can be manufactured.

[Brief description of the drawings]

FIG. 1 is a flowchart of a restoration program having a boot function of a computer system through detection of the type of a CD-ROM drive according to the present invention.

FIG. 2 is a flowchart of a method of booting a computer system through detecting the type of a CD-ROM drive according to the present invention.

FIG. 3 is a flowchart of a device driver mounting method according to the present invention.

FIG. 4 is a memory configuration diagram for explaining a process of changing the arrangement order of programs mounted on a memory for mounting a device driver according to the present invention.

Claims (7)

[Claims] 1. A CD-R applied to a computer system having a hard disk and a CD-ROM drive
A boot method for detecting the type of an OM drive, comprising: (a) a step of transmitting an ATAPI identification drive command to an IDE controller; and (b) a step in which the IDE controller operates the CD-ROM drive in accordance with the ATAPI identification drive command. Reading information about the drive type stored in the memory; (c) selecting a device driver for driving the CD-ROM drive according to the information; and (d) storing the selected device driver in the memory. A booting method comprising the steps of: 2. The boot method according to claim 1, further comprising the step of: (a) judging an equipment port of the CD-ROM drive based on CMOS setup information before performing the step (a). 3. The boot method according to claim 1, further comprising a step of notifying a user of information on the type of the CD-ROM drive. 4. The boot method according to claim 3, wherein the step (c) is performed by a user using information on a type of the CD-ROM drive. 5. A step of relocating a program mounted in a memory to secure a mounting area of a new device driver in the memory, reading the new device driver from a storage medium, and performing booting. A step of obtaining a final address of the device driver mounted on the memory, a step of creating a command packet for controlling the new device driver, and a step of performing a strategy routine and an interrupt routine of the new device driver and initializing the same. Connecting the address of the new device drive to the final address of the device driver installed at the time of booting, and ending the program by making the new device driver resident in the memory. Method. 6. The device driver mounting method according to claim 5, wherein the area for mounting the new device driver is 64 kilobytes. 7. The method according to claim 5, wherein the new device driver is a device driver of a CD-ROM drive.