This note describes an exciting electronic update to LAN WorkPlace 
for DOS that greatly simplifies the use of the dialup SLIP and PPP 
features provided in the original package for MS Windows users.

LWPDIAL.ZIP contains new and updated TCP/IP Transport modules that
comprise a complete WinSock v1.1 and LAN WorkPlace BSD Socket DLL
implementation with comprehensive and automatic dialup networking
support.  While LWPDIAL.ZIP contains all the necessary files to run
generic "WinSock" applications via PPP or SLIP, it is provided and
supported for LAN WorkPlace licensees only.  The following files 
are up-to-date versions of files supplied with LAN WorkPlace for 
DOS v4.1X and v4.2:

CONTENTS --

     tcpip.exe       \net\bin     TCP/IP kernel
     vtcpip.386      \net\bin     Virtual TCP/IP Interface
     wlibsock.dll    \net\bin     Original Novell Windows Sockets DLL
     slip_ppp.com    \net\bin     Serial ODI driver (SLIP & PPP frames)
     lwputil.dll     \net\bin     LWP application coordinator DLL
     winsock.dll     \net\bin     WinSock v1.1 DLL (released post-v4.1)
     novasync.exe    \net\bin     (released post-v4.1)
     iptunnel.exe    \net\bin     IPTUNNEL (IPX over UDP/IP) ODI driver
     ipxodi.com      \net\bin     IPXODI.COM v2.20
     ping.exe        \net\bin     basic DOS ICMP echo test
     ping.msg        \net\bin     ping message file

These files contain significant updates to previous versions, and 
are tested to work as a set.  Problems may occur if an older 
version of one or more of these files is located elsewhere on your 
system.  Note that if you are now happily using the SLIP_PPP.COM ODI
driver that ships with LAN WorkPlace for DOS v4.X, you may wish to 
make a backup copy of that driver before applying this update.

The following files are new with this release:

     slpmon.exe      \net\bin     VxD for Serial ODI to Windows API
     slpapi.dll      \net\bin     DLL interface for Modem access via ODI
     dialer.exe      \net\bin     Dialer Main Program
     dialer.hlp      \net\bin     Dialer Help file
     mdmapi.dll      \net\bin     Modem API Linkage DLL
     config.exe      \net\bin     Initial Configuration Program
     config.hlp      \net\bin     Initial Configuration Help file
     codes.dlr       \net\hstacc  International Area Code database
     aiomdms.mdc     \net\hstacc  Modem Definition Script collection

Note:	Files located in \NET\HSTACC are there because that's the default
	path for the "PATH LWP_CFG" variable in the "Protocol TCPIP" 
	section of NET.CFG.  If the "PATH LWP_CFG" variable points to 
	a different path or series of paths (e.g. "c:\net\hastacc;n:\share"), 
	that is where the dialer will look for these files.  If you do
	not see a list of supported modems when performing the initial
	configuration of the Dialer, it is likely that the "PATH LWP_CFG"
	setting in NET.CFG is pointing to the wrong place, or that you
        simply neglected to load TCPIP.EXE prior to starting Windows.

Finally, the following files are included as documentation and 
example configuration files:

     lwpdial.txt     \net         This file
     lan.cfg         \net         Example NET.CFG for LAN usage
     modem.cfg       \net         Example NET.CFG for Modem usage
     both.cfg        \net         Example NET.CFG using LAN *and* Modem
     autoexec.txt    \net         Example AUTOEXEC.BAT using above options
     choice.com      \net         Novell DOS 7 "Choice" command (used by
                                  example AUTOEXEC.BAT menu), not needed for
                                  MS- or PC-DOS 6.x or Novell DOS 7 users.
     *.*             \net\tcp     TCP/IP database files.  Some are renamed 
                                  to avoid overwriting your originals
          
                        
The Dialer
----------

The Dialer is an MS Windows utility program that establishes connections
for you between your workstation and network dial-in services on TCP/IP
networks.  The Dialer opens connections by dialing in over telephone
lines using your workstation's modem.

Once connected, you can use any combination of LAN WorkPlace or WinSock-
based networking applications to communicate over the network.  You can
also set up the Dialer to make connections automatically and to answer
incoming calls.

