Hi!

[del]
>I suspect that the mopd binary might work ok for booting pmax but that a
>special pmax bootloader would be needed for the mop-boot to work on my
>pmax machines.  Is this correct?

I don't think so. The mopd worked out of the box for me after I some
tweaking from Simon Burge, IIRC. The bootloader is PROM resident.

From the mopd man page:

DESCRIPTION
     Mopd services MOP Load requests on the Ethernet connected to interface or
     all interfaces if `-a' is given.  In a load request received by mopd a
     filename can be given. This is the normal case for e.g. terminal servers.
     If a filename isn't given mopd must know what image to load.

     Upon receiving a request, mopd checks if the requested file exists in
     /tftpboot/mop, the filename is normaly uppercase and with an extension of
     .SYS. If the filename isn't given, the ethernet address of the target is
     used as filename, e.g.  08002b09f4de.SYS and it might be a soft link to
     another file.

     Mopd supports two kinds of files. The first type that is check is if the
     file is in a.out(5) format. If not, a couple of Digital's formats are
     checked.

     In normal operation, mopd forks a copy of itself and runs in the back­
     ground.  Anomalies and errors are reported via syslog(3).

OPTIONS
     -a      Listen on all the Ethernets attached to the system.  If `-a' is
             omitted, an interface must be specified.

     -d      Run in debug mode, with all the output to stdout. The process
             will run in the foreground.

     -f      Run in the foreground.

HTH,
Uli
-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to:Something Good To Go By(The Decibels)
24539 Neumuenster, Germany|Cheap Excitement (Stratford Mercenaries)