/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\ * |_o_o|\\ Copyright (c) 1988, 1989, 1990 The Software Distillery. * * |. o.| || All Rights Reserved * * | . | || Written by Doug Walker and John Toebes * * | o | || The Software Distillery * * | . |// 405 B3 Gooseneck Drive * * ====== Cary, NC 27513 * * BBS:(919)-471-6436 * \* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */ This material is Copyright (c) 1988, 1989, 1990 The Software Distillery. All Rights Reserved. The Parallel Port Network code (PPN code) is Copyright (c) 1989 by Matthew Dillon. This project brought to you by: Doug Walker and John Toebes (NET: handler, lots and lots of code) Matthew Dillon (PPN code communications module) It may be distributed freely as long as the following restrictions are met: 1. All files present in the distribution package must be redistributed with the package, including this documentation file. If you distribute on diskette, all files must be on a single diskette. 2. The distributor may charge a fee to recover distribution costs. The fee for diskette distribution should not be more than the cost to obtain the same program from Fred Fish or The Software Distillery, whichever is greater. Current charge from The Software Distillery is $6 per disk, including all postage and handling charges. 3. The distributor agrees to cease distributing the programs and data involved if requested to do so by authors or any member of The Software Distillery. ------------------------------DISCLAIMER Neither The Software Distillery nor any of its members will be liable for any damage arising from the failure of this program to perform as described, or any destruction of other programs or data residing on a system attempting to run the program. While we know of no damaging errors, the user of this program uses it at his or her own risk. -----------------------------FUNCTIONALITY The programs in this distribution allow a one-way network file system to be established via the parallel ports of two Amigas. A special cable is required to connect the parallel ports. Once connected, the NET: file system behaves just like a disk device, allowing copies, reads, writes and so forth. It works with the workbench. ============================================================================ RUNNING THE NETWORK HANDLER: These instructions talk about a 'local' machine and a 'remote' machine. The 'local' machine has the NET: handler running. The 'remote' machine has the server running, and is likely the one with the hard disk you want to access. 0. Make a cable according to the instructions in the enclosed 'Cable.doc' file. Connect the two Amigas with the cable. 1. Copy parnet.device to your DEVS: directory on both machines. 2. Put a mountlist entry for the network handler in the local machine's DEVS:MOUNTLIST. You can do this by appending the enclosed 'mountlist' file to your DEVS:MOUNTLIST file. Simply attach the enclosed file to the end of DEVS:MOUNTLIST with a text editor. 3. Copy netpnet-handler to the l: directory on the local machine. 4. Copy netpnet-server to the C: directory on the remote machine. Issue the command 'run netpnet-server' on the remote machine. WHENEVER YOU START THE NETWORK, YOU MUST BE SURE TO RUN THE SERVER ON THE REMOTE SIDE FIRST. 5. Issue the CLI command "MOUNT NET:" on the local node. The first reference to NET: after the MOUNT command will load the handler. 6. NET: will at first appear to be empty if you do a DIR of it from the CLI. You can refer to devices on the remote side by NET:devicename/path (for example, NET:DH0/C/LIST) This will force NET: to mount the remote device. The device (DH0 in this case) will appear in a DIR of NET: after this. The 'devicename' you use can be any mounted device or volume on the remote machine. 7. If you want to use NET: with the workbench, you must provide an icon file for each device you mount on the remote machine. You can do this by copying any drawer-type icon file to NET:devicename.info after the specified devicename has been mounted. CD NET:DH0 ; make sure DH0 is mounted COPY SYS:C.INFO NET:DH0.INFO ; make sure DH0 has an icon file You only need to do this once for hard disks and other permanent devices, but RAM: will 'forget' this icon every time you reboot, so you will need to recopy the icon each time. (NOTE: A file will appear in the root of the remote device called 'node.rinfo'. This is where NET: stores the icon file you give it. Deleting the node.rinfo file will remove your device's icon.) Note that if you do a DIR of NET:, you will always see the .info files for your mounted remote devices EVEN IF THEY DO NOT EXIST. NET: assumes the icon files are there, and doesn't go check unless it needs to. If your .info files are appearing with the DIR command, but not under workbench, you need to copy a drawer-type icon into NET: as described above. ============================================================================ The provided NETSTAT command gives you a visual idea of how much work your network is doing. Run it with the command RUN NETSTAT NET: Click on the close gadget in the upper left corner to exit. ============================================================================ Differences and enhancements: VERSION 05/09/89: First version released using DNET VERSION 07/18/89: - Speed improved due to decreasing minimum packet size Should help when loading executables over the network and when doing directory operations. - Debugging code removed This makes the code smaller and faster - Bug fixed in the ACTION_CREATE_DIR packet VERSION 08/89: First Parallel port version released VERSION 04/90: Second parallel port version released - Various minor bug fixes - ACTION_SET_DATE packet implemented - Support added to allow rebooting of one node independant of the other - Automatic mounting of remote nodes at first reference added - Using Matt Dillon's new parnet.device ============================================================================