/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\
* |_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                                *
*                    PLINK: DWALKER   BIX: DJWALKER                *
*                    BBS:(919)-460-7430  Deep Thought              *
\* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */

SEE THE FILE 'README' IN THIS DISTRIBUTION FOR IMPORTANT COPYRIGHT
INFORMATION.  CONTACT THE AUTHORS IF YOU DO NOT HAVE THIS FILE.

====================================================================

INSTALLING THE NETWORK FILESYSTEM:

1. Obtain and install a copy of Matt Dillon's freely redistributable
   serial port networking software, DNET.

2. Copy netdnet-server whereever you copy your DNET servers on your
   machines.  Add an entry to your S:DNET.SERVERS file for NET: with
   a server number of 9492.  A sample DNET.SERVERS file is included.

3. Put a mountlist entry for the network handler in the DEVS:MOUNTLIST
   file on both Amigas.  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.
   Mountlist entries are included for two devicenames, NET: and DNET:.
   If you also use the parallel port version of NET:, mount this version
   as DNET:.

4. Copy netdnet-handler to the l: directory on both machines.

====================================================================

RUNNING THE NETWORK FILESYSTEM:

1. Issue the MOUNT command on both Amigas:

      MOUNT NET:

2. NET: is now ready for access.  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.  No drawer icons will appear in the 
   workbench window for NET: until you have forced NET: to load them.  Simply 
   issuing the command

      CD NET:devicename

   will be sufficient to load the device 'devicename'.

   The 'devicename' you use can be any mounted device or volume on the
   remote machine.

4. 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 08/90

- Fixes for AmigaDOS 2.0

- Reboot support cleaned up

- Two-way connections supported

- One level of data copying removed to improve performance

- DNET version updated as well as new parallel port version

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

VERSION 08/89:
  First Parallel port version released

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 05/09/89:
  First version released using DNET

====================================================================