Minimum Remote Boot Diskette
Here is the minimum set of files needed for making a REMOTE BOOT diskette. A REMOTE BOOT diskette is used for setting up a diskless workstation on the network (i.e., a workstation that loads DOS from a file server, instead of a local disk drive). The REMOTE BOOT diskette must contain all the files needed to boot the diskless workstation.
Directory of REMOTE BOOT diskette
COMMAND.COM
AUTOEXEC.BAT
CONFIG.SYS
NET30.INI
NET30.EXE
REDIRECT.OVL
N30DEV.SYS
HIMEM.SYS
Contents of CONFIG.SYS
buffers = 20
files = 20
device = himem.sys
device = n30dev.sys
dos = high
Contents of AUTOEXEC.BAT
net30
prompt $p$g
path c:\;c:\dos;c:\net30
Contents of NET30.INI
net30.hardware = Ethernet_2000
net30.name = remote
net30. redirector = y
map.c = \\server\c:
(Note: The "net30.hardware" parameter must be present, but its value is ignored since the ROM on the diskless workstation already knows the hardware type. The value of "net30.name" is the name you want to assign to the diskless workstation. The value of "map.c" is the network path for mapping the diskless workstation's C: drive; you can add additional mappings by including "map.d" or "map.lpt1" etc.)
Unlinking
Remote boot uses a disk image that is booted across the network from the remote boot server. This disk image is loaded across the network as a read-only virtual A: boot drive. If you have a local floppy diskette drive, you can unlink from the remote boot server in order to activate your local A: drive. To do this, add the following statements to your AUTOEXEC.BAT:
SET COMSPEC = c:\command.com
C:
unlink
Additional Information
For additional information on setting up diskless workstations, refer to the Invisible LAN DOS User Manual.
Notices: Copyright 1996 by Invisible
Software, Inc. Invisible Software and InvisibleLAN are trademarks
of Invisible Software, Inc. Other trademarks are the property of
their respective holders.
This document was prepared on 05/23/96, and was believed to be
accurate as of that date. Procedures, specifications, and
compatibility may change without notice, and therefore this
document may be out-of-date and/or inapplicable to current
product versions. Invisible Software provides this document
"AS IS" and without warranty of any kind. Under no
circumstances shall this document be construed as creating or
expanding any warranty of product performance.