README.TXT for WanderLink PPP Client Release 2.11  (11/29/95)
========================================================================
WanderLink Client
README FILE

Funk Software, Inc.
222 Third Street
Cambridge, MA  02140
========================================================================
(617) 497 6339    (Phone number)
(617) 491-6503    (Technical Support)
support@funk.com  (Internet address for support)
www.funk.com      (World Wide Web URL)

========================================================================
NOTES ON THE WANDERLINK CLIENT
========================================================================

This file provides important information not included in the 
WanderLink Client manual.
 
This file is divided into the following sections: 
 
1. Special WanderLink Support for IP Stacks
   1.1  TGV IP stack
   1.2  LAN Workplace IP stack

2. Troubleshooting 
   2.1  Connection Problems
   2.2  Problems attempting to log in to servers
   2.3  Problem seeing NetWare 3.x server through Domain Filter
   2.4  Throughput problems

3. Tips and Miscellaneous Information 
   3.1 Sharing your COM port with other programs 
   3.2  Printing help files
   3.3  Using VLM 1.20

4. Integrating WanderLink access with existing programs
   4.1  Connecting and disconnecting within Lotus Notes
   4.2  Launching WanderLink within Microsoft Office
   4.3  Launching within Novell NetWare Tools

5. Using WanderLink with Windows for Workgroups (WFW)  

6. Using WanderLink with Windows 95
   6.1  Using the Windows 95 PPP Client
   6.2  Using the WanderLink Client with Windows 95

7. Customizing the WanderLink Client installation
   7.1  Adding New Files
   7.2  Adding New Connections
   7.3  Adding New Icons
   7.4  Modifying or Adding New .PIF or .BAT files
   7.5  Changing Group Names, Default Selections, and Directories

8. Restrictions 
   8.1  Simultaneous connections to local and remote networks 
   8.2  Unloading WLODI.COM 


========================================================================
1.  Special WanderLink Support for IP Stacks
========================================================================
This section describes how WanderLink provides direct integration to
specific TCP/IP stacks.  The stacks listed here are not able to use
RARP or BOOTP to obtain dynamically allocated IP addresses.
WanderLink makes direct calls or changes to the stack setup once a PPP
connection is made to set the local IP address, and router (peer)
address of the server.

------------------------------------------------------------------------ 
1.1  TGV IP stack
------------------------------------------------------------------------ 
The TGV IP stack will be supported if the following parameter appears in
the [Settings] section of WLINK.INI:

	TGV=n
	
	where n is a non-0 value indicating the TGV interface number.

Usually, this entry is set to TGV=1.

Upon connection the MULTINET.INI file will be written with data to set
up the stack. The [InterFace 1] (the "1" may be any non-0 value and is
taken from n) section is written with the following values:

	Enabled=1
	IPAddress=a.b.c.d
	
	where a.b.c.d is the negotiated local address.

The [Routing] section is written with:

	DefaultGateway=r.s.t.u
	
	where r.s.t.u is the negotiated peer (server) address.

Note that if the TGV stack is loaded when the connection is made,
this won't work because it is too late -- the stack already obtained
its parameters from the MULTINET.INI file. This implies that if any
IP apps are running, they should all be closed down prior to making a
connection when a dynamic IP address is to be assigned.

------------------------------------------------------------------------ 
1.2  LAN Workplace IP stack
------------------------------------------------------------------------ 
The LAN Workplace stack is supported by WanderLink when either WLINK.EXE
or WLINKW.EXE detects LAN Workplace is present (this occurs if TCPIP.EXE
is loaded).  If LAN Workplace is loaded, WanderLink calls LAN Workplace
directly to set the local IP and peer (server) addresses based on the
result of the PPP negotiation.

The [Settings] section of WLINK.INI may contain the entry LanWP=0, but
this is only required if you wish to disable the LAN Workplace stack
detection and IP address updating.  Normally, you should not have to
actively disable this feature.


========================================================================
2.  Troubleshooting 
========================================================================
This section describes how to deal with problems that may occur while 
using WanderLink.

