

				  README
	       PC/TCP Network Software for DOS, version 2.31
			 Release of January, 1994


				 CONTENTS
        PREFACE
	1  Kernels and Drivers
	   1.1	Installing the IBM Token Ring Kernel
	   1.2	Install Guide Change, NDIS Protocol.ini File
	   1.3	New Crynwr Packet Drivers Available
	   1.4	Packet Driver Problems
	2  Using PCTCP.INI Continuation Files
	3  Tunnelling IPX over IP
        4  InterDrive NFS Client Enhancements
	5  Windows Application Problems and Enhancements
	   5.1	New Features in Windows Terminal Emulation
	   5.2	Other Winapp Enhancements
	   5.3	Network Control Problems
           5.4  PCTCPNET Enhancements
	6  DOS Application Problems and Enhancements
	   6.1	Using LPD and other Applications in a Background
		Windows DOS Session
	   6.2  Using Predir with Lotus 1-2-3 version 3.1
	   6.3	Accessing IBM 3270 IMS systems with TN.EXE
	   6.4	Nicname.exe MIL Address
	   6.5  Idconfig.exe Command Line Options
	   6.6  Tnglass.exe Command Line Options
        7  Compatability with Windows for Workgroups, v. 3.11


                       READING PATH


If you have this PC/TCP product     Read these sections

PC-2xx                              All

K-2xx  (Kernel only)                1    Kernels and Drivers
                                    2    Using PCTCP.INI Continuation Files
                                    3    Tunneling IPX Over IP

PC-440 (InterDrive)                 1    Kernels and Drivers
                                    2    Using PCTCP.INI Continuation Files
                                    3    Tunneling IPX Over IP
                                    4    InterDrive NFS Client Ehancements
                                    5.3  Network Control Problems
                                    5.4  PCTCPNET Enchancements
                                    6.4  Idconfig.exe Command Line Options




                           PREFACE

This section summarizes the PC/TCP bug fixes and enhancements since the
last release.

o The PC/TCP kernels now support 

    Loading into extended memory without sometimes hanging in Windows.  
    All Multicast addresses (not just even addresses).
    Multicast loopback over NDIS drivers.
    InterDrive and background network activity more reliably.
    Windows for Workgroups 3.11.
    The PPP16550 packet driver at int 0x62 without reporting an
     0x61 interrupt conflict.
  
o Windows Applications

  PCTCPNET
    Query errors fixed.
    Now supports enable/disable banner page.
    Now supports lpr raw/binary printing.
    Now does its own spooling (see section 5.4 PCTCPNET enhancements).
    Does not report "PCTCPNET not loaded" if "netwarn=0" in [Windows]
      section of your WIN.INI file (file INIT.C). 
    Now gets banner setting out of [pctcp lpr xxx] section of pctcp.ini file.


  WTNVT/WTN3270

    Support a larger (200 line) screen buffer scrollback limit.
   
    Support a new option to improve performance with certain X servers 
      and background applications running. 
   
    Retain the screen size when you maximize then minimize its icon.
   
    Retain the National Character Set and DOS Remap File settings when 
      you create a new session.
   
    WTN3270 now displays  a correct screen image during horizontal scrolling
      after switching to True Type Font.

    The WTN3270 Session-> New Session Parameters "Use DOS keyboard remap file"
    checkbox now does the right thing (instead of having no effect).


o  DOS Applications

   FTPSRV no longer allows you to log in with the command "quote pass".  
   LPD works reliably in the background with Windows For WorkGroups.
   Telnet (tn)now runs reliably in the background in Windows. 
   PC Eudora now works reliably over NFS mounted drives.
   Pop2 now reports correct UIDs when run with an empty mailbox.	


o InterDrive NFS Client

  Supports a local hostname with up to 64 characters (the previous limit was
      32 characters). 
  Supports a negative time zone offset
      See the "time-zone-offset" in the [pctcp general] section of your
      pctcp.ini file.  
  Supports new configuration file options to times out connections that
     have terminated on the server. For more information see section 4 of
     this README file.
  
o  NetBIOS

  Resolves name conflicts when a name query is answered
  simultaneously by a node and a name server.



IMPORTANT NOTE

