Product Release Notice

PathWay Runtime
Microsoft Windows Systems

Release 4.1.2
April 1996

Product names appearing in this notice are trademarks of their respective
manufacturers.
(C) 1982-1996 Attachmate Corporation. All rights reserved.

This README file includes important information about product features, 
limitations, and media contents. Please read this entire notice before you 
install the product.

After you have read this notice, please take a few moments to complete the 
registration card and return it to Attachmate. Doing so will make you 
eligible for the support services available for this product.

This README file provides information about PathWay Runtime Release 4.1.2.

PathWay Runtime provides the lower layer services that permit TCP/IP 
applications (such as TELNET) to function on your computer. Specifically, 
it provides the TCP/IP kernel and support for the associated device drivers.


Release contents

This release includes:

--  Product software: 
  --  PathWay  Runtime Setup: Two high-density 3.5-inch floppy diskettes
      (5.25-inch floppy diskettes are available upon request)

  --  PathWay Runtime documentation consisting of:
  --  PathWay Runtime Installation Guide
  --  PathWay Runtime User Guide
  --  PathWay Runtime Reference Guide
  --  Product Release Notice

PathWay Runtime provides the TCP/IP kernel and driver support for the following: 

--  PathWay Runtime applications (such as Dialer and Ping)
--  PathWay Application (includes Web browsing, News, Mail, FTP etc.)
--  PathWay Accessories (such as TELNET, Terminal Emulators)
--  PathWay Client NFS
--  Internet Access applications (such as Mosaic and Gopher)
--  Custom applications invoking the API functions developed using the 
    PathWay API Developer's Tool Kit 
--  Custom applications invoking the API functions, including Windows 
    Sockets

PathWay Runtime must be installed and configured before PathWay Runtime 
applications or PathWay API Developer's Tool Kit can be installed and used.


New features and enhancements
=============================

This section highlights some of the features available with this release 
of PathWay Runtime.

Supports 32 bit applications  over our 32 bit windows sockets API.

NetBIOS support over TCP/IP  to access remote applications.

NetBIOS Configuration manager.

The RECORD feature in dialer to record and generate scripts.

Support of authentication protocol CHAP in PPP.

DOS applications such as Ping, Telnet, FTP, TFTP, RSH, RCP and RDATE are
supported.


Supported platforms and systems
===============================

To install PathWay Runtime, you need this configuration for your PC:

--  Minimum 386 or compatible computer running Microsoft Windows 95,
    Microsoft Windows for Workgroups 3.11 or Microsoft Windows 3.1 (in 386
    Enhanced Mode)
--  EGA, VGA, SVGA, (or better) monitor 
--  A network interface card in your PC (Ethernet, Token Ring, or ARCNET) 
    or a modem (internal, external, or null-modem) for a SLIP, CSLIP or PPP 
    interface
--  4 MB of RAM minimum; 8 MB recommended
--  Approximately 3MB of disk space for PathWay Runtime 


PathWay Runtime has been successfully tested in the following shared 
environments:


--  Microsoft Windows for Workgroups 3.1 or 3.11, Windows 95
--  Novell NetWare 3.11, 3.12, or 4.1

The following asynchronous communications servers have been successfully 
tested with Attachmate's SLIP and PPP drivers (as appropriate) using the 
PathWay Dialer:

--  3Com's AccessBuilder 4.0
--  Livingston Portmaster 2E
--  Microsoft's Windows NT RAS 3.5
--  Telebit's NetBlazer ST 2.0


Special notes

--  If the machine is already running a third-party TCP/IP stack, it must 
    first be removed before PathWay Runtime can be installed properly. 


-- Windows 95/Windows 3.xx: 

   In order for PathWay Runtime to function properly on a machine running
   both the environments, it is recommended that PathWay Runtime be
   installed separately in both the environments and in different directories.

   Make sure there is just one copy of winsock.dll (and wsock32.dll for
   Windows 95) in the PATH. If you had installed Microsoft's TCP/IP, make
   sure you uninstall it and rename the files winsock.dll and wsock32.dll.
   


--  If you upgrade from Runtime 2.0 to Runtime 4.1.2 and then uninstall 
    Runtime 4.1.2, the original Runtime 2.0 functionality will not be 
    restored automatically. You may need to manually edit your AUTOEXEC.BAT 
    and CONFIG.SYS files and uncomment the Runtime 2.0 entries that were 
    commented out during the upgrade.

--  The previous version of PathWay Runtime, Release 2.0, included a 
    utility to de-allocate the TCP/IP kernel called pwtcprm. De-allocating 
    the TCP/IP kernel and most drivers in PathWay Runtime Release 4.1 is 
    accomplished simply by exiting Microsoft Windows. However, if the 
    ODI driver has been loaded, and additional memory is required, you 
    can de-allocate the ODI driver by typing the command:

    ODI -U 

    at the DOS prompt, after exiting Windows.

                        
Known limitations and problems

This section describes the known limitations and problems of this 
release of PathWay Runtime. 

Installation (host name and domain name)

The official host name consists of a host name and a domain name. If you 
enter a domain name, you must enter a host name.

NDIS and TOKENDIS drivers for NDIS 2.0.1

NDIS and TOKENDIS NDIS20 real-mode protocol drivers use the default 
software interrupt 64 to communicate with the VxD stack. If another 
application uses the same interrupt, the NDIS entry in AUTOEXEC.BAT 
must be edited manually as follows: 

NDIS -D:Sec# -H:Int#

Where Sec# is the section number in PROTOCOL.INI (this number was added 
automatically by the Setup program and should not be changed), and Int# 
is an interrupt number, a value between 60 - 65. For example:

    NDIS -D:3 -H:63.

Backward compatibility for third-party applications

The backward compatibility of third-party applications is provided  
through the socket APIs which include winsock and the static BSD socket 
library. Applications that use the static BSD socket library must be 
relinked with new socket libraries in order to run. Applications that 
use winsock are compatible with PathWay Runtime 4.1. Applications that 
use sockdos are not compatible with PathWay Runtime.  Applications that
run in a Windows DOS box must be linked with the PathWay API Developer's
Tool Kit socket library.

PPP/SLIP

Because the PathWay Runtime asynchronous driver (TWGASYNC.386) supports 
two communication protocols, SLIP (and CSLIP) and PPP, you must use the 
PathWay Dialer to select a protocol and establish a serial connection.

Dialer

The Dialer does not support numeric result codes (for example, 0 for OK).

NetBIOS

- NetBIOS in Windows 95 environment is not supported.
- NBCONF doesn't show local names in the Adapter Status Menu.

SOCKDOS.DLL

SOCKDOS.DLL is not supported.

Windows Sockets API limitations

The Windows Sockets API has the following limitations:
--  Only 64 Windows sockets can be opened at any one time.
--  Raw sockets are not supported
--  The setsockopt( ) call has four unsupported options (listed in Table 1).

Table 1. Unsupported Socket options
===================================
SO_KEEPALIVE
SO_RCVBUF
SO_DONTROUTE
SO_SNDBUF
===================================


Media contents 

This section lists the contents of the distribution diskettes for 
PathWay Runtime. 

PathWay Runtime  disk 1

The Setup diskette contains the following files: 

cmdialog.vb_
config.hl_
config.ex_
configrc.dl_
copyrigh.t
ctl3d.dl_
dhcp.ex_
load.co_
migratrt.dl_
mscomm.vb_
ndis.ex_
netbind.co_
odi.ex_
protman.ex_
protman.do_
protocol._
pwpatch.ba_
pwping.hl_
pwping.ex_
pwstart.ex_
pwver.ex_
readme_r.txt
runtime.hl_
services._
setup.exe
setuprc.dll
spin.vb_
support.hl_
threed.vb_
tokendis.ex_
twgasync.38_
twgdial.dl_
twgdial.ex_
twgdial.hl_
twgins16.dll
twgins32.dll
twginsrc.dll
twginst.exe
twginst.hlp
twginst.inf
twgmodem.in_
twgndis3.38_
twgndis3.vx_
twgping.dl_
twgshim.38_
twgtcp.38_
twgwscb.ex_
unload.co_


PathWay Runtime Disk 2

ftp.ex_
nbconf.ex_
nbconf.hl_
ping.ex_
rcp.ex_
rdate.ex_
readme_r.txt
rsh.ex_
stat.ex_
statres.ex_
support.hl_
telnet.ex_
tftp.ex_
twgnb.38_
vbrun300.dl_
vt220.ex_
winsock.dl_
winsock.w9_
wsock32.dl_

