| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 734.1 | Must define all logicals first | DECWET::CUSTER | | Fri Jul 31 1987 12:46 | 10 |
| This error has occurred on some of our systems here at DECwest. It is a
particularly nasty error as it is difficult to bring your system back
up. I believe it happens when SYLOGIN.COM (or worse, SYSTARTUP.COM)
references a logical name that has not yet been defined.
So @DOC$ROOT:[SETUP]DOC$SETUP is probably not at fault. More likely,
it's the sequence of events occurring in your SYSTARTUP.COM or
SYLOGIN.COM files.
-hkc
|
| 734.2 | | MARTY::FRIEDMAN | | Fri Jul 31 1987 13:55 | 3 |
| I never did understand why the system manager's login.com would
be executed during boot.
|
| 734.3 | | CLOSET::ADLER | | Fri Jul 31 1987 17:04 | 13 |
| Perchance did you just install SECURPACK? I ask because I had a similar
problem on my MicroVAX when I installed SECURPACK, and the solution
was to modify SYSTARTUP.COM so that
SYS$MANAGER:SECPACK_STARTUP.COM
is executed before
SYS$MANAGER:STARTVWS.COM
If that's not the problem, ignore this reply.
--Brian
|
| 734.4 | | MARTY::FRIEDMAN | | Fri Jul 31 1987 17:06 | 5 |
| I think .1 hit the nail on the head, in that the general problem
is one of timing and is usually caused by an inappropriate invocation
of things (order or otherwise) in the files called during boot time.
Marty
|
| 734.5 | Startup Files | DECWET::CUSTER | | Fri Jul 31 1987 17:30 | 14 |
| RE .2
The file called SYLOGIN.COM is a system-wide analog of your personal
LOGIN.COM file. It simply sets up certain logicals, definitions, and
software that need to be available to everyone on a particular system.
It is executed before your personal LOGIN.COM file so that LOGIN.COM
can override the default environment. When a VAX is booted, the file
SYSTARTUP.COM is executed before SYLOGIN.COM and performs even more
fundamental tasks, such as starting workstation windowing software and
starting up DECnet.
Hope this explanation helps.
-hkc
|
| 734.6 | | MARTY::FRIEDMAN | | Mon Aug 03 1987 11:37 | 5 |
| re .-1
I am referring to SYS$MANAGER:LOGIN.COM, not SYLOGIN.COM.
|
| 734.7 | SECUREPACK was the culprit | CUPOLA::JHUGHES | Looking for a few good... | Tue Aug 04 1987 14:20 | 8 |
|
Thanks Brian,
I had the same problem, I changed SYSTARTUP to execute SECUREPACK
before STARTVWS, and the system boots fine.
JpH
|