Conference bulova::decw_jan-89_to_nov-90

712.0. "fyi - Sessions that don't clear the screen of Logos." by MAMIE::EARLY (Bob Early CSS/NSG Dtn 264-6252) Tue May 02 1989 09:48

    Not sure if this is a "feature" or a "bug".
    
    This what happened:
    
    Last night I "quit" the sessione to get to the ">>>" prompt to format
    some RX33's. No problem. Before goin home I booted the system (per
    normal b esa0). 
    
    Today, I logged in, and everything came up (more/less) fine. The usual
    stuff. The "default files" were all reinitialized. I thought it strange
    that the "DECw$CALENDAR_FILE.DWC" wasn't found. SInce I wanted to use
    my "saved" calandar, I said NO to the prompt asking if I wanted to
    create a new file. Then the odd thing. 
    
    After the windows and notepad came up; the "DArN" DIGITAL logo and
    "Login prompt" window stayed on the screen and wouldn't go away. 
    
    It covered the  "move bar" on the "decview" window, so I couldn't
    select a new calendar. SO, what the heck, I logged in again, expecting
    some convoluted file would be satisfied and the extraneopus stuff would
    go away. Some of  a gun. It created  a whole new session, with the same
    windows and files over the original session. 
        
    So  at the same time, I had TWO -not one --but two -- two 
 		DECterm 1's
		DECterm 2's,
		NOTEpad Untitled
		Session Icons
    
    So, again being very clever, I felt I no longer needed or wanted the
    "extra" session (having only 14mb memory), so I "quit" the "extra"
    session. Sone of a gun you say .. yep .. BOTH sessions went away, and
    got me back to the "Normal Login Window". 
    
    
    So I logged on again. THIS time it not only appears normal, but
    everything came up "as I would have expected it too" the first time. 
    
    Great! It works now. (Or seems to be). 
    
    Also being very clever, I went in through "the back way" and did a
    "set/host log" and memorized the "sho system" in a file (if thats of
    any use in deciphering what "really" went on here. 
    
    Bob
    
    
    
    
    

It is a known problem that two loginout sessions can be running simultaneously.
This is probably what happened to you, although I don't know exactly how
this might have happened.  If you somehow got DECW$STARTUP run more than
once, it might, for example.  Check your various startup files.

We are working on fixing this problem so that Loginout can figure out whether
there is another copy running and can terminate.

Burns

I got this to happen by accidentally having @SYS$STARTUP:DECW$STARTUP more
than once in my SYSTARTUP file.

--PSW

    You haven't recently upgraded to T5.2, have you?  V5.2 will
    automatically invoke DECW$STARTUP and the installation asks that
    you remove the invocation of DECW$STARTUP from SYSTARTUP_V5.COM.
    
    				-John