================================================================
		   Norton Ghost for NetWare
                   TCP/IP Utilities Release
		     Symantec Corporation
		       www.ghost4nw.com
                 support@ghost4nw.com
================================================================

September 13, 1999

			   CONTENTS

A.  Introduction.

B.  List of files in this release.

C.  Command description and usage.

D.  Packet driver configuration.

E.  Novell client configuration with Novell TCP/IP.

F.  Novell client configuration with Novell TCP/IP and DHCP.

G.  Novell client configuration with ODIPKT.COM.

H.  Additional information and support.

I.  FAQ

================================================================

A.  INTRODUCTION

This package contains the TCP/IP send and receive data transfer utilities.

These utilities are used to transfer data or files from machine
to machine. These utilities use TCP as the transport protocol for
data transfer.  These utilities are often used to transfer image
files for Norton Ghost for NetWare.

Supported Operating Systems:

1) MS-DOS.
2) DR-DOS.
3) Windows 95.
4) Windows 98.
5) Windows NT.
6) Windows 2000.

Supported Ethernet Hardware:

1) All Ethernet cards that support the Ethernet II frame type.

Supported Device Drivers:

1) Packet Drivers.
2) Novell Client with Novell's TCP/IP.
3) Novell Client with ODIPKT.COM.
4) Novell Client32.

The Novell Client is available in three configurations. The older
NETX style, the VLM style and the Client32 style.

================================================================

B.  LIST OF FILES IN THIS RELEASE

README   TXT    25,322

Directory of \BIN
RECV     EXE    88,150
RECVNOV  EXE    85,808
RECVPKT  EXE   119,266
RECVW32  EXE    73,728
SEND     EXE    88,156
SENDNOV  EXE    87,983
SENDPKT  EXE   120,272
SENDW32  EXE    77,824
TCPIPN   GLL     6,762
TCPIPW   GLL    96,197

Directory of \DOCS

TCPIP    PDF   183,599
WATTCP   PDF    23,316

Directory of \Drivers
ODIPKT   COM     3,307

Directory of \EXAMPLES\ODI

NET      CFG       660
STARTNET BAT       356

Directory of \EXAMPLES\ODIPKT

NET      CFG       497
STARTNET BAT       177
WATTCP   CFG       255

Directory of \EXAMPLES\PACKET

STARTNET BAT       107
WATTCP   CFG       255

Total 21 files

================================================================

C.  COMMAND DESCRIPTION AND USAGE

********************
        RECV
********************

Description:

	The executable recv.exe is a utility that verifies the TCP/IP
	configuration and then launches the appropriate recv utility.

	If recv.exe detects that the Novell Client with Novell
	TCP/IP is installed, then recvnov.exe will be executed.

	If recv.exe detects that the Novell Client with ODIPKT
	is installed, then recvpkt.exe will be executed.

	If recv.exe detects that a Packet Driver is installed, then
	recvpkt.exe will be executed.

	If recv.exe detects that it is executing under Windows 95/98/NT,
	then recvw32.exe will be executed.

	The TCP/IP device driver configuration can be displayed with
	the -config option

Syntax:

	recv <option>
	recv <ip address> <file name>

Options:

	-
		No files will be created. All received data will be discarded.
		This option is useful to measure the raw TCP/IP performance.

	-config:
		Display the current TCP/IP configuration. After the
		configuration is displayed, the program will exit.
		This option will also display each PCI Ethernet Adapter
		detected.

	- help:
		Display the command options and parameters.

	-autosize=n:
		Receive the data into a file. Close the file after n MB.
		Allow the user to specify a new file for each n MB.
		This option can be used to automatically size received
		files that are written to removable media or CD-ROMs.

	-autoname:
		Automatically name received files when using the autosize
		option. The files with end with ".000" and will be
		incremented by one for each file. Do not use this option
		for removable media if the total size of the received
		file will be larger than the media.

	-port=n:
		Change the default TCP/IP port that the software uses.
		The default port is 111.

Parameters:

	ip address:
		This is the TCP/IP address of the machine to receive data
		from. This string is in Internet dotted format.

	file name:
		This is the name of file to create and write the
		received data to. If a file with the same name exists,
		the user will be prompted to confirm deletion. If the
		file name is the dash character -, no file will be created.
		Instead the data will be received and then discarded.

Examples:

	Display the current TCP/IP configuration:
	recv -config

	Connect to another machine and transfer a file "test.img":
	recv 192.7.4.3 test.img

	Connect to another machine and discard received data:
	recv 192.7.4.3 -

