China DOS Union

Looking for the PC TCP software and its licenses from American FTP companies. Thanks in advance

A while ago, our company was also using PCTCP, but I didn't pay attention.

Boss, is there anyone who knows?

READ ME
PC/TCP (TM) Software Development Kit 3.2 for DOS
Release of November 1995

NOTICE


The information in this document is subject to change without notice
and should not be construed as a commitment by FTP Software, Inc.

While every effort has been made to assure the accuracy of the information
contained herein, FTP Software, Inc. assumes no responsibility for errors
or omissions. No liability is assumed for incidental or consequential
damages resulting from the use of the information contained in this
document.

The software described in this document is furnished under a license and
may be used or copied only in accordance with the terms of such license.

(C) Copyright FTP Software, Inc. 1986 - 1995. All rights reserved.

(C) Copyright Unipalm Limited 1994 - 1995. All rights reserved.

(C) Copyright Spyglass, Inc. 1986 - 1995. All rights reserved.
(C) Copyright Board of Trustees of the University of Illinois 1993 -1995.
NCSA Mosaic was developed by the National Center for Supercomputing
Applications at the University of Illinois at Urbana-Champaign. NCSA
Mosaic has been commercially enhanced by Spyglass, Inc. Enhanced
versions developed and supported by FTP Software, Inc.

FTP Software, InterDrive, and PC/TCP are registered trademarks and
OnNet and CyberAgent are trademarks of FTP Software, Inc.

Other tradenames, trademarks, or registered trademarks are the property
of their respective owners.


CONTENTS

1.0 Installing the PC/TCP Software Development Kit
1.1 Installation Requirements
1.2 Upgrading and Other Information
1.3 Installation Special Considerations
1.3.1 Overwriting Files
1.3.2 Upgrading or Reinstalling to a Different Directory
1.3.3 Welcome Screen Message Might Be Unclear
1.3.4 README.TXT Reference Is Incorrect
1.3.5 Setup Program Finish
2.0 New Features
3.0 Special Considerations for Applications
3.1 Configure Application
3.2 Serial Connection Tuning Guidelines
3.3 Kernel Name Resolution and Third-Party Applications
4.0 Special Considerations for Application Programming Interfaces
4.1 RPC Library Special Considerations
5.0 Additions and Corrections to the Documentation
5.1 User's Guide Additions and Corrections
5.1.1 Corrections to Section 3.1, "Features of the
PC/TCP Software Development Kit"
5.2 RPC Programming Additions and Corrections
5.2.1 Header Files in Code Examples
5.2.2 Correction to Section 1.4, "RPC Utilities
Command Reference"
5.2.3 Correction to Chapter 2, "The rpcgen
Programming Guide"
5.2.4 Correction to Section 2.4.9, "Special Classes"
5.2.5 Addition to Section 4.4.6, "Strings"
5.3 System Call Reference Additions and Corrections
5.3.1 Additions to Section 2.2, "Routine Reference."
5.3.2 Corrections to Section 2.2, "Routine Reference."
6.0 Fixed Problems
6.1 Fixes in the FTP Library
6.2 Fixes in the RPC Library

----------ooo-----------


1.0 Installing the PC/TCP Software Development Kit

1.1 Installation Requirements

Processor In DOS
286 (or higher)
In Windows
Standard mode: 286 (or higher)
386 Enhanced mode: 386 (or higher)

Memory In DOS
(RAM) To install the PC/TCP Software Development Kit
(PC/TCP SDK), you must have 435K of conventional
memory freely available.
In Windows
Standard Mode: 1 MB
386 Enhanced Mode: 4 MB
Operating MS-DOS version 3.3 (or higher)
Systems Microsoft Windows Version 3.1
Microsoft Windows for Workgroups version 3.11

Disk Space Determined by the components selected for installation.
The Components dialog box, viewable during New
installations or if you select a Custom installation,
displays the disk space required for the components you
have selected.

Note: If you have a temporary swap file, the size of the
swap file can increase and prevent the copying of files
to your PC.

