| 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 |
The following note was entered as reply 32 to note 70. I have added
it here for more visibility.
______________________________________________________________________
We are having a major problem implementing VWSLAT on DECwindow'ed
VS2000's with 6 meg. memory. The problem is that the first session
connects properly to whatever node, but the second attempt at
connecting to another node "craps out" with the basic stack dump, at
which point the first session gets disconnected (window goes away) and
LAT, of course, is dead.
We have the "latest" version of VWSLAT (taken from PRNSYS::) and
also the "latest" version of CHILD (also from PRNSYS::). We have tried
implementing VWSLAT from SYS$MANAGER:DECW$SYLOGIN.COM, from the user's
DECW$LOGIN.COM, OR from entering commands directly in an existing
DECterm window. (All three work on VSII's and VAXstation 3100's with
varying amounts of memory - but it ALWAYS fails on second connect on
VS2000's).
Here are the commands we have used which worked, or didn't, as stated
above:
1) CHILD/SHRINK/PAGE=24/PROC="LAT"/itit="some icon"/tit="some
title"/decterm/line/insert "RUN SYS$SYSTEM:VWSLAT"
2) CHILD/IMAGE=SYS$SYSTEM:LOGINOUT.EXE/NOPASSWORD/PRIV/INPUT=STARTLAT.COM
/DETACH/PAUSE=5/SHRINK/DECTERM/LINE/INSERT/PROC="process
name"/itit="icon title"/tit="some title"
where STARTLAT.COM is:
$define/user sys$input sys$output:
$run sys$system:vwslat
$logout
Please assume that the above commands are either on a single command
line or are properly continued on the next line (hyphenated).
My question is basically this: Why does this work on a VSII (one with
only 5 Meg memory) or a VS3100 (8 meg minimum), but NOT on a "standard"
VS2000 with 6 meg?
Does anyone have recommendation(s)? Are there SYSGEN parameters that
may be recommended that we are overlooking? Working set parameters?
Job limits or quotas? We are mildly frustrated and confused (!) and
would GREATLY APPRECIATE ANY HELP AND SUGGESTIONS. We anxiously await
any replies. Thanks, David
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1581.1 | QUARK::LIONEL | Free advice is worth every cent | Mon Oct 16 1989 19:15 | 5 | |
Why don't you ask in the VSG::VWSLAT conference, since neither CHILD nor VWSLAT are a component of DECwindows. Steve | |||||
| 1581.2 | One possibility | AGBEAR::HORNER | A.G.Bear, Old fashion teddy bear | Wed Oct 18 1989 09:09 | 11 |
This is a long shot, but I've seen what you describe happen when a bad
packet causes the VWSLAT$LAD.DAT file to be corrupted. Once this
corruption happens, it is permanent. Sometimes one or two connections
can be established, sometimes no connections can be made before the
stack dump. Try completely deleting your VWSLAT$LAD file while VWSLAT
is not running, and have it create a brand new file the next time you
start it up. We have eight 6MB VS2000's here, and they have no problems
with VWSLAT.
Dave
| |||||