[comp.unix.ultrix] Can't log in

jdubb@bucsf.bu.edu (jay dubb) (02/19/91)

   I am posting this for a friend of mine who doesn't have access
to USENET, so please respond directly to mlevin@jade.tufts.edu.

   I have two questions about my Vaxstation II/RC running Ultrix. The
first is about the monitor. Is it ok to just shut off the monitor when
it isn't going to be used for the day? I have done this, and it seemed
fine when I checked it later that day, but this morning I discovered
that it seemed hung - the cursor didn't move when I moved the mouse,
or typed on the keyboard. Could this have been caused by my shutting
off the monitor overnight? If so, is there a better way to save it,
and my electric bill (perhaps some program I can run before I do it)?
If not, any other ideas as to what could have happenned?
   The other question is about the DecWindows system. The story is as
follows: I install Ultrix 4.2 (I am testing 4.2 on this machine), and
it loads all the software subsets with no problem (verify never
complains). Then, the DEC logo appears, and I log in as root (for the
first time) fine.  Without doing anything else whatsoever, I discover that
setld -v (the verify option) tells me that the following sets have
problems: UWSSER420, UWSSER421, and UWSX11421. Checking, I find that
/usr/bin/Xgb, /usr/bin/Xqdsg, /usr/bin/dxfc3d, and
/usr/lib/ucode/vs3520 (which are supposed to be in those sets) are
missing. However, the manual says my workstation demands only Xqvsm
(which is present, and is in fact what the last line of /etc/ttys
has). In any case, all of the applications (puzzle, etc.) run fine
from the menus, but when I try to run them from the DecTerm shell,
they say "X Toolkit Error: Can't open display", and refuse to run.
What's worse, when I log out, quit the session, and try to start
another session, I type in my username and password, the screen
clears, but then instead of starting the session manager and all that,
it goes back to the logo and the login: prompt. I imagine it can't
start the X server, or something like that. The best I can do now is
bring it up to single-user mode. The questions are:
1) what is the problem (or how do I find out what the problem is)?
   Is there any kind of a log-file which could tell me what exactly
   went wrong as it tried to run the session manager and X server?
   What is the "X Toolkit error: Can't open Display" mean?
2) whatever is missing was obviously there before, because the session
   did get started once, and everything passed verify once. So, what
   happenned to it?
3) Most importantly, how do I get it to run again?

I appreciate any help - I am real desperate to get this thing going.
Please reply directly to mlevin@jade.tufts.edu.

			Mike Levin