KR100706514B1 - Booting method of operating system on hard disk - Google Patents

Abstract

The present invention relates to an operating system booting method for stably processing a booting process by controlling a booting process for each partition when booting is performed through a storage medium such as a hard disk. Searching for and executing a boot loader after the boot sector is registered in the memory; Loading a boot program of the first partition according to path information when the boot failure count of the first hard disk partition is determined by the boot loader and the boot failure count is less than or equal to a predetermined number of times; And if the number of boot failures of the first partition is greater than or equal to a predetermined number of times, if the number of boot failures of the second partition is determined by the boot loader, and if the number of boot failures of the second partition is less than or equal to a predetermined number of times, booting of the second partition is performed. The program is characterized in that it comprises a step of loading.

Description

Booting method of operating system on hard disk}

1 is a structural diagram schematically showing the structure of a typical hard disk.

2 is a flowchart illustrating a general operating system booting method on a hard disk.

3 is a data block diagram schematically showing the configuration of a hard disk used in the embodiment of the present invention.

4A is a flowchart illustrating a method of booting an operating system on a hard disk using a boot program, "NK.bin", according to an embodiment of the present invention.

4B is a flowchart illustrating a method of booting an operating system on a hard disk using a boot program, "NK_F.bin", according to an embodiment of the present invention.

FIG. 5 is a table showing a data structure of an MBR on a hard disk used in an embodiment of the present invention. FIG.

Fig. 6 is a block diagram showing a file structure related to booting on a hard disk used in the embodiment of the present invention.

<Explanation of symbols for main parts of drawing>

100: MBR (Master Boot Record) 101: bootcode

102, 103, 104, and 105: partition entry 106: signature word

200: spare sector 300: PBR (Partition Boot Record)

400: FAT1 500: FAT2

600: root directory 700: file area

701: First partition 702: Second partition

703: third partition 704: fourth partition

The present invention relates to a method of booting an operating system using a hard disk.

In general, products such as HDTV, digital video systems such as PVR (Personal Video Recorder), desktop computers, notebooks, telematics terminals, etc. adopt a method of storing and loading an operating system (OS) with a hard disk. have.

Using Microsoft's Windows environment as an example, a general digital processing system stores an operating system such as Windows 98 or Windows 2000 on a hard disk, and uses a BIOS such as phoenix or AMI when the power is turned on. To load and run the operating system stored in the hard disk.

Such a digital processing system may not be able to boot if an error occurs in a specific area of the hard disk. Therefore, the user should regularly check the hard disk, back up data, etc., which is cumbersome and time consuming. This makes the user feel uncomfortable.

1 is a structural diagram schematically showing a structure of a general hard disk.

According to FIG. 1, in the hard disk, several disks 20 are positioned on the cylinder connecting shaft 10, and each disk 20 is divided into a sector 30, a head 40, and an upper and lower cylinder 50. . In general, hard disks are classified into a cylinder head sector (CHS) mode and a logical blocking addressing (LBA) mode according to an address mapping method. The hard disk of the CHS mode is the cylinder 50 (0 to 1023 bytes). The address mapping is possible up to 528 MBytes through three elements, head 40 (0 to 15 bytes) and sector 30 (1 to 63 bytes).

On the other hand, the LBA mode hard disk uses a linear address method with a block range of 0 to 268435456 bytes, and normally one block is composed of 512 bytes. If the BIOS supports LBA, it has a virtual head count, and the range of the head is increased in the range of 0 to 255 bytes, and the maximum address mapping space is 8GByte. Using PIO / DMA access, the cylinder ranges from 0 to 65535 bytes, the head ranges from 0 to 15 bytes, the sector ranges from 0 to 255 bytes, and the address mapping area is 128G (28 powers of 2) bytes.

Usually, the internal address area of hard disk is composed of Master Boot Record (MBR), Partition Boot Record (PBR), File Allocation Table (FAT), Root Directory, File Area, etc. Using the 2000 environment as an example, the general booting process is as follows.

2 is a flowchart illustrating a general operating system booting method on a hard disk.

First, when power is supplied, a POST (Power On Self Test) for initializing basic functions such as connecting an external device is performed (S100), and when the POST is terminated, a master boot record (MBR) is read into a memory (S105). . The MBR searches a partition boot record (PBR) to find an active partition among hard disks (S110), and executes ntldr (Windows 2000 boot program loader) by referring to a FAT when a boot sector is registered in memory (S115). ).

The ntldr is converted into a 32-bit flat memory model and then starts a mini file system required for booting (S120).

First, the ntldr reads a "boot.ini" file and provides a user with an operating system menu. For example, when Windows 98 and 2000 are installed together, the ntldr displays a multiboot window displaying both operating systems (S125).