1.2 Upgrading and Other Information

The PC/TCP SDK includes the FTP Software terminate-and-stay resident
(TSR) TCP/IP stack (networking kernel) and some network
troubleshooting applications. When you run the PC/TCP SDK
installation program, if you do not have a networking kernel
installed, the installation program installs the TSR kernel. If you
already have a TCP/IP kernel installed, other than a previous version
of the PC/TCP or OnNet kernel, the PC/TCP SDK installation program
does not install the PC/TCP kernel.

For more information on upgrading and for other installation
information, see the User's Guide, Part II.

1.3 Installation Special Considerations

1.3.1 Overwriting Files

The installation program creates backups of existing configuration
files such the AUTOEXEC.BAT and PCTCP.INI files. It also creates
backups of the SERVICES and PROTOCOL files that exist in the
\PCTCP\ETC directory. However, if you run the installation program a
second or subsequent time, then the installation program overwrites
those backup files with the files from the previous installation. To
save information from your original setup, you should backup your
files and use unique filenames that the PC/TCP SDK installation
program will not overwrite.

1.3.2 Upgrading or Reinstalling to a Different Directory

If you have an OnNet, or PC/TCP Network Software version 2.3 or
older, product on your system and you choose not to install the OnNet
SDK to the same directory as the existing product, if you then delete
the original directory, the kernel might fail to load. In these
cases, FTP Software, Inc. recommends that you upgrade or reinstall to
the directory where the previous version resides. However, if you
upgrade or reinstall to a different directory, do not delete the
original directory before changing references to the new directory
and moving device drivers (for example, packet drivers and NDIS
drivers) to the new directory.

If you install this product over a previous OnNet for Windows 2.0
installation, and you install the PC/TCP SDK to a different top-level
directory, when you reboot your system you receive an error message
that says that the pctcplfn.dll is not accessible. A result of this
is that InterDrive will not work. To remedy this situation, do the
following:

- Add to your PATH statement the path to the OnNet for Windows directory.
- Reset your PCTCP environment variable to point to your old
PCTCP.INI file.
- or -
- Merge your InterDrive configuration entries from your old
PCTCP.INI file into your new PCTCP.INI file.

1.3.3 Welcome Screen Message Might Be Unclear

The Welcome screen in the installation program displays a message
that starts, "If you wish to run FTP's network stack for Windows with
another stack..." That message is referring to running the FTP
Software TCP/IP stack in conjunction with network operating systems
such as LAN Manager, NOVELL Netware, or Windows for Workgroups. See
the User's Guide for more information.

1.3.4 README.TXT Reference Is Incorrect

The DOS installation program suggests that you view a file named
README.TXT for the latest information on the PC/TCP SDK. That
reference is incorrect. The Write file, README_D.WRI, and the ASCII
version of that file, README_D.TXT, contain information that was
unavailable when the printed documentation was prepared.

1.3.5 Setup Program Finish

At the end of the setup, a message refers you to the Getting Started
manual for more information. The OnNet SDK documentation set does
not include that manual. See the User's Guide for more information
on installation and configuration.


2.0 New Features

The FTP Software, Inc. software development kit has been split into
the following two products:

?PC/TCP Software Development Kit 3.2 for DOS (PC/TCP SDK)

?OnNet Software Development Kit 4.0 for Windows

The PC/TCP SDK provides application programming interfaces for
developing DOS applications. It is distributed on 3 1/2 inch
diskettes.

The OnNet SDK provides application programming interfaces for
developing Windows applications. It is distributed on a CD-ROM.

The new features of the PC/TCP SDK are the following:

- Graphical installation programs for DOS and for Windows.

- A PC/TCP terminate-and-stay resident (TSR) TCP/IP stack
(networking kernel).

- LAN and serial line interfaces.

- The bootp program for configuring network information on your
PC from a Bootp server.

- The comscrpt program for serial communications.

- The dhcp program for dynamically configuring your PC from a server.

