1. es031.exe Driver
2. WS-400.TXT File Contents

WS-400.TXT Driver File Contents (es031.exe)

To Switch On or OFF remote booting
Rename Config.sys and Autoexec.bat to *.old respectively
Reboot computer and unit will say Boot from Network ?  Y/N
Select N to boot from floppy on hard disk. Time and date then should
be displayed.
On system supervisor disk a directory call FBIOS exists, 
containing a file called Upgrade.Com. Run the program and select

F1	No boot Rom (Boot from Hard Disk)- To swicth off startup message
F2	Novell Ethernet 802.3 - To remote boot using this protocol
F3	Novell Ethernet II - To remote boot using this protocol
F4	Token Ring - To use token ring ooption
ESC	Exit without Upgrade
Remote Booting Instructions after Selecting necessary option
Create these files on a blank DOS, but Dos v 6 bootable disk 

Autoexec.Bat (ODI Support) **Preferred
				
Prompt $p$G
Echo off
LH LSL
LH RPLODI		-------	Needed for Remote Boot Only
LH NE2100
LH IPXODI		
LH NETx		-------	Must be Netx.exe Ver 3.32	
F:
Login									

or Autoexec.bat (Normal IPX image files)

IPX			-------	Ne2100 IRQ=5 Port=300 DMA=5
NETX			-------	Must be Netx.exe Ver 3.32
F:
Login

These files are available upon WS400 System Supervisor Diskette supplied

Config.sys	

Files=60
Buffers=30
Stacks=9,256
Device=Himem.sys /M:2
Device=Emm386.exe /y=y:EMM386.EXE /d=48 rom=C800-CA00 I=E000-EFFF NOEMS
DOS=HIGH,UMB




When Using ODI drivers

Net.cfg when using (F2) Ethernet 802.3

Link Support
	Max Stacks 8
	Buffers 8 1500
	MemPool 4096

Link Driver NE2100
	INT 5
	Port 300
	DMA 5
	Frame Ethernet_802.3
		
Net.cfg when using (F3) Ethernet II

Link Support
	Max Stacks 8
	Buffers 8 1500
	MemPool 4096

Link Driver NE2100
	INT 5
	Port 300
	DMA 5
	Frame Ethernet_II
		
On the WS-400 workstation.

It is necessary to enter the BIOS SETUP via <ESC> Key at Boot up, 
and then go to the section marked SHADOW and check all items are 
set to default as displayed by a (*) along side.

Later : Use dos command  MEM / C  to show how much is available memory  

To create a boot image file WS400.SYS or NET$DOS.SYS

To run the DOSGEN procedure we enter the login directory and run command

\system\DOSGEN A: WS400.SYS
	This will actually create the file WS400.SYS

\System\DOSGEN 
	This will actually create the file NET$DOS.SYS

This principle is applied to create a Bootconf.sys
* Installation Manual Appendix D - Topic - Dosgen  
see how to create your own WS400.SYS,NET$DOS.SYS or BOOTCONF.SYS




When the DOSGEN procedure has completed the NET$DOS.SYS or WS400.SYS 
file must reside in the LOGIN directory, also it is necessary to use
the following command when using DOS ver 5 or 6.

TYPE FOLLOWING COMMANDS AT THE F: PROMPT IN THE LOGIN DIRECTORY

RPLFIX WS400.SYS    or   RPLFIX NET$DOS.SYS

FLAG WS400.SYS RO S or   FLAG NET$DOS.SYS RO S   (Read Only,Shareable)

Rplfix.com is a utility provided by your Novell supplier and is 
standard on Elonex Servers..

The System Login Script of Server

Your Novell server must have its second root mapping to Dos 6 upon the
server containing the full version of Dos files that were used to 
create the floppy diskette.

MAP ROOT INS S1: = SYS:PUBLIC
MAP ROOT INS S2: = SYS:PUBLIC\%MACHINE\%OS\%OS_VERSION
COMSPEC = S2: COMMAND.COM

DOS Ver 6

All dos versions should reside in this type of tree structure 
SYS:	PUBLIC\	IBM_PC\	MSDOS\	V6.00
These are the defaults as determined by the Net.cfg parameters.

Other Examples

SYS:	PUBLIC\	IBM_PC\	PCDOS\	V3.30
Where we are using an IBM Pc using its own version of PCDos  3.3

SYS:	PUBLIC\	COMPAQ\	MSDOS\	V4.01
Where we are using a Compaq Pc using MSDos ver 4.01

All these parameters are defined by the Shell.cfg or Net.cfg
preferable to use NET.CFG only, not a combination of both.