Subsequently, when a confirmation command is input from the user (S130), the ntldr loads an operating system. For example, when Windows 2000 is selected, the "ntoskrnl.exe" file is read (S140), and when Windows 98 is selected, "bootsect.dos". The file is read (S135).

If the "ntoskrnl.exe" file is read, the "ntoskrnl.exe" file reads the "ntdetect.com" file to obtain hardware information (S140), and finally the Windows 2000 operating system is performed (S150).

However, as described above, if the executed ntldr starts a mini file system (S120) and an error occurs in the process of searching for and executing a file related to booting, booting is not normally performed.

In this case, a blue screen displaying an error code is displayed on the screen, and a reboot is performed. If a file related to a boot is damaged, booting is difficult to be successful, and booting in a reset (safe) mode is attempted.

However, if the booting by the reset mode fails, recovery of the failed hard disk becomes impossible and the hard disk needs to be formatted.

When dust or dust enters the hard disk or is affected by the formation of magnetic field, heat generation, or impact, the sectors often occur. A digital processing system that uses a hard disk for booting is a safety / security management system. If the boot is not executed in an urgent situation, such as being used, there is a problem that is at risk.

Accordingly, an object of the present invention is to provide a method for booting an operating system on a hard disk, in which a booting process is controlled by a partition when the booting is performed through a storage medium such as a hard disk so that the booting process is stably processed.

In addition, the present invention is that the boot process is controlled by partitions of the hard disk, when the first activated boot program is damaged, another copy of the boot program is loaded and at the same time restores the damaged boot program hard to effectively respond to unexpected hard disk damage Another goal is to provide a way to boot an operating system on disk.

In addition, the present invention provides a method for booting the operating system on the hard disk to prevent the hard disk damage is difficult to recover by controlling the initial booting program used in the production of the product as well as the booting program of the operating system installed by the user partition by partition. For another purpose.

In order to achieve the above object, the operating system booting method on a hard disk according to the present invention comprises the steps of searching for and executing a boot loader after the boot sector of the hard disk is registered in the memory; Loading a boot program of the first partition according to path information when the boot failure count of the first hard disk partition is determined by the boot loader and the boot failure count is less than or equal to a predetermined number of times; And if the number of boot failures of the first partition is greater than or equal to a predetermined number of times, if the number of boot failures of the second partition is determined by the boot loader, and if the number of boot failures of the second partition is less than or equal to a predetermined number of times, booting of the second partition is performed. The program is characterized in that it comprises a step of loading.

In order to achieve the above object, the operating system booting method on a hard disk according to the present invention relates to an operating system booting method when an operation error occurs in the digital data processing system, a first booting fails, or the hard disk is initialized. Providing an interface by the BIOS and being selected to enter the reset mode; Searching for and executing the boot loader after the boot sector of the hard disk is registered in the memory; When the boot failure count of the initial booting program used in the production of the product recorded on the first hard disk partition is confirmed by the boot loader and the boot failure count is less than a predetermined number of times, the initial booting program of the first partition according to path information. Is loaded; If the number of boot failures of the first partition is greater than or equal to a predetermined number of times, the number of boot failures of the initial booting program on the second partition is checked. If the number of boot failures of the second partition is less than or equal to a predetermined number of times, the initial boot of the second partition is not. The program is characterized in that it comprises a step of loading.

Hereinafter, an operating system booting method on a hard disk according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

3 is a data block diagram schematically showing the configuration of a hard disk used in an embodiment of the present invention, Figure 4a is booting an operating system on a hard disk using a boot program, "NK.bin" according to an embodiment of the present invention A flowchart illustrating the method. 4B is a flowchart illustrating a method of booting an operating system on a hard disk using a boot program “NK_F.bin” according to an embodiment of the present invention.

First, in describing an operating system booting method on a hard disk according to an embodiment of the present invention, the hard disk is mounted on a PVR, and the PVR is provided with a memory in which a BIOS (Basic Input / Output System) is stored. Windows CE is used.

Referring to FIG. 3, the hard disk includes an MBR 100, a spare sector 200, a PBR 300, a FAT1 400, a FAT2 500, a root directory 600, and a file area 700. When AC power is applied to the PVR, the BIOS checks basic devices such as memory, input device, and serial port by using the Applied Computing System Firmware Library (ACSFL), and makes the functions operable by initializing the functions (POST). (S100).

Subsequently, the BIOS starts reading an initial start area (0: 0: 1 in the case of CHS) of the hard disk, and as described above, the MBR 100 is located. The BIOS searches the PBR 300 of the activated area through the data structure table of the MBR 100 and checks the location of the boot loader and the boot program using the information stored in the PBR 300 (S105).

5 is a table showing a data structure of the MBR 100 on the hard disk used in the embodiment of the present invention.

The MBR is composed of one sector, which is usually 512 bytes in size, of which the first 446 bytes contains a preparation step code (boot code) 101 for reading an operating system.

