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 |
I have looked at previous notes on FILEVIEW for help but so far to no use. When FILEVIEW Starts up on LOGIN, after about 20 secs, I get the message "FileView stopped message number 10778088" What does this mean ? I can spawn fileview from my DECTERM window, but not get it run on LOGIN. The H/W I am using, is a VS2000 (6Mb) in an LAVC with a VS3500 as the boot node, running SDC 5.1 software. Stephen D
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
389.1 | More data on original error. Any help gratefully received. | 45437::DAVIES | Wed Mar 15 1989 03:05 | 27 | |
Here is some more info re .0 I created a file in SYS$LOGIN:, called decw$login.com. The file is shown below. <<<SYS$LOGIN:DECW$LOGIN.COM $ set verify $ define decw$vue_output pipkin$dua1:[user.davies]vue_errors.dat When I start FILEVIEW from the session manager, the request still fails with the error as in .0, and produces an error file as shown below. %SET-W-NOTSET, error modifying PIPKIN$DUA0: -CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device DAVIES logged out at 15-MAR-1989 07:57:54.10 I first thought that something in LOGIN.COM or SYS$MANAGER: SYLOGIN.COM was doing a funny 'set' operation. I therefore removed all 'SET' commands from the files, and still the request to start fileview fails. Are there some other command files that are executed during this startup operation ? Stephen D | |||||
389.2 | Repost in BULOVA::FileView | TOOK::MERSHON | Ric Mershon | Wed Mar 15 1989 07:56 | 10 |
RE: < Note 389.1 by 45437::DAVIES > Try reposting your notes in the FileView notes conference. I think you might get a quicker response there. Press KP7 to add it to your notebook... -ric. :-) | |||||
389.3 | STAR::BENSON | Wed Mar 15 1989 11:37 | 6 | ||
Check for INQUIRE commands in your LOGIN and SYLOGIN command files. These will fail because SYS$INPUT is not a terminal device when you start FileView from the session manager. Tom | |||||
389.4 | UFP::MURPHY | The SUN just set! | Wed Mar 15 1989 22:36 | 5 | |
Most likely candidate is a SET TERMINAL/INQUIRE. Or any SET TERMINAL commands. Either prefix them with a SET NOON or (better) make them dependent on F$MODE() .EQS. "INTERACTIVE". -Rick | |||||
389.5 | Thanks... | 45437::DAVIES | Fri Mar 17 1989 03:23 | 8 | |
Thanks for the suggestions, I will post the problem in the FILEVIEW conference. Stephen P.S. I had already looked at all the SET commands, and made them conditional. |