Thread View: comp.sys.dec.micro
5 messages
5 total messages
Started by Todd Miller
Fri, 12 Apr 1991 17:03
P/OS hardware Error codes
Author: Todd Miller
Date: Fri, 12 Apr 1991 17:03
Date: Fri, 12 Apr 1991 17:03
48 lines
1889 bytes
1889 bytes
New Pro 350 owners are so worried about the error codes I have reproduced the most common ones here. These are taken from the P/OS handbook. Note that unless you want to buy new components all you can do is reseat connections! Code Problem area Corrective Action 000100 P/OS keyboard handler 1: Check cables and connections 2: Reseat option modules in card cage. 3: Reset all IC's in sockets on system module. 5: Replace system module 6: Reload Operating system. 000200 Terminal driver [deleted] 000300 Executive/general If error occured on first access of RX or RD subsystem, check that subsystem is in order: 1: Check cables and reseat controller in card cage 2: Replace Drive 3: Replace RX or RD subsystem controller If error not found on first access of mass storage, goto 000200 corrective action. 000400 System startup processing 000500 Terminal driver (video and printer port) Second line Error Codes 000000 IOT in system state 000001 Stack overflow or cannot install task CBOOT 000002 Trace Trap or breakpoint or cannot spawn task CBOOT 000003 Illegal instruction trap or cannot spawn task CBOOT 000004 Odd address or other trap to 4 000005 Segment fault 000006 A task on P/OS without a parent aborted 000007 EMT trap or required file not found 000010 TRAP trap
P/OS security? (or how to break into a P/OS system)
Author: William Thomas Daugustine
Date: Sun, 14 Apr 1991 21:26
Date: Sun, 14 Apr 1991 21:26
19 lines
1227 bytes
1227 bytes
Today I was able to remove the hard drive from a Pro 350 before it went to the scrap heap. When I got it home, and put it in my 350, it booted right up into P/OS 3.1. Some kind soul defined a default accout on it, so I am able to get into the menu. Unfortunatly, the default account is _not_ the system account, and I am wondering if anyone knows of any way to finf out how I can get into the system account? I tried 'system', and password 'system', but that of course, didnt work. I am able to do just about anything I want with it, execpt for account maintaince. I am able to access DCL, but when I do a $ DIR DW2:[*] because I am not the system, I get lots off access errors. Thanx Billy D'Augustine Azog-Thoth@cup.portal.com
Re: P/OS security? (or how to break into a P/OS system)
Author: slsw2
Date: Tue, 16 Apr 1991 19:49
Date: Tue, 16 Apr 1991 19:49
29 lines
2103 bytes
2103 bytes
In article <41275@cup.portal.com>, Azog-Thoth@cup.portal.com (William Thomas Daugustine) writes: > Today I was able to remove the hard drive from a Pro 350 before it > went to the scrap heap. When I got it home, and put it in my 350, > it booted right up into P/OS 3.1. Some kind soul defined a default > accout on it, so I am able to get into the menu. Unfortunatly, the > default account is _not_ the system account, and I am wondering if > anyone knows of any way to finf out how I can get into the system > account? I tried 'system', and password 'system', but that of course, > didnt work. Well, I've never really dealt with P/OS, but a long, long time ago I was involved with a group that had a similar problem with a PDP-11/60 that we bought from another group at the site. It ran RSX-11M, but we didn't get any passwords from the group from which we bought the machine. After a lot of poking about in manuals, I found a way to get to the password file, which in that version of RSX-11M was not encrypted. While the machine was booting, executing the startup command file, I pressed ^C. That gave me an MCR prompt at which I could type a command. Since the machine was executing the startup command file, the MCR prompt was attached to the system account. In an obscure manual that I no longer have and don't remember very well, I found the name of the password file. The MCR command that I issued, then, typed the password file on the console. Since P/OS is related to RSX-11M, it might work. Wish I could remember the name of the account file, though... Roger Ivie slsw2@cc.usu.edu
Re: P/OS security? (or how to break into a P/OS system)
Author: christophe m kalisiak
Date: Thu, 18 Apr 1991 00:36
Date: Thu, 18 Apr 1991 00:36
22 lines
1607 bytes
1607 bytes
In article <1991Apr16.134937.47433@cc.usu.edu> slsw2@cc.usu.edu writes: >In article <41275@cup.portal.com>, Azog-Thoth@cup.portal.com (William Thomas Daugustine) writes: >While the machine was booting, executing the startup command file, I pressed >^C. That gave me an MCR prompt at which I could type a command. Since the >machine was executing the startup command file, the MCR prompt was attached to >the system account. In an obscure manual that I no longer have and don't >remember very well, I found the name of the password file. The MCR command >that I issued, then, typed the password file on the console. What was the command? I would say that if one were to delete the password file, then you could probably start from scratch... Don't quote me on it. >Since P/OS is related to RSX-11M, it might work. Wish I could remember the >name of the account file, though... [0,0]RSX11.SYS Chris Kalisiak V076N3W7@ubvms.cc.buffalo.edu kalisiak@acsu.buffalo.edu
Re: P/OS security? (or how to break into a P/OS system)
Author: slsw2
Date: Mon, 22 Apr 1991 21:49
Date: Mon, 22 Apr 1991 21:49
31 lines
2050 bytes
2050 bytes
In article <71506@eerie.acsu.Buffalo.EDU>, kalisiak@acsu.buffalo.edu (christophe m kalisiak) writes: > In article <1991Apr16.134937.47433@cc.usu.edu> slsw2@cc.usu.edu writes: >>In article <41275@cup.portal.com>, Azog-Thoth@cup.portal.com (William Thomas Daugustine) writes: >>While the machine was booting, executing the startup command file, I pressed >>^C. That gave me an MCR prompt at which I could type a command. Since the >>machine was executing the startup command file, the MCR prompt was attached to >>the system account. In an obscure manual that I no longer have and don't >>remember very well, I found the name of the password file. The MCR command >>that I issued, then, typed the password file on the console. > > What was the command? I would say that if one were to delete the > password file, then you could probably start from scratch... > Don't quote me on it. It was just PIP TO:=filename. Since the file was not encrypted, the passwords showed up. BTW, deleting the password file is probably not a good idea. If you do it on VMS, you just plain can't get in unless you do a conversational bootstrap and set the startup file to OPA0:... > >>Since P/OS is related to RSX-11M, it might work. Wish I could remember the >>name of the account file, though... > > [0,0]RSX11.SYS I dunno; sounds like the system image to me. I'd want to poke about the documentation for a while before I deleted that one. Roger Ivie slsw2@cc.usu.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads