`
`UIllted States Patent [19]
`Oka
`
`llllllll|||l|||||llllllllllllllllllll|I|||||||I|||||lllllllllllllllllllllll
`
`(1)5274316A
`[11] Patent Number:
`[45] Date of Patent:
`
`5,274,816
`Dec. 28, 1993
`
`[54] PERSONAL COMPUTER CAPABLE OF
`CHANGING BOOT "loam
`
`[56]
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`~ [75] Inventor: M‘yulm- oka’ Tokyo, Japan
`
`5,l28,99$ 7/]992 Arnold ........................ .. 364/DIG.>I
`
`_
`_
`_
`[73] Assignee: ihbushiki Kmsha Toshiba, Kawasaki,
`“Pan
`[21] APPL No; 736,795
`
`[22] Filed:
`
`Nov. 1, 1991
`
`_
`,
`,
`"m8" "Wad" mm" D'“
`[30]
`Nov. 2, 1990 [JP]
`Japan ................................ .. 2-295365
`Nov. 30, 1990 [JP]
`Japan ................................ .. 2-340406
`_
`[51] Int. Cl.5 ............................................ .. G06F 9/445
`[52] U5. Cl. ........................... .. 395/700; 364/DIG. 1;
`364/2802
`[58] Field of Search ....................... .. 364/200; 395/700
`
`FOREIGN PATENT DOCUMENTS
`0364115 9/1989 Europe“ PM’ on _
`wow/06554 6/1990 PCT lnt‘l App]. .
`Primary Examiner-Thomas M. Heckler
`Attorney. Agent, or Firm-Cushman, Darby & Cushman
`[57]
`ABSTRACT
`A boot process is performed from one of a ?oppy disk
`drive, a detachable hard disk drive, and a DOS-ROM.
`The boot priority is changed in accordance with the
`connection state of the detachable hard disk drive. The
`boot priority can be changed quickly by depressing a
`function key from a normal boot mode to an HDD boot
`mode or vice versa.
`
`9 Claims, 9 Drawing Sheets
`
`'0 51
`H ;
`s
`C P U
`Q HDD
`I /F
`
`|
`
`l2
`
`208
`
`r_.-- - _ _ - _ _ -_-h
`
`20
`A 120
`l
`:
`
`__________ 'n'
`
`= ,
`
`13
`5
`
`vex
`
`L FDD A 32
`
`H F D 1:
`
`12°F .
`
`33
`
`FOB B I
`
`---
`
`34
`
`,4
`-- em —-E__PD~_T_E'1_ '
`S
`[ DMAT]----—-l UART
`15
`|:_4_|’_
`P l C
`24
`___\
`
`11s
`
`D1 5 P -
`
`23
`1110.11.82 e
`KEYBOARD “'36 35
`l x
`360
`3?
`
`1. c D
`
`11
`
`-—-" VRAM
`
`-- DOS-ROM
`
`L
`
`"8K
`“- 26
`
`2 C
`9 ,9
`g u
`<
`§§~
`
`ILI
`
`40
`
`1s
`’
`VBK
`EXTENDED
`>— RAM
`
`‘
`
`-I PS-IF ‘~28
`
`"9
`30s
`"'
`VBK
`>__ BACKUP __
`1
`l" "I
`M ' @ “‘
`AC
`:- VBK
`Ac)‘- ADAPTER *’>‘ POWER
`I.’
`l
`29
`3'A “El S-BATT 31s
`
`1
`
`AMI/MSI/GBT EX 1004
`IPR of Pat. No. 6,282,641
`
`
`
`U.S. Patent
`
`Dec. 23, 1993
`
`Sheet 1 of 9
`
`5,274,816
`
`FDD B
`«- ———— -—-§3—-
`l_.__...P_E!r:'_T_E.R J
`'fi%é%$&EE
`23
`-‘_"1°_U_5§_’.,._J
`KEYBOARD
`36
`3‘5
`
`'’‘‘r ““ "*
`
`I I
`
`2'
`
`22
`
`VB
`
`K
`
`14
`DMAC
`g5
`
`PRT -
`CONT
`UART
`
`CONT
`
`DOS-ROM
`
`VB“
`
`RTC
`
`25
`
`as
`V3” EXTENDED
`
`V3“
`
`:9
`BACKUP
`
`RAM
`
`3
`
`Ac
`
`Ac
`ADAPTER
`
`29
`
`30
`
`‘VBK
`
`555
`at:
`3 %
`
`
`
`F'|
`
`(1
`
`1
`
`2
`
`
`
`US. Patent
`
`Dec. 28, 1993
`
`Sheet 2 of 9
`
`5,274,816
`
`@
`
`4|
`=
`5
`w
`SET VECTOR ADDRESS OF INT I3H TO START
`ADDRESS OF FDD FUNCTION PROCESS AS
`DEFAULT VALUE
`
`T
`
`.
`IS HARD DISK PQCK ATTACHED
`Yes
`1
`SET VECTOR ADDRESS OF m {3H TO
`START ADDRESS OF HDD FUNCTION
`PROCESS
`
`43
`
`"0 '
`
`545
`
`INT 19H BOOT PROCESS
`
`547
`
`{- _____?|
`I
`|
`531-1-
`g
`"DD
`
`V
`
`5?
`HDIN mg
`E 2
`:8
`ID n:
`
`55
`
`‘20
`
`I 59
`
`3
`
`
`
`US. Patent
`
`Dec. 23, 199;
`
`Sheet 3 of 9
`
`5,274,816
`
`6‘ BOOT FROM HDD'
`"° 0
`
`63
`.‘
`(NT (3H I
`READ BOOT RECORD OF FDD (DRIVE A)
`
`BOOT FROM FDMA)
`
`67
`,‘
`INT (3H I
`READ BOOT RECORD OF FDD (DRIVE 8)
`
`BOOT FROM FDIHB)
`
`INT (3H1
`READ BOOT RECORD OF DOS-ROM
`(DRIVE D; DEVICE NO. NH]
`
`77
`1
`’
`INT (3H1
`READ BOOT RECORD or DOS-ROM
`(DRIVE 0; DEVICE NO. aom
`
`75
`
`READ SUCCESSFUL
`BOOT FROM
`DOS-ROM (DRIVE D;
`DEVICE no. em) “0
`
`(ERROR PROCESS )
`
`79
`IS
`READ SUCCESSFUL
`BOOT FROM
`"0
`nos -ROM
`(DRIVE c;
`DEVICE NO. 80H)
`
`(6.
`
`4A
`
`4
`
`
`
`US. Patent
`
`Dec.28,1993
`
`Sheet 4 of9
`
`_
`
`5,274,816
`
`INT (3H1
`READ BOOT RECORD OF HDD
`(DRIVE C ; DEVICE NO. BOHI
`
`94
`5
`
`INT (3H1
`READ BOOT RECORD OF DOS-RM
`(DRIVE C; DEVICE NO. BOHI
`
`B5
`
`IS
`READ SUC’CESSFUL
`BOOT FROM
`HDD (DRIVE 0;
`DEVICE NOMHI
`
`"0
`
`~\
`INT (3H1
`READ BOOT RECORD OF DOS_
`8?
`ROM (DRIVE DZDEVICE NOBIHI
`
`IS
`READ SUC’CESSFUL
`YES
`
`ERROR
`PROCESS
`
`BOOT FROM DOS-ROM
`.
`(DRIVE C, DEVICE NOBOHI
`
`B9
`
`I S
`READ SU'CCESSFUL
`
`"0 ERROR PROCESS
`
`BOOT FROM DOS-ROM
`(DRIVE DIDEVICE NOBIHI
`
`FIG. 4B
`
`5
`
`
`
`U-S. Patent
`
`Dec. 28, 1993
`
`Sheet 5 of 9
`
`@o FUNCTION PROCESS)
`101
`
`IS DEVICE
`NUNIBER OOH OR MORE
`?
`
`DEVICE NUMBER BI H
`7
`
`TO FDD FUNCTION
`PROCESS
`
`DOS‘ROM FUNCTION)
`PROCESS
`
`(SUCCEEDING HOD
`FUNCTION PROCESS
`
`FIG. 5
`
`Q00 FUNCTION PROCESS)
`I05
`
`DEVICE NU'I’ABER 80H
`
`DOS-ROM FUNCTION)
`PROCESS
`
`I
`SUCCEEDING FDD
`FUNCTION PROCESS
`
`FIG. 6
`
`6
`
`
`
`US. Patent
`
`Dec. 28, 1993
`
`Sheet 6 of 9
`
`5,274,816
`
`g 85228.; H 8:
`
`T5 Em 556w
`2: g u we: 8 5??
`
`3.2% “ 5.5:: 88
`
`
`
`
`
`S25 32% N 22523 £53m
`
`8:82 5% 58 55 58 mwmm 5a .68
`
`~ :8 g n E: 88.2 828.285
`
`E 3522 H 225M528 55;:
`
`
`
`
`to H 35%: E32,. 522:
`
`
`
`to u 515% 553
`
`
`
`u “3&2 E2 52m: 2222:.
`
`
`
`
`
`ea; 95:. 9.3” 9.8” g 952 2%. 96
`
`
`
`
`
`
`
`m: 55m wwuEB 22 Q. @818 E3 $2 :52 E; 5: 53%
`
`u Hz 2% 22:
`
`m 2. gm $55 8 :2; =2 8
`
`7
`
`
`
`US. Patent
`
`Dec. 2a, 1993
`
`Sheet 1 of 9
`
`5,274,816
`
`IRT
`
`INITIALIZE AND TEST _/ I01
`REGISTERS AND DEVICES
`
`103
`
`IS
`F1 KEY ogmesszo
`
`“0
`
`YES
`
`105
`1
`
`FLAG -— I
`
`'
`FLAG __ o
`
`107
`I
`
`EXECUTE INT 19H
`
`~-\
`
`1
`
`EXECUTION 0F
`"5- D08
`
`8
`
`
`
`US. Patent
`
`Dec. 28, 1993
`
`Sheet 8 of 9
`
`5,274,816
`
`INT i3H I
`
`INT {3H I
`READ BOOT RECORD OF FDD (DRIVE 8)
`
`7/‘!
`INT |3HI
`7
`INT 13H:
`’
`READ BOOT RECORD or DOS-ROM READ BOOT RECORD OF DOS-ROM
`(DRIVE 0; DEVICE n0. am)
`(DRIVE c; DEVICE no. son)
`
`IS
`READ sugcsssruL
`
`75
`
`79
`IS
`new sq’ccEssFuL
`
`'
`BOOT mom
`DOS-ROM(DRIVE 0) N0
`
`'
`7N0
`
`TO ERROR PROCESS
`FIG. 9A
`
`BOOT mom
`DOS-ROM
`(DRIVE Cl
`
`9
`
`
`
`US. Patent
`
`Dec. 2a, 1993
`
`Sheet 9 of 9
`
`5,274,816
`
`83
`{
`INT ISHI
`READ BOOT RECORD OF HDD
`(DRIVE C; DEVICE NO. 80H)
`
`9I
`I
`INT I3HI
`READ BOOT RECORD OF DOS-ROM
`IDRIVE CLDEVICE NO. OOH)
`
`BOOT
`FROM HOD
`IDRIVE c1
`
`8-,
`1
`’
`m 13H;
`READ BOOT RECORD OF 00s-
`ROM I DRIVE D'- DEVICE NOBIHI
`
`93
`
`IS
`READ SUCCESSFUL
`ERROR
`PROCESS
`
`YES
`
`BOOT FROM DOS-ROM
`‘DRIVE CI
`
`"o ERROR PROCESS
`
`B9
`
`IS
`READ SUC’CESSFUL
`
`YES
`
`BOOT FROM DOS- ROM
`IDRIVE DI
`
`10
`
`
`
`1
`
`PERSONAL COMPUTER CAPABLE OF
`CHANGING BOOT PRIORITY
`
`5,274,816
`
`15
`
`20
`
`2
`According to a second aspect of the present inven
`tion, a method for performing the boot process in a
`personal computer having a plurality of bootstrap de
`vices, each of them having a different boot priority and
`one of them being a detachable type, comprises the
`computer steps of: at) detecting the connection of the
`detachable bootstrap device; and b) changing the boot
`priority of the bootstrap devices in response to the de
`tection of the detachable bootstrap device.
`According to the present invention, when the system
`is powered, the CPU refers the ?ag during the execu
`tion of the IRT routine to recognize the connection
`state of the detachable hard disk pack. Different boot
`priorities are prefixed depending on the presence or
`absence of the hard disk pack. The bootstrap devices
`(namely, a ?oppy disk drive, a hard disk drive, and a
`DOS-ROM) are set up in accordance with the boot
`priorities corresponding to the connection state of the
`hard disk pack. ,
`Additional objects and advantages of the invention
`will be set forth in the description which follows, and in
`part will be obvious from the description, or may be
`learned by practice of the invention. The objects and
`advantages of the invention may be realized and ob
`tained by means of the instrumentalities and combina
`tions particularly pointed out in the appended claims.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`The accompanying drawings, which are incorpo
`rated in and constitute a part of the speci?cation, illus
`trate presently preferred embodiments of the invention,
`and together with the general description given above
`and the detailed description of the preferred embodi
`ments given below, serve to explain the principles of the
`invention.
`FIG. 1 is a system block diagram of a personal com
`puter to which the boot priority changing apparatus of
`the present invention is applied;
`FIG. 2 is a ?owchart showing an IRT routine to be
`executed by the personal computer shown in FIG. 1;
`FIG. 3 is a block diagram showing an arrangement
`for detecting the hard disk pack;
`FIGS. 4A and 4B show a ?owchart of a bootstrap
`process routine;
`FIG. 5 is a ?owchart of an I'IDD function process;
`FIG. 6 is a ?owchart of an FDD function process;
`FIG. 7 shows an example of a screen menu of a sys
`tem setup;
`FIG. 8 is a ?owchart showing an IRT routine of a
`second embodiment according to the present invention;
`and
`FIGS. 9A and 9B show a ?owchart of a bootstrap
`process routine in the second embodiment according to
`the present invention.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`FIG. I is a system block diagram of a personal com
`puter to which the boot priority changing apparatus of
`the present invention is applied.
`As shown in FIG. 1, the computer comprises a sys
`tem bus 10 and components 51 and 11 to 28 which are
`connected to the bus 10. These components include: a
`main CPU (Central Processing Unit) 11, a basic input
`and output read only memory (BIOS-ROM) 12. a RAM
`(Random Access Memory) 13 serving as a main mem
`ory, a DMAC (Direct Memory Access Controller) 14,
`a PIC (Programmable Interrupt Controller) 15, a PIT
`
`BACKGROUND OF THE INVENTION
`Field of the Invention
`The present invention relates to a personal computer
`having a plurality of bootstrap devices including a hard
`disk drive detachable to the personal computer.
`Description of the Related Art
`Compact, light-weight and low-cost‘personal com
`puters have been developed. Such a personal computer
`is equipped with minimum functions and any other
`functions which are optionally provided. Some per
`sonal computers have a single ?oppy disk drive, others
`have dual ?oppy disk drives, and other having a single
`?oppy disk drive and a hard disk drive. In order to set
`up a system, a boot process is performed. More speci?
`cally, a CPU ?rst reads the boot record of the ?oppy
`disk drive (FDD). If the CPU cannot read the boot
`record of the FDD, then it reads the boot record of
`another FDD, if present, or the boot record of the hard
`disk drive (I-IDD) if the second FDD is not present. If
`the CPU can read the boot record of the FDD or the
`HDD, then it loads an operating system program stored
`in FDD or HDD. Thus, the system is set up.
`As described above, in the prior art, the boot priority
`is preliminarily ?xed.
`Recently, a type of personal computer having a de
`tachable hard disk pack has been developed in order to
`further improve the portability. This type of personal
`computer is provided with a disk operating system
`(DOS) read only memory (ROM) (hereinafter referred
`to as DOS-ROM). The DOS»ROM has a similar format
`as the hard disk drive and stores a DOS file. More spe
`ci?cally, if the hard disk drive is not attached to the
`computer's main body, the DOS-ROM serves as the
`hard disk drive. The device number “80H” is assigned
`to the HDD and the device number “?ll-I" may be
`assigned to the DOS-ROM in accordance with the
`speci?cation of the industry standard interface.
`However, if the device number “80H“ is designated
`while the HDD is not attached and a device having the
`device number “?ll-I" is present, the boot process can
`not be performed due to the constraint of the industry
`standard DOS.
`
`25
`
`35
`
`45
`
`SUMMARY OF THE INVENTION
`An object of the present invention is to provide a
`personal computer having a plurality of bootstrap de
`vices and which can execute the boot process in accor
`dance with the boot priority preliminarily de?ned de
`pending on the connection state of the bootstrap device.
`Another object of the present invention is to provide
`a personal computer capable of quickly changing the
`boot priorities.
`According to a ?rst aspect of the present invention, a
`personal computer comprises: a plurality of bootstrap
`devices, and at least one of the bootstrap devices being
`detachable to the personal computer, means for detect
`ing the connection state of the detachable bootstrap
`device; means for preliminarily de?ning the boot prior
`ity order in response to the detection of the connection
`state of the detachable bootstrap device; and means for
`setting up the bootstrap devices in the order of the boot
`priorities.
`
`50
`
`55
`
`65
`
`11
`
`
`
`25
`
`5,274,816
`3
`(Programmable Interval Timer) 16, and a RTC (Real
`Time Clock) 17.
`The main CPU 11 controls the entirety of the system
`and executes the various routines represented by the
`?owcharts shown in FIGS. 2, 4A and 4B, 5, 6, 7, 8, 9A
`and 9B. The main CPU 11 serves as a host CPU to the
`power control CPU 306 incorporated in the power-sup
`ply circuit 30 to be described later.
`The ROM 12 stores a basic input and output program
`(BIOS). The BIOS includes the program shown in
`FIGS. 4A and 4B, 5, 6, 8, 9A and 9B. The main CPU 11
`executes the BIOS when the power switch of the com
`puter is turned on to read the setup data stored in a
`speci?c area of the RAM 13 (or register) to determine
`the system environment, to further read a boot from a
`hard disk drive (HDD) 20A, and to load a Disk Operat
`ing System (DOS) program stored in the HDD 20A
`into the RAM 13. The RAM 13 stores the DOS pro
`gram, application programs, and various data. Backup
`power VBK is supplied to the RAM 13 from the power
`supply circuit 30. Hence, the data stored in the RAM 13
`does not vanish even if the power switch of the com
`puter is turned off.
`The DMAC 14 performs a direct memory access
`control. The PIC 15 can be set by a program. The PIT
`16 can be set by a program and supplies an interrupt
`signal to the main CPU 11 under control of the PIC 15
`when its count reaches a value set by a program. In
`response to the interrupt signal, the main CPU 11 exe
`cutes a vector interrupt processing routine. The RTC
`17 is a timer module which has a dedicated built-in
`battery (not shown) and measures time; its output repre
`sents the present time.
`As is shown in FIG. 1, the personal computer further
`comprises an extended RAM 18, a backup RAM 19, a
`hard disk pack 20, a ?oppy disk controller (FDC) 20F,
`a printer controller (PRT-CONT) 21, an I/O interface
`22, a keyboard controller 23, a display controller 24, a
`video RAM 25, a DOS-ROM 26, and a power-supply
`interface 28. These components are all connected to the
`system bus 10.
`The extended RAM 18 is a large-capacity memory
`removably inserted in the card slot formed in one side of
`the main body of the personal computer, and the backup
`power VBK is supplied to the extended RAM 18. The
`45
`backup RAM 19 is also supplied with the backup power
`VBK and keeps storing the data required to perform a
`resume function. The hard disk pack 20 is removably set
`in a dedicated housing made in one side of the main
`body of the computer, and consists of, for example, a
`2.5-inch hard disk drive (HDD) 20A and a hard disk
`controller (HDC) 20B. The ?oppy disk controller
`(FDC) 20F controls an external 3.5-inch ?oppy disk
`drive 32 and a 5-inch external ?oppy disk drive 33. The
`printer controller 21 is connected to a printer 34, the
`printer being externally connected to the computer.
`The 1/0 interface 22 is a universal asynchronous recei
`ver/transmitter (UART). If necessary, RS-232C inter
`face units are connected to the I/O interface 22. The
`keyboard controller (KBC) 23 controls the keyboard
`60
`36. The keyboard 36 is provided with alphanumeric
`keys and function keys including an F1 key 360. The
`display controller (DlSP-CONT) 24 controls a liquid
`crystal display (LCD) 37. The video RAM (V RAM) 25
`is supplied with the backup power VBK and stores the
`video data. The DOS-ROM 26 has a similar format as
`the hard disk pack 20 and stores a disk operating system
`(DOS) program. The power-supply control interface
`
`4
`(PS-IF) 28 connects the power-supply circuit 30 to the
`main CPU 11 through the system bus 10.
`When necessary, an AC adapter 29 is plugged into
`the main body of the personal computer. It transforms
`the commercially available AC power into a DC power
`of a predetermined voltage. An expansion connector 40
`is connected at one end to the system bus 10. An expan
`sion unit is selectively connected to the other end of the
`connector 40. The power-supply circuit 30 (an intelli
`gent power supply) has a power control CPU (PC
`CPU) 306. A main battery 31A, which is a chargeable
`battery pack, is removably mounted on the main body
`of the personal computer. A sub-battery 318, which is
`also chargeable, is incorporated into the main body of
`the computer.
`FIG. 2 is a ?owchart showing an IRT (Initialize and
`Reliability Test) routine which is stored in the BIOS
`ROM and executed when the system is powered.
`In step 41, the CPU 11 sets the vector address of INT
`131-! to the start address of the FDD ?oppy disk drive
`function process, shown in FIG. 6, as a default value.
`In step 43, the CPU 11 determines whether or not the
`hard disk pack 20 is connected. This determination is
`made by referring to a status register 59, which is shown
`in FIG 3. More speci?cally, as shown in FIG. 3, when
`the hard disk pack 20 is attached to the system main
`body, the lock mechanism 50 is operated to lock the
`hard disk pack 20 into the system main body. The
`switch 53 is actuated in cooperation with the operation
`of the lock mechanism 50. When the hard disk pack 20
`is detached from the system main body, the lock mecha
`nism $0 is released. Accordingly, the switch 53 is turned
`off in cooperation with the release operation. One ter
`minal of switch 53 is connected to the ground and the
`other terminal thereof is connected to a speci?ed pin of
`the connector 55. The speci?ed pin of the connector 55
`is connected to Vcc through a pull-up resistor 57. As a
`result, when the hard disk pack 20 is not connected to
`the system main body, the high level (logic “l”) I-IDIN
`signal is output. When the hard disk pack 20 is attached
`to the system, a low level (logic “0“) HDIN signal is
`output. The l-IDIN signal is stored in the status register
`59.
`As per the determination of step 43, if the hard disk
`pack 20 is attached to the computer main body, the
`CPU 11 sets the vector address of INT 13H to a start
`address of the hard disk drive (HDD) function process
`shown in FIG. 5. Thereafter, the CPU 11 executes a
`process INT 19H (boot process). Note that both INT
`13H and INT 191-! are a system call and a function
`request for calling a function of DOS.
`FIGS. 4A and 4B show a ?owchart of the boot pro
`cess INT 19H. Suppose ?rst that the hard disk pack 20
`is connected and thus the vector address of INT 13H is
`directed toward the HDD function process. The CPU
`11 determines in step 61 whether or not the boot process
`is a normal boot or an HDD boot. The user will have
`preliminarily selected either a normal boot or an I-IDD
`boot by using the system setup as shown in FIG. 7, and
`the setup data will have been stored in the backup RAM
`19. The CPU 11 refers to the backup RAM and deter
`mines whether the normal boot or the HDD boot has
`been selected. If the detennination in step 61 is the
`normal boot, the CPU 11 sets the device number "00"
`designating the ?oppy disk drive A in a speci?ed regis
`ter (DI. register) and calls INT 13H. In this case, since
`we are assuming that the hard disk pack 20 is connected,
`the vector address of INT 131-] has been set to the HDD
`
`40
`
`50
`
`65
`
`12
`
`
`
`20
`
`25
`
`5
`
`5,274,816
`5
`.
`6
`function process in FIG. 5. Therefore, the CPU 11 skips
`the succeeding DOS-ROM function process. Accord
`to and executes the HDD function process. The CPU
`ingly, the CPU 11 reads in step 87 the boot record from
`11 determines in step 101 whether or not the device
`the DOS-ROM 26. If it is determined in step 89 that the
`number is “801-!” or not. Since in this case the device
`read operation of the step 87 is successful, the CPU 11
`number has been set to "00” because we have assumed
`executes the boot process from the DOS-ROM 26. If
`that the user selected a normal boot, the CPU 11 skips
`the read operation is not successful in step 89, the CPU
`to and executes the FDD function process shown in
`11 executes the error process.
`The previous discussion assumed that the hand disk
`_ FIG. 6. The CPU 11 further determines in step 105 that
`the device number is not “80H” and it executes the
`pack 20 was connected. A case wherein the hard disk
`succeeding FDD function process. Thus, the CPU 11
`pack 20 is not connected will now be described. In this
`reads, in the step 63, the boot record of floppy disk
`case, the vector address of INT 13H is directed toward
`drive A (FDD A). (The boot record is stored in cylin
`the FDD function process. Assume ?rst that the user
`der 0, head 0, sector 1.) The CPU 11 then determines in
`has selected the normal boot. Since the steps 63 to 69
`step 65 whether or not the boot record can be read out.
`will proceed in a similar fashion as in case wherein the
`If the boot record can be read out, the CPU 11 executes
`hard disk pack 20 is connected (described above), the
`the boot process from the FDD A. More speci?cally,
`description thereof will be omitted. Skipping to step 71,
`the CPU 11 loads the operating system program (OS)
`the CPU 11 determines that the hard disk pack 20 is not
`from the ?oppy disk drive A.
`connected. Then, the CPU 11 sets in the DL register
`If the CPU 11 cannot read the boot record from the
`"SOI'P’ and calls INT 13H. As a result, the CPU 11
`FDD A, it reads, in step 67, the boot record of FDD B.
`executes step 105 in FIG. 6. Since the determination of
`The CPU 11 sets the device number “01" designating
`step 105 is affirmative, the CPU 11 executes the DOS
`the ?oppy disk drive B in the DL register and calls INT
`ROM function process. Accordingly, the CPU 11 reads
`13H. Similar to the case of ?oppy disk drive A, the CPU
`the boot record from the DOS-ROM 26. If the read
`11 executes the succeeding FDD function process pass
`operation of the boot record is successful, the CPU 11
`ing through the steps 10] and 105. If the boot record
`executes the boot process from the DOS-ROM 26.
`can be read out from FDD B, the CPU 11 executes the
`On the other hand, if the HDD boot was selected and
`boot process from the FDD B.
`is determined in step 61, the CPU 11 determines in step
`If the boot record can be read out neither from the
`81 whether or not the hard disk pack 20 is connected.
`FDD A nor from the FDD B, the CPU 11 determines
`Since in this case we are assuming that the hard disk
`in step 71 whether the hard disk pack 20 is connected.
`pack 20 is not connected, the CPU 11 sets in the DL
`This determination is required in order to change the
`register “SUI-I" and calls INT 13H. Then, the CPU 11
`device number of the DOS-ROM 26. Continuing with
`executes the FDD function process in FIG. 6. The CPU
`our assumption that the hard disk pack 20 is connected,
`11 determines in step 105 that the device number is
`the device number of the DOS-ROM 26 should be
`"80H" and therefore executes the DOS-ROM function
`"81H“ since the device number “80H” is assigned to the
`35
`process. Accordingly, the CPU 11 reads the boot re
`hard disk pack 20. Thus the CPU 11 sets in the DL
`cord from the DOS-ROM 26. If the read operation of
`register "81H" and calls INT 13H, to execute the HDD
`the boot record is successful, the CPU 11 executes the
`function process shown in FIG. 5. Since the content of
`boot process from the DOS-ROM 26.
`the DL register is “Ell-l", the determination of steps 101
`A second embodiment of the present invention will
`and 103 are affirmative. Therefore, the CPU 11 executes
`now be described with reference to FIGS. 8, 9A and
`the DOS-ROM function process. Accordingly, the
`9B.
`CPU 11 reads in step 73 the boot record of the DOS
`In the first embodiment, the boot priority is changed
`ROM 26 and detennines in step 75 whether or not the
`by designating the normal boot or the HDD boot on the
`boot record could be read out. If the boot record was
`system setup screen shown in FIG. 7. In the second
`read out, the CPU 11 loads the OS from the DOS-ROM
`embodiment, the boot priority can be quickly changed.
`45
`26 into the main memory 13. If the boot record could
`Therefore, a DOS command must be input in order to
`not be read out, the CPU 11 executes an error process.
`display the screen shown in FIG. 7, and the system must
`On the other hand, if the HDD boot was selected,
`be rebooted in order to change the boot mode.
`then the CPU 11 determines in step 61 that an HDD
`FIG. 8 is a ?owchart of the IRT routine in the second
`boot should occur and in step 81 whether or not the
`embodiment. The keyboard 36 is provided with a func
`50
`hard disk pack 20 is connected to the computer. Since
`tion key (F 1) 36a for designating the change of the boot
`we have assumed that the hard disk pack 20 is con
`priority. The CPU 11 detects the depression of the F1
`nected, the CPU 11 executes step 83. In step 83, the
`key 360 in the IRT routine. More speci?cally, the CPU
`CPU 11 sets the DI. register to “80H” and calls INT
`11 initializes and tests registers and devices in step 101.
`13H. The CPU then executes the HDD function pro
`55
`Then, the CPU 11 determines in step 103 whether or
`cess in FIG. 5. Since the determination of step 101 is
`not the F1 key 360 is depressed. If the determination is
`affirmative, the CPU 11 determines in step 103 whether
`affirmative, the CPU 11 sets a flag, i.e., sets logic "I" in
`or not the device number is “81I-I". Since the device
`the status register 59. Alternatively, if the determination
`number is "80H" in this case, the CPU 11 executes the
`is negative in step 103, the CPU 11 sets logic “0" in the
`succeeding HDD function. Accordingly, the CPU 11
`speci?c register. Then, the CPU 11 executes the INT
`reads in step 83 the boot record from the hard disk pack
`19H in step 109.
`20. If the read operation is successful in step 85, the
`FIGS. 19A and 19B show a ?owchart of the INT
`CPU 11 executes the boot process from the hard disk
`19H process. The reference numerals as in FIGS. 4A
`pack.
`and 4B denote the same steps in FIGS. 9A and 9B, and
`If the read operation is not successful in step 85, the
`a detailed description of these steps will be omitted.
`65
`CPU 11 sets in the DL register “8ll-I" and calls INT
`The CPU 11 determines in step 62 whether or not the
`13H. In this case, the determinations of both steps 101
`flag (of the status register 59) is
`If the flag is “0", it
`and 103 are affirmative. Therefore, the CPU 11 executes
`means that the “FI" key 360 is not depressed. Accord
`
`40
`
`13
`
`
`
`O
`
`20
`
`5,274,816
`7
`ingly, the CPU 11 executes steps 63 to 79 which have
`of the function key, said accessing means accessing the
`been described with reference to FIG. 4A.
`bootstrap devices in accordance with the flag means.
`On the contrary, if it is determined in step 62 that the
`4. The computer according to claim 3 wherein the
`plurality of bootstrap devices comprises a ?oppy disk
`?ag is “1", it means that the boot priority is changed
`from the normal boot mode to the HDD boot mode.
`drive, a hard disk drive, and a DOS-ROM, and said
`accessing means accesses the floppy disk if the flag
`Therefore, the CPU 11 executes the steps 81 to 93
`shown in FIG. 98.
`means stores no depression of the function key, accesses
`the hard disk drive if the ?ag means stores the depres
`On the other hand, if the determination is the HDD
`sion of the function key and the hard disk drive is con
`boot in step 61, the CPU 11 determines in step 80
`nected, and accesses the DDS-ROM if the flag means
`whether or not the ?ag is “0". If it is determined that the
`stores the depression of the function key and the hard
`?ag is "I", it means that the boot mode is switched from
`disk drive is not connected.
`the HDD boot mode to the normal boot mode. Thus,
`5. A personal computer according to claim 2,
`the CPU 11 executes steps 63 to '79 shown in FIG. 9A.
`wherein the means for changing the boot priority
`On the contrary, if the determination in step 80 is af‘?r
`changes between a normal boot mode wherein a boot
`mative, the change of boot priority is not caused. There
`process is executed from one of the ?oppy disk drive
`fore, the CPU 11 executes the steps 81 to 93 shown in
`and the DOS-ROM and a hard disk drive boot mode
`FIG. 9B. Thus, in the second embodiment, when the
`wherein the boot process is executed from one of the
`system is powered while the F1 key 360 is being de
`hard disk drive and the DOS-ROM.
`pressed, the normal boot priority is changed to the
`6. A personal computer according to claim 1,
`HDD boot priority or vice versa.
`wherein the plurality of bootstrap devices include a
`Additional advantages and modi?cations will readily
`?oppy disk drive, a hard disk drive, and a disk operating
`occur to those skilled in the art. Therefore, the inven
`system memory.
`tion in its broader aspects is not limited to the speci?c
`7. A personal computer according to claim 1,
`details, representative devices, and illustrated examples
`wherein the detachable bootstrap device is a hard disk
`shown and described herein. Accordingly, various
`drive.
`modi?cations may be made without departing from the
`8. A method for performing the boot process in a
`spirit or scope of the general inventive concept as de
`personal computer having a plurality of bootstrap de
`?ned by the appended claims and their equivalents.
`vices, each of them having a different boot priority and
`What is claimed is:
`one of them being a detachable type, and at least one of
`l. A personal computer, comprising:
`the bootstrap devices having an operating system pro
`a system bus;
`gram, said method comprising the computer steps of:
`a plurality of bootstrap devices, coupled to the sys
`a) detecting the connection of the detachable boot
`tem bus, at least one of the bootstrap devices being
`strap device;
`detachable from the system bus and having an
`b) changing the boot priority of the bootstrap devices
`operating system program;
`in response to the detection of the detachable boot
`means, coupled to the system bus, for detecting the
`strap device; and
`connection state of the detachable bootstrap de
`c) accessing the bootstrap devices in the order of the
`vice; and
`changed boot priority in order to load the operat
`means, coupled to the system bus, for de?ning the
`ing system program.
`boot priority order in response to the detection of
`9. A method according to claim 8, wherein the per
`the connection state of the detachable bootstrap
`sonal computer has a normal boot mode wherein a boot
`device; and
`process is executed from one of a ?oppy disk drive and
`means for accessing the bootstrap devices in the order
`a DOS-ROM and a hard disk drive boot mode wherein
`of the boot priorities de?ned by said de?ning
`the boot process is executed from one of a hard disk
`means in order to load the operating system pro
`drive and the DOS-ROM, the method further com
`prises the steps of:
`gram.
`2. A personal computer according to claim 1, further
`a) detecting, during an execution of an initialize rou
`comprising means, coupled to the system bus, for
`tine after the personal computer is powered, an
`changing the boot priority upon the personal computer
`input signal indicating the change of the boot prior
`being powered.
`ity from an input device; and
`3. A personal computer according to claim 2,
`b) changing the normal mode to the hard disk drive
`wherein the means for changing the boot priority com
`mode or vice versa in response to the detection of
`the input signal.
`prises a function key for requesting the change of the
`boot priority and a ?ag means for storing the depression
`
`I t I
`
`35
`
`45
`
`SO
`
`55
`
`65
`
`‘ Q
`
`14
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ ChargeStill Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site