| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 55.1 | Could be SYSGEN parameters | CADSYS::BAY | Jim, SEG/CAD Systems | Fri Jan 27 1989 18:48 | 12 |
| I had a similar problem and it turned out that it was caused by sysgen
parameters. In my case, when the SDC version was released and
installed, changes had to be made in MODPARAMS.DAT and then the system
had to be rebooted.
I can't tell you which parameters or values, because I didn't do the
changes, but I *think* there is some documentation on the required
values to run DECwindows.
Jim
|
| 55.2 | check DECW$STARTUP.LOG | CSSE32::MERMELL | Window Pain | Fri Jan 27 1989 20:06 | 3 |
| Also, DECW$STARTUP will report parameters that it
knows are set wrong if it finds any. Check the log file!
|
| 55.3 | Where is DECW$STARTUP.LOG? | BROKE::DNELSON | Chance favors the trained mind. | Tue Feb 21 1989 11:15 | 7 |
| I'm also having a similar problem, but I can't seem to find DECW$STARTUP.LOG
anywhere. Can you provide me a pointer to it?
Or do I have to do something special to get the log created?
-- Don
|
| 55.4 | System is up, no logon screen | CAPL::KAYGEE | | Thu Apr 06 1989 12:46 | 9 |
|
Having the same problem. Gray background, no DEC logo or login
screen. Anyone have more info?
-KG
|
| 55.5 | Easy to cause this if you WANT to! | VINO::WITHROW | Robert Withrow | Thu Apr 06 1989 13:18 | 9 |
| BTW: I have found a very simple way to cause this: Simply put a `logout'
command in your DECW$LOGIN.COM file. Now why does this happen?
PS: You may wonder why anyone would do this. Well, its because some of us
use UWM, which has the ability to start terminal window, which is just about
the only thing most people use the thing for anyway... So you simply RUN
the UWM (rather than spawning it) and logout when it exits. Only.... It
don't work right....
|
| 55.6 | If your not part of the solution... | CAPL::KAYGEE | Keep it simple... | Thu Apr 06 1989 13:48 | 9 |
|
If your so good at creating the problem, how about helping solve
it.
-KG
|
| 55.7 | No source of information TO solve it! | VINO::WITHROW | Robert Withrow | Thu Apr 06 1989 14:36 | 12 |
| > If your so good at creating the problem, how about helping solve it.
Because the developers seem to want to keep the information necessary to
solve these sorts of problems secret. Perhaps it is an oversight, perhaps
it is due to limited resources, but the ONLY place I have seen information
associated with the details of starting and stopping decwindows sessions
is in replys to notes in this conference. And most of that has been
deduced by users attempting to solve problems.
Incidentally, I was not bragging about causing the problem, I was simply
distributing information that might be usefull to others.
|
| 55.8 | Check out 431.5 | MCNALY::MILLER | Bush For President...Kate Bush! | Thu Apr 06 1989 14:50 | 10 |
| re .5 Easy to cause this if you WANT to!
Particularly list numbers 5 & 6. That should explain why you lose it with
a 'logout' in DECW$LOGIN.COM
Regards,
== ken miller ==
|
| 55.9 | Magic explanation in 431.5 | ROBOT::ENDSLEY | MJ Endsley, SWS @ St. Louis | Thu Apr 06 1989 14:53 | 10 |
| >>> BTW: I have found a very simple way to cause this: Simply put a `logout'
>>> command in your DECW$LOGIN.COM file. Now why does this happen?
See note 431.5 for some background. As I understand it, your LOGOUT will kill
things before the session manager and window manager get started.
Mike Endsley
SWS @ STO
|
| 55.10 | WM started BEFORE DECW$LOGIN is executed. | VINO::WITHROW | Robert Withrow | Tue Apr 11 1989 15:18 | 6 |
| > See note 431.5 for some background. As I understand it, your LOGOUT will kill
> things before the session manager and window manager get started.
My research shows that the window manager is running *before* DECW$LOGIN is
executed. The ICON box shows up before DECW$LOGIN is executed.
|
| 55.11 | Beware: Many conditions yield same results .. | AHIKER::EARLY | Bob_the_Hiker | Mon Apr 24 1989 16:19 | 24 |
| re: .7
Extraneous aside to the problem:
A word of caution: After being in engineering for several years and
working on some pretty "strange" problems; it evventually became
apparent that it is possible to devise a "set of conditions" which will
emulate a "problem",and even provide the same manifestation.
However, getting the "same" manifestation to a problem does not
necessarily mean the problem has been duplicated.
In short: Many sets of conditions will yeild the same "obvious" result,
but not all of them will be solved by the same solution.
Developers, firmware or software, are typically driven by a "business
manager".
sorry if this sounds pedantic. It is intended to be helpful in finding
the real solution.
Bob
|
| 55.12 | getting a start dialog box | MAMIE::FEDORA | insignificant yet meaningless | Thu Sep 20 1990 13:23 | 12 |
|
My problem is on a VAxstation running VMS V5.2 (for reasons I won't go
into here). I've AUTOGEN'ed several times but still ,now and again, get
a grey screen with no dialog box when I quit the session. A restart of
decwindows clears it up but it's annoying. DECW$SERVER_0_ERROR.LOG and
DECW$SERVER_0_SERVER.LOG don't contain anything interesting. VPA report
looks ok too. When this happens I go to a remote terminal and MONITOR
shows no activity and SHOW SYS and SHOW MEM all are normal.
System runs a graphics package all day long pretty well but this "quit
the session and hang" thing is upsetting the user.
What should I start to look for?
|