------------------------------------------------------------------------ 
2.1  Connection problems
------------------------------------------------------------------------ 
If you are having trouble making a connection with WanderLink, one of 
the following may be the problem:

   -    You haven't loaded the WanderLink ODI driver (WLODI.COM). 

	If the driver is not loaded, the Status line at the bottom of 
	the screen will indicate "Driver Not Loaded".

   -    You haven't selected the correct modem in the Setup dialog. 

	Check the Setup dialog. If the modem is incorrect, you may get 
	a "Modem error" when trying to connect. Also, listen for the 
	telltale sounds the modem makes while picking up the phone, 
	dialing, etc.

   -    You haven't selected the correct COM port in the Setup dialog. 

	If you haven't, you will hear no sounds from the modem since 
	no data is being sent to it. Also, you may get a "Timeout" 
	error after trying to connect.

   -    Your modem and the server's modem have compatibility problems. 

	This can result in various errors when attempting to connect. 
	One common problem is that different modems try to negotiate 
	v.42bis and MNP in different orders. You may need to modify 
	your modem's command strings to force it to negotiate in a 
	manner compatible with the modem to which you are trying to 
	connect.  

   -    There is a high error rate over your serial port. 

	If the error rate is too high, you may get an error when 
	attempting to connect. Even if you do connect successfully, 
	the throughput of the connection may suffer. Check the Port 
	Statistics dialog for error rates. The ratio of "Rx errors" to 
	"Rx total" should be at least 1 in 1,000; ideally it should be 
	1 in 10,000 or better. If this seems to be a problem, lower 
	your baud rate.

------------------------------------------------------------------------ 
2.2  Problems attempting to log in to servers
------------------------------------------------------------------------ 
If, once you've established a WanderLink connection, you have problems 
initially attaching to a remote access server or you have problems 
logging in to a server, it may be due to one of the following causes:

   -    The Remote Access Server may be improperly configured.

	One typical problem is that the remote access server has not
	been configured for IP or IPX. For a WanderLink server,
	this would happen if a BIND was not made to IP or IPX. For
	other remote access servers, the configuration for IP or IPX
	may have been incorrect. This will prevent all communication
	with the network. Contact your administrator.

   -    Your access to the network may be restricted.

	Your administrator has the capability of limiting your access 
	to particular addresses on the network. If you attempt to 
	attach a server to which you have no access, you will be 
	unsuccessful. For a WanderLink server, this can be the result
	of Domain Filtering.

------------------------------------------------------------------------ 
2.3  Problem seeing NetWare 3.x server through Domain Filter
------------------------------------------------------------------------ 
You may have a problem seeing NetWare 3.x servers, if you are using
Domain Filtering and NetWare 4.x servers are also on the network.

The symptom of this problem is a long delay and the inability to 
connect to NetWare 3.x servers.  If you make a WanderLink connection,
then load VLMs, you will see the message:

	"You are attached to server "

Normally, the line would indicate the name of the server you are
attached to.

This condition only occurs if:

   1    The WanderLink server has a domain filter restriction which
	only allows access to NetWare 3.x servers.

   2    The WanderLink Server is running on a 3.x server.

   3    NetWare 4.x servers also reside on your network.

   4    Your NET.CFG file contains the following line:

		Netware Protocol = NDS BIND

	or no NetWare Protocol section (which defaults to NDS BIND).

The "NDS BIND" order in the NetWare Protocol line instructs VLMs
to use a Directory Services connection as a primary preference.  To
resolve this problem, change the line to read:

		Netware Protocol = BIND NDS

------------------------------------------------------------------------
2.4  Throughput problems
------------------------------------------------------------------------ 
If throughput seems slow, it may be due to one of the following causes: 

   -    You are using NETX, and not VLM for NetWare connections 

	Using NETX will cause significant slowing of file transfers.
	You should always use the latest VLM for connecting to Novell
	servers.

   -    There is a high error rate over your serial port. 

	Check the Port Statistics dialog for error rates. The ratio of 
	"Rx errors" to "Rx total" should be 1 in 10,000 or better for 
	maximum throughput. If this seems to be a problem, lower your 
	baud rate.

   -    Your serial port's baud rate is too low.

	You can't send or receive data any faster than your baud rate. 
	If your baud rate is set too low, it may limit the throughput 
	of your connection. However, you don't want to set it so high 
	that a high error rate occurs.

	On a reasonably fast machine with a 16550 UART, you should be 
	able to set your baud rate to the maximum (115200 bps) without 
	a problem.

   -    You may be running programs from a network drive.

	Try to run local copies of programs so the program does not 
	have to be transported over the phone line. Make sure you have 
	local copies of programs such as LOGIN, ATTACH, and MAP so you 
	can make network connections quickly.
	