Use this number to request Internet information from the Network Information
Center (NIC): 

              1-800-444-4345

Please DO NOT use telephone number that appears in the Foreword of our
release manuals.

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


1  Kernels and Drivers

This  section describes problems and enhancements  to  PC/TCP  kernels	and
drivers.

NOTE:  The PC/TCP kernel loads into UMB memory by default (contrary to what
the printed documentation states.)
 
1.1  Installing the IBM Token Ring Kernel

Some  users have reported problems with their PC  mouse  when  running	the
ibmtr.exe  kernel.  To correct the problem,  enter  the  network  interface
hardware interrupt in the pctcp.ini file.    Set the "[pctcp ibmtr 0] irq="
entry to the IRQ value of the network driver.  This entry does not exist in
the default pctcp.ini file template, or in the documentation.

1.2  Install Guide Change, NDIS Protocol.ini File

On page 4-5 of the Installation Guide, section 4.2.2, the protocol.ini file
entry for NE2000 card needs to be changed.  The printed documentation gives
the  "[NE2000_NIF] drivername" entry as NE2000$.   It  should  be  MS2000$.
Even if the card is a Novell NE2000 card, the protocol.ini file expects the
drivername to be MS2000$.

1.3  New Crynwr Packet Drivers Available

An updated release (version 11) of Crynwr Packet drivers  is  available  on
disk 6 (Supported Packet  Drivers)  in	the  PC-210 distribution.  Existing
users with version 10 drivers may want to upgrade.  The  WD8003E.COM driver
has  been  renamed  to SMC_WD.COM.  The 3C507.COM has a  new  command  line
syntax.  See the file "readme.pd" on disk 6 for details.

1.4  Packet Driver Problems

There is a known problem with the 3c505 Crynwr Packet  Driver.	 Until this
problem is addressed, please choose another type of driver, such as NDIS.

The 3c507 Packet Driver displays problems using IRQ 9.


===========================================================================
2  Using PCTCP.INI Continuation Files

FTP Software reserves the right to  change  the design of and way pctcp.ini
continuation files work in subsequent releases.

For this release, to use a pctcp.ini continuation file with InterDrive, the
general  [pctcp  idrive]  entry  must	be  in	the  main  pctcp.ini  file.
Individual filesystem sections	([pctcp  idrive filesys]) can reside in the
continuation file.

The NetBIOS program, the pctcpnet.drv  driver, and the Wmsg application all
require configuration entries to reside in the main pctcp.ini file.

For more information on  using	continuation  files,  see the PC/TCP User's
Guide, Appendix A.


=======================================================================
3  Tunnelling IPX over IP

This section clarifies IP tunnel procedures from Chapter 6  of	the  PC/TCP
Installation Guide.

You  need  to  load the pd_pctcp.com  driver  (from  the  command  line  or
autoexec.bat file) with the SAME  software interrupt number that you assign
to pdether.exe	in  the  net.cfg  file.  See page 6-12 for a sample net.cfg
file.  See Section 6.5.4 on page 6-14 for a sample autoexec.bat entry.

Section  6.5.3	describes  two options for configuring IP tunnelling on the
client: 1) Using the Netware tunnel driver, pdether.exe, or 2) generating a
Netware shell.	If you choose option 2,  the  IPX.COM  version	3.02 driver
works.	However, the IPX.COM version 3.10 driver does not.


===========================================================================
4  InterDrive NFS Client Enhancements

These are additional InterDrive enhancements for this release:

  Supports a local hostname with up to 64 characters (the previous 
    limit was 32 characters). 
  Supports a negative time zone offset. 
    For more information, see the "time-zone-offset" in the [pctcp general]
    section of your pctcp.ini file.  
  Supports options that let you time out connections that have terminated
    on the server.

    These are the new pctcp.ini configuration parameters.

       [pctcp idrive]
       drive-tmo= [yes|no]

       [pctcp idrive filesys]
       drive-tmo= [yes|no]

    drive-tmo=no causes an Abort, Retry, Fail? prompt to be displayed
    when a network timeout error occurs. If drive-tmo=yes the drive is
    disconnected instead.

    The default is no for both. You can display the InterDrive 
    global setting using idutil -t and the mount point specific setting 
    using idutil -f.



