INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

VAX Alpha 2100 system hung up VMS ver. 7.1

VAX Alpha 2100 system hung up VMS ver. 7.1

(OP)
We currently have a system disk that is low on free space that is preventing the system from starting up.

The system goes into a loop because there is not enough free space to start the Queue Mananger.


Does anyone know of a quick way, from the boot statement po>>>   that will allow us to by pass the normal startup
to just boot up to DCL ($) so we can edit the startup to prevent the Queue Mananger from starting up.....

RE: VAX Alpha 2100 system hung up VMS ver. 7.1

You can avoid the normal startup by using the following (I don't have a system in front of me, you should check the syntax - it's been quite a while since I had to do this)...

>>> b -fl 0,1
(assuming your system disk is already set to the default boot device, and the system root is "1" - change the command appropriately if not...)

(at the next prompt, I think the following does it - use HELP if it doesn't)

>>> SHOW STARTUP*

(Record the settings for all STARTUP* params for the system. Specifically, look for one indicating something like startup.com or systartup.com - sorry, been so long I can't recall precisely which one it is)

When you find the param with the above *startup.com as the definition, set THAT parameter to OPA0: (the system console)

>>> SET STARTUPxxxx OPA0:
(I think you need the ":" - can't recall)

>>> CONTINUE

The system should boot, but will not have ANY of the normal system startup stuff running - be careful what you do with the system in this state!!!

There is some funny stuff re the passwords with the system in this state - I think it actually asks for the system account password twice - just do what it asks, and hopefully it will let you into the system...

I think when you shutdown the system after this, you may need to reset the startup to the previous flag, or it may retain the above startup command - hence the recording of the previous settings.

Hope this helps!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close