********************
        SEND
********************

Description:

	The executable send.exe is a utility that verifies the TCP/IP
	configuration and then launches the appropriate send utility.

	If send.exe detects that the Novell Client with Novell
	TCP/IP is installed, then sendnov.exe will be executed.

	If send.exe detects that the Novell Client with ODIPKT
	is installed, then sendpkt.exe will be executed.

	If send.exe detects that a Packet Driver is installed, then
	sendpkt.exe will be executed.

	If send.exe detects that it is executing under Windows 95/98/NT,
	then sendw32.exe will be executed.

	Send supports the transfer of multiple files as one data
	stream to support very large image restores. Adding the -pause
	option will cause the software to wait before opening each
	file. An example of using the option is a multiple CD restore.

Syntax:

	send [options] [file1] [file2] [filen]\n"

Options:

	-
		No files will be opened only random data will be sent.
		The current send limit is 2^64 bytes.
		This option is useful to measure the raw TCP/IP performance.

	-config
		Display the current TCP/IP configuration. After the
		configuration is displayed, the program will exit.
		This option will also display each PCI Ethernet Adapter
		detected.

	-help
		Display command help.

	-pause
		Pause before opening each file to insert new media.

	-port=n:
		Change the default TCP/IP port that the software uses.
		The default port is 111.

	-readsize=n
		Set disk read buffer size to n bytes. This variable can
		be modified to support various hardware performance levels.
		Valid range: 512 to 32768 bytes

	-sendsize=n
		Set send buffer size to n bytes. This variable can be
		modified to support various hardware performance levels.
		Valid range: 1 to 32768 bytes

Parameters:

	file name:
		This is the name of the file to transmit. Multiple
		file names can be specified. If multiple file names
		are specified they will be concatenated during the
		data transfer.

		If the file name is the dash character -, no files will
		be opened. Instead the data will be created randomly.
		To stop the sending of data, press any key.

Examples:

	Display the current TCP/IP configuration:
	send -config

	Connect to another machine and transfer a file "test.img":
	send test.img

	Connect to another machine and send data continually:
	send -

	Connect to another machine and send an image file set:
	send image1 image2 image3

================================================================

D.  PACKET DRIVER CONFIGURATION

Packet Drivers are loaded into memory by executing them.

Examples:
	3COM 3c90x 10/100 Ethernet card:
		3c90xpd

	IBM Netfinity 5000 (AMD PC-NET)
		pcntnw.com

The driver name can be placed in the autoexec.bat to be autoloaded
after each boot.

The Norton Ghost for NetWare Utilities require a configuration
file to be setup (wattcp.cfg). Note this is valid only for Packet
Drivers and does not apply when using the Novell Client for DOS with
Novell's TCPIP module.

Example wattcp.cfg file:

	# Set the following field to the TCP/IP address of this machine
	IP=192.36.45.12

	#Set the following field to the Net Mask for your network
	NETMASK=255.255.255.0

	#Set the following field to the address of your gateway (router)
	GATEWAY=192.35.45.1

If the software can not open the wattcp.cfg file, then the TCP/IP
stack will attempt to get the TCP/IP configuration using BOOTP.
This can take several minutes to timeout if you do not have a
BOOTP server located on your network.

Currently these programs use the current working directory to locate
WATTCP.CFG. Solution: set the environment variable GHOSTIP=<filename>
to set the full path name.

For more detailed information refer to the wattcp.pdf and tcpip.pdf
documents included with this release.

================================================================

E.  NOVELL CLIENT CONFIGURATION WITH NOVELL TCP/IP

Novell Client for DOS provides client connectivity for Novell
NetWare servers. It can also provide a robust TCP/IP protocol stack.

Example net.cfg file for configuring the 3COM 3c90x Ethernet Cards:

	Protocol TCPIP
		BIND 3c90x #1 Ethernet_II LAN_NET_II
		IP_ADDRESS 192.35.131.91 LAN_NET_II
		IP_ROUTER  192.35.131.66 LAN_NET_II
		IP_NETMASK 255.255.255.0 LAN_NET_II

	Link driver 3c90x
		FRAME Ethernet_II

	Link Support
		Buffers 8 1504
		MemPool 8192

	NetWare DOS Requester
		FIRST NETWORK DRIVE F
		NETWARE PROTOCOL NDS BIND

