Using the Netware Client Installation Program

1. Insert Disk 1 of the NetWare Client kit into your machine's A: drive. (If you used the download instructions, this would be the diskette you created from the VLMKT1 archive file.)

2. Set your current drive to A: by entering the command, “A:”, at the DOS command prompt.

3. Run the installation program by entering the following command at the DOS prompt:

A> INSTALL

4. The installation program requires you to make only five choices. Respond as follows:

Response 1. C:\NWCLIENT
Response 2. Yes
Response 3. No
Response 4. No
Response 5. (follow the on-screen instructions to select and configure an adapter driver)

Note: Part of the hardware configuration options will be a “Frame” type. TCP/IP is not supported on all frame types. For an Ethernet installation, select frame type Ethernet_II. For a token-ring installation, select frame type Token-Ring_SNAP.

5. Highlight the line numbered “6.” on the screen and press the <Enter> key to proceed with the installation. Insert additional diskettes as prompted. When the program completes the installation, exit the program back to DOS instead of rebooting the machine.

6. You are now ready to modify the STARTNET.BAT file. This file will be found in the NetWare Client directory, C:\NWCLIENT. To use the text editor that came with your DOS installation, enter the following command at the DOS prompt:

C> EDIT C:\NWCLIENT\STARTNET.BAT

7. Using the editor, make the following changes:

Remove the line specifying, “VLM.EXE”

If you will not be using the IPX network protocol, remove the line specifying, “IPXODI.COM”

If you will be using the TCP/IP protocols, add a line like the others, only specify the file “TCPIP.EXE”

The contents of the STARTNET.BAT file should now look similar to the following:

SET NWLANGUAGE=ENGLISH
C:\NWCLIENT\LSL.COM
C:\NWCLIENT\NE2000.COM
C:\NWCLIENT\IPXODI.COM /A
C:\NWCLIENT\TCPIP.EXE

8. Use the “Save” option on the editor's “File” menu to save the modified STARTNET.BAT file to your hard disk. Then exit the editor (choose the “Exit” option from the “File” menu).

9. Copy files:

If you are using the purchased set of diskettes from Novell, we recommend you use the following set of copy commands instead of running the TCP/IP installation program. Insert the disk labeled, “TCP/IP Transport for DOS v4.12”, into your A: drive and copy the files TCPIP.EXE, PING.EXE, and PING.MSG to the C:\NWCLIENT directory:

C> COPY A:\NET\BIN\TCPIP.EXE C:\NWCLIENT
C> COPY A:\NET\BIN\PING.EXE C:\NWCLIENT
C> COPY A:\NET\BIN\PING.MSG C:\NWCLIENT

If you used the TCP16.EXE archive file to create a diskette, insert the diskette into your A: drive and copy the files TCPIP.EXE, PING.EXE, and PING.MSG to the C:\NWCLIENT directory:

C> COPY A:\TCPIP.EXE C:\NWCLIENT
C> COPY A:\PING.EXE C:\NWCLIENT
C> COPY A:\PING.MSG C:\NWCLIENT

10. You are now ready to modify the network configuration file, NET.CFG. This file contains all of the information necessary to configure the operating characteristics of the 16-bit Novell transport software.

The contents of NET.CFG are organized into sections identified by a section header line. Section headers do not have any leading spaces before the first word on the line. All parameter lines within a section must have at least one space or tab at the beginning of the line. Text appearing after a semi-colon (';') is regarded as a comment. Upper-case and lower-case letters are treated the same.

Invoke the editor:

C> EDIT C:\NWCLIENT\NET.CFG

Then edit the file according to the following steps:

Delete the “NetWare DOS Requester” section header and its parameter lines.

If you are planning to use the TCP/IP network protocols, add the following section to the beginning of the file exactly as shown below:

Link Support
Buffers 32 638
MemPool 40K
Max Boards 4
Max Stacks 4

If you are planning to use the TCP/IP network protocols, add the following section to the end of the file as shown below, altering only the IP information to match your site's network addressing scheme:

Protocol TCPIP
ip_address 204.250.100.1
ip_netmask 255.255.255.0
ip_router 0.0.0.0
tcp_window 598
tcp_sockets 32

Note: If you have no IP router on your LAN connecting it with other LAN segments, you may omit the “ip_router” line or leave the value of “0.0.0.0”.

Note: Obtain correct IP address, router, and net-mask values from your network administrator. If you don't have a network administrator and your new LAN is going to remain isolated from other networks, use the values as shown in the example above. This will configure the server machine as node 1 on network 204.250.100; the workstations on your network would need to be configured with the same network number and a node number between 2 and 254, inclusive. Each workstation must use a unique node number; duplicating node numbers will cause your network to malfunction.

If you are planning to use the IPX network protocol, add the following section to the end of the file exactly as shown below:

Finally, you must inspect and possibly modify the “Frame” parameters in the Link Driver” section.

If you are going to use only TCP/IP protocols, or if you are going to use both TCP/IP and IPX protocols on a new network, there should be only a single “Frame” parameter:

Frame Ethernet_II
;(or Token-Ring_SNAP)

If you are going to use only the IPX network protocol, there should be only a single “Frame” parameter; if you are installing your server on an existing network that uses Novell NetWare with IPX, you should force the IPX protocol to use the same frame type that is already being used by other nodes on the network. Otherwise, you may choose any frame type supported by IPX. For example:

Frame Ethernet_802.2
;(or Token-Ring)

If, however, you are going to use both TCP/IP and IPX protocols on an existing network that uses Novell NetWare with IPX, and the frame type being used is not Ethernet_II (or Token-Ring_SNAP), you should force the IPX protocol to use the same frame type that is already being used by other nodes on the network. You will then have two “Frame” parameter lines, the first of which will automatically be used by IPX:

Frame Ethernet_802.2
;(or Token-Ring)
Frame Ethernet_II
;(or Token-Ring_SNAP)

11. Use the “Save” option on the editor's “File” menu to save the modified NET.CFG file to your hard disk. Then exit the editor (choose the “Exit” option from the “File” menu).

12. Remove any diskettes from your machine's A: drive and reboot the machine. Watch the messages displayed by each network software module as it loads. If everything is working, you will receive no error messages and only a single warning; when TCPIP.EXE loads, it will issue the following warning message:

WARNING: LSL buffer size too small (minimum:1500 bytes).

Ignore this warning; it is expected. If other errors occur, you may have mis-typed something in the NET.CFG file, or your hardware may not match the driver settings in the NET.CFG file.

13. If you need additional information or examples regarding system configuration, please see the section titled, TCP/IP and MCP/IPX Software Configuration . You may also call Aspen Research Technical Support at 1-970-945-2921. Otherwise, proceed to the section, Miscellaneous DOS Configuration Tips for AspeNet Servers .