==============================================================================
5  Windows Application Enhancements

These features were added to the Windows programs after documentation went
to press.


5.1  New Features in Windows Terminal Emulation

  1.  Wtn3270 has a  new  feature  which,  when  scroll  bars  are enabled,
      automatically scrolls the window to ensure the cursor is visible (not
      scrolled off screen) when the user types at the keyboard.

  2.  The  Wtn3270  Settings  menu  Terminal  Emulation  dialog  has a	new
      checkbox, "Alternate Screen Overrides  Default".	If  you  check this
      option, Wtn3270 never uses  the  default	screen	size for the chosen
      terminal type when connecting to a 3270 host.    It  always  uses the
      alternate screen size.

      This option exists as a workaround for what FTP Software considers to
      be a  bug  in  the  IBM  IMS  application.  If you do not enable this
      option, connecting to the IMS  application  with	Wtn3270  results in
      garbled  screens. This fix was also added to the DOS TN program.	See
      the section "DOS Application Bugs and Enhancements"

     
  3.  The WTN3270 Session-> New Session Parameters "Use DOS keyboard remap
      file" checkbox now does the right thing (instead of having no effect).
  
  4.  Wtnvt now reads the pctcp.ini  file for the "[pctcp vt] allow-8-bit="
      variable (already in use by the DOS TN program). If you set the entry
      to  "off",  the  VT emulator does  not  switch  to  8-bit  mode  when
      requested by the user or remote host software.

  5.  Wtnvt/Wtn3270 now support a larger (200 line) screen buffer
      scrollback limit.
 
  6. Wtnvt/Wtn3270 supports a new option to run faster with certain X servers.

     If you are experiencing performance problems running Wtnvt/Wtn3270 
     with an X server select the High Priority option in the Sessions 
     menu. 
                  
     This uses special processing (PC/TCP v2.2-style) to compete with
     certain background Windows applications which might be monopolizing
     Windows' CPU time. 
     
     Note that this background processing may adversely affect the
     performace speed of other applications because it causes WTN to
     operate as if it were a background process. 


5.2  Other Winapp Enhancements

1.  Wtnvt, Wtn3270, Wftp, Wping, and Wmsg users can now close the session
    and application without waiting for name resolution to complete.

2.  You can maximize Wftp to a full screen size.
  

5.3  Network Control Problems

Problems  have been  found when  receiving a very long listing of available 
printers from a v. 2.0 PCNFSD.  As a workaround query  a list of  available 
printers from the Print Manager Network Connections  screen until a  fix is 
available.


5.4  PCTCPNET Enhancements

These are new PCTCPNET enhancements that are not documented in
the printed manuals. 

This release of PCTCPNET

  Lets you enable/disable an lpr banner page.
  Lets you specify raw/binary printing.
  Manages its own spooling.
   Note that this version of PCTCPNET generates its own unique spool file
   names and ignores any Spool File Name you specify in the Print Options
   dialog box. 

To specify an lpr banner page you can use

  o  The "banner=" setting in the [pctcp lpr print_connection_name]
     section of your pctcp.ini configuration file, or 

  o  The Banner setting in the Print Options dialog box. 
 
  PCTCPNET gets its initial value from the 
  [pctcp lpr print_connection_name] section.  

  If you do not specify a "banner=" in your pctcp.ini configuration file,
  PCTCPNET uses the Banner option setting in the Print Options dialog box
  *for the current Windows session*.  
   
  If you exit Windows and start Windows again, PCTCPNET will again get the
  banner value from the PC/TCP configuration file.

  To specify raw/binary printing you can use  

  o  The "format=" setting in the
     [pctcp lpr print_connection_name] section  of your pctcp.ini
     configuration file, or  

  o  The Raw/binary option in the Print Options dialog box. 

  PCTCPNET gets its initial value from the
  [pctcp lpr print_connection_name] section.  

  If you do not specify a "format=" in your pctcp.ini configuration file,
  PCTCPNET uses the Raw/binary setting in the Print Options dialog box
  *for the current Windows session*.  
   
  If you exit Windows and start Windows again, PCTCPNET will again get the
  banner value from the PC/TCP configuration file.

==========================================================================
6  DOS Application Problems and Enhancements