The Dialer is documented to a great extent within the MS Windows help
system.  Should you desire additional information, an on-line DynaText
Manual is also available for download (or soon will be).

Programmers and advanced users can control the Dialer through the use 
of DDE.  See DialDDE.WRI for details.

Note that the use of the Dialer requires that MS Windows requires
that Windows be run in "386 Enhanced" mode.


INSTALLATION --

Extract all files to the appropriate LAN WorkPlace directories.  
The preferred method for doing this is to make the LWP base directory 
the current one:

	C:\NET> pkunzip -d d:LWPDIAL.ZIP

Note the "-d" option to PKUNZIP.  LWPDIAL.ZIP contains sub directories,
and using this switch restores the files to the correct sub directories
under \NET\.  To overwrite the preexisting files without confirmation,
use the "-o" (overwrite) switch as well. 


SYSTEM FILE CHANGES:

NET.CFG
-------

For SLIP or PPP usage, your NET.CFG file should resemble this example, 
which is explained within the subsequent text:

		Link Support
		     buffers 8 1500
		     mempool 4096 

                Link Driver SLIP_PPP
                     FRAME  PPP
                     ACCM   00000000
                     INT    3		(set for your modem port)
                     Port   2F8			"	"
                     TCPIPComp VJ    

		Protocol TCPIP
		     path lwp_cfg c:\net\hstacc  
		     path tcp_cfg c:\net\tcp;z:\etc
		     path script  c:\net\script
        	     path profile  c:\net\profile 
		     tcp_window   4096

The "Link Support" section allocates ODI receive buffers and
a memory pool for staging data to be sent.  These are used by
TCPIP.EXE.  You may reduce the number of buffers if memory is
an issue.  More buffers than in the above example are rarely
useful.	 Please refer to the TCP/IP Transport documentation for
more details.

The purpose of the "Link Driver SLIP_PPP" section in the 
example	is to:

  1.)  Identify the COMM Port "INT" and "Port" values to use when
       SLIP_PPP is loaded in the default "COMMOwner" mode, usually:
	
       COM1 - Port 3F8
              Int  4
       COM2 - Port 2F8
              Int  3
       COM3 - Port 3E8
              Int  4
       COM4 - Port 2E8
              Int  3

       (the example above shows COM2)

       These values are unnecessary and are overridden by the Dialer 
       later if you're using "WinCOMM" mode (load "slip_ppp /w").  See
       the section on "Operational Information" for details about the
       various modes of operation.

  2.)  Specify an initial frame type of PPP.  TCP/IP can 
       load and bind to a PPP frame assuming that an IP address
       will be assigned via the driver at a later time.  If you
       plan to use SLIP rather than PPP, the Windows Dialer will
       allow for this regardless of the PPP frame type listed in 
       NET.CFG -- so don't worry.
			

The "Protocol TCPIP" section needs to:

  1.)  Set directory path location pointers for:

       "path tcp_cfg"  Location of TCP/IP Transport database files (hosts, 
                       networks, services, protocol and resolv.cfg files)
       "path lwp_cfg"  Used by upper-layer applications to locate public 
                       and private versions of various files (Dialer looks 
                       for modem definition files here, for example).
       "path script"   Used by Dialer (and others) to store / share scripts.
       "path profile"  Used by other LWP applications to store / share 
                       profiles.  This value is not used by Dialer.

  If multiple directories are listed, the applications will search each 
  sequentially to locate required files.  As in the example, multiple
  paths are delimited with semicolons ";".

  2.)  Configure non-default TCP/IP settings such as TCP window size,
       number of TCP or UDP sockets, etc.  Refer to the TCP/IP Transport
       manual for more details.
       
It is not necessary to specify an IP address, subnet mask, or default
router in NET.CFG when using the SLIP_PPP driver.  These settings, as
well as DNS settings, will be set as needed through the Dialer or by 
the remote router at connect time.


AUTOEXEC.BAT 
------------

The TCP/IP Transport and PPP drivers are loaded into memory using 
the following batch-file-ready sequence:

     cd D:\   <change to directory with LSL.COM and NET.CFG>
     lsl 
     slip_ppp
     tcpip

