Conference bulova::decw_jan-89_to_nov-90

It might be worth looking in DECW$SM.LOG, to see if there is anything of
interest in there.

Of course, this might more difficult than it sounds, if you can't log in at all!
You might have to do a MINIMUM boot, and start the machine without a window
system, then just log in on OPA0:

Good luck,
/Mike

    
    I've looked there, and all it has is a description of my working set and
    nothing else. I've also sifted through various log files with DECW in
    front of them and come up with a big zero there too.
    
    I'm considering doing the upgrade again, but if anyone could save my
    time I would appreciate it.
    
    John.

    Did you have any "custom" methods for starting applications before the
    upgrade?  We ran into many incompatibilities between the way we did
    things in DECW V1 and the way things now work in DECW V2.  By removing
    all of our workarounds and unsupported utilities and starting with a
    clean slate, all problems disappeared.  None of them were as severe as
    what you are experiencing, but you never know.  I've also noticed that
    DECW V2 is a little more resource hungry than V1.  Make sure that your
    UAF and SYSGEN quotas and parameters are sufficient.

                Dave

Yet another idea. Have you done an AUTOGEN lately? Might be an idea to log into
OPA0:, when DECwindows is waiting for login, and do an AUTOGEN with feedback.

.-1's statement about resources is very valid. We saw problems too with V2, only
in our case we didn't even get the LOGIN window. I think the problem is that
when the UPGRADE does an AUTOGEN, DECwindows is not running at all, and if any
feedback data you have lying around is not to AUTOGEN's liking, (too old
perhaps), then it is ignored. The result is that AUTOGEN gives you fewer
resources than you had before, when you may actually need more.

Just a thought,
/Mike

We had some trouble with people who define decw$display instead of 
SET/DISPLAY/NODE command.

Jatin

    Hi.
    
    I've Autogen'd it daily (over 24 hrs) and have removed all previous
    customisations of windows etc, I have also check my SYSGEN paramaters
    with those of another machine, though a different machine. If anyone
    has 5.3 and DECWindows running on a WS3200 could they please post a
    copy of thier SYSGEN parameters  and an example UAF account for me to
    check off against my own.
    
    Thanks,
    	John.
    

	Re: .0

	I had the same problem as you are describing and it was fixed when
	I put the following lines at the top of my login.com:

	$ DEVICE = F$TRNLNM("SYS$COMMAND")
	$ DEVICE = F$EXTRACT(F$LOCATE("$",DEVICE)+1,99,DEVICE)
	$ IF F$EXTRACT(0,2,DEVICE) .EQS. "MB" THEN EXIT

    I was just about to suggest something like .-1.  If you do anything
    in login.com that assumes that INTERACTIVE implies that you have a
    terminal, symptoms like this will happen.  Thus, $INQUIRE, $SET
    TERM/INQ, etc will all cause trouble.  Look in SYLOGIN.COM too.
    
    Burns
    

    
    Problem solved.
    
    It was a call to part of securpack in the sylogin that asked for input
    before the window was created, so causing it to give up.
    
    It is still a bit of a puzzle as to why this used to work on V5.2 but
    not on V5.3.
    
    Anyway, thanks for the help. Merry Christmas.
    
    John

I believe that the "interactiveness" of the DECwindows process changed between
5.2 and 5.3.  Maybe someone else can give more details, cuz I don't know them.

Burns