From: MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX" 25-AUG-1992 13:19:49.24 To: info-vax@kl.sri.com CC: Subj: RE: VS4000/60 problem - SUMMARY and ADDENDA I wrote describing MOTIF login problems on just one of two "identical" new VS4000/60 systems. Thanks to all for the rapid, to-the-point, helpful, and - most of all - gentle replies to my cry for help. Between the ****** lines I summarize the replies with my comments in square brackets "[]". Most respondents correctly described the fact that both SYLOGIN.COM and user's LOGIN.COM are run when the Session Manager is started AND when a DECterm is created. Below this summary I present some new information. I don't believe the problem has really been solved! ************ From: Ian Burgess Does SHOW TERMINAL offer any clue? You get this message if the terminal is set spooled, as in driving a printer. ... Shouldn't it? [Hang on a read operation] Assuming there is no /TIME_OUT [there WAS a /TIME_OUT but MAYBE I didn't wait long enough] - - - From: BEAR@NUC.anu.edu.au The fix is simple: Add the following line at the very top of the SYS$SYLOGIN file and all user LOGIN.COM files: $IF F$GETDVI("SYS$OUTPUT","MBX") THEN EXIT [This doesn't work! It always returns "FALSE"] [WRITE SYS$OUTPUT F$GETDVI("SYS...","DEVNAM") generates: SESSION MANAGER time DECterm time SYS$INPUT _DKA300: _DKA300: SYS$OUTPUT _DKA300: _FTAxx: SYS$COMMAND _DKA300: _FTAXX: ] - - - From: Larry Horn The quick fix is to put this at the top of any LOGIN.COM's (and SYLOGIN.COM, if used): $ if f$mode() .nes. "INTERACTIVE" then exit [etc.] [No joy, both .COM files were (nearly) DEC standard and had this.] - - - From: reed%vax1@cbemc.att.com (Brian D Reed) You should install Motif 1.0A, if it's not already. Forget just what it does, but I think 1.0 crashes periodically. [See below] Sounds like you may want to put a timeout on the 'read ...' command. [See above] ... Sounds like you're trying to read from a window that doesn't exist. One way would be to do a 'write sys$output ""' to create a window (if one doesn't exist), then you know you have a window for input. [Not tried] - - - From: Mighty Firebreather ... The first time LOGIN.COM executes, input is from a mailbox. [Maybe from DECWINDOWS, NOT here! see above] ... The solution is to check to be sure you are talking to a terminal before doing any of these things. The lexical function F$GETDVI("SYS$INPUT", "TRM") can be used to determine whether or not the device is a terminal. [No joy! From the table above I guess this would work if I used "SYS$OUTPUT" but, fer sure, "SYS$INPUT" doesn't work.] - - - From: Dan Wing Include a line similar to the following in your SYLOGIN.COM and the users' LOGIN.COM: $ IF F$TRNLNM("DECW$DOING_SESSION") .NES. "" THEN EXIT [This works as advertised and I have included it in my .COM files - but - see below.] - - - From: MJR059@MIPL5.JPL.NASA.GOV (Malcolm J. Rayfield) ... I use F$GETDVI to see if SYS$COMMAND has DEVCLASS of 66 (DC$_TERM). If it does, then check for DEVTYPE of 0 (TTYUNKN) before doing a SET TERMINAL/INQUIRE. [looks like it should work] ********** Finding a way to skip SYLOGIN and LOGIN at Session Manager time is helpful. Variants on some of the other schemes suggested would have worked but I selected Dan Wing's as the most to-the-point. I am still puzzled as to why DECW$STARTSM.COM wrote NOTHING to the DECW$SM.LOG file (even the errors!) until I connected the external SCSI peripherals (all DEC standard: TZ30, RZ56, RRD42) to the system. I moved the peripherals from one VS4000 to the other to do a backup and now BOTH systems write to the log file, regardless of where the peripherals are. Before I first successfully mounted DKA0: one system NEVER wrote to the log. (Of course, the error messages have been eliminated.) In addition, I failed to mention that the system often hangs when I select a pull-down menu from the session manager (at least one system does). I've had to reboot to get unstuck. On the question of MOTIF revision, Help..On version from the SM says V1.0 -- but DECW$SERVER_0_ERROR.LOG says: "This is the VMS DECwindows Motif server V1.1-920203" so I GUESS I have 1.1 -- anybody know a better way to find out? I'm still afflicted with DECitis! -------------------------- J. A. Biggerstaff Internet: jbr@stc10.ctd.ornl.gov Bitnet: jbr@ornlstc