The LAN WorkPlace for DOS installation creates "LANWP.BAT", and
edits AUTOEXEC.BAT to call this batch file.  You may decide to 
edit LANWP.BAT, or refer to the example AUTOEXEC.BAT file which 
is included in the root directory of LWPDIAL.ZIP as "AUTOEXEC.TXT".  
This is a much more elaborate example that presents a menu of 
various configuration options and bypasses LANWP.BAT altogether.


SYSTEM.INI
----------

The TCP/IP kernel (TCPIP.EXE) will request of MS Windows to load 
VTCPIP.386 when Windows is started in "386 Enhanced" mode.  This
means it is no longer necessary to have the "device=vtcpip.386"
line added to the SYSTEM.INI.  However, VTCPIP.386 must be in the 
DOS/Windows search path so that it can be loaded by Windows, and 
older copies of this file should be eradicated.

Also, when using the driver in it's default "COMMOwner" mode, 
watch out for SYSTEM.INI entries under the [386Enh] section
specifying the Port and Interrupt values of your modem's COMM 
port.  Remove lines such as the following:

        [386Enh]
        COM2Irq=3
	COM2Base=02F8

These lines are most frequently inserted as a result of playing
with the Control Panel's "Ports" --> "Settings" --> "Advanced" 
values, and can be removed using a text editor, or by changing the 
"Advanced Settings for COMn:" values for Port and IRQ to "Default"
using the Control Panel.  These settings are nonexistant by 
default, and need only be in place if you're running using non-
standard serial port hardware settings.  Such settings are not
a problem if using the "WinCOMM" mode of operation.  (see the
section on "Operational Information" regarding these different 
modes of operation).


CONFIGURING THE DIALER
----------------------

Once LSL.COM, SLIP_PPP.COM and TCPIP.EXE have been loaded, you
can start MS Windows and configure the Dialer.  The first step
is to add the Dialer to the LAN WorkPlace program group.  

The first time the Dialer is run on your system, the configuration 
program (\NET\BIN\CONFIG.EXE) is launched.  The screens are 
fairly straight forward, instructions are provided in addition
to extensive online help.  The Dialer Configuration program will 
create an initial entry in the Dialer's "Connection Directory".  
Editing this entry, or creating new entries is a straight forward 
process for somewhat experienced MS Windows users.

Users with V.42bis, or other data-compressing modems may wish
to specify an alternate "baud rate" by editing their Connection
Directory entry, and selecting "Port Settings".  The default
values assume "safe" settings for computers with low-speed UARTs
and less capable CPUs.

The Dialer provides a very basic scripting language that can 
automate the ASCII login process required by many dial-up routers.
To "Auto-Record" a script, simply Edit the Connection Directory
entry and type the name of a new script in the "Script" field.  
Click on "OK" to save the entry, and then IMMEDIATELY dial the 
connection entry to record the script...  

  Note:  If you don't execute the dialing of the entry immediately 
  after entering a new script name, the script name will be forgotten 
  and the Auto-Record will not occur (this rather odd misbehavior 
  should be changed in a future release when the auto-record feature 
  is made more obvious).

Once connected to your dial-in Router, the title bar of
the Login Window should indicate that your script is being 
recorded.  If your newly recorded script contains a password, you
may "password protect" the usage of your script through the Dialer's
Script menu.  Scripts are NOT stored on disk in clear text format.


Operational Information
-----------------------

