| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
I just installed SDC VMS v5.1 and DECwindows but am having several
problems.
At first I managed to get the Session Manager started up and was
able to play with several of the applications. Whenever I tried
do create a terminal the session manager would crash with an access
violation. After looking through the various conferences I started
playing with my UAF settings and things have gotten worse since
then.
Now when I log in the session manager starts up and tells me it's
starting Fileview. It then starts with
"DECterm Controller Process stopped: Normal Successful Completion"
"DECterm Controller Started"
after about 4 of these I get
"FileView Stopped: Message Number 13AE8204"
and then about 4 more of the DECterm controller messages until I
finally get "Fatal Error - No Retry Possible" and it just sits there.
Help! The .LOG file doesn't have any other info and I can't find
any sort of log file for the controller. I'm going to continue to
play with the UAF settings (pure trail and error since I can't find
any documented suggestions) and see what I can do.
Thanks,
Ray
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 219.1 | LESLIE::LESLIE | Introducing Yehudi Menhuin on drums | Wed Feb 15 1989 16:36 | 11 | |
Here's a cut from my SYSUAF entry. Note that WSMAX on LESLIE:: is se to
3100. A WSextent greater than WSmax can cause problems.
Maxjobs: 0 Fillm: 150 Bytlm: 60000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 20 BIOlm: 120 JTquota: 1024
Prclm: 35 DIOlm: 120 WSdef: 1024
Prio: 5 ASTlm: 120 WSquo: 2048
Queprio: 0 TQElm: 40 WSextent: 3100
CPU: (none) Enqlm: 512 Pgflquo: 45000
| |||||
| 219.2 | Some things to try | STAR::BROUILLETTE | Fri Feb 17 1989 21:40 | 41 | |
Create a file sys$login:decw$login.com and put the following line in
$define decw$decterm_output decw$decterm_output.log
That will be sys$output for the controller process started by the
session manager.
The logical name for a log file for FileView is
$define decw$vue_output decw$vue_output.log
Or, run the controller interactively
$set display/create
$run sys$system:decw$terminal
$run sys$system:vue$master
Either of these methods may give you more information.
Here are some other tips:
1. Make sure you don't have old versions of files hanging around in
sys$specific:[sysexe], sys$specific:[syslib], sys$specific:[sysmgr].
Look for an old version of loginout.exe or decw*.exe.
2. Make sure you are not running out of global pages.
$mcr install
mcr>/global
At the end of the list of installed images, you will find a line
which tells you how many global pages and sections are free. For every
local client you need a little over 300 global pages. So you need
around 1000 to run session manager/window manager/terminal controller.
3. After the session manager is running and has stopped trying to
start controllers, set host into your workstation from another
workstation or a terminal. Try running some applications which do not
use the toolkit, like ico.exe or xclock (if you can get them). If they
fail to connect, they may give more information about the error.
| |||||
| 219.3 | UFP::MURPHY | The SUN just set! | Tue Feb 21 1989 08:27 | 9 | |
Ray's problem was caused by running out of global sections. This one
is obviously difficuly to track, as DECW$STARTUP is usually spawned
early in the boot process, before application startup files get their
chance to suck up the global pages/global sections. Once the server
gets it's act together, they're all gone.
Just another hint for your troubleshooting bag of tricks.
-Rick
| |||||