| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2128.1 | | STAR::MFOLEY | Rebel Without a Clue | Wed Jan 24 1990 15:27 | 5 |
|
The WINDOW_SYSTEM parameter in SYSGEN should be set to 1.
mike
|
| 2128.2 | LOGO WON'T COME UP | APACHE::MCKINNON | | Thu Jan 25 1990 14:02 | 3 |
| Mike, the window_system parameter IS set to 1, but
the windows won't come up!
|
| 2128.3 | Perhaps GBLPAGES? | STAR::VATNE | Peter Vatne, VMS Development | Thu Jan 25 1990 14:17 | 1 |
| What value do you have for the SYSGEN parameter GBLPAGES?
|
| 2128.4 | SYSGEN vs MODPARAMS | OAHU::BEERMAN | Charlie Beerman | Fri Jan 26 1990 08:22 | 11 |
| > <<< Note 2128.2 by APACHE::MCKINNON >>>
> -< LOGO WON'T COME UP >-
>
> Mike, the window_system parameter IS set to 1, but
> the windows won't come up!
I don't want to beat this one to death, but are you *sure*? The
reason I ask is that I had the same problem, and I *thought* I had
set WINDOW_SYSTEM to 1 in SYSGEN, but it turned out that my
MODPARAMS.DAT (created by the VMS installation procedure??) had set
it to 0.
|
| 2128.5 | GBLPAGES 30000 & Window System =1 | PGG::MCKINNON | | Mon Jan 29 1990 18:31 | 13 |
| My GBLPAGES are set at 30000 AND
Window_system is set at 1.
(Modparams.dat does not redefine it).
All other system parameters check out.
BUT for some reason the WORKSTATION process
DIES each time I try to invoke DECTERM or
FILEVIEW.
I have 16MBytes of memory on a single user GPX.
My system disk is NOT beyond 70% capacity.
|
| 2128.6 | Hold it... start describing this all over again | STAR::VATNE | Peter Vatne, VMS Development | Mon Jan 29 1990 20:18 | 10 |
| Wait a second... your problem description doesn't make sense. In the
original description, you said that the Logo and the Login box wouldn't
come up. But now you say that the "WORKSTATION" process dies when you
try to invoke DECterm or Fileview. How did you attempt to start DECterm
or Fileview without being able to login through the Login box?
Please tell us the whole story with lots more details.
Also, please post the contents of SYS$MANAGER:DECW$SERVER_0_ERROR.LOG and
SYS$LOGIN:DECW$SM.LOG, if any.
|
| 2128.7 | OK-2 different installations of same | PGG::MCKINNON | | Tue Jan 30 1990 13:04 | 20 |
| Sorry..about 2 stories! I used a VS325 terminal to set host
to my system so that I could examine it.
When the Blue Login Box wouldn't come up, I logged into
my system over the network and I used the DECW$tailor
utility to remove decwindows. I then added it again with
DECW$tailor (selecting everything, as I thought I did
before).
Then I got the blue login box and logged into the system. However,
when I selected the session Manager window for DECTERM, the Workstation
process died. I then checked the *Session_0_error.log files and
ALL the error log files were empty.
I NOW have discovered that the problem may be caused by my login file
which sets up some VWS logicals, fonts and installs VWS fonts.
I am removing the VWS related commands and then I will try again.
Linda
|
| 2128.8 | MAXPROCESSCNT? | WINERY::VILAINMI | More garlic, says the cooking lady... | Tue Jan 30 1990 20:02 | 6 |
| By chance, what is your MAXPROCESSCNT? If it's to low, DECwindows
can't start all the processes it needs to run.
Just a SWAG,
/MeV/
|
| 2128.9 | Window won't come up | PGG::MCKINNON | | Wed Jan 31 1990 09:40 | 21 |
| MAXPROCESSCNT is 28 (current). What should it be?
Here is my DECW$server_0_error.log file
Note: that fileview (connection 98d00 and
98d38 are closed); I think these are DECTERM
and FILEVIEW.
---------------------------------------------------
31-JAN-1990 09:05:28.6 Hello, this is the X server
Dixmain address=127b0
Now attach all known txport images
%DECW-I-ATTACHED, transport DECNET attached to its network
in SetFontPath
out SetFontPath
GPX color/monochrome support loaded
gpx$InitOutput address=1297f4
Connection Prefix: len == 42
31-JAN-1990 09:06:54.1 Now I call scheduler/dispatcher
31-JAN-1990 09:07:04.5 Connection 98d00 is closed by Txport
31-JAN-1990 09:13:09.1 Connection 98d38 is closed by Txport
|
| 2128.10 | | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Wed Jan 31 1990 10:18 | 7 |
| I think you need to define WORKSTATION PROCESS for us. I take it from the log
that you are not talking about the server, since there are no errors in the
server log. (This is the process called DECW$SERVER_0 or some suche).
Do you mean the session manager? Can we see sys$login:decw$sm.log?
Burns
|
| 2128.11 | 2nd Disk Controller a problem? | PGG::MCKINNON | | Wed Jan 31 1990 10:49 | 13 |
| When I did a show system, I got a process DECW$_wxxx for the
workstation process I assume. This process kept getting
"killed".
Anyway, i think i have it resolved. I mentioned I was using 2 RD54
controllers, because I have 2 RD54, a TK and an RX on 1 controller
and 1 RD54 on the second controller. My login directory was on
the second controller. Apparently, DECWINDOWS cannot support
2 controllers... I moved the directory to the first controller's
device DUA1: and EVERYTHING works like a charm!
Thanks,
|