Example startnet.bat for loading the Novell Client:

	lsl	<--- This loads the Novell NetWare Link Support Layer
	3c90x	<--- This load the ODI driver for 3COM 3c90x
	tcpip	<--- This loads the tcpip Novell client TCP/IP layer

A common configuration error is not including the line "FRAME Ethernet_II"
to the net.cfg file. This frame type is necessary to support TCP/IP.

================================================================

F.  NOVELL CLIENT CONFIGURATION WITH NOVELL TCP/IP and DHCP

Novell Client for DOS provides client connectivity for Novell
NetWare servers. It can also provide a robust TCP/IP protocol stack.

Example net.cfg file for configuring the 3COM 3c90x Ethernet Cards:

# This example is used for the Novell Client for DOS
# for the 3COM 3c90x family of Ethernet Cards using DHCP to obtain
# the network address.

	IF_CONFIGURATION DHCP

	Protocol TCPIP
	    PATH TCP_CFG C:\NWCLIENT\TCP

	Link driver 3c90x
	    FRAME Ethernet_II

	Link Support
	    Buffers 8 1504
	    MemPool 8192

	NetWare DOS Requester
	    FIRST NETWORK DRIVE F
	    NETWARE PROTOCOL NDS BIND

Example startnet.bat for loading the Novell Client:

	lsl	<--- This loads the Novell NetWare Link Support Layer
	3c90x	<--- This load the ODI driver for 3COM 3c90x
	tcpip	<--- This loads the tcpip Novell client TCP/IP layer

A common configuration error is not including the line "FRAME Ethernet_II"
to the net.cfg file. This frame type is necessary to support TCP/IP.

================================================================

G.  NOVELL CLIENT CONFIGURATION WITH ODIPKT.COM

---> IMPORTANT NOTE: There are a number of Ethernet cards that are not
---> supported by the ODIPKT.COM driver. On these cards, the machine
---> will hang during data transfers or behave incorrectly.

Novell Client for DOS provides client connectivity for Novell NetWare
servers. ODIPKT.COM can provide a Packet Driver interface on top of
the Novell Client.

---> For some Ethernet Adapters using the Novell Client, the line
---> Frame Ethernet_II needs to be the first frame type specified.

Example net.cfg file for configuring the 3COM 3c90x Ethernet Cards:

	Link driver 3c90x
		FRAME Ethernet_II

	Link Support
		Buffers 8 1504
		MemPool 8192

	NetWare DOS Requester
		FIRST NETWORK DRIVE F
		NETWARE PROTOCOL NDS BIND

Example startnet.bat for loading the Novell Client:

	lsl	<--- This loads the Novell NetWare Link Support Layer
	3c90x	<--- This load the ODI driver for 3COM 3c90x
	odipkt	<--- This loads the ODIPKT Packet Driver Layer

A common configuration error is not including the line "FRAME Ethernet_II"
to the net.cfg file. This frame type is necessary to support TCP/IP.

================================================================

G.  ADDITIONAL INFORMATION AND SUPPORT

****************************************
Symantec Resources:
****************************************

For your convenience, we have collected third party network drivers and
other relevant files. To browse our collection, go directly to our ftp site:

ftp.symantec.com/public/english_us_canada/products/ghost/

****************************************
Novell Client for DOS:
****************************************

www.novell.com/download/

****************************************
Novell Client for DOS TCPIP Module:
****************************************

ftp.novell.com/pub/update/cp/unixconn/tcp1607.exe

****************************************
The Packet Driver Collection:
****************************************

www.crynwr.com

****************************************
Packet Driver Resources:
****************************************

www-commeng.cso.uiuc.edu/nas/nash/packet/packet.html

support.3com.com/infodeli/tools/nic/3c905.htm

www.amd.com/products/npd/software/pcnet_family/drivers/pktdrvr.html

www.intel.com

****************************************
The Simtel.Net MS-DOS Ethernet Driver Collection:
****************************************

www.heanet.ie/simtel.net/msdos/pktdrvr-pre.html

****************************************
ODIPKT
****************************************

ODIPKT.COM: www.danlan.com

****************************************
TIP: Go to the web site for your Ethernet Hardware and click on their
search button after entering the text packet+driver
****************************************

================================================================

H. FAQ

********************************************************************************

Q) What is a Packet Driver?

A) A packet drivers is small TSR program that provide an interface for
   TCP/IP applications that connect to a network, regardless of what
   kind of network interface card (NIC) is installed. A packet driver
   allows applications that contain their own TCP/IP stacks, such as
   Norton Ghost for NetWare, to use the network interface card and
   share the card with other applications. The packet drivers permit
   simultaneous use of multiple protocols with the interface card,
   e.g., TCP/IP and Novell IPX. 

