From sm5ncz%sm5ncz.bbs@sm5sxl.ampr.org Sat May 02 04:06:02 1992 Received: from sm5sxl.ampr.org by sm5sxl.ampr.org with SMTP id AA266 ; Sat, 02 May 92 04:06:00 CET Received: from sm5ncz.bbs by sm5sxl.ampr.org with BBSFWD id AA263 ; Sat, 02 May 92 02:09:11 CET Date: Sat, 02 May 92 02:09:11 CET Message-Id: <516_sm5ncz.a@sm5sxl.ampr.org> From: sm5ncz%sm5ncz.bbs@sm5sxl.ampr.org To: sm5sxl Subject: tcpip410 X-BBS-Msg-Type: P Date: Thu, 30 Apr 92 18:45:41 CET Message-Id: <516@sm5ncz.ampr.org> From: sm5ncz@sm5ncz.ampr.org (Björn Karlsson, Vikbolandet.JO88FH.E.SWE.EU) Reply-To: sm5ncz@sm5ncz.ampr.org To: sm5sxl@sm5sxl Subject: tcpip410 X-Mailer: User Agent V1.3 X-BBS-Msg-Type: P SUPERTCP.ZIP (566704 b) ligger i mitt c:\users\program\tcpip -bibliotek. Detta är en tcpip avsedd för INTERNET och körs under WINDOWS. Den har SLIP så att det går kanske att använda den för våra applikationer. Zippa upp filen med "PKUNZIP -D SUPERTCP A:" så skapas det en installations- disk som man sedan kör INSTALL via windows. Nedan en READ-ME fil från disken: Copyright 1990-1991 Frontier Technologies Corporation .Super-TCP for Windows 3Version 1.2 4README.TXT 4July 1991 3INTRODUCTION For information on the Super-TCP for Windows applications, consult the printed manual after reading this file. If any discrepancies exist between the printed manual and this README.TXT file, this file should prevail. In addition to this README.TXT file, you have access to an Online Manual after Super-TCP has been installed. You may access the Online Manual by double clicking the "Online Manual" icon found in the Super-TCP group box. As is true of this README.TXT file, the Online Manual contents are more current and have precedence over the printed manual. (NEW FEATURES/ENHANCEMENTS IN VERSION 1.2 TELNET with TN3270 enulation: There is a TELNET with TN3270 emulation for accessing IBM systems using TELNET. Please see the Super-TCP for Windows Manual for details on the TN3270 program and the keyboard mappings. DOMAIN NAME: The host name resolution will now support up to three domain name servers. The SetupTCP program can be used to enable the domain name resolution and set up the main name server address. af NDIS Network Drivers: Super-TCP for Windows now supports 3Com/MicroSoft NDIS drivers. NDIS drivers are provided or can be obtained from the hardware manufacture. NDIS is the default method for Super-TCP for Windows to access the hardware. Token-Ring Support: Super-TCP for Windows now supprts TCP/IP over 802.5 Token-Ring. With the proper NDIS drivers for any Token-Ring hardware, Super-TCP is fully compliant with RFC-1042 on the usage of 802.5 Token-Ring. Windows SLIP support: Without the use of any special network drivers, Super-TCP for Windows can be used to connect to a remote system using the Serial Line Internet Protocol (SLIP) as defined by RFC-1055. This allows any 2 PCs to connect through the COM ports. This feature can also be used to connect to a network over a modem. Van Jacobson, Karn, and Nagle Algorithms: Super-TCP for windows now fully implements the Van Jacobson "Congestion Avoidance and Control", Karn "Round Trip Time Estimation", and Nagle "Congestion Control in IP/TCP" algorithms for throughput enhancements. LPR Enhanced Postscript printer support: LPR will correctly work with Postscript printers attached to computers running operation systems other than Windows. TELNET: TELNET should now properly respond to all TELNET negotiations. The user may specify a hostname and port number on the command line. There are several options for examining network activity. PING: Ping will perform integrity checks on data received from the network to ensure that it is what was sent. Ping timeout and interval can be configured. EMAIL: Has an option to send a preformatted RFC-822 message. This option allows for messages created elsewhere to be sent by specifying the file name. Sufficient header information must be present. af FTP: Will initialize with the local subdirectory as "\". (INSTALLATION AND SETUP NOTES There is now a separate program, INSTALL.EXE, that will copy all of the Super-TCP For Windows executable, library and data files onto your system and into the directories specified. INSTALL provides a status box indicating which files are being processed; both the source and destination filenames are displayed. You may abort installation at any time by pressing the key or clicking the "Cancel" button. Please be patient if the application does not repond immediately, the installation process will continue until the current file is copied. Once that file is copied, a message box asks you to confirm the decision to abort. Responding NO will continue installation; YES will end installation. If you elect not to modify AUTOEXEC.BAT, the file "SUPERTCP.BAT" will contain the batch file commands required to start the network. These commands must be executed before starting windows. To install and setup Super-TCP for Windows, a few steps must be followed: 1) Start Windows. For this installation, Windows should not be started automatically from boot up, (i.e. from AUTOEXEC.BAT). This is because the installation procedure will modify the AUTOEXEC.BAT file. 2) Place the "Distribution Disk P/N: R-284-01-01" disk into a floppy drive and from Windows Program Manager, choose "Run" from the "File" and type ,a:INSTALL where "a" is the drive letter of the floppy drive. When INSTALL begins, you are asked if you wish to veiw the README.TXT file on the distribution disk. If you answer NO, INSTALL continues; responding YES will launch NOTEPAD with the README.TXT file. NOTEPAD will run simultaneously with INSTALL; therefore, you will see a dialogbox for INSTALL. Ignore this dialog and select NOTEPAD to bring it to the top. When you have finished reading the text, you can exit NOTEPAD and return to INSTALL and the dialog will still be present and waiting. af 3) After all of the files have been installed onto your system, INSTALL will launch the Super-TCP for Windows setup program. SETUPTCP reads parameters from SETUPTCP.INF which has been copied to your system. SETUPTCP will allow the system administrator to configure the network parameters for this PC Host. You will be prompted for +a) directories in which the Super-TCP software should .be placed; +b) local internet address (IP address); +c) local official hostname; +d) gateway address, if one exists; +e) domain name server, if one exists; and +f) network hardware type and required parameters. 4) If you install an NDIS Network Driver, you MUST ensure that the the parameters for that driver are correct in the PROTOCOL.INI file found in the subdirectory where the NDIS files were installed (the default subdirectory is \ETC\NDIS). NOTEPAD can be used to edit this file. 5) Exit Windows. When the "Exit Windows" dialog box asks for confirmation of the exit request, ensure that the "Save Changes" check box is NOT checked. After Windows exits, you need to reboot the PC Host to start the network drivers and network software. 6) The installation has modified the AUTOEXEC.BAT and/or the CONFIG.SYS file. In order for these drivers to be available to Super-TCP for Windows the PC MUST be rebooted. 7) When Windows starts up again, you will find a Super-TCP group box. The system administrator should start the SETUPTCP program, enter "SYSADMIN" as the "User Login." As installed, no password has been assigned to the SYSADMIN account. The system administrator should use the "Change Password" feature of SETUPTCP to assign a password as soon as possible. The printed manual provides the necessary information about SETUPTCP that is required during installation. The system administrator account, SYSADMIN, is created during installation and must always exist. SYSADMIN has privileges that normal accounts do not. af During installation and setup, SETUPTCP may create or modify the following system files: AUTOEXEC.BAT boot batch file AUTOEXEC.FTC backup of original AUTOEXEC.BAT CONFIG.SYS boot configuration file CONFIG.FTC backup of original CONFIG.SYS WIN.INI windows configuration file SYSTEM.INI windows configuration file PROGMAN.INI windows configuration file PACKET DRIVER INSTALLATION 1) Frontier Technologies provides these packet drivers under General Public License (see COPYING.DOC found on the packet drivers disk). The packet drivers and source code can be obtained from Clarkson University. 2) During the installation of the packet driver, you will be prompted to enter information about the software interrupt used by the packet driver. SetupTCP includes a default value (0x7f) which should be proper for most installations of the packet driver. If the default value is not proper for your setup, your network administrator will be required to determine the proper value. Please refer to the file INSTALL.DOC found on the packet drivers disk for further information on the Packet Drivers. TO UPDATE A PREVIOUS INSTALLATION: 1) If NFS was previously installed use NotePad to remove the FTCNET.DRV from the network.drv= line in the SYSTEM.INI, exit Windows and then restart Windows to ensure that the printer client is not running during the update installation. If LPR has previously been enabled, use SETUPTCP to disable the network printer client, exit Windows and then restart Windows to ensure that the printer client is not running during the update installation. 2) Make sure the Super-TCP network software is not running. If it starts automatically, shutdown the Master-Server and Netup (for version 1.0c) or SuperTCP Messages (for version 1.1 or later). 3) Follow the steps listed above for installing Super-TCP Version 1.2. It is important to use the installation program on the Distribution Disks. 4) If you had any optional packages you MUST install the new version of that option. af PROBLEMS DURING INSTALLATION Should you experience difficulties during the installation procedure, you may need to abort out of INSTALL. If this happens, you should remove SUPERTCP.INI from your Windows subdirectory and try again. .