The $25 Network
							---------------

This is a very simple, facility-sharing network.  At this point it
will only connect two machines, but both machines are useable while
the net is in place, and very little memory is used.  The author
is preparing a multi-node version.

A standard null modem cable is used to connect the computers.

CONFIGURATION -
-------------

CONFIG.SYS:

buffers=10
	Must be 10 at least

device=netshare.sys lpt2 lpt1
	May have this line as many times as you have non-disk
	devices to share.  In this case LPT2 is the name you want to
	use locally, while LPT1 is the `real name' on the remote.
	"device=netshare.sys fred con" would assign the remote
	console (screen) to the device name Fred.  Again, you may
	have as many lines as you want here, one for each device.
	We are talking about HIS devices here, not yours.

device=netunits.sys
	Simply put this in.  It establishes the drive blocks.

device=net00000.sys
	Must be the last thing in your CONFIG.SYS.  Extablishes the device
	driver stack pointer, which DOS fails to do.


AUTOEXEC.BAT:

net$25 int12
	Put anywhere (I think).  Other options on the command line
	include:
		debug - verbose error/status messages
		server - one side should have this.  Eliminates
		         some conflicts.  The server will wait
		share:xy - specifies which drives to share.  Without
				   it, all drives are shared.  share:cd would
				   share only the hard drives, etc...
	    comx - Allows you to assign other com port besides com1

	Also note that INT12 means use interrupt 12.  You may want to
	change this if things do not work.


That's it!
 
 You can boot one system and not the other, and as long as you do not try
 and access net drives/devices, it is not a problem.  (If you do you get
 normal DOS device not ready, and so on).  The docs claim that the net
 will not work with `big drive' drivers like vFeature, but I think they
 may be wrong - still experimenting myself.

-s-