From: ARISIA::EVERHART "GLENN EVERHART, 609 486 6328" 25-SEP-1987 08:47 To: EVERHART Subj: CMU PCIP, how to get Date: Mon, 21 Sep 87 23:38:10 -0400 (EDT) From: Drew Daniel Perkins To: pcip@louie.udel.edu Subject: How to get MIT/CMU TCP/IP Package Well at least one person wants to know and I haven't posted it for a while so... We're pretty much finished with a full DEC VT102 emulator and I hope to release it pretty soon. Thanks to Ken Key from UTK I also have the Stanford FTP and multiconnection TCP running under MSC. And boy does it fly! I will be able to give this to anyone who can show me a license from Stanford, so if you don't have one yet, send them some a check and get yours! Can you beleive I'm promoting someone else's code :-) ? Drew The TCP/IP package for PC's better known as PCIP was developed at MIT using a cross compiler on a UNIX VAX. In order to make developement using this package easier, it has been "ported" to the Microsoft C compiler and Microsoft Macro assembler. You must have version 3.0 or higher of both the compiler and the assembler. Also you must have the Microsoft Make program, Librarian and linker that are distributed with the compiler and assembler. Getting CMU PCIP from the arpanet To get the CMU Microsoft C version of the PCIP package from the arpanet, connect to host "lancaster.andrew.cmu.edu" with FTP (no quotes when you really type it). This machine is a 4.2bsd UNIX system. Login in as user "anonymous", password "guest". Next, use the "cd" command to change your working directory to "pub". Now if you do a "dir" command you will get a listing of all the necessary files. First, "get" the files "readme" and "install.bat" in netascii mode. The rest of the files must be retrieved in binary/octet/image mode. Now retrieve the files "tarread.exe", "root.tar", "include.tar", "srcdev.tar", "srclib.tar" and "srccmd.tar". The file "doc.tar" is also available if you want the scribe documentation. The three large files, "srclib.tar", "srccmd.tar" and "doc.tar" are also available in "compressed" format. These files have a ".Z" extension. If you retrieve these, there is no reason to retrieve the original ".tar" files. These files are provided in case you have trouble transferring the large files over the network. The UNIX "uncompress" program may be used to regenerate the original ".tar" files. Once you have these on your local machine, use TFTP, kermit or some other file transfer program to get them to your PC. Put the files under a subdirectory such as c:\pcip. Make sure you do the transfers in the proper mode (octet or ascii, as above). The file "readme" explains what you have, and how to proceed farther. The program tarread.exe is a very small tar file reading program that I wrote. It has very few features, but it serves the purpose here. Getting CMU PCIP from BITNET To get the CMU Microsoft C version of the PCIP package from BITNET, retrieve the "pcip package" from host cmuccvma. To do this from an IBM VM system, type the command: "tell listserv at cmuccvma get pcip package" From a VMS system running JNET say: "send listserv@cmuccvma get pcip package" If you would like to automatically receive updates you can "subscribe" yourself. From VM use the two commands: "tell listserv at cmuccvma pw add 'password'" "tell listserv at cmuccvma afd add pcip package pw='password'" And from VMS: "send listserv@cmuccvma pw add 'password'" "send listserv@cmuccvma afd add pcip package pw='password'" In either case, replace 'password' with some string. Once you have received all of the files, you should have a collection of plain ascii files with a "boo" extension. These files are formatted specially so that they can get through BITNET unchanged (hopefully!). Once you have these on your local machine, use TFTP, kermit or some other file transfer program to get them to your PC. Put the files under a subdirectory such as c:\pcip. Since boo files are all plain ascii files, make sure you transfer them in netascii mode. I.e. if you are transferring them from a VM system, make sure that EBCIDIC to ASCII translation is done. If you are transferring them from a VMS system, JNET should have already done the transformation. The file "read.me" explains what you have, and how to proceed farther. Good luck, Drew Perkins arpanet: Drew.Perkins@andrew.cmu.edu phone: (412) 268-8576 US mail: Drew D. Perkins Carnegie-Mellon University 4910 Forbes Ave. Pittsburgh, PA 15213