********************************************************************************

Q) Where can I find a packet driver for my NIC?

A) Most LAN cards come with packet drivers on their software disk.
   There are also many Internet archives of packet drivers from which
   you can download this software.  Refer to Section H.

********************************************************************************

Q) I can not find a Packet Driver for my Ethernet card. What do I do next?

A) You have many options:

	1) Install the Novell Client with Novell's TCPIP.
	2) Install the Novell Client and ODIPKT.COM.
	3) Install Microsoft's NDIS Drivers.

********************************************************************************

Q) Is there a mailing list for Packet Drivers?

A) Yes. An Internet mailing list for packet driver support is available.
   Send the word "help" in the body of an Email message to:

	listserv@sun.soe.clarkson.edu

********************************************************************************

Q) How do I install a Packet Driver?

A) Installing a packet driver is very easy. Most packet drivers auto
   configure. Some basic information will be required for your TCP/IP
   network, and you may need to contact your network administrator to
   obtain this information. The installation document that comes with
   the packet driver or with the packet driver archive explains
   installation in detail. Be sure to carefully read the section that
   describes installation for the card you have. The command line
   parameters can vary from one card to the next. Refer to section D.

********************************************************************************

Q) What is ODIPKT.COM?

A) ODIPKT.COM is a Packet Driver that sits on top of Novell NetWare
   Client for DOS. This driver converts the Packet Driver interface
   to the ODI interface that Novell provides.

---> IMPORTANT NOTE: There are a number of Ethernet cards that are not
---> supported by the ODIPKT.COM driver. On these cards, the machine
---> will hang during data transfers or behave incorrectly.

********************************************************************************

Q) I have setup my wattcp.cfg file and loaded a packet driver.
   When I ping this machine, there is no reply. What's wrong?

A) Nothing. Even though a packet driver is loaded, a TCP/IP stack is
   not yet executing. Each utility (send / recv) contains its own TCP/IP
   stack. Only after one of these commands is running with there be
   a response to the ping command.

   Note: The Novell NetWare Client for DOS TCP/IP stack does support the
   responding to the ping command.

********************************************************************************

Q) I have installed the Novell Client for DOS and then I installed a
   Packet Driver. My machine hangs. Why?

A) Packet Drivers and Novell Client for DOS are not compatible when
   combined together.

   Your options are to remove the Novell Client for Dos when using a
   Packet Driver or configure the Novell Client for DOS TCPIP module.

********************************************************************************

Q) How do I know which model of Ethernet Card is installed in my machine?

A) Many Ethernet manufacturers have utility programs that will detect
   the model and version of their cards. Go to their web site for more
   details. The -config option of both send and recv will scan the PCI
   bus for Ethernet Adapters. Each one found will be displayed.

********************************************************************************

Q) I have setup the Novell Client for DOS. I then added ODIPKT.COM.
   When I execute these utilities, they seem to hang for long periods
   of time.

A) Check that you have configured the wattcp.cfg configuration file.
   Also check that this file is located in the current directory.
   Note: you can set the environment variable GHOSTIP=<filename>
   to set the full path name to the wattcp.cfg file.

********************************************************************************

Q) Do I need to configure the GATEWAY line in wattcp.cfg?

A) No, if you do not have a router installed on your network.
   Yes, if you do have a router installed on your network and you
   want to communicate with another machine on a different network
   segment.

********************************************************************************

Q) I am getting the following error message. What does it mean?

	50: BOOTP failed
	Error: TCP/IP Protocol Stack is not installed correctly.
	Error: Could not initialize the TCP/IP Protocol Stack.

A) The utility could not read the wattcp.cfg file or it was incorrectly
   formatted. The software then attempted to use the BOOTP protocol
   to dynamically obtain a TCP/IP address. A BOOTP server could not
   be found.

********************************************************************************

Q) I am getting the following error message. What does it mean?

	50: Network hardware unsupported, class=11
	Error: TCP/IP Protocol Stack is not installed correctly.
	Error: Could not initialize the TCP/IP Protocol Stack.

A) The Novell Client has not been setup to use the proper
   frame types for TCP/IP. You need to add the following line to
   your net.cfg file under the Link Driver line:

	Frame Ethernet_II

   Note: You will need to reboot your computer so that lsl can
   read the new net.cfg file.