- The host program for obtaining a hostname or IP address from a
local host table or a remote domain name server.

- The inet program for obtaining information on your PCs network
configuration and statistics on network or serial line
activity.

- The mibfmt program for interfacing a private management
information base (MIB) with the SNMP library.

- The kernel program for loading the PC/TCP TSR kernel into memory.

- The lwpe program for running Novell NetWare IP over the PC/TCP stack.

- The ping program for testing connectivity and tracing hops.

- The pctcpcfg command line program and the Configure graphical
program for configuring the TSR kernel.

- A DOS rpcinfo program for getting information from a Remote
Procedure Call (RPC) server.

- The following new configuration library routines:

config_cancelwrites()
config_getvalue()
config_geterrno()
config_isopen()

- The following new FTP, Rlogin, and Telnet library routines
that implement quitting the program when the user enters Control-C:

FTP Library Rlogin Library Telnet Library

ftp_dir_nb() rl_open_nb() tn_open_nb()
ftp_open_nb()
ftp_get_nb()
ftp_put_nb()
ftp_ls_nb()

- A new DNS routine, net_dns_aliases(), in the system call library.

- The ERROR.H header file contains a new system call error code,
NET_ERR_USER_CANCELED.


3.0 Special Considerations for Applications

3.1 Configure Application

The following items listed when you start the Configure application
are not distributed with this product:

- InterDrive
- Mail and News
- Terminal Emulation
- File Transfer
- Printing
- Print Server (Advanced Mode only)
- Archiving

3.2 Serial Connection Tuning Guidelines

The following guidelines are especially important for slower serial
environments. Some combination of one or all of the following
parameters should result in a performance improvement. However,
these guidelines are a starting point, and are not a substitute for
testing, adjusting, and trial-and-error tuning. For more information,
see the User's Guide.

In the section of the PCTCP.INI configuration file,
use the following settings:


rtt-multiplier=2
slow-link-multiplier=2
do-slow-start=yes
mtu-discovery=no
disable-timeout=yes

These configuration file settings do the following:

rtt-multiplier=2
Although a value higher than 1 is usually not necessary, a value of 2
might be helpful, and this is a useful parameter to adjust during
final tuning. The kernel calculates the time it takes for one packet
to travel a round trip over a TCP connection, using this value as a
multiplier. Therefore, if this value were set to 3, the kernel would
use a value of three times the round-trip time to receive an ACK,
before retransmission.

slow-link-multiplier=2
This parameter does not affect a LAN connection but does improve
performance over a serial connection. The kernel uses this value to
determine the number of transmitted packets that can be outstanding,
before receiving an ACK. This value overrides the foreign window
size.

do-slow-start=yes
This parameter defaults to YES in the PC/TCP or OnNet kernel for
serial connections. When set to YES, this forces the kernel to
determine the correct round trip time. Set this parameter to NO if
applications are not prepared to handle a failed send.

mtu-discovery=no
This parameter might be the only one needed to eliminate retransmit
problems; at other times it has no effect. This parameter forces the
maximum segment size (MSS) to be set to 536 bytes.

disable-timeout=yes
This parameter prevents the kernel from resetting a TCP connection
after the retransmit limit for one packet has been reached.

3.3 Kernel Name Resolution and Third-Party Applications

To make the TSR kernel smaller, domain name resolution code was moved
out of the PC/TCP 2.3 TSR kernel. If you are using applications that
were written to use the TSR kernel for name resolution, keep the
following setting in the PCTCP.INI file:


kernel-does-dns=yes

Setting this parameter to no shrinks the TSR kernel by 6.5K. Set
this parameter to no if you do not use old applications that require
DNS support in the TSR kernel, and if you want to free more
conventional memory.


4.0 Special Considerations for Application Programming Interfaces

This section describes known bugs in the PC/TCP SDK application
programming interfaces (APIs), and any workarounds for the problems.

4.1 RPC Library Special Considerations