The next 64 bytes of the MBR contain partition entries (partition information) 102, 103, 104, and 105, so that the BIOS can find partitions of the active area by using them. In the last two-byte area, a signature word (0x55AA) 106 for confirming that the MBR is properly selected is recorded.

As shown in FIG. 5, since a 16 byte area is required to specify one partition, the partition is divided into four (64/16), and if divided into five or more partitions, the subpartition is divided from the main partition. The partition can be expanded. That is, the primary partition or subpartition is recorded as four partitions in one sector, and the subpartition has a structure in which the location of the subpartition is specified in one partition.

6 is a block diagram showing a file configuration related to booting on a hard disk used in an embodiment of the present invention.

A delimiter of files related to booting on the hard disk is described in the root directory 600 and the actual file data is stored in the file area 700.

As described in the data structure table of the MBR, the file area is divided into four partitions (e.g., root directories of "c:", "d:", "e:", and "f:") 701, 702, and 703. 704, a first partition 701 is designated as an active region by the file entries 102, 103, 104, and 105.

According to the present invention, if the same boot-related files are stored in both the first partition 701 and the second partition 702, and booting through the first partition 701 which is the first active area fails, the second partition ( 702) Attempt to boot by accessing the region.

Files such as NK.bin, NK_F.bin, Assets.CAB, and Boot.dat are stored in the first partition 701 and the second partition 702, and a software module for the PVR function in the third partition 703. And content information is recorded.

In addition, the fourth partition 704 records logging data, eletric program guide (EPG) information, and user information related to broadcasting.

As described above, the BIOS to identify the location of the boot loader and boot program using the information stored in the PBR (300), FAT1 (400), FAT2 (500) and the root directory (600) (S110), The boot loader is called "bldr", the boot program is called "NK.bin", and the initial boot program is called "NK_F.bin".

Referring to the above files, first, bldr is a boot loader used in Windows CE, and second, NK.bin is a boot program used in Windows CE.

Third, the NK_F.bin is an initial booting program (reset mode) used in the production of the product. Fourth, the Boot.dat includes boot failure times, boot success times, and path information of the NK.bin and NK_F.bin. The boot information file is recorded. Fifth, the Assets.CAB is a D / B file including information on an image, a font, etc. constituting a window screen including a boot screen.

Subsequently, when the position is confirmed, the bldr is executed, and the bldr opens the Boot.dat (hereinafter referred to as “first Boot.dat”) of the first partition 701 to check the number of boot failures (S115). .

At this time, if the number of boot failures of the first Boot.dat is "0" (S120), the bldr determines that the data area of the first partition 701 is safe, and the first partition according to the path information of the first Boot.dat. NK.bin (hereinafter referred to as "first NK.bin") of 701 is loaded and executed (S125). The executed first NK.bin proceeds with the booting process until Windows CE is loaded and executed (S130).

On the other hand, if the number of boot failures of the first Boot.dat is greater than or equal to a predetermined value (S120), bldr determines that the first NK.bin is not normal, and the Boot.dat (hereinafter, " 2 Boot.dat ") to check the number of boot failures (S135).

If it is determined that the number of times of boot failure of the second Boot.dat is "0" (S140), bldr indicates NK.bin of the second partition (hereinafter, "second NK.bin") according to the path information of the second Boot.dat. The second NK.bin proceeds with the booting process (S145).

At this time, bldr recovers the damaged first NK.bin by copying the second NK.bin and writing it to the first partition 701, and transfers the path information described in the first Boot.dat to the second partition 702 area. Change it. In addition, bldr initializes the boot failure count described in the first Boot.dat to "0" (S150).

On the other hand, if the number of boot failures of the second Boot.dat is equal to or greater than a predetermined value (S140), bldr determines that the data area of the second partition 702 is not secure and does not load the second NK.bin.

In this case, when the booting process is not performed on the operating system installed by the user or when an error occurs in the operation of the PVR or when initializing the hard disk (YES in S140), bldr reboots through the NK_F.bin. The booting method in the reset mode will now be described.

The booting method through NK_F.bin uses the data areas of the first partition 701 and the second partition 702 as the booting method through NK.bin described above.

For the first time, the BIOS enters the reset mode by selecting a particular local key on the front panel provided to the user or by being prompted to press a designated remote key.

As described above, if bldr is searched and executed after the boot sector of the hard disk is registered in the memory (S155), the bldr opens the first Boot.dat and records NK_F.bin (hereinafter, referred to as the first partition 701). In step S160, the boot failure count of " first NK_F.bin "

If the number of boot failures of the first NK_F.bin is "0" (S165), the bldr determines that the data area of the first partition 701 is safe, and according to the path information of the first Boot.dat, the first NK_F.bin. The bin is loaded and executed (S170).

