3. It is a good idea to install and configure the NIC first before anything else. There are many ways to skin a cat (or is it a chicken), I prefer doing it this way:
If it is a trickle down machine, first format the HDD with the boot disk
Reboot, then create a directory called HOLD (C:\Hold), and copy all the files from the boot disk to that directory.
cd hold
Run the necessary files to get on the network (LSL, E100BODI [or appropriate NIC Driver], IPXODI, NETX)
Log in to MCS/INSTALL and cd to OS\DOS\622 and run SETUP
After installation is complete and done rebooting, log back in to MCS/INSTALL and cd to OS\WINDOWS\WFW311 and run setup. I normally select Custom Install and select the components you believe the user will need, including Print Drivers.
When prompted to install Support for Networks, I select NONE. Continue till setup completes.
Reboot again and login back in to the network with the drivers in c:\hold
Login in to MCS/INSTALL and cd to DRIVERS\NETWORK\NOVELL\NWCLIENT and run INSTALL
When prompted, select Support for Windows, and hit the enter key for NIC Drivers and type in C:\HOLD in place of A:\.
Select INSTALL Files now when ready.
When installation is complete, go back to a DOS Prompt and edit the AUTOEXEC.BAT file and place the @CALL C:\NWCLIENT\STARTNET.BAT from the beginning to the end of the file.
CD to C:\NWCLIENT and edit the net.cfg file to just below the line to the bindings for the NIC Card and remove the line for the FRAME 802.2. We use 802.3 and if you don't remove that line or move it, you will hang when loading the VLM'S. Here is a typical example of an ideal NET.CFG:
PREFERRED SERVER = SERVERNAME
FILE HANDLES = 99
SHOW DOTS = ON
Link Driver E100BODI
FRAME Ethernet_802.3
FRAME Ethernet_II
FRAME Ethernet_SNAP
NetWare DOS Requester
FIRST NETWORK DRIVE = F
NETWARE PROTOCOL = NDS BIND