========================================================================
3.  Tips and Miscellaneous Information 
========================================================================
------------------------------------------------------------------------ 
3.1  Sharing your COM Port with Other Programs 
------------------------------------------------------------------------ 
WanderLink supplies a VxD (WLODIV.386) that optimizes serial
communication in Windows enhanced mode.  If WLODI.COM is loaded, the VxD
automatically loads when you start Windows.  WanderLink will properly
share the COM port, in most cases, with other Windows applications.

------------------------------------------------------------------------ 
3.2  Printing Help Files 
------------------------------------------------------------------------ 
WanderLink Help provides a handy tool for printing help files called the
Navigator. To print out the entire help file, do the following:

   1    Access WanderLink Help. 

   2    Press the Navigator button. The WanderLink Navigator screen
	appears. 

   3    Press File Print and the Print popup dialog appears. 

   4    Choose All Topics and Press OK. The entire help file is then sent 
	to your printer. 

You can also choose to print just the current topic or the current topic
and its subtopics. 

------------------------------------------------------------------------ 
3.3  Using VLM 1.20
------------------------------------------------------------------------ 
You should always use the new NetWare Client (VLM 1.20), which is 
included with the WanderLink Client.

Unlike previous versions, VLM 1.20 will display error messages
whenever you disconnect from a WanderLink connection, and then try to
re-connect to a different network. You will be prompted to "Retry or
Cancel" for these network errors; you should always answer "Cancel."

========================================================================
4.  Integrating WanderLink access with existing programs
========================================================================
This section contains instructions on how to add icons to the toolbars
of the following applications:

   -    Lotus Notes.  Adds two icons to your Lotus Notes toolbar: the
	WanderLink Launch icon, which launches WanderLink, and the
	WanderLink Disconnect icon, which terminates a connection.

   -    Microsoft Office. Adds a WanderLink launch icon to the
	Microsoft Office toolbar.

   -    NetWare Tools.  Adds a WanderLink launch icon to the NetWare
	Tools toolbar.

These procedures show how to add icons that launch the WanderLink
Windows Client program.  If you want to create an icon that launches
WanderLink and establishes a remote connection, you must specify the
name of a batch file instead of the WLINKW.EXE program.  For more
information about creating and using batch files, refer to the
documentation. 

------------------------------------------------------------------------ 
4.1  Connecting and Disconnecting Within Lotus Notes
------------------------------------------------------------------------ 

4.1.1  Benefits
------------------------------------------------------------------------ 
Remotely connecting to Lotus Notes via WanderLink offers a number of
benefits over remotely connecting using the Remote Notes feature.

The benefits of WanderLink for remote access to Notes include:

   -    Access to all Notes servers.  

	Remote users dialing in with WanderLink have full access to 
	all Notes servers on the network. Remote users are no longer 
	limited to connecting to one Notes server at a time.

   -    Access to the rest of the network as well.

	The same WanderLink connection you use to access Notes servers 
	can be used to access file servers, network printers, E-mail, 
	etc.

Once you have set up Notes for remote access, you can then read and
respond to mail and perform any other database operations.  You can 
use Notes' powerful "Replication" feature to create mail off-line, then
connect with WanderLink to only send and receive mail.

4.1.2  Before You Start
------------------------------------------------------------------------ 
Before using WanderLink to access Notes, you should first install Notes
on your remote workstation, then replicate all databases you want to
access.  The first time you replicate, you may want to be directly 
connected to the LAN.  This will speed up the process.

Make sure that you have set up WanderLink to connect from Windows.
If you have not already done this, you will need to exit from Windows
and load the WanderLink drivers.  See Chapter II-4 of the WanderLink
documentation for instructions.

You need to create a WanderLink connection called "NOTES".  This
connection should dial up the WanderLink server on the Notes network
that you wish to access.  The "NOTES" connection will be invoked
by the supplied Notes macro file (WLINK.MAC).

If you are using NETBIOS to run Notes, remember to modify your
LOADVLM.BAT file to load NETBIOS directly after IPXODI.