The executed first NK_F.bin proceeds with the booting process until the operating system of the reset mode is loaded and executed (S130).

On the other hand, if the number of boot failures described in the first Boot.dat is greater than or equal to a predetermined value, bldr determines that the first NK_F.bin is not normal and opens the second Boot.dat to check the number of boot failures (S175).

If it is determined that the number of boot failures of the second Boot.dat is "0" (S180), bldr indicates NK_F.bin of the second partition 702 (hereinafter referred to as "second NK_F") according to the path information of the second Boot.dat. .bin ") (S185), and the second NK_F.bin proceeds with the booting process (S130).

Subsequently, the bldr recovers the damaged first NK_F.bin by copying the second NK_F.bin to the first partition 701 and restores the path information described in the first Boot.dat to the second partition 702 area. Change it. In addition, the bldr initializes the boot failure count of the first NK_F.bin described in the first Boot.dat to "0" (S190).

On the other hand, if the number of boot failures of the second NK_F.bin is equal to or greater than a predetermined value, bldr determines that the second NK_F.bin is also abnormal data, and the booting process finally fails.

If the boot fails through the first NK.bin, the second NK.bin, the first NK_F.bin, and the second NK_F.bin, the boot recovery is impossible and bldr cannot find any more boot programs. The impossible message is displayed to allow the user to take another action (S195).

However, according to the present invention, since the first NK.bin, the second NK.bin, the first NK_F.bin, and the second NK_F.bin are sequentially applied to attempt to boot, the probability of boot failure may be greatly reduced. Will be.

The present invention has been described above with reference to the preferred embodiments, which are merely examples and are not intended to limit the present invention, and those skilled in the art to which the present invention pertains do not depart from the essential characteristics of the present invention. It will be appreciated that various modifications and applications are not possible that are not illustrated above. For example, each component specifically shown in the embodiment of the present invention can be modified. And differences relating to such modifications and applications will have to be construed as being included in the scope of the invention defined in the appended claims.

According to the present invention, when the operating system is booted using a hard disk other than a flash memory or a boot-only ROM, a situation in which initial booting is not performed due to a hard disk error can be prevented.

In addition, according to the booting method of the operating system on the hard disk according to the present invention, it is possible to implement a digital processing system that is stably operated by managing a boot program for each partition and activating each partition sequentially according to a boot failure.

In addition, according to the present invention, not only the booting program of the operating system installed by the user, but also the initial booting program used in the production of the product is managed by partitions, so that if an error occurs in the hard disk, a repair can be easily performed without requesting a specialized company. Can improve the reliability of the product.

Claims (8)

Searching for and executing a boot loader after the boot sector of the hard disk is registered in the memory; Loading a boot program of the first partition according to path information when the boot failure count of the first hard disk partition is determined by the boot loader and the boot failure count is less than or equal to a predetermined number of times; If the number of boot failures of the first partition is greater than or equal to a predetermined number of times, the boot failure number of the second partition is confirmed by the boot loader. If the number of boot failures of the second partition is less than or equal to a predetermined number of times, the boot program of the second partition is less than or equal to a predetermined number of times. Is loaded; And If the boot failure count of the second partition is equal to or more than a predetermined number of times, an interface is provided by a BIOS on a memory to select to enter the reset mode, and a user area located on another partition of the hard disk is initialized, and an initial product used in production Operating system booting method on a hard disk, characterized in that the booting program is provided with a step of loading. The method of claim 1, And a booting program of the second partition is copied to the first partition so that the booting program of the first partition is restored. delete delete delete delete A master boot record (MBR) module for managing a data structure table including partition entry information; A partition boot record (PBR) module configured to find a partition designated as an active area by using the partition entry information, to find and execute a boot loader with data structure information stored in the partition; A module for loading a boot program of the first partition if the boot failure number of the first hard disk partition is checked by the boot loader and the boot failure number is less than or equal to a predetermined number of times; And If the number of boot failures of the first partition is greater than or equal to a predetermined number of times, the boot failure number of the second partition is confirmed by the boot loader. If the number of boot failures of the second partition is less than or equal to a predetermined number of times, the boot program of the second partition is less than or equal to a predetermined number of times. A computer-readable recording medium having recorded thereon a program for operating a module for loading a computer. The method of claim 7, wherein If the boot failure count of the second partition is more than a predetermined number of times, an interface is provided to receive an input of whether to execute an initial booting program. A module for loading the initial booting program of the first partition when the number of booting failures of the initial booting program used in the production of the product recorded on the first partition of the hard disk by the boot loader is less than or equal to a predetermined number of times; ; And If the number of boot failures of the first partition is equal to or greater than a predetermined number of times, the number of boot failures of the initial booting program on the second partition is confirmed. A recording medium further recording a program for functioning the module to be loaded.

Images