The clnt_broadcast() function never invokes the reply handling
procedure supplied as an argument in a call to clnt_broadcast().

5.0 Additions and Corrections to the Documentation

5.1 User's Guide Additions and Corrections

5.1.1 Corrections to Section 3.1, "Features of the PC/TCP Software
Development Kit"

Section 3.1 of the User's Guide incorrectly lists the Retriever
diagnostic utility as one of the features of the PC/TCP SDK. The
Retriever application is not a feature of the PC/TCP SDK.

Section 3.1 also says that the PC/TCP SDK provides the source code
for an rpcinfo application, which you must compile to build the
rpcinfo.exe file. The PC/TCP SDK contains the rpcinfo.exe file
already compiled, along with the source code for building the
executable.

5.2 RPC Programming Additions and Corrections

5.2.1 Header Files in Code Examples

The RPC Programming manual is based on documentation from Sun
Microsystems. Some of the examples include header files that are not
part of the PC/TCP SDK. For example, the server code in Section
3.2.2, "Intermediate Layer," includes the header files utmp.h and
rpcsvc/rusers.h, neither of which is in the PC/TCP SDK. For the code
in Section 3.2.2, the only header files needed are rpc/rpc.h and
stdio.h.

5.2.2 Correction to Section 1.4, "RPC Utilities Command Reference"

The description of the rpcinfo command, on page 1-7, incorrectly
states that the rpcinfo command is not supplied in executable form,
and that you must compile it from the source code supplied. The
PC/TCP SDK contains the rpcinfo.exe file already compiled as well as
the rpcinfo source code.

5.2.3 Correction to Chapter 2, "The rpcgen Programming Guide"

Note number 2 on page 2-2 lists the compiler flags you should use.
The /Au flag is incorrectly listed as /AU. The compiler is case
sensitive for this flag, so the "u" must be lowercase.

5.2.4 Correction to Section 2.4.9, "Special Classes"

The examples in this section are not code. They exemplify the
differences between xdr code and C language code. For example, the
Booleans example is the following:

bool married; --> bool_t married;

The "bool married;" is the xdr representation, and the "bool_t
married;" is the C language representation.

5.2.5 Addition to Section 4.4.6, "Strings"

The second to the last paragraph on page 4-10 mentions a buffer
pointed to by *sp. Note that the length of that buffer must be
greater than maxlength to accommodate the NULL that gets appended to
the end of the string.

5.3 System Call Reference Additions and Corrections

5.3.1 Additions to Section 2.2, "Routine Reference."

Because of a kernel limitation, the first UDP write, using
net_write() or net_writeto(), to an unconnected host blocks during an
ARP. This is true even for a nonblocking network descriptor.

5.3.2 Corrections to Section 2.2, "Routine Reference."

- The ad_res_name(), nm_prs_addr(), and nm_res_name() name
resolution functions do not return errors when the IP address
specified is an invalid address. For instance, the functions
interpret the address string "128.127.2" as "0.128.127.2".
If passed an invalid IP address, the ad_res_name() and
nm_res_name() functions eventually return the error code
NET_ERR_HOSTUNKNOWN instead of returning NET_ERR_BADFORMAT.
This behavior supports some addressing conventions that are
now obsolete. For instance "128.127.50.105" and
"128.127.12905" are equivalent IP addresses; however, the
latter form fell out of common use with the advent of
subnetting.

- The net_write() routine returns 0, not -1, if the error
conditions NET_ERR_RESET or NET_ERR_WOULD_BLOCK occur.


6.0 Fixed Problems

This section describes the problems in the previous release that have
been fixed in this release.

6.1 Fixes in the FTP Library

The ftp_put() routine no longer writes an "opening data connection"
message to STDOUT.

6.2 Fixes in the RPC Library

A DOS server application created using the Borland libraries can now
run in a DOS session in Windows while the Portmapper for Windows
(Wportmap) application is running. Portmapper for Windows is part of
the OnNet SDK.

http://cndos.l009.com/filedown/files/PCTCPSDK.zip