This help file describes some of the most frequently encountered problems with the oven window system. The recommended solutions are also given. If any of these problems reoccur frequently, you may be doing something wrong. The old name of this file was "problems".
window dies
window gone
The most frequent window to die is saoimage, which
cannot deal with talking to two tasks at once. You therefore should
be careful not to run odisp while a ovenc is running.
To intentionally quit a window, move the mouse to the top
border of the window and hold down the right mouse button. Select
QUIT.
syntax errors
frozen xterm windows
incomplete plot
frozen graphics windows
screwy cursor keys
no scrollbar
mouse button initialization for imcur
green boxes on your imtool
If you accidently type
If a window dies completely, move the mouse to the gray
background area and press the right mouse button to get the "rootmenu"
called WORKSPACE. Slide over to select the OVEN menu, then select the
window type that you wish to recreate and release the button. Note
that this does not "reset" a window; it creates a new one. Be sure
that the old window is not still around; otherwise you could wind up
with two copies of the same window, which is bad news. Remember the
old window could be hidden or closed somewhere. The console cmdtool,
mailtool, perfmeter and clock are not oven specific, so you get them
from the PROGRAMS menu.
If you start getting lots of syntax errors from an IRAF
window, try giving the cl command flpr. flpr may be the
most useful IRAF task you ever learn. If flpr doesn't work,
recheck the task parameters. Otherwise, log out of IRAF, then
restart the window as above.
If a xterm (or gterm) window "freezes up", it could be because
you hit 256 characters without hitting a carriage return. This
usually occurs when you accidentally lean on the keyboard. The window
will just beep at you when you try to enter more characters.
Often the graph in the graphics window associated with an xterm
will appear incomplete. To flush the graphics buffer and complete the
graph select REFRESH from the top of the graphics window.
If the graphics window of an xterm stops accepting keystroke
input and just beeps at you, that usually means that it needs a series of
REFRESHes and RESETs. This assumes, of course, that you were typing valid
keystrokes.
If you are using ograph or something else in the
graphics section of a gterm window, and you quit the window while
=gcur is active, then the cursor keys will not work in the text
part of the gterm window unless you put on caps lock. This can also
occur if you control-C out of =gcur. The solution is to go to
the submenu in the xterm window by typing
If you want to see the scroll bar on your xterm window, press
When pilot first logs in the mouse buttons are not initialized.
This means that if you attempt to access imcur from the oven program
to find an oven location, you cannot use the left mouse button to return.
Use "t" or "l" or "w" or "b" to return from the imtool.
To initialize the mouse button, enter "=imcur" from the blue window.
Then type "t" in the imtool to return. Then enter "=imcur" again in the
blue window. Then type
After accidentally creating a little green marker box with the mouse
in ximtool, you can blow it away by simply moving the mouse pointer to
within the marker box and pressing the DEL key on the keyboard.
BUGS
These are the bugs, but not all of them.
SEE ALSO
"man xterm", "man saoimage"