Remote booting of an operating system by a network

• US 5,577,210 A
• Filed: 06/16/1993
• Issued: 11/19/1996
• Est. Priority Date: 10/17/1991
• Status: Expired due to Term

• Current Assignee: CP8 Technologies (Thales SA)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Demortain, Stephane, Abdous, Arave, Dalongville, Didier
• Primary Examiner(s): An, Meng-ai T.
• Assistant Examiner(s): Rinehart, Mark H.
• Application Number:
  US08/075,578
• Time in Patent Office: 1,252 Days
• Field of Search: 395/200, 395/400, 395/200.09, 395/200.10, 395/200.11, 395/200.2, 395/404, 395/438, 395/439, 395/894, 364/280.23, 364/248.1, 364/280.2, 364/280.3, 364/280.6, 364/975.2
• US Class Current: 709/219
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]

Abstract

A method for remote booting by a server of at least one terminal, including a volatile memory (RAM), at least one processor, a telecommunications card enabling connection to the server by a network, said server being provided with telecommunication device and memory of sufficient capacity to store the communications protocol, the operating system of the terminals recopied into an image file, its own operating system, and the applications programs, wherein the method includes the remote loading of a startup program by transforming the first interruption produced by a terminal following its being powered up into a request for reading an image file memorized in the server.

Claims

1. A method for remote booting by a server of at least one terminal, wherein said terminal includes a volatile memory, at least one processor, a telecommunications card enabling connection to the server by a network, said server being provided with telecommunication means and memory means of sufficient capacity to store a communications protocol, an operating system for the terminal stored in an image file, a server operating system, and applications programs, wherein said method comprises the steps of remote loading said terminal with a startup program, and transforming a first interruption produced by the terminal when the terminal is powered up into a request for reading the image file stored in the server;

wherein said step of remote loading said terminal with a startup program includes loading a file allocation table (FAT) into the volatile memory to define a diskette number, a head number, a track number, a track sector number, and a file name for said terminal files, and loading a sector description table (SDT) into the volatile memory to establish a correspondence between said terminal files and a diskette number, a track number, a track sector number, and chapter numbers of the image file of the server;

and further wherein the step of remote loading of the startup program comprises the steps of loading a startup (BOOT) sector into the volatile memory, starting the execution of said startup program, wherein the execution of said startup program includes file request interruptions for requesting access to nonexistent terminal files of nonexistent magnetic peripherals of the terminal, and transforming said file request interruptions into requests for reading a corresponding image file in the server; and

said method further including the step of providing an emulation program for transformation of the file request interruptions, and storing said emulation program in a nonvolatile memory of the telecommunications card.

2. The method of claim 1, wherein the step of transforming said file request interruptions comprises the steps of transforming coordinates of physical sectors of the nonexistent terminal files on the nonexistent magnetic peripherals into logical chapter numbers of the image file, transmitting to the server a request by the terminal to read chapters corresponding to the chapter numbers, and sending the requested chapters of the image file to the terminal.

3. The method of claim 1, further including the step of enabling the remote loading of files of the terminal operating system, wherein said terminal operating system files include IO.SYS, MSDOS.SYS, CONFIG.SYS and COMMAND.COM files.

4. The method of claim 1, wherein the step of loading the file allocation table (FAT) includes storing the file allocation table with eternal status in the random access memory, said eternal status being indicated by one bit of a word in the sector description table.

5. The method of claim 1, further including the steps of establishing time periods T1, T2, T3, T4, and T5 for effecting operation of the server and using a manager process to manage said time periods, wherein at least a first and second terminal are connected to the server, and further wherein the step of transmitting a reading request for a first chapter to the server, includes causing the server to wait for time period T1 before sending the requested first chapter, and checking if the second terminal transmits the same request during time period T1.

6. The method of claim 5, wherein if said second terminal sends a request for a first chapter during time period T1 and before time period T2 following the request for the same first chapter by the first station, restarting the procedure of remote booting of the first and second terminals.

7. The method of claim 5, further including the step of causing the server to wait for time period T3 between the sending of chapters and time period T5 between frame transmissions which together define the chapters.

8. The method of claim 5, further including the step of causing the server to close a session at the end of time period T4 after sending an end of chapter frame, if no other station has sent a request.

9. The method of claim 5, further including the step of selectively setting the length of each of said time periods T1, T2, T3, T4 and T5.

10. The method of claim 1, further including the step of sending chapter-specific data frames which include an Ethernet address of a receiving terminal.

11. The method of claim 1, further including the steps of causing the terminal, when executing an instruction to open a file, to read the file allocation table, thus determining a sector, reading the sector description table to determine a chapter, executing the chapter if the chapter resides in the volatile memory, and sending a request for remote loading to the server if the chapter is not in the volatile memory.

12. The method of claim 11, wherein the sector description table includes a state byte, and further including the step of indicating by a first bit of the state byte, reception of a chapter, by a second bit use of a chapter, by a third bit of the state byte, a eternal status, by a fourth bit of the state byte, a number of segments, by a fifth bit of the state byte, presence of a fill value, and by a sixth bit of the state byte, a data-specific sector.

13. The method of claim 1, wherein the terminal includes a state register for an emulated interruption function, and further including the step of using said state register at a reception of an end of remote boot frame to determine, by reading registers DL and AL of the processor of the terminal, whether it is necessary to perform a "load data segment" function or a "shutdown" function.