Chapter 3 ROM Monitor Commands
The boot command display (using bfs) looks like this:
monitor:: boot
Enter boot file name[(ip) “oper.63.enet”,\ (mop) “OPER_63_ENET.SYS”]::
Requesting default boot file “OPER_63_ENET.SYS” for MOP/VMS\ loads and “oper.63.enet” for all other protocols.
Unanswered requests shown as ‘?’,transmission errors as ‘*’. Requesting boot from 192.9.200.88 via Ethernet...
Booting BFS file using open delay of 8 Booting BFS file from 192.9.200.88
Header received OK. Received data blocks shown as ‘.’.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. . . . . . . . . . . ? . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . *
. . . . . . . . . . . . . . . . . . . . . . . . . . . . * . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . ? . . . . . . . . . . . . . . . . . .
. . . . . . . . EOF
The next example shows a boot using tftp. The Remote Annex always tries to open a file using bfs first. If unsuccessful, the Remote Annex uses tftp to open the file.
monitor:: boot
Enter boot file name [(ip) “oper.63.enet”, \ (mop) “OPER_63_ENET.SYS”]::
Requesting default boot file “OPER_63_ENET.SYS” for MOP/VMS\ loads and “oper.63.enet” for all other protocols.
Unanswered requests shown as ‘?’,transmission errors as ‘*’. Requesting boot from 192.9.200.88 via Ethernet...
Booting BFS file using open delay of 8
?
Booting TFTP file using open delay of 8 Booting TFTP file from 192.9.200.88
Header received OK. Received data blocks shown as ’.’.
.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . .. . . . . . . . . . . ? . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . * . . . . . . . . . . . . . . . . . . . . . . . . . . .
. * . . . . . . . . . . . . . . . . . . . ? . . . . . . . . . .
. . . . . . . . . . . . . . . . EOF