4.1.3  Adding the WanderLink Launch Icons to Lotus Notes
------------------------------------------------------------------------ 
To add the WanderLink Launch icon to the Lotus Notes toolbar, do the
following:

   1     Copy the following files from your WanderLink directory
	 to your NOTES\WIN subdirectory:  WLINK.BMP, WLINK.MAC,
	 WLINKD.BMP, and WLINKD.MAC.

   2     Start Notes.  Within Notes, select Tools, then SmartIcons.

   3     Scroll to the end of the Available icons list on the left.

   4     Select the WanderLink Launch icon. (It is a yellow bolt on a
	 purple background.)

   5     Drag and drop the icon into the Default Set list on the right.
	 We recommend you place it near the File Save icon.

   6     Click on the WanderLink Launch icon in the Default Set list.

   7     Press Edit Icon. The Edit SmartIcons window appears.

   8     In the Description field, type WanderLink Launch.

   9     Press Formula. The SmartIcons Formula window appears.  In the
	 formula window, you will see the following entry:

		 @Command([Execute]; "c:\\wlink\\wlinkw.exe"; "NOTES")

	 If necessary, edit the command line to change the WanderLink
	 default directory (initially set to c:\wlink), or to add a
	 connection name after the 'wlink.exe' string.

  10     Press OK, Done, and OK.

  11     Click on the WanderLink Disconnect icon in the Default Set
	 list.

  12     Press Edit Icon. The Edit SmartIcons window appears.

  13     In the Description field, type WanderLink Disconnect.

  14     Press Formula. The SmartIcons Formula window appears.  In the
	 formula window, you will see the following entry:

		 @Command([Execute]; "c:\\wlink\\wlinkw.exe"; "/d")

	 If necessary, edit the command line to change the WanderLink
	 default directory (initially set to c:\wlink).

  15     Press OK, Done, and OK.

You can now launch WanderLink within Notes by pressing the WanderLink
Launch icon.  This will use the "NOTES" connect that you have 
previously defined in WanderLink.

You can disconnect WanderLink within Notes by pressing the WanderLink
Disconnect icon.

------------------------------------------------------------------------ 
4.2  Launching WanderLink Within Microsoft Office
------------------------------------------------------------------------ 
You can add the WanderLink icon to the Microsoft Office toolbar.
Pressing the icon will launch WanderLink, automatically dialing in and
establishing your remote connections.  The following procedure shows
how to add the WanderLink icon, however, you can also add the WanderLink
name to the Microsoft Office menu.  For information about this procedure,
refer to your Microsoft Office documentation.

To add the WanderLink icon to the Microsoft Office toolbar, perform the
following:

   1    Start Microsoft Office.

   2    Press the Microsoft Office button. When the drop-down menu
	appears, select Customize.

   3    Select the Microsoft Office Toolbar. 

   4    Press Add.

   5    In the Description field, type WanderLink. 

   6    In the Command Line field, type the complete pathname of the
	WanderLink Client windows program, i.e., C:\WLINK\WLINKW.EXE.

   7    In the Working Directory field, type the name of your WanderLink
	directory, i.e., C:\WLINK.

   8    Select Application Icon from the Button Image list box. 

   9    Press OK.  The X should appear in the Wanderlink box. Press OK
	again to complete the setup.

------------------------------------------------------------------------ 
4.3  Launching Within Novell NetWare Tools
------------------------------------------------------------------------ 
You can add the WanderLink icon to the NetWare Tools toolbar.  When you
click on the icon, WanderLink launches.  This will automatically dial in
and establish your connection to the remote server.

To add the WanderLink icon to the NetWare Tools toolbar, perform the
following steps:

   1    Start NetWare Tools.

   2    Press User Defined button 1 by pressing [Alt]-1.  The command
	line box will appear.

   3    In the Command Line field, type the complete pathname of the
	WanderLink Client program, i.e., C:\WLINK\WLINKW.EXE.
	The WanderLink Client Connections screen appears.

   4    Configure WanderLink the way you want and press Exit.

To add the WanderLink "Disconnect" icon to the NetWare Tools toolbar,
perform the following steps:

   1    Start NetWare Tools.

   2    Press User Defined button 2 by pressing [Alt]-2.  The command
	line box will appear.

   3    In the Command Line field, type the complete pathname of the
	WanderLink disconnect program, i.e., C:\WLINK\WLINKWD.EXE.
	The WanderLink Disconnect box appears.

The next time you invoke NetWare Tools, the WanderLink disconnect
icon will appear on the toolbar.  You can invoke a WanderLink 
disconnect by pressing the button (a WanderLink icon with a red
slash through it). 

