BZZZZZTTTT!!!!! You cannot set access the boot prom to set
this'n'that, but the box can still netboot as long as all the
proper settings have been made in the support files and assuming
the hosts rarpd and tftpd programs work properly.
By the numbers: (Larry has already done some of this)
1) Make a host file entry for the unit
2) Make a hostname/mac addr entry in /etc/ethers
3) mkdir /tftpboot;cd /tftpboot; ln -s tftpboot .
4) Uncomment tftpd from /etc/inetd.conf. I typically take out
the -s "secure" argument as well, it seems many UNIX's don't
get this right - besides, when you're done you should re-comment
tftpd anyway, it's a loser. Worse, on a coupla flavors of UNIX
the tftpboot dir and the boot image must be mode 777
5) Send inetd a HUP signal
6) Start rarpd -a
7) Do a binary get of the appropriate GENERIC image from Livingston
and place it in /tftpboot, in Larry's case it's easiest just to
leave it named GENERIC.IRX and forget all the hex hooha.
8) If your ComOS is already toast then just power it up, if this
is a non-fried ComOS netboot, raise DIP 2 and power up.
If it still doesn't work, well, that's why we added the boot
prom capability in D and new ROMS. :-)
-- Bri