The only file required in an MGR installation is the server
itself. That would give you terminal emulator windows with shells
running in them and cutting and pasting with the mouse,
but no nice clocks, extra fonts, fancy graphics,
etc. Depending on options, a monochrome server needs about 200K of RAM
plus dynamic space for windows, bitmaps, etc.
If /usr/mgr/bin is in your PATH,
then just type "mgr" to start up.
After enjoying the animated startup screen, press any key.
When the hatched background and mouse pointer appear, hold down
the left mouse button, highlight the "new window" menu item, and
release the button. Then drag the mouse from corner to corner
where you want a window to appear. The window will have your
default shell running in it. Hold down the left mouse button over
an existing window to see another menu for doing things to that
window. Left-clicking on an obscured window raises it to the top.
The menu you saw that pops-up over the empty background
includes the quit command.
For people with a two button mouse:
press both buttons together to emulate the missing middle button
used by some clients.
The quit submenu includes the "really quit" option,
a suspend option which should only be used if you run a
job-control shell, and a screen saver and locker option, which
waits for you to type your login password when you come back
to your machine.
When trying to run MGR, if you get:
can't find the screen
make sure you have a /dev entry for your display device,
e.g. on
a Sun /dev/bwtwo0. If not, as root cd to /dev, and type
"MAKEDEV bwtwo0". Otherwise, you might need the
-S/dev/bwtwo0
or (on Linux) the -S640x480 command line option when starting mgr.
On Linux, you might also make sure that /usr/mgr/bin/mgr was
installed setuid root.
can't find the mouse
make sure /dev/mouse exists, usually as a symbolic link to the
real device name for your mouse. If you haven't permission to
write in /dev, then something like a -m/dev/cua0
option can be
given when starting mgr. Also, make sure you've supplied the
right mouse protocol choice when you configured mgr. The mouse
may speak Microsoft, even if that is not the brand name.
can't get a pty
make sure all of /dev/[tp]ty[pq]?
are owned by root, mode 666,
and all programs referenced with the "shell" option in
your .mgrc startup file (if any) exist and are executable.
none but the default font
make sure MGR is looking in the right
place for its fonts. Check the Configfile in the source or
see whether a -f/usr/mgr/font option to mgr fixes the problem.
completely hung (not even the mouse track moves)
login to your machine from another terminal (or rlogin) and kill the
mgr process.
A buckey-Q key can quit MGR if the keyboard still works.
Any tty-oriented application can be run in an MGR window
without further ado. Screen-oriented applications using
termcap or curses can get the correct number of lines and
columns in the window by your using shape(1)
to reshape the window or using
set_termcap(1) to obtain the correct termcap entry.