========================================================================
5.  Using WanderLink with Windows for Workgroups (WFW)
========================================================================
WFW has a number of built-in networking features.  Because of this, you
will need to carefully configure WFW to work correctly with WanderLink.
This section outlines the steps you need to follow.

   1    Install the NetWare Client (VLM 1.20), by running the WanderLink
	installation and checking "Novell NetWare Files", or by using
	the NetWare installation disk.

   2    Launch the WFW Network Setup and click on the Networks button.
	Choose "Install Windows support for the following network only".
	
   3    Choose Novell NetWare (Workstation Shell 4.0 and above).

   4    WFW will give you an option to copy new files over.  Answer
	"No" and close.

An alternative to the above is to select "No Windows support for
networks" from the Networks button in the WFW Network Setup.  This
instructs WFW that you are on a stand-alone machine with no networking
capabilities.  Choosing to install VLM's in the WanderLink
install will override this setting and install the appropriate drivers
and make the necessary changes to the INI files.  However, this
is not recommended since the Network Setup dialog may not match 
your system initialization (INI) files.

Another alternative is to "Install Microsoft Windows Network", which 
is a peer to peer network that supports NDIS based protocols (however,
Novell only supports ODI based protocols).  This option also contains
a subsection that allows you to install an additional network, which
usually contains either NetWare 3.x or NetWare 4.x drivers.  What WFW
does to make NDIS and ODI work together is to map ODI calls to NDIS
calls, which is done through a "shim" called ODIHLP.EXE.  This option
appears to work, but you may see error messages when starting Windows
and your peer to peer functionality will probably not work.

========================================================================
6.  Using WanderLink with Windows 95
========================================================================
You can access a WanderLink server from Windows 95 in two main ways:

   1    Install the Windows 95 built-in PPP Client, and use with
	the Windows 95 NetWare Client.

   2    Install the WanderLink Client, and use it in 16-bit mode along
	with the Novell VLM 1.20 client.

------------------------------------------------------------------------ 
6.1  Using the Windows 95 PPP Client
------------------------------------------------------------------------ 
By using the Windows 95 PPP Client, you will be able to take 
advantage of Windows 95 PPP services.  This allows you to access both
IPX and TCP/IP based capabilities of the WanderLink server.  Since the
Windows 95 PPP client does not support advanced features of WanderLink
such as reliability, compression, and encryption, you will not be able
to use these features.  However, you will get the benefit of using the
Microsoft NetWare Client, which provides Windows-based logon script
processing for NetWare 3.x networks.

IMPORTANT NOTE:  Your WanderLink Administrator must allow you to 
connect using the PAP (Password Authentication Protocol), or you will
not be able to connect!

Configure the Windows 95 PPP Client:

   1    Bring up the Control Panel (Press [Start], then select 
	Settings -> , and then Control Panel). 

   2    Open the Network icon.

   3    Add the Dial-Up adapter.  Select the Configuration tab menu,
	then press [Add], and select Manufacturer "Microsoft" and
	Network Adapter "Dial-Up Adapter".

   4    Configure the Properties of the Dial-Up Adapter, and select
	the "Bindings" tab menu to turn on IPX/SPX or TCP/IP
	protocols.  Note that WanderLink does not currently support
	NetBEUI protocol.

Now, setup Microsoft's NetWare client:

   5    In the Control Panel Network section, add the Client
	Microsoft Client for NetWare Networks.

   6    Configure the client for the preferred server, first network
	drive, and automatic logon script processing option.  This
	will automatically perform your NetWare logon when you
	connect to the WanderLink server.

   7    Press [OK] to save all changes.  You don't have to reboot
	right now, but you will when you are all done to make the
	changes.

Finally, to make a connection:

   8    Select the "My Computer" folder, and select "Dial-Up
	Networking".

   9    Select "Make New Connection", and you will be prompted for
	information on your local modem, phone number to dial, 
	username, and password.  You can also create new connections
	in this way.

  10    Connect to a WanderLink server by double-clicking on a 
	connection you have created.

------------------------------------------------------------------------ 
6.2  Using the WanderLink Client with Windows 95
------------------------------------------------------------------------ 
By using the WanderLink 16-bit client in conjunction with Novell 
NetWare VLM 1.20, you can use all the advanced features of WanderLink
such as reliability, compression, and encryption.  In addition, you
will be able to access NetWare 4 NDS services using the DOS-based
LOGIN program or the NetWare Tools utility.