This section describes known problems  with and changes to DOS applications
after documentation went to press.


6.1  Using LPD and other Applications in a Background Windows DOS Session

The PC/TCP LPD program was designed to run as a dedicated DOS server.
You can run it in a background Windows DOS session, but may  encounter
problems doing so.
 
Likewise, other  DOS  applications  may  experience a GPF when run
in the background with certain video drivers.  FTP  Software
is  working with Microsoft to correct this problem.


6.2  Using Predir with Lotus 1-2-3 version 3.1

If  you  are  using Lotus 1-2-3  version  3.1  with  the  predir.exe  print
redirector, load predir using the following command line:

	predir localpsp on

If you are  using  other  versions  of	Lotus  1-2-3,  you do not need this
switch.


6.3  Accessing IBM 3270 IMS systems with TN.EXE

To connect to an IBM 3270 IMS application, use the following pctcp.ini file
setting or TN command line option to prevent screens from becoming garbled.
These options exist as a workaround for what FTP Software considers to be a
bug in the IBM IMS application.

Set the pctcp.ini file entry [pctcp 3270] "alt-overrides-default" to "yes."
This causes  TN  to  never  use the default screen size for the chosen 3270
terminal type.	It always uses the alternate.

The  TN "-a" command line switch takes effect on a per-session basis.  When
used  on the command line, TN does not use the default screen size for	the
3270 terminal type chosen; it uses the alternate.

A similar fix exists in the Wtn3270 application.  Refer to the section "New
Features in Windows Terminal Emulation."


6.4  Nicname.exe MIL Address

On  page  2-77	of  the  Command  Reference,  the  Internet address for the
Department of Defense (DoD) at	NIC.DDN.MIL  should  be  192.112.36.5. This
does  not affect the way the nicname command works.  When you use the  "-d"
command-line  option,  the  nicname request goes to  the  correct  Internet
address.

6.5  Idconfig.exe Command Line Options

The Command Quick Reference does not list an available idconfig.exe option. 
The idconfig -g option displays a list of  group identifiers (GIDs) you can
select on the  mounted drive.   Note that  you  cannot combine idconfig.exe
options on the command line.

6.6  Tnglass.exe Command Line Options

The Command Reference and Quick  Reference  include  a tnglass "t" escape
command that sends a telnet break signal.  There is no "t" escape command
currently in the program.


=========================================================================
7  Compatability with Windows for Workgroups, version 3.11

Since our last newsletter, Microsoft Windows for Workgroups 3.11 was
released.  There were some changes from the beta version of this
release which alter the configuration necessary for PC/TCP Network
Software v2.3, DOS/Windows.

In addition these are some known problems running PC/TCP NFS services with
WFW 3.11.  (FTP Software Inc. and Microsoft are working to resolve them.)

o   Print Manager gives ERROR "Network does not support this function"
    when displaying NFS,LPR connected printers.  The NFS,LPR connected
    printers work but will not be shown correctly from Print Manager.
   
o   File Manager can sometimes experience delays of up to 30 seconds when
    switching between LAN Manager and NFS mounted drives.  Please wait
    and system will come back if you are experiencing these pauses.

NOTE:  To use PC/TCP with WfW 3.11 you must upgrade to PC/TCP v2.31.  This
assures that you have the newest wfwftp.386 and pctcpnet.drv. Use these 
new files ONLY with PC/TCP 2.3(and above) and WFWG 3.11.

You can download the newest wfwftp.386 from the BBS/VAX:

   filename: wfw311.exe

You now have three configuration choices for running Windows for Workgroups
3.11 with NetBIOS; run over NetBEUI only, run with NetBEUI and NetBIOS, or
run with NetBIOS only.  

NetBEUI Only

Follow these steps to configure PC/TCP, DOS/Windows with Windows
for Workgroups Version 3.11 over NetBEUI only:

1. Choose Real Mode NDIS Driver (NDIS2) during the Windows for
Workgroups setup.

2. Review the config.sys file to make sure:

* The Windows for Workgroups installation program inserted the
Device=drive:\path\ifshlp.sys entry which is necessary to load the
NDIS2 converter.

* There are no entries that load the Protocol Manager or an NDIS card
specific driver.  If they exist in this file, remove them.

