[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

123.0. "5.2 Freezing Session Startup" by BULEAN::CARSON (Knockwurst & Excommunications) Fri Feb 03 1989 14:26

    I don't know if my answer was in 73.*, if so I didn't recognize it.
    (This could also be related to 108.*?)
    
    While in the "Start Session" window, in Version 5.2 genned standalone,
    (ie not in the cluster), if I get a OPCOM message, (Circ Up, Circ Down
    etc.), the message appears in the to 8 or so lines and 
    my DECWindows interface freezes completely.  I've tried pushing
    all the buttons on the mouse in all the portions of the screens,
    (the mouse needs the equivilent of a ^Y perhaps on it's backside).
    
    At any rate, stopping DECW$SERVER_0, (which I could only do via SET
    HOST), and then logging on to my video tube with decwindows, logging
    off and then starting via @DECW$STARTUP on my SET HOST process seems
    to get me back on track.
    
    I've looked through the ONLINE_DOC and V52_REL_NOTES, but have seen
    nothing concerning this.  Is this intended behaivor, and if so, is
    there a trick to unlock your workstation?
    
    It is not related to the circuit bouncing as I've had the same scenario
    from AUDIT messages.
    
    Also, is there a clean method for "bringing down DECWINDOWS"?
    Stopping DECW$SERVER_x doesn't count...
    
        			Pete Carson
T.RTitleUserPersonal
Name		DateLines
123.1...to ask the obvious question...KONING::KONINGNI1D @FN42eqFri Feb 03 1989 17:005
Control/F2 is the normal way to get rid of the OPCOM "window" -- did you
try that?

	paul
123.2No, I hadn't...BULEAN::CARSONKnockwurst & ExcommunicationsMon Feb 06 1989 10:0812
	Thanks Paul,

		Unless I missed this, I suggest that this be indexed
	in the DECWINDOWS User ONLINE DOC.  It may be an obvious question,
	but the person that told me also spent a great deal of time trying
	to find this answer.  (Right Dave?)

		Thanks again, 

		Pete
123.3 Floating off to Never-Never Land BAGELS::MCQUADEits a your hand..., Buckaroo!Tue Feb 07 1989 15:1012
    I'm having the same problem with screen and system lockup on an
    OPCOM message running on a PVAX with V5.0T3B2.  Toggling F2 doesn't
    do a thing for me.  Is this just the way it is?  I might add that
    I require OPCOM during certain Network Testing Configurations I
    am setting up on my private Net.  This is more advantageous for
    certain tests than going back and checking the Neteventlog.  Am
    I stuck here with potentially locking my system up with no way to
    extricate myself?
    
    McQ
123.4KONING::KONINGNI1D @FN42eqTue Feb 07 1989 16:455
Unless you change it (Session Manager Customize->Keyboard), it's Control/F2,
not F2 alone.

	paul
123.5can't login to system under VMS V5.28410::PFROMEREd Pfromer, HSC S/W DevelopmentTue May 23 1989 23:1312

I just upgraded from VMS T5.2 to V5.2.  The system booted fine, but I can't log 
into the login window!  The prompt blinks on the 'username' line but typeing does
nothing.  The mouse moves, but pushing mouse buttons over 'OK'/'Clear' buttons
does nothing either.

I am able to login w/o problems via SET HOST (I am writing this note with this 
method). 

Any ideas?
123.6ORPHAN::WINALSKIPaul S. WinalskiWed May 24 1989 02:1613
RE: .5

First off, whatever you did, you didn't upgrade from VMS T5.2 to V5.2.  There
isn't a V5.2 yet--the latest and greatest field test kit is still a T5.2-xxx
release, and says so when it starts up and when you log in.

I don't know what your problem could be--I'm running the latest T5.2 on 
DECwindows workstations without any problems.  The AUTOGEN run after the
upgrade seems to have a bad tendency to underconfigure things--check your
SYSGEN parameters and make sure they're all high enough.

--PSW
123.732905::SWEENEYGotham City's Software ConsultantWed May 24 1989 09:3211
    re: .6
    
    Paul, the VMS 5.2 kits that you and I have of May 12, since we're both
    distribution sites, yield VMS V5.2-42N as the version number in SHOW
    SYSTEM.
    
    re: .5
    
    I've loaded VMS V5.2-42N on a number of workstations without the
    problem you report.
123.8why no startup error?8410::PFROMEREd Pfromer, HSC S/W DevelopmentWed May 24 1989 13:139

	So, it may be that the new AUTOGENed parameters are high enough to 
	allow a remote login, but not allow a direct DECwindows login?  I
	can't understand why the DECwindows login didn't flag an error 
	at startup if this is the problem.

	--ed
123.9occasional characters appear8410::PFROMEREd Pfromer, HSC S/W DevelopmentWed May 24 1989 13:196
More on the startup problem w/ v5.2...

If I start typing fast, I get an occasional character on the login
line.  It seems that somewhere, interrupts are only occasionally being
processed.
123.10two server processes is a no-no8410::PFROMEREd Pfromer, HSC S/W DevelopmentThu May 25 1989 12:4810
re: last few

I fixed my problem.  With VMS versions prior to V5.2-42N one had to start
DECwindows manually within the SYSTARTUP_V5 file.  However, with the latest
version, this is done automatically.  I ended up creating two server processes
which is apparently a no-no.

Is this documented anywhere?
123.112702::WINALSKIPaul S. WinalskiThu May 25 1989 18:316
RE: .10

It's in the V5.2 release notes.

--PSW
123.12How high.....OLDTMR::SYSTEMThu Jun 15 1989 16:2312
    RE: .6
    
    I am wondering what SYSGEN parameters are in question and how high
    should they be. I have installed V5.2-42N on a 3600 and cannot get
    DECwindows to start. The DECW$SERVER_x process does not start at all
    and I am wondering if it is due to a low parameter or two. I can't
    seem to find a parameter list to check. 
    
    Any help would certainly be appreciated
    
    george