The SLIP/PPP ODI driver and MS Windows-based Dialer can operate
in one of TWO MODES:

     *  (the default) "WinCOMM" mode makes use of the MS Windows serial
        communications driver (COMM.DRV), and therefore suffers from the
        inherent limitations of the Windows serial line drivers.  
        Nonetheless, there are some advantages to running in this 
        mode:

             -  Windows-based applications such as FAX drivers and
                standard communications packages can use your modem when
                it's not being used for a PPP or SLIP network connection.

             -  PCs with the less-capable National Semiconductor 8250
                or 16450 UARTs may actually perform better in this mode.

             -  The automatic disconnect feature only works in this mode.

             -  The little LED-like "lights" on the Mobile Monitor Icon 
                blink like a modem's Carrier Detect, Transmit and Receive 
                lights in this mode (see the section about "SLPMON.EXE").  
                This Icon is not updated in COMMOwner mode.

        Since some applications may access the network in such a way as
        to prevent the Windows System VM and COMM drivers from delivering
        data, lockups may occur in this mode (rarely).  This is usually
        an indication of a flaw in a Windows application, but is a fact
        of life with certain DOS applications and network redirectors.
        If you experience difficulties running in "WinCOMM" mode, try the
        "COMMOwner" mode instead.

     *  (the alternate) "COMMOwner" mode, the ODI driver takes full
        control of the serial port that your modem is connected to and
        hides the port from the Windows COMM drivers -- this mode enables
        DOS-based TCP/IP applications to operate reliably in Windows' DOS
        boxes, and enables Windows applications that make heavy use of
        blocking network operations to work well over serial lines.  This
        mode of operation is required if one wishes to use the NFS Client
        provided in LAN WorkPlace for DOS v4.2 over SLIP or PPP, for 
        example.  

        In "COMMOwner" mode, it is possible to exit and renter MS Windows
        without affecting the state of a SLIP or PPP connection.
        
        In "COMMOwner" mode, the SLIP_PPP.COM ODI driver hides the
        COMM port that it's aimed at by removing record of it from the 
        BIOS.

	To load SLIP_PPP.COM in "COMMOwner" or "Exclusive" mode, use
	the /E command-line option, like so:

		C:\NET> slip_ppp /e
	
	Note:  SLIP_PPP.COM will automatically switch to COMMOwner
	       mode if IPTUNNEL.EXE is loaded subsequent to SLIP_PPP
	       (since NetWare Client access requires IPTUNNEL and 
	       COMMOwner mode at present).


Modem Control Files
-------------------

The latest collection of Modem definitions in "AIOMDMS.MDC" are
available on FTP.Novell.COM in /pub/netwire/novlib/01/nwcmod.exe.

This file is common to NetWare Connect (both Server and Workstation)
as well as the Windows Dialer.  The version in LWPDIAL.ZIP is 
current as of today - May 12, 1994.

 
SLPMON.EXE
----------

SLPMON.EXE is a Windows VxD that monitors the state of the dialup
network connection and (in conjunction with SLPAPI.DLL) provides
a means for the Dialer to communicate with the modem.  SLPMON is
loaded automatically when Windows starts in 386 Enhanced mode whenever
SLIP_PPP.COM is resident.  

Normally, SLPMON works invisibly, but it can be made visible by 
adding the following lines to your LWP.INI file (normally found
in \NET\HSTACC\LWP.INI):

        [SLPMON]
        Visible=True

This LWP.INI setting will cause SLPMON.EXE to become visible as
an icon.  When SLIP_PPP.COM is loaded in "WinCOMM" mode, the icon
can simulate the transmit and receive LEDs of your modem.  When
"Restored" or "Maximized", SLPMON provides information through
various menu picks that may be useful for troubleshooting purposes.

Most users will not want to be bothered by a visible SLPMON.EXE, but
it can provide useful information and statistics when troubleshooting.
Apart from these notes, a visible SLPMON.EXE is an "undocumented 
feature".


NOTE TO IBM THINKPAD USERS
--------------------------

Certain IBM ThinkPads with PC-DOS and Windows come pre-configured to
load a TSR called "FUELDOS".  This driver interferes with the Dialer
driver files and should not be loaded (note that it is not needed 
for the Windows-based power management features of the ThinkPad).


NetWare Client
--------------

NetWare Client access over SLIP or PPP will not be supported until 
the next release of the NetWare DOS Requester and most likely only in 
"COMMOwner" mode. 


Support
-------

These files (or slightly modified versions) will be made available
on NetWire (CompuServe) and FTP.Novell.COM in the near future (by
June, 1994).  At that time, the Dialer and corresponding drivers 
will be supported through normal Novell support channels just as all 
other elements of LAN WorkPlace are today.  In the meantime, please
send all bug reports or queries regarding this software and 
documentation via Internet mail to: "lwpdial@novell.com".  

Thank you!
