Boot Disk using IPXODI
This had to be done as two protocols were running on the network. IPX and TCP/IP for internet
access.
The files on the boot disk are
AUTOEXEC.BAT
ANSISCSI.SYS
CONFIG.SYS
COMMAND.COM
EMM386.EXE
HIMEM.SYS
IPXODI.COM
LSL.COM
MMOUSE.SYS
NET.CFG
NETX.EXE
NE2000.COM
SETVER.EXE
SHARE.EXE
RPLODI.COM
TCPIP.EXE
VTCPIP.386
CONFIG.SYS (This will not change)
device=setver.exe
device=himem.sys
device=ansiscsi.sys
DEVICE=EMM386.EXE NOEMS /Y=SYS:PUBLIC/MSDOS/V6.22/EMM386.EXE
DOS=HIGH,UMB
DEVICEHIGH=MMOUSE.SYS /A7
files = 99
buffers = 40
stacks=9,256
LASTDRIVE=E:
AUOTEXEC.BAT
prompt $p$g
lh share
set temp=h:
set tmp=h:
LH LSL
REM Load the Link Support Layer (helps to decide which protocol to use)
RPLODI
REM Needed only if you are going to create a Remote Boot Disk
REM Image-NIC has a boot ROM in it and you wish to boot the
REM workstation from an image of the boot disk on the network)
LH NE2000
REM Driver for the Network Card
LH IPXODI
REM IPXODI protocol
LH netx/ps=HEATHMONT2
REM Network Dos Requester
TCPIP -c=F:\LOGIN\A6\NET.CFG
REM TCP/IP protocol
f:
login any
NET.CFG
#NET.CFG File for HEATHMONT2
show dots=on
file handles=90
buffers=40
First Network Drive=F:
Link Support
Buffers 8 1514
MemPool 4096
#
# Protocol Stack Section:
#
Bind ne2000
# Link Driver Section
Link Driver ne2000
Port 320
Int 5
Frame Ethernet_802.3
Protocol IPX 0 Ethernet_802.3
Frame Ethernet_II For TCP/IP
Protocol TCPIP
path tcp_cfg f:\login
#With this section REMMED out, the address will be served by a BOOTP
server
#Admin loop
# ip_router 203.21.34.252
# ip_address 203.21.34.1
| 
