Browse Prior Art Database

Remote IPL of Workstations with Hard Files but without Diskettes

IP.com Disclosure Number: IPCOM000104192D
Original Publication Date: 1993-Mar-01
Included in the Prior Art Database: 2005-Mar-18
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Related People

Dubke, RE: AUTHOR [+2]

Abstract

Most computers gain access to the network by loading adapter support code from their fixed disk or diskette drive. The IBM remote program load (RPL) module, located on the token-ring local area network (LAN) adaptor, for example, makes it possible for a personal computer (PC) or PS/2* system to gain access to a LAN network for boot-up. It can then request that it be loaded with programs from a server, even though it may not have a hard file or diskette drive.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 61% of the total text.

Remote IPL of Workstations with Hard Files but without Diskettes

      Most computers gain access to the network by loading adapter
support code from their fixed disk or diskette drive.  The IBM remote
program load (RPL) module, located on the token-ring local area
network (LAN) adaptor, for example, makes it possible for a personal
computer (PC) or PS/2* system to gain access to a LAN network for
boot-up.  It can then request that it be loaded with programs from a
server, even though it may not have a hard file or diskette drive.

If the system has a hard file and/or diskette, RPL can still be used
for boot-up if neither contains a "boot record."

      There are applications that require a hard file for performance
but not a diskette.  The diskette may be undesirable for security
reasons.  A system configured in this manner could be very desirable
but may also be a service problem if the hard file becomes "software
damaged" though it may be physically good.  Normally, recovery
requires the hard file to be replaced or for a diskette to be
temporarily installed for the executing recovery programs.

      The present RPL implementation will not work.  This is due to
the priority that the RPL module provides in conjunction with the
system BIOS.  Presently, if the hard file is marked bootable, the
hard file has priority.  RPL is unable to gain control; therefore, it
cannot be used to recover the hard file.

      The solution is to create a new version o...