********************************************************************************

Q) What should my net.cfg look like when I am using a packet driver?

A) The file net.cfg is not used when using Packet Drivers. However,
   when using ODIPKT.COM, then net.cfg is used. See the example above
   in section G.

********************************************************************************

Q) I am confused by net.cfg and wattcp.cfg. Which one do I need?

A) NET.CFG is used by the Novell Client for DOS. WATTCP.CFG is used
   by Packet Drivers. Both are used if ODIPKT.COM is installed.

********************************************************************************

Q) Which file does a packet driver read to get its TCP/IP parameters?

A) TCP/IP Stacks based upon the packet driver interface use the TCP/IP
   parameters in the wattcp.cfg file and ignore the TCP/IP parameter
   settings in net.cfg.

********************************************************************************

Q) How do I setup the a packet driver to use DHCP to setup my TCP/IP
   address parameters?

A) To obtain the TCP/IP parameters via DHCP, delete or rename the
   wattcp.cfg file.

********************************************************************************

Q) How do I setup the Novell Client with TCP/IP to use DHCP
   to setup my TCP/IP address parameters?

A) Modify your net.cfg to include the following line:
	IF_CONFIGURATION DHCP

   Supported options for the IF_CONFIGURATION parameter are: static,
   BOOTP, DHCP, RARP.

   Also see Section F above.

   Example:

# This example is used for the Novell Client for DOS for the
# 3COM 3c90x family of Ethernet Cards using DHCP to obtain
# the network address.

	IF_CONFIGURATION DHCP

	Protocol TCPIP
	    PATH TCP_CFG C:\NWCLIENT\TCP

	Link driver 3c90x
	    FRAME Ethernet_II

	Link Support
	    Buffers 8 1504
	    MemPool 8192

	NetWare DOS Requester
	    FIRST NETWORK DRIVE F
	    NETWARE PROTOCOL NDS BIND

********************************************************************************

Q) There are three types Novell Clients. The older NETX style, the VLM style
    and the newer client32 style. Which one is supported?

A) All of them. The examples above are for the NETX style Novell Client.
   To use the newer VLM client, follow the Novell installation and
   be sure to select TCP/IP option.

********************************************************************************

Q) I installed the 3COM Ethernet driver using 3Com's autolink utility.
   The send and recv reported a configuration error. What do I do next?

A) 3com's autolink utility installs a basic Novell Client without TCP/IP.
   You will need to do the following to enable TCP/IP:

	1) Edit the net.cfg file and add the following line under the
	   LINK DRIVER 3C90X entry:

		FRAME ETHERNET_II

	2) Add the following lines to your net.cfg (modify with your TCP/IP
	   address parameters):

		Protocol TCPIP
		    BIND 3c90x #1 Ethernet_II LAN_NET
		    IP_ADDRESS 192.34.131.90 LAN_NET
		    IP_ROUTER  192.34.131.66 LAN_NET
		    IP_NETMASK 255.255.255.0 LAN_NET

		Link Support
		    Buffers 8 1504
		    MemPool 8192

	2) Locate a copy of the TCPIP.EXE module and copy to your NWCLIENT
	   directory. Go to www.novell.com and execute a web search for the
	   file tcp1607.exe. Extract the files. Copy tcpip.exe to your
	   \novell\client32 directory.

	   As of 7/24/99 this file was at:
		ftp.novell.com/pub/update/cp/unixconn/tcp1607.exe

	   It is also located in the NetWare Service Pack 6a (iwsp6a.exe)
	   in the directory iwsp6a/misc.

	3) Add tcpip.exe to your autoexec.bat after the Novell Client.

	4) Execute send -config to verify that the stack is setup correctly.

********************************************************************************

Q) What happens if more than one packet driver is installed?

A) The packet driver with the lowest software interrupt number is selected.

********************************************************************************

Q) When I execute send.exe or recv.exe in a different directory then where
   the programs are installed it tries to use DHCP instead of reading the
   WATTCP.CFG file?

A) Currently these programs use the current working directory to locate
   WATTCP.CFG. Solution: set the environment variable GHOSTIP=<filename>
   to set the full path name to the wattcp.cfg file.

********************************************************************************

Q) When I execute the Novell Client TCPIP.EXE module I get the following error:
	FATAL: No LSL memory pool (minimum: 1024 bytes).

A) You need to add the following statements to your net.cfg file:

	Link Support
		Buffers 8 1504
		MemPool 8192

********************************************************************************
