T.R | Title | User | Personal Name | Date | Lines |
---|
300.1 | | STAR::ORGOVAN | Vince Orgovan | Fri Feb 24 1989 18:13 | 3 |
| I've seen this when I've accidently invoked decw$startup.com
twice in my system startup files. Any chance that's the problem?
|
300.2 | Checked out location of DECW$STARTUP. | HYEND::STONEHAM | | Mon Feb 27 1989 12:07 | 8 |
|
I did not find anything unusual with the placement of DECW$STARTUP
thoughout the system. The only place the DECW$STARTUP is found,
outside of standard DECwindows command procedures is in
SYSTARTUP_V5.COM. Thanks for the idea.
Charlie
|
300.3 | SYSMAN maybe? | A6INTR::SOCHA | Out in the Field | Tue Feb 28 1989 10:25 | 11 |
| It is also possible that DECW$STARTUP.COM could be getting executed
during system startup through the SYSMAN method. To check do the
following:
$ MCR SYSMAN
$ STARTUP SHOW FILE/FULL DECW$STARTUP.COM
If has an entry, then it is also executing the file.
Kevin
|
300.4 | Problem and Solution | HYEND::STONEHAM | | Tue Feb 28 1989 17:52 | 12 |
|
Our System Manager discovered and solved the problem. The fix
in this case was to remove the reference to SYS$MANAGER:DECW$STARTUP
in the RSM$STARTUP_COMMANDS.DAT file and replace it with rsm(#)keine.
I don't know anything about RSM but I assume that DECW$STARTUP was
executed twice, once in SYSTARTUP_V5 and again by RSM. This fix worked
fine. Thanks for all your suggestions.
Charlie
|