If the signal window is solid white, your X server has a bug. Click on any of
the navigation controls (e.g., 
, 
, 
,
or 
), or resize the window, to make the signals appear.
If the signal window is solid or nearly solid blue (or black if you have a monochrome or greyscale display), the signals are too big. WAVE may be attempting to display signals that fill the entire window. In rare cases, noise in the signals themselves can produce this effect. More common causes include incorrect signal format or gain specifications in the header file for the record you have opened, incorrect display calibration, or a choice of amplitude scale that results in excessive vertical range of one or more signals. This effect can also occur as a result of various problems related to the DB calibration file, for example, if the DBCAL environment variable does not name an accessible DB calibration file (see dbcal(5) for details), if any of the signals in the record are of types not listed in the DB calibration file, or if the DB calibration file does not contain appropriate default display scales for all of the signal types in the record. See the next several questions for suggestions on correcting these problems.
If the signal window contains horizontal lines (in blue if you have a color
display) where the signals should appear, the signals are too small. In this
case, the signal gains specified in the header file may be incorrect, the
display calibration may be incorrect, or you may have specified an amplitude
scale that reduces the vertical range of the signals to zero. Click on
to check the scales, and adjust them if necessary.
If the signal window contains time indicators in the lower corners,
look for the signal names along the left edge of the window. If there
are no signal names visible, click on , then on
signal names and 
in the View window. If signal
names still do not appear, either the header file or the signal file
for the record you have opened may be inaccessible. Find these files
(see the next question), add the directory that contains them to your
DB path, and try to read a few samples using `rdsamp -r
record -t 1'. If this fails, examine the header file for the record
(a text file), and be sure that it specifies at least one signal in an
accessible signal file.