NOTE:  Funk Software is working on a Windows-95 native 32-bit client
which should be available by the first quarter of 1996.

First, make sure that the NetWare VLM 1.20 client is installed and
configured for use in Windows 95, and that you install WanderLink!

   1    Install NetWare VLM 1.20 from the Novell NetWare disk set on
	a NetWare 4.10 server, or from the WanderLink Client by
	selecting only the "NetWare Files" checkbox and a destination
	directory of C:\NWCLIENT.  Don't reboot right now.

   2    Run the WanderLink client installation (again), and this time,
	select the C:\WLINK destination directory.  Select both the
	"WanderLink Client" and the "NetWare Files" checkboxes.  
	SETUP will detect that the NetWare client was installed, and
	you should answer "Use current VLM" to the prompt.  You can
	setup the WanderLink settings now if you wish.

Next, Configure the Windows 95 Network Settings to use the Novell
NetWare client, an "existing ODI driver", and the Novell IPX ODI
driver.  This instructs Windows 95 to use the ODI driver that is
loaded in at startup time.

   3    Bring up the Control Panel (Press [Start], then select 
	Settings -> , and then Control Panel).  Click on Network.

   4    In Control Panel Network section, add Client ->
	Novell NetWare (Workstation Shell 4.0 and above VLM).

   5    If necessary, add Driver "Existing ODI driver".
	Select the Configuration tab menu, then press [Add], and
	select Manufacturer "existing ODI driver".

   6    If necessary, add the Protocol "Novell IPX ODI driver".
	Add Protocol, then select manufacturer "Novell", then
	select "Novell IPX ODI driver".

   7    Make sure that you don't have any other protocols or
	services configured that would conflict with the setup.

   8    To save your settings, press [OK].  This will likely go
	out to your Windows 95 CD-ROM (or request diskettes) to
	copy files, etc.  In addition, you may be prompted for
	network drivers (which you can skip), and the location
	of the IPXODI.COM file (you can use C:\WLINK).  At the
	end of this process, a reboot will be requested.  Don't
	reboot the computer quite yet.

Finally, update your AUTOEXEC.BAT file so that when you re-boot, 
you will be using the WanderLink ODI driver.  You can use MS DOS'
multiboot configuration, or do a straight-line boot.  The
following lines need to be in the AUTOEXEC.BAT (usually at the
very end of the AUTOEXEC.BAT) file:

	 C:\WLINK\DPMS.EXE
	 SET NWLANGUAGE=ENGLISH
	 CD \NWCLIENT
	 C:\NWCLIENT\LSL.COM
	 C:\WLINK\WLODI.COM
	 C:\NWCLIENT\IPXODI.COM
	 C:\NWCLIENT\VLM.EXE

Now, reboot your computer.  On startup, you will be prompted to
log into a network.  Press [Cancel] to get out of this, and
at any time later you should be able to use the WanderLink
client to make dynamic connections from Windows 95.  You can also
use third-party TCP/IP stacks supported by WanderLink.

========================================================================
7.  Customizing the WanderLink Client installation
========================================================================
The Client installation uses the standard Microsoft SETUP.EXE program.
Files are either normal (not compressed), or compressed.  A flat (i.e.,
no subdirectories) directory structure is used on all disks.  This
information pertains the Disk 1 of the client; Disk 2 contains the
NetWare VLM files.

------------------------------------------------------------------------ 
7.1  Adding New Files
------------------------------------------------------------------------ 
To add new files, or change existing files for distribution, you need to
update the .INF file, which contains a list of all files to copy.
Generally, you will want to copy your files when the user checks the
"WanderLink Client" checkbox.  To do this:

   1    Expand file SETUPC.IN_ by typing:
			EXPAND SETUPC.IN_ SETUPC.INF
   2    Edit the resulting SETUPC.INF file [Client] section.  This
	section contains all files copied with the "Client" box is
	checked.  For example, the line...
	      
	      1, guest.bat,,,, 1995-05-15,,,, !READONLY,,,,,, 253,,,,,
	
	... copies the file guest.bat, from disk 1, with the file date
	1995-05-15, size 253 bytes.
		
	When adding (or editing) lines, make sure that the date and file 
	size match that of the file(s) to be copied.

   3    Compress the SETUPC.INF by typing:
		
		COMPRESS SETUPC.INF SETUPC.IN_

   4    For every line you inserted in step 2 above, put that file on
	the distribution diskette.
	
	Note:  New files added can either be normal or compressed.