3. Make the following changes to the autoexec.bat file:

* Arrange the entries so that the net start command, inserted by the
Windows for Workgroups installation program, precedes any TSRs
(Terminate and Stay Resident programs).  Make sure the net start
command includes the full path, if the command precedes the path
statement.

* If the netbind command exists, remove it.

* Add the drive:\path\kernel command, to load the PC/TCP kernel,
after the net start command.

4. Make the following changes to the Windows system.ini file:

* Add the Secondnet.drv=drive:\path\pctcpnet.drv entry after the
Network.drv=wfwnet.drv entry in the [Boot] section.

* Add the Secondnet=drive:\path\vpctcp.386 entry to the [386Enh] section.

* If you are going to use NFS to mount remote drives or printers in
Windows, add the Device=drive:\path\wfwftp.386 entry to the [386Enh]
section. 

Note: You must use the wfwftp.386 file that FTP Software created
specifically for Windows for Workgroups Version 3.11.  You can get
this file from our Technical Support BBS (filename: wfw311.exe) or
our vax.ftp.com anonymous FTP server
(filename:/support/fixes/pctcpdos/wfw311.exe).

This wfwftp.386 file created for Version 3.11 will also work with
Windows for Workgroups Version 3.1, but the wfwftp.386 file created
for Version 3.1 will not work with Windows for Workgroups Version
3.11.

* Make sure the following entries are in the [network drivers]
section:

Netcard=Your_NDIS_driver_filename.ext
Transport=ndishlp.sys,*netbeui
LoadRMDrivers=Yes

By the way, the asterisk in *netbeui is an accurate character in the
filename used by Microsoft.

* Add drive:\path\dis_pkt.gup to the values that are already assigned
to the Transport= entry.

5. Add a [PKTDRV] section in the protocol.ini file with the
following entries:

[PKTDRV]
DriverName=PKTDRV$
Bindings=Windows_for_Workgroups_driver_section_name
IntVec=Available_Software_Interrupt
ChainVec=Available_Software_Interrupt

By the way, common interrupts available for IntVec and ChainVec are
0x60 and 0x65, respectively.

6. Restart your PC to start running Windows for Workgroups over
NetBEUI.


NetBEUI and NetBIOS

Follow these steps to configure PC/TCP, DOS/Windows with Windows
for Workgroups Version 3.11 over the PC/TCP, DOS/Windows
netbios.com program and NetBEUI stack:

1. Follow steps 1 - 5 in the previous section, "NetBEUI Only."

2. Add the drive:\path\netbios command to the autoexec.bat file.

3. Make the following changes to the protocol.ini file:

* Change the lana0= entry to lanan= (where n is the next available
adapter number) in the [network.setup] section.  An example of this
entry follows:

lana2=ms$elnk3,1,ms$netbeui

* Change LANABASE=0 to LANABASE=n (where n is the same number as the
adapter number in the previous bullet) in the [NETBEUI] section.  

Note: The reason for these two changes is that the lana0= and
LANABASE=0 settings are reserved for the PC/TCP . DOS/Windows
netbios.com program.

4. Edit the [pctcp netbios] section of the pctcp.ini file to include
the following NetBIOS specific parameters:

[pctcp netbios] 
Ncbs=64 
Names=32 
Sessions=n (where n equals the same value that is assigned to the
Tcp-Connections= entry in the [pctcp kernel] section of the pctcp.ini
file.)

5. Restart your PC to start running PC/TCP, DOS/Windows with
Windows for Workgroups Version 3.11 over the PC/TCP, DOS/Windows
netbios.com program and NetBEUI stack.


NetBIOS Only

Follow these steps to configure PC/TCP, DOS/Windows with Windows for
Workgroups Version 3.11 over the PC/TCP, DOS/Windows netbios.com
program:

1. Follow all the steps in the two previous sections, "NetBEUI Only"
and "NetBEUI and NetBIOS."

2. Comment out the NetMisc= and Transport= entries in the [386Enh]
section in the Windows system.ini file by placing a semi-colon (;)
before each entry.

3. Restart your PC to start running Windows for Workgroups over the
PC/TCP, DOS/Windows netbios.com program.


