Sun Microsystems Sun Workstation 100U System Manager's Manual page 152

Power-up and Bootstrap
Sun 100/150 Installation Manual
No controller at mbio zzzz
The monitor is trying to boot, but it can't find a device controller where you asked it
to look. You should try another boot command, or make sure that your controller
board is plugged in and has all its jumpers and switches set properly.
No default boot devices
The monitor is trying to boot but it can't find a disk or Ethernet interface to boot
from. To boot from a tape, you must specify the device name explicitly, as in 'b
arO'.
No label found.
No label found -- attempting boot anyway.
The monitor or boot program is trying to boot from a disk, and can't find a valid label
on the disk. This is best fixed by booting a copy of diog(8S) from a different device
(for example, network disk or tape) and using the 'verify label' and 'label' commands.
See the warning under "Corrupt label" above. This error might also be caused by
missing or bad disk cables.
No more file slots
The current program is using the standalone I/O library and has opened too many dev-
ices or files.
not a directory
The current program (possibly the boot program) has tried to open a disk or network
disk file with a pathname, but one of the names in the path is not a directory.
name not found
The boot program has searched for the requested file, but cannot find it. You can retry
your boot command, using "." instead of name, to get a list of the names that exist in
that directory.
null path
The current program (possibly the boot program) has tried to open a file whose name is
empty.
PageMap
000000
[II]:
zzzxxxzz!
"fhe monitor is displaying or modifying a page map entry because you entered a 'p'
command.
000000
is the virtual memory address whose map entry is being examined.
" is the segment map entry which is being used to map this page map entry and page.
~ZZZZZZZ
is the page map entry itself. You can enter a space and type 'RETURN' to
get back to command mode
Parity Bus Error ...
See "Bus Error ... ". The attempted access was probably valid, but was cancelled
because the preceding access was to memory with bad parity. (Parity errors are
reported on the memory cycle after the failing cycle.) If neither "Upper Byte" nor
"Lower Byte" is rel>orted, the parity on both bytes was invalid. The access address
printed in the Bus Error message is probably not relevant to the parity error. There is
no general way to recover from this error; a good starting point, though, is to boot
po"con(8S), which will search all of memory for parity errors.
Please clear keyboard to begin
A-lO
The monitor is trying to listen for your typing on the keyboard, but cannot tell which
shift keys are down until you release all the locking keys (Caps Lock and Shift Lock).
Once it has seen all the keys released, it can then track the movements of the keys and
typing will work.
Revision
H
of
12
March 1984