------------------------------------------------------------------------ 
7.2  Adding New Connections
------------------------------------------------------------------------ 
To create a new WanderLink connection in the WLINK.INI file for
distribution:

   1    Use a newly installed ('clean') copy of the WanderLink client.

   2    Run WLINK or WLINKW to create a connection, with the phone
	number, account, and connection options.

   3    Save and exit the WanderLink program.

   4    Edit the WLINK.INI file and remove the MACAddress= line in the
	[Setup] section.
	
	WARNING:  Failure to remove the MACAddress= line will propagate
	duplicate node addresses to any users of this disk!

   5    Copy the new WLINK.INI file to your master diskette.

------------------------------------------------------------------------ 
7.3  Adding New Icons
------------------------------------------------------------------------ 
To create a new icon, you must first have a connection (see above,
Adding New Connections).

Next, you can modify the ICONS.INC file, which creates the Windows icon
on the desktop at installation time.  You can remove the default icons
provided by Funk Software, and replace them with completely customized
icons.

See the ICONS.INC file for information and actual script code examples.

------------------------------------------------------------------------ 
7.4  Modifying or Adding New .PIF or .BAT files
------------------------------------------------------------------------ 
You may also wish to modify, or replicate, the existing BAT and PIF
files.  To change BAT files, simply expand, edit, and re-compress the
files as needed (see above "Adding New Files").  To modify PIF files,
you will need to run PIFEDIT from Windows, open the PIF file and then
save it.  PIF files do not generally change size, so you can change the
default GUEST.PIF file to your own requirements.

------------------------------------------------------------------------ 
7.5  Changing Group Names, Default Selections, and Directories
------------------------------------------------------------------------ 
The SETUPC.INC file contains default settings for the SETUP program,
such as the program's name, group name, default directory, etc.  With
the exception of the Installation Group information, you normally would
not want to change these values.

The following lists the contents of the SETUPC.INC file, with the default
shipped values.  Comments are in [brackets].

ClientName$ = "WanderLink"      [Name of the client]
ClientExe$ = "WLINK"            [Name for the executable file]
InstallGrpName$ = "WanderLink Client"   [Windows group name]
InstallGrpFile$ = "FUNK.GRP"    [Windows group file name]
InstallClient$ = "TRUE"         [Allow WanderLink client checkbox]
InstallNovell$ = "TRUE"         [Allow NetWare files checkbox]
InstallMaster$ = "TRUE"         [Allow Proxy Master checkbox]
InstallHost$ = "TRUE"           [Allow Proxy Host checkbox]
ClientDir$ = "C:\WLINK"         [Default Client install directory]
ProxyDir$ = "C:\PROXY"          [Default Proxy install directory]

========================================================================
8.  Restrictions 
========================================================================
The following restrictions apply when using the WanderLink Client. 
 
------------------------------------------------------------------------ 
8.1  Simultaneous Connections to Local and Remote Networks 
------------------------------------------------------------------------ 
The client workstation cannot have a local network connection (Ethernet,
token ring, etc.) as well as a remote WanderLink connection on the same
protocol (e.g., IPX). If you are already connected to a local network,
you need to log out and unload the network modules.

If you are already connected to a network, unload the network modules in 
the reverse order in which they were loaded.  For example, if you are
connected to the network using the NETX shell, you would unload the 
modules as follows:

	NETX /U         (unload NETX shell)
	
	IPXODI /U       (unload IPX ODI driver)
	
	NE2000 /U       (unload ethernet card driver)
	
	LSL /U          (unload link services layer) 
	
Now, you can reload the network modules using WanderLink.
 
------------------------------------------------------------------------ 
8.2  Unloading WLODI.COM 
------------------------------------------------------------------------ 
If you have loaded WLODI.COM in high memory with the "LH WLODI" command,
then it is possible to accidentally unload WLODI before unloading other
TSRs loaded after it (such as IPXODI.COM and VLM.EXE).  If you do this,
you will not be able to unload other TSRs loaded after WLODI.

Make sure you unload TSRs in the reverse order of loading them.  Use
the supplied batch files HANGUP.BAT or UNLOAD.BAT to do this.

