Chip 1995 March

home *** CD-ROM | disk | FTP | other *** search

/ Chip 1995 March / CHIP3.mdf / demo / pctcp / program / disk1 / readme.txt < prev next >

Wrap

Text File | 1994-07-14 | 14.7 KB | 378 lines

README.TXT PC/TCP ONNET 1.1 PC/TCP NETWORK SOFTWARE 3.0 Contents 1 Installing PC/TCP OnNet and PC/TCP Network Software 1.1 Using Multiple TCP/IP Protocol Stacks 1.2 Choosing a DOS or Windows Install 1.3 Upgrading 1.4 Installing with Windows for Workgroups 3.11 1.5 Removing Obsolete Parameters From The \WINDOWS\SYSTEM.INI File 1.6 Possible Problem With NDIS 1.X, PROTMAN.DOS, and NETBIND 1.7 Deleting files during an upgrade from PC/TCP Network Software, V.2.3 1.8 Installing Multiple Kernels, and Adding New Components or Interfaces 1.8.1 Installing More than One Type of Kernel 1.8.2 Installing both a TSR and VxD kernel (OnNet only) 1.9 Decompressing Files 1.10 Installing PC/TCP With Microsoft Chicago (Windows 4.0) 1.11 Windows Install bug updating SYSTEM.INI 1.12 Reinstall New behavior is misleading 2 Kernel Name Resolution And Third-Party Applications 3 Using InterDrive With a 3C503 Card 4 TN Negotiating The X-Display Option 5 Resizing The PC/TCP Windows TNVT Scrollback Buffer 6 PC/TCP Windows FTP Application 6.1 Percent Transferred Graph 6.2 Using a Command File 7 PC/TCP Windows FTP Server and Server Control Applications 8 PC/TCP Windows Archiver Application 8.1 Setting the working directory when you archive files 8.2 Setting the working directory when you restore files 9 Customizing Sessions in the Reference Desk "Beyond Books" Menu 1 Installing PC/TCP OnNet and PC/TCP Network Software 1.1 Using Multiple TCP/IP Protocol Stacks Two TCP/IP protocol stacks cannot run simultaneously over a single network card and driver. Both TCP/IP stacks require the same packets (such as IP and ARP), and the driver can give these packets to only one stack. Because of this, you cannot use PC/TCP concurrently over a single network card with another TCP/IP protocol stack, such as Microsoft TCP/IP. 1.2 Choosing a DOS or Windows Install The INSTALL.EXE program in DOS does not install any Windows files or configure the product to run in Windows. To use PC/TCP in Windows, you must use the PC/TCP Windows SETUP.EXE program. For more information on how the Install program lets you choose networking programs for Windows or in DOS, see the PC/TCP manual "Getting Started" and the PC/TCP Release Notes. 1.3 Upgrading If you are upgrading, exit any PC/TCP Windows applications before you run SETUP.EXE. The kernel and other TSRs, such as InterDrive, can be loaded when you run the Setup program. 1.4 Installing with Windows for Workgroups 3.11 When installing with Windows for Workgroups (WfW) 3.11, you must use the WfW Network Setup program to install an NDIS driver before running the PC/TCP SETUP.EXE. You usually do this at the time you install Windows for Workgroups. For PC/TCP Networking software (TSR kernel), choose a Real Mode NDIS Driver. For OnNet (VxD kernel), choose an Enhanced Mode NDIS driver (or if you want to manually switch between the VxD and TSR kernels, choose "Real Mode and Enhanced Mode NDIS Driver"). You can also run over ODI drivers under WfW with either the TSR or the VxD kernel. See the installation procedures in the manual "Managing PC/TCP" for more information. 1.5 Removing Obsolete Parameters 1.5.1 From The \WINDOWS\SYSTEM.INI File These SYSTEM.INI lines were required in the PC/TCP Network Software v.2.3 release, but are now obsolete. The Install program removes any of these entries: [386Enh] device=wfwftp.386 secondnet=wfwftp.386 device=vpctcp.386 secondnet=vpctcp.386 Install does not remove the dis_pkt.gup entry from the Windows SYSTEM.INI file. This entry does no harm but you can remove it if you do not intend to use the TSR kernel. 1.5.2 From the AUTOEXEC.BAT File Setup, when installing the VxD kernel, will remove netbios.com, idrive.exe, idmnt.exe, idnet.exe and setclock.exe commands from AUTOEXEC.BAT because the VxD does not support networking in DOS. If you have other network commands in AUTOEXEC.BAT they will fail. If the netbios.com command is in AUTOEXEC.BAT, Setup adds the parameter "vnbep=yes" to the [pctcp vxdinit] section of the PCTCP.INI file. If the idrive.exe command is in AUTOEXEC.BAT, Setup adds the parameter "vidrive=yes" to the [pctcp vxdinit] section of PCTCP.INI. This provides NetBIOS and InterDrive functionality under Windows using the VxD kernel, if you were previously using this functionality. If you were using setclock.exe in AUTOEXEC.BAT you can manually add the setclock.pif to the Windows Program Manager startup group. See the manual "Using PC/TCP in Windows" for more information. 1.6 Possible Problem With NDIS 1.X, PROTMAN.DOS, and NETBIND The INSTALL and SETUP programs copy the NDIS 2.xxx redistributable files PROTMAN.DOS and NETBIND.EXE when you install an NDIS driver. If you already have older copies of these NDIS files, and the netbind command in AUTOEXEC.BAT does not include a path, the netbind command may fail. The \PCTCP directory is added to the path first. This causes the new version of netbind to run, which is not compatible with the old version PROTMAN.DOS in the CONFIG.SYS file. To resolve this, either add the complete path to the old netbind command. Or, change the pathname in CONFIG.SYS to use the new PROTMAN.DOS in the PCTCP directory. 1.7 Deleting Files During an Upgrade from PC/TCP Network Software, V.2.3 The install program is conservative in choosing the files it deletes when upgrading into the same directory. It does not delete the following old files, which you may want to delete manually: aexecftp.bat autoinst.cwa autoinst.exe autoinst.hlp board.dat config.ins ftp.ico kappconf.cwa kappconf.exe kappconf.hlp kappconf.pif lpq.ico lpr.ico mail.ico merger.exe pctcp.aib pctcp.ico ping.ico protocol.ftp samp_net.cfg system.ftp template.ini tn.ico To see which files are removed see the [remove] section of FILES.INF. 1.8 Installing Multiple Kernels, and Adding New Components or Interfaces 1.8.1 Installing More than One Type of Kernel If you use your computer over both a LAN (Local Area Network such as Ethernet) and a Serial port using SLIP or PPP, you need to install two kernels, and need to run the install program twice. 1. Run the Install program. If an existing driver is found you should choose not to use it. 2. Choose Serial port using SLIP or Serial port using PPP from the list of Network Cards. 3. Then run the install program a second time. 4. At the Reinstallation dialog choose "Add" If an existing driver is found you should choose it, otherwise choose your driver from the list of Network Cards. 1.8.2 Installing both a TSR and VxD kernel (OnNet only) To install both a TSR and VxD kernel you must run the install program twice. 1. Run the Install program 2. Choose "Custom" from the New or Upgrade dialogs. 3. Choose "Dos and Windows" (TSR Kernel) at the Network Connectivity dialog. 4. Run the Install program a second time 5. Choose "Add" from the Reinstallation dialog. 6. Choose Windows (VxD Kernel) at the Network Connectivity dialog 7. Choose an existing driver or a Card from the Network Card dialog. This creates an additional interface. 8. You can either enter IP configuration for this interface or use the Configuration program later to remove this extra interface. 1.8.3 Adding Components When reinstalling and you just want to add Components (not a new network card), make sure that you choose none in the Found Existing Drivers dialog and choose none in the Network Card dialog. If you add a new network interface card, the program prompts you to add a new IP address. 1.9 Decompressing Files The PC/TCP files are compressed using a Microsoft compression utility. To manually decompress a file from the disks, you can use the standard Windows EXPAND.EXE utility, usually located in the \WINDOWS directory. As described in the hardcopy doc, you can also use the SETUP.EXE /Z or the INSTALL.EXE /Z command. 1.10 Installing PC/TCP With Microsoft Chicago (Windows 4.0) During its second Beta, Microsoft changed the Chicago protocol-to-driver interface from NDIS version 3.0 to NDIS version 3.1 to support the dynamic loading and unloading of drivers and protocols. FTP Software supports NDIS version 3.0 and is working on support of the updated NDIS 3.1 VxD. If you are a Chicago Beta site and need to use Chicago with PC/TCP, contact FTP Software Technical Support. 1.11 Windows Install bug updating SYSTEM.INI If the existing SYSTEM.INI file has the secondnet.drv parameter set to PCTCPNET.DRV (capitalized or mixed case), Windows Install does not recognize that pctcpnet is already installed and sets secondnet.drv to pctcpnet.drv (in lower case) and adds parameter pctcpchain=PCTCPNET.DRV. This causes Windows to fail to load. If you find both secondnet.drv and pctcpchain parameters set to pctcpnet.drv remove the pctcpchain parameter. 1.12 Reinstall New behavior is misleading When running install a second time the Reinstallation dialog offers choices Add and New. The choice New says that it uses existing installation information. It does use existing IP and DNS configuration but it creates a new PCTCP.INI file. The old PCTCP.INI file is backed up so you can restore all your old configuration from there. 2 Kernel Name Resolution And Third-Party Applications To make the PC/TCP kernel smaller, Domain Naming Service (DNS) code was moved out of the kernel into a separate library. If you are using applications written with the PC/TCP Development Kit in an earlier version of PC/TCP and which use the PC/TCP kernel for name resolution, keep the [pctcp kernel] parameter "kernel-does-dns=yes" in the PCTCP.INI file. Setting this parameter to "no" shrinks the kernel by 6.5K. Set this parameter to "no" if you do not use old applications which require DNS support in the kernel, and want to free more low DOS memory. 3 Using InterDrive With a 3c503 Card The 3c503 interface card and some older network cards such as the NI5210 or 3c501 do not work well with 8K reads from the InterDrive VxD or TSR client. If you are using the 3c503 card with InterDrive and are having problems copying files or running programs from the network drive, set the parameter "read-size=1024" in the [pctcp idrive] or [pctcp (filesystem)] section of the PCTCP.INI file. 4 TN Negotiating The X-Display Option If you have an X-server running on your system, DOS TN.EXE does not negotiate the X-display option. To do so, specify "pktdrv-loopback=yes" in the [pctcp kernel] section of your PCTCP.INI file. 5 Resizing The PC/TCP Windows TNVT Scrollback Buffer If you change the size of the TNVT scrollback buffer, TNVT will only retain (or save) one screen of data containing the last 25 lines of the scrollback buffer. This frees memory resources for other applications. 6 PC/TCP Windows FTP Application 6.1 Percent Transferred Graph When you transfer files with the PC/TCP FTP Windows application, a copy progress bar shows the percentage of files transferred. If you transfer files larger than 6.3 Megabytes, the percentage increments correctly and the file is transferred, but the black bar disappears and then a while later starts over again at the far left of the bar frame. If you transfer files from a UNIX host, FTP includes newline and formfeed characters in this calculation. Due to the addition of these characters, a transfer may continue after the graph indicates that 100% of the files have been transferred. When cancelling a file copy of a very large file, the cancel may take several minutes. 6.2 Using a Command File The FTP Windows application does not support using a command file as documented in the "Transferring Files" chapter of the "Using PC/TCP in Windows" manual and in the online help for the FTP application. This application does not contain the Run Command File entry on the Command menu. 7 PC/TCP Windows FTP Server and Server Control Applications If you have a file transfer in progress with the Windows FTP Server, and you attempt to close the Server Control application, Server Control will not exit cleanly, and you will not be able to reload Server Control and the servers later. If you are using the FTP server and have an active file transfer in progress, first stop the Windows FTP Server, then exit the Server Control application. 8 PC/TCP Windows Archiver Application When you use Archiver, you usually restore files to the same directory that contained the files when Archiver backed up the files. You can also restore files to a different directory. To do so, you must: -Set the working directory when you archive files -Set the working directory when you restore files 8.1 Setting the working directory when you archive files 1. In Archiver, choose Archive from the Commands menu. The Archive dialog box appears. 2. Under Archive To, specify the information for the archive. 3. Under Archive Files, type a dot (.) in the File Names box. 4. Set the working directory by choosing a Select Files button. In the Select Files box, select the Drive and Directory that you want archive from. Choose CANCEL to close the box. Windows sets the working directory for Archiver as the directory that you selected. 5. Choose Start Archive. 8.2 Setting the working directory when you restore files 1. In Archiver, choose Restore from the Commands menu. The Restore dialog box appears. 2. Under Restore From, specify the information for the restoration. 3. Under Restore Files, type a dot (.) in the File Names box. 4. Set the working directory by choosing the Select File button. In the Select Files box, select the Drive and Directory that you want to restore to. Choose CANCEL to close the box. Windows sets the working directory for Archiver as the directory that you selected. 5. Choose Start Restore. Note: Any time that you select a drive and a directory in a Select Files dialog box, Windows sets that directory as the working directory for Windows applications. 9 Customizing Sessions in The Reference Desk "Beyond Books" Menu The manual "Using PC/TCP in Windows", Chapter 2 (Viewing Documentation Online) states that you cannot customize the Beyond Books menu with specific Windows FTP and TNVT session names. However, it IS possible to use the -S session_name option when you customize the Beyond Books menu. This lets you launch pre-defined FTP or TNVT sessions from within the viewer.