Product Release Notice

PathWay Runtime
Microsoft Windows Systems

Release 4.0
March 1995

Product names appearing in this notice are trademarks of their respective
manufacturers.
(C) 1982-1995 The Wollongong Group, Inc. 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 Wollongong. Doing so will make you 
eligible for the support services available for this product.

This README file provides information about PathWay Runtime Release 4.0.

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: One high-density 3.5-inch floppy diskette
      (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 Client NFS
--  PathWay Access applications (such as FTP and TELNET)
--  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.

VxD 32-bit implementation
PathWay Runtime is now implemented as Microsoft Windows virtual device 
drivers (VxD). The following PathWay Runtime components are VxDs: TCP/IP 
kernel, NDIS 2.0.1 driver, NDIS 3.0 driver, and PPP/SLIP driver.

Windows Sockets API support
Third-party applications written to Windows Sockets (version 1.1) API are 
supported over PathWay Runtime. 

Express and Custom installation

PathWay Runtime offers two installation paths: Express asks for the 
minimum information needed to make the PC network-ready. Custom allows 
the user to configure additional parameters such as ARP cache and 
alternate gateways. Both read information about the system's current 
configuration, and incorporate that information into the installation 
procedure where appropriate.

Multiple interfaces

Two network interfaces and one serial port can be configured for network 
connection.

Configuration file in ASCII

An ASCII-format kernel configuration file, TWGTCP.INI, replaces 
PWCONFIG.EXE.

Dialer for SLIP and PPP

PathWay Dialer is a program that lets you maintain a directory of 
locations with associated telephone numbers. To call a location, you 
simply select it in the Dialer Directory window and click Dial to 
establish the connection. You can also use the Dialer in an interactive 
dialing mode. 

The Dialer uses the PathWay Runtime asynchronous driver, TWGASYNC.386. 
Choose the SLIP, CSLIP, or PPP protocol from within PathWay Dialer as your 
communication protocol. Dialer allows dynamic changes to be made to PPP 
configuration, and supports 57.6 Kbps communication. 

Ping

An enhanced Windows-based ping utility is included. A Results window allows 
you to track the result of a defined number of pings, or continuous pings.

Stat

Windows-based Management Information Base (MIB) statistics viewer that 
supports PPP (Link Control Protocol and IP Control Protocol) is included.

DHCP client

PathWay Runtime now includes Dynamic Host Control Protocol (DHCP) client 
for Ethernet, Token Ring, SLIP, and PPP.

On-line Help

PathWay Runtime now includes on-line Help for Setup, Config, Dialer, 
and Ping.

PPP driver

The Point-to-Point Protocol (PPP) driver connects a PC via a serial line 
to any computer that supports TCP/IP over PPP. This serial line may be 
either a null modem cable or a telephone line connection using modems. 
PPP now supports MIB, IP address assignment, Maximum Receive Unit (MRU) 
negotiation, automatic dialing, auto disconnect and auto connect for 
idle timeout.

Compressed SLIP

SLIP includes a TCP header compression option.

NDIS driver for Ethernet, ARCNET, and Token Ring

NDIS driver supports: NDIS 3.0 for all three network types and NDIS 
2.0.1 for Ethernet and ARCNET. TOKENDIS driver supports NDIS 2.0.1 for 
Token Ring.

ODI support

PathWay Runtime supports Novell's ODI drivers.

256 TCP connections

The PathWay Runtime kernel now supports up to 256 concurrent TCP 
connections, 208 more than the previous release of PathWay Runtime.

Multiple default gateways

This version of PathWay Runtime supports multiple default gateways. 
When you install or modify PathWay Runtime, you can set up addresses 
for up to five gateways. If the default gateway goes down, PathWay 
Runtime automatically switches to the next available gateway. 

Number of UDP sessions is now configurable

You can use the setup or config program to select the number of User 
Datagram Protocol (UDP) sessions. The minimum is 1; the default value 
is 7; the maximum is 256.

Maximum number of queued UDP received packets is now configurable

You can use the setup or config program to select the maximum number of 
User Datagram Protocol (UDP) received packets that can be queued. The 
minimum is 1; the default value is 4; the maximum value is 256.


Supported platforms and systems

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

--  Minimum 386 or compatible computer running Microsoft Windows 3.1 (in 
    386 Enhanced Mode) or Microsoft Windows for Workgroups 3.11
--  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 or PPP 
    interface
--  4 MB of RAM minimum; 8 MB recommended
--  Approximately 2MB of disk space for PathWay Runtime 

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

--  Microsoft LAN Manager 2.2
--  Microsoft Windows for Workgroups 3.1 or 3.11
--  Novell NetWare 3.11, 3.12, or 4.0.1
--  Performance Technology's POWERLan 3.0

The following asynchronous communications servers have been successfully 
tested with Wollongong'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. 

--  If you upgrade from Runtime 2.0 to Runtime 4.0 and then uninstall 
    Runtime 4.0, the original Runtime 2.0 functionality will be not 
    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.0 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.

--  PathWay Dialer files from PathWay Runtime Release 2.0 are 
    fully-compatible with the PathWay Dialer included in Release 4.0. 
    To use earlier files (a file should exist for each entry in the 
    PathWay Runtime Directory list) you must ensure that your Dialer files 
    and the file FILELIST.DLR are located in the directory that contains 
    PathWay Runtime Release 4.0. 

--  If you were a Beta site for this release of PathWay Runtime, please 
    note the following points that may help you upgrade to the final 
    product:

    a. If you are running NDIS 2.0, remove this entry from the 
       [386Enh] section of the SYSTEM.INI file: 

       DEVICE=C:\PWAYBETA\TWGNDIS2.386

       Note that PWAYBETA was the default installation directory which 
       might not be where your Beta software resides.

    b. Remove other Beta-related entries from AUTOEXEC.BAT, CONFIG.SYS, 
       SYSTEM.INI and WIN.INI, if any.

    c. To avoid confusion with a fresh installation, from the Program 
       Manager, remove the PathWay 4.0 Beta program group. The final 
       version of PathWay Runtime installs all program icons in the 
       PathWay Access program group. (The default installation directory 
       for Beta software was \PWAYBETA.)

    d. PathWay Dialer profile files created with the Beta software are 
       not compatible with the final product.


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.0. 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

Applications that use NetBIOS-dependent protocols such as SMB 
(e.g., PathWay Client Plus) should be used with PathWay Runtime 
Release 2.0, not PathWay Runtime Release 4.0.

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 Setup diskette 

The Setup diskette contains the following files: 

CMDIALOG VB_
CONFIG   HL_
CONFIG   EX_
COPYRIGH T  
CTL3D    DL_
DHCP     EX_
LOAD     CO_
MSCOMM   VB_
NDIS     EX_
NETBIND  CO_
ODI      EX_
PING     HL_
PING     EX_
PROTMAN  EX_
PROTMAN  DO_
PROTOCOL _  
PWPATCH  BA_
PWSTART  EX_
PWVER    EX_
README_R TXT
RUNTIME  HL_
SERVICES _  
SETUP    EXE
SPIN     VB_
STAT     EX_
SUPPORT  HL_
THREED   VB_
TOKENDIS EX_
TWGASYNC 38_
TWGDIAL  DL_
TWGDIAL  EX_
TWGDIAL  HL_
TWGINST  EXE
TWGINST  HL_
TWGINST  INF
TWGMODEM IN_
TWGNDIS3 38_
TWGPING  DL_
TWGSHIM  38_
TWGTCP   38_
TWGWSCB  EX_
UNLOAD   CO_
VBRUN300 DL_
WINSOCK  DL_

