DEC Digital Alpha VME 4/224 User Manual page 304

$ create sample.
show version
ls -l sample
(Control-Z exit)
$
2. Make the file compatible with the MOP load protocol. To accomplish this,
run the add_header.exe program to append a one-block header to the file,
making it compatible with the MOP load server. This executable program
is on the Firmware Update CD at [ALPHAVME]ADD_HEADER.EXE. If
you prefer, copy the file to the SYS$LOGIN area and define it as a foreign
command, for example, addhead. To run the program, invoke addhead, and
supply the file name as input and a name for the resulting output file.
The current MOP load protocol only supports 15-character file names. To
make use of all 15 characters in the name, do not specify a file extension.
The MOP server defaults to a file extension of .sys.
3. Place the output file in the MOP server's load file directory, MOP$LOAD.
Whenever MOP gets a request for the script, it searches in its service area.
At this point, the script file is available on the Ethernet segment of the MOP
server. If the Digital Alpha VME 4 system is on the same Ethernet segment as
the MOP server, the following example copies the script file over the network.
The string, mopdl:sample.sys/eza0, specifies that the file, sample.sys, can be
accessed over the Ethernet device, eza0, using the MOP download protocol driver,
mopdl:.
>>> cat mopdl:sample.sys/eza0
show version
ls -l sample
>>>
The redirection ( > ) operator may be used to redirect the output of the cat
command into a local file. In this case, the output is redirected to sample.
>>> cat mopdl:sample/eza0 > sample
Once the >>> prompt returns, the file copy has completed. The resident script
file, sample can then be displayed and executed using the following sequence of
console commands:
12–16 Console Primer
Note
# Be patient! The MOP protocol is slow.
# Remember be patient!