 wjm 28-apr-1997: NDFP V5.4  , 	This is the third BETA release of NDFP, the 		Network DOS File Protocol + 	which is intended to make a PC running DOS 0 	(or the like) into a file & disk (etc.) server.  2 	Featuring My Own Ethernet Protocol (MOEP) ... :-)   Pieces included:/ 	- stand-alone PC server program sources [.PC], & 	   written in Borland Turbo PASCAL V6  2 	- VMS client library & utility sources [.VMS...],& 	   written in C and very little MACRO   Legal:1 	Like any piece of software not marked otherwise, . 	NDFP is implicitly copyrighted by its author.  4 	Seeing the paranoia (as it seems to me) that people3 	have about PC software, I went into the trouble of / 	including explicit copyright notes into all of  	[.PC]*.PAS, viz.   H Copyright (C) 1997 Wolfgang J Moeller. All rights reserved. NO WARRANTY!  5 	Nonetheless, this is a fun project, and not intended 1 	as a commercial offering, so for the time being,   5 	"License is granted to everyone to evaluate, modify, 2 	 and use for non-commercial purposes the software) 	 contained within this ("NDFP") package. 4 	 Non-commercial re-distribution permitted, provided2 	 it contains all of the original files, including 	 the above copyright notice."  0 	If there's sufficient interest, I intend to put2 	all of my material under the GPL, so keep telling- 	me about your experiences & enhancements ...   5 	All of the files in the [.VMS.GCE-*] subdirectories, / 	plus [.VMS]FQHOST-ND.MAR, are exempt from this 9 	conditions, being (mostly) the work of Glenn C Everhart; , 	maybe they even are in the "public domain".   Disclaimer: : 	"Wolfgang J Moeller ASSUMES NO RESPONSIBILITY FOR THE USE; 	 OR  RELIABILITY OF HIS SOFTWARE ON EQUIPMENT WHICH IS NOT ! 	 SUPPLIED BY Wolfgang J Moeller" 2 	In fact, there's pretty little such equipment :-)  4 	So far, my employer (GWDG), hereby acknowledged for4 	permitting me to beta-test & distribute my software2 	via their facilities, has little to do with NDFP,, 	which is all "home-grown" in my spare time.  	 Features: 0 	LAN-wide access to most of DOS's I/O facilities4 	(files, directories, disks, pseudo-files like PRN), 	and the DOS system clock.  ( 	All "synchronous" (non-overlapped) I/O.  4 	Theoretically, an unlimited number of client nodes,2 	with  up to 255 client connections per node - the1 	current server implementation, however, imposes  0 	much smaller (arbitrary & configurable) limits.  1 	In the best DOS tradition, no access protection  0 	at all - adding some authorization based on LAN% 	addresses should be do-able, though.   2 	Virtually state-less server operation: the server2 	program can be (orderly) terminated any time, and2 	re-started later, without causing harm to clients1 	(not that I had tested _all_ possible cases :-).   3 	Moderate throughput - a Vs2000 talking to a 16 MHz 0 	80386 will rarely reach 100 kb/sec; more recent: 	hardware has been seen to attain more than 300 kb/sec ...   Hardware requirements:# 	"IBM compatible" PC with at least  & 	  several hundred kilobytes of memory  9 	Some PC "network card" with "DOS packet driver" support.    	Ethernet (or equivalent).  < 	One or more operational VMS systems with ethernet interface 	 (or equivalent).   Software requirements:# 	A reasonably recent version of DOS - 	 (so far, I know nothing but MS-DOS 6.22 :-)   / 	DOS "packet driver" for the PC's network card.   5 	VMS V5 or later (approximately; VAX V5.3 .. AXP V6.2  	have been tested).   !     For building the PC software: ? 	Borland Turbo PASCAL, minimum of V6 ((anyone around with V7?))   "     For building the VMS software:< 	C compiler as appropriate (VAX C V3.2, GNU C V2.7.1, DEC C)% 	VMS "program development" subset :-)    Optional hardware: 	PC floppy disks (maximum of 2) " 	PC hard disks (maximum of 24 [?])" 	PC CD-ROM drives (maximum of ???) 	PC printer, ...  D 	VMS diskette drive (for duplicating floppies across the network :-)   Optional software:- 	SMARTDRV, Windows 3.x (plus WINPKT.COM), ...   7 	VMS virtual disks & tapes (cf. [.VMS...]000README.WJM)    Installation & use:   C     PC: Somehow transfer the .PAS sources in the [.PC] subdirectory : 	to a PC with Turbo PASCAL V6 (a later version might work,> 	but I haven't seen one yet) and compile them, e.g. by running% 	MAKE5.BAT, resulting in ETHNDS5.EXE.   ; 	Caveat: ETHNDS5 has no intelligence (yet) to automatically 6 	locate the packet driver (like e.g. KERMIT), instead = 	ETHNDS5.PAS has a packet driver interrupt of 0x78 hard-coded D 	(which really isn't anyone's default but mine); modify as required.  ; 	On the target PC(s), load the packet driver appropriate to 6 	their network card, and invoke ETHNDS5.EXE, like e.g.  
 		NE2000 0x78 	 		ETHNDS5   " 	Note: ETHNDS5 isn't a TSR. Sorry.  8 	Terminate the server program (any time) by hitting the 7 	space bar (currently, any key not mentioned below will 2 	also do). Hit <RETURN> to have some packet driver7 	statistics displayed, or hit "L" (provided ETHNDS5 has 6 	been compiled with LOGGING enabled) to enable/disable2 	a comprehensive "transaction" logging. That's it!  2 	In case you want to try ETHNDS5 under Windows 3.x4 	(it _seems_ to work there, but not much testing has3 	been done), find WINPKT.COM somewhere (part of the 3 	"Crynwr packet driver collection" PKTD*.ZIP), and  3 	load it after the packet driver, prior to starting  	Windows, like  
 		NE2000 0x78 
 		WINPKT 0x78  		WIN   5 	Note: WINPKT seems to be unforgiving in that loading 6 	it twice makes the packet driver un-usable until next4 	boot. I'm not aware of any "installation check" :-(2 	((anybody seen the source code of this beast???))  3 	BTW, this is quite analogous to the setup required 4 	for running Trumpet TCP/IP over Ethernet. Maybe the 	two can even co-exist ...    *     VMS: Compile the sources in [.VMS] via   		@MAKE-SHR  		@MAKE-UTIL  7 	resulting in NDFP_SHR.EXE (shareable "access" library) # 	and a lot of ND_*.EXE executables.   8 	Define logical names NDFP_SHR (preferably system-wide),3 	optionally NDFP_ETH_DEVICE (also system-wide), and 7 	NDFP_SERVER (any way you like), plus maybe DCL symbols 9 	for the execuatbles. See [.VMS]SETUP.COM for an example.   ; 	Find some more information, plus some more things that you ( 	can "MAKE", in [.VMS...]000README.WJM .  4 	Somehow get hold of SYSLCK privilege - the programs4 	will not run without it! See you system manager :-)   	Beginner's example:  ( 	$ define NDFP_SHR dev:[dir]NDFP_SHR.EXE: 	$ define NDFP_ETH_DEVICE ESA0:		! name of ethernet device 	... 	$ set process/priv=SYSLCK 	...: 	$ define NDFP_SERVER 00-11-22-33-44-55	! PC's LAN address 	$ mcr dev:[dir]ND_DIR-R  C:     Limitations etc.: 9 	- This version of NDFP uses Ethernet protocol type 60-06 9 	  ("reserved to DEC customers"). It seems that a private 8 	  protocol type is hard to come by these days, although8 	  only a very small fraction of the ~60k possible types5 	  are generally known to be used. Donations welcome!   ' 	  BTW, if you have to, locate & modify " 		"($60,$06)"	in [.PC]ND_CONST.PAS  		"0x6006"	in [.VMS]NDFP_PROTO.H  < 	- if this software indeed finds use outside of my home LAN,9 	  something ought to be done about access control. If it 8 	  wasn't for my SLOW home machines, I'd consider using  	  nothing but "encryption" :-)   6 	- there are NO provisions made for file sharing among8 	  clients of a NDFP server, and nothing in the software6 	  is aware of the fact that all of DOS files, disks, 6 	  and "drives" in fact refer to the same set of data. 	  BE CAREFUL!  5 	- probably more that I'm not aware of (still waiting  	  for BETA test reports!).   O Wolfgang J Moeller, <moeller@gwdg.de> (preferred), and also <w.j.m@t-online.de> 