 wjm 04-apr-1999:@ 	2nd beta test version (V0.13) of a 'secondary bootstrap' image E 	for Vs2000/uVAX2000 that allows for booting from a SCSI system disk  3 	(with PK2KDRVR & friends installed on the latter).   " 	Changes over V0.10 (22-feb-1999):  0 		(1) Support for a SCSI host id other than zero- 			(this goes together with *new* PK2K V1.3). * 			By default, the host id is still zero, . 			so there should be no compatibility issues.  % 		(2) Rudimentary CD-ROM boot support   			(still essentially untested).5 		This 'feature' adds a SCSI command into the normal  7 		disk boot path, which _could_ confuse some SCSI disk  9 		(for the ones I tested, it didn't). In 2KBTDRIVER.MAR,  1 		make "cdrom=1" into "cdrom=0" to turn this off.    -----   3 	The secondary bootstrap image comes in 2 versions: @ 	- 2KVMB.EXE (linked /SYSTEM=0/HEADER) for loading via ethernet:, 	  	Copy this image on some MOP server, then> 		 $ MCR NCP SET NODE {Vs2000} HARD ADDR {xx-xx-xx-xx-xx-xx} -% 					LOAD FILE {dev}:[{dir}]2KVMB.EXE  		Boot the {Vs2000} via  		 >>> B/{flags} ESA0 6 		with {flags} being those that you'd like to use with% 		"B DKAn00" if that command existed.   2 		Once 2KVMB runs, it prompts for "Boot device:" -6 		reply with "DKAn" (it understands only 4 characters)2 		to mean the SCSI disk known as "DKAn00:" to VMS.  4 		2KVMB will then boot from the SCSI disk so named, : 		expecting to find SYS$LOADABLE_IMAGES:PK2KDRVR.EXE there 		(plus the rest of VMS :-). 		  A 	- 2KVMB-SYSBOOT.EXE (linked /SYSTEM=0/NOHEADER) for loading from ? 		a disk bootable via ROM ('DUA0','DUA1' = "RD" type MFM disk,  ( 		'DUA2' = RX33-compatible floppy disk).  ? 		Make this image (contiguously, as it already is) available as $ 			DUA{x}:[SYS{k}.SYSEXE]SYSBOOT.EXE3 		in order to be able to boot into DKAn00:[SYS{k}], % 		{k} being the system root 'number'. < 		(CAREFUL - don't use a system root that exists on DUA{x}!)   		 >>> B/{flags} DUA{x} A 		will then load this image, which will prompt for "Boot device:" ? 		as above, and boot into DKAn00: if you reply "DKAn" as above. < 		The boot {flags} specified apply to both the 'primary' and; 		the 'secondary' boot. They would be e.g. {k}0000001 (i.e. 8 		8 hex digits) for an 'interactive' boot into [SYS{k}].   	Bugs/Features: 8 		- By default, SCSI unit 0 is being used by the 'host'.; 		  This means that the SCSI disks must be DKA100 .. DKA700 ; 		  in 'VMS standard' notation. With *new* PK2KDRVR (V1.3), A 		  this default can be changed; see 00README that comes with it.   3 		- the 'DKAn' boot replaces the 'MUA0' bootstrap.  > 		  Code for the remaining devices bootable via ROM (DU,ES,PR)= 		  is present in 2KVMB, and likely to work (but has no use).   8 		- the SCSI disk bootdriver does all data transfers via9 		  'programmed I/O'. This is very slow - not so relevant 4 		  at boot time, but _very_ noticeable at DUMP time7 		  (it takes several minutes to do a full memory dump  7 		  of a 'sizeable' Vs2000, i.e. one with 8MB or more).   C 	The 'source code' is mostly the product of DISM32 (old DECUS tool, : 	available these days from archives like ftp.wku.edu etc).A 	I didn't understand (or even read) most of 2KVMB.MAR, but added   	a few comments nonetheless.G 	2KBTDRIVER.MAR is the only thing that you can hold me responsible for, G 	but it's also largely based on TVBTDRIVER from the "KA410-B V2.3 ROM".   # 	*** No warranties *** (of course)!   < Wolfgang J. Mller, Gttingen, F.R.Germany	<moeller@gwdg.de>