• Please review our updated Terms and Rules here

RSX-11m-plus v3.0 bl24 backdoor?

PG31

Veteran Member
Joined
May 31, 2011
Messages
506
Location
Sefton, Meresyside, England
I've finally managed to get an RD54 and RQDX3 for my 11/73. It's a long time since I've used RSX and after booting entering the time and date and typing hello or logon I'm asked for a username and password. If I remeber correctly ctrl c gets me to mcr but I still can't do anything. Any ideas how to find one of the logons used? I plan on putting a fresh o/s on the disk.

Thanks.
 
The best thing to do is intercept the startup.cmd's execution by aborting it before it can complete [runs on the system console].

Try hitting ^Z repeatedly while it's executing. If you can terminate it before the end, you'll be logged in as SYSYEM.

Then type "run $acnt" and force in any passwords you like.


p.s. - If it is BASELINE 3.0, I'd like to get a copy if you can manage it.
 
Great thanks, brings 20 year old memories coming back.

p.s. yes, let me know how anf if I can help.

What I need is a disk image [like used by E11 or SIMH] of that drive before you wipe it.

This can be created by a number of means, depending on what devices were included in that sysgen. If there's a DD [tu58] device, it's easy. Run PUTR on a PC, connect an rs232 cable to the system and rediect the DD device to the serial port. Then BRU to the DD device, capturing the output on the [PUTR] emulated tape.

Otherwise, it might be a little more primitive and involves a similar technique based on a PC capture program. [I'll give instructions in another post if needed]

Either way will take time, and unless you've done it before, it may "hold you up" more than you want. But it could provide a way to re-instate that version should you later choose.

Please do this... login to that system from a PC VT100 emulator that you can capture the screen session. Type the "DEV" command at the MCR prompt and capture the entire output to post here. That will tell me which alternatives we have.

Thank you for considering it.
 
I'm embarrassed that I didn't think to suggest it before, but - Did you try login SYSTEM with SYSTEM as the password?

Maybe you did.

The second alternative [to PUTR] is to run rsx DMP to dump the whole disk to a serial port... and capture the output on a PC. [using any common terminal emulator]
Code:
         Connect to the RSX system using a PC terminal program with
        logging enabled, and type:

        >INS $DMP        (if DMP.TSK wasn't already installed)
        >DMO ddu:/DEV/LOCK=V    (if you're dumping the system disk)
        >MOU ddu:/FOR        (if it's some other disk)
        >DMP TI:=ddu:/WD/BL:0    (dump out the whole device)

        The transfer will generally take hours, possibly days if the
        disk is big enough.  

        When the transfer is complete, close the log file
Then I could get that capture log file from you. I'd be happy to send it back as tape dump you could later use with PUTR should you like to restore it to the system.

If you decide to proceed, let me know, and I'll provide a place for you to ftp the capture.

Thanks.
 
I still don't have a DLV11 to connect to the TU58 emulator. I do have the following DHV11, DPV11, DHQ11, KMV2A-S, 2 x MDB MLSI-DZ11, DEQNA, DELQA, RQDX, RQDX3, RD54, RLV12 and a TK50 with controller (no tapes yet though!). I have just inherited a second PDP, so I now have an 11/73 and 11/53. I also have 2 Tandon TM65-1L 5 1/4 floppy, I'm planning to use them as RX50. Does anybody know if they will work?

DEV attached.

>DEV
CO0: TT0: Loaded
TT0: [GROUP,MEM] [1,5] - Logged in Loaded
TT1: Offline Loaded
TT2: Offline Loaded
TT3: Offline Loaded
TT4: Offline Loaded
TT5: Offline Loaded
TT6: Offline Loaded
TT7: Offline Loaded
TT10: Offline Loaded
TT11: Offline Loaded
VT0: Loaded
VT1: Loaded
RD0: Loaded
DU0: Public Mounted Loaded Label=RSX11MPBL24 Type=RD54
Cached

MU0: Loaded Type=TK50
NL0: Loaded
TI0:
CL0: TT0:
SP0: DU0:
LB0: DU0:
 
I still don't have a DLV11 to connect to the TU58 emulator. I do have the following DHV11, DPV11, DHQ11, KMV2A-S, 2 x MDB MLSI-DZ11, DEQNA, DELQA, RQDX, RQDX3, RD54, RLV12 and a TK50 with controller (no tapes yet though!). I have just inherited a second PDP, so I now have an 11/73 and 11/53. I also have 2 Tandon TM65-1L 5 1/4 floppy, I'm planning to use them as RX50. Does anybody know if they will work?

DEV attached.

>DEV
CO0: TT0: Loaded
TT0: [GROUP,MEM] [1,5] - Logged in Loaded
TT1: Offline Loaded
TT2: Offline Loaded
TT3: Offline Loaded
TT4: Offline Loaded
TT5: Offline Loaded
TT6: Offline Loaded
TT7: Offline Loaded
TT10: Offline Loaded
TT11: Offline Loaded
VT0: Loaded
VT1: Loaded
RD0: Loaded
DU0: Public Mounted Loaded Label=RSX11MPBL24 Type=RD54
Cached

MU0: Loaded Type=TK50
NL0: Loaded
TI0:
CL0: TT0:
SP0: DU0:
LB0: DU0:

Ok, that system didn't have TU58 support gen'd in, so let's forget PUTR for now. You can use the generic capture method in my previous post from the console terminal.
 
LOL !

Who knew it was so popular?

Must be a STEALTH following...
 
I'm going to resurrect an old thread, because I found this while googling RSX-11. There's a large post-it on the front of an ST-412 I just imaged:



Sadly, I don't check vcfed as often as I should, but if anyone wants the drive image, let me know. I have yet to figure out how to read it myself, but do have a PDP-11/73 I'll be keeping for myself.
 
The PiPDP11 project has various O/S images for SIMH, including RSX11m-Plus, for Raspberry Pi - see build intructions at:-

You can run it on a PI without the panel.

On the original question in this thread, at the date/time prompt in startup you can press ^C to get an `MCR>` prompt
and then type `ABO AT.` to kill the command file processor, which gets you back to the system prompt.
 
The PiPDP11 project has various O/S images for SIMH, including RSX11m-Plus, for Raspberry Pi - see build intructions at:-

You can run it on a PI without the panel.

On the original question in this thread, at the date/time prompt in startup you can press ^C to get an `MCR>` prompt
and then type `ABO AT.` to kill the command file processor, which gets you back to the system prompt.

On the systems I worked on, it was "ABO ...AT." YMMV.
 
GreyHairedDECfan...

ABO AT. or ABO AT.T0 work to kill it on my test system, which is a PiDP-11 as described in the link I put up.
It seem these tasks get AT.T<terminal-number> automatically on this system.
My previous experiences were on RSX11M where the 1st user did indeed get ...AT. if it was not in use already by another user ...
so, as you noted YMMV indeed !
 
Hunta...

Ctrl+Z does indeed work to get out of the command file processor, ending that AT. task instance. Neat.

I believe your `exotic` REM AT. at that point (as AT.T0 no longer exists) will remove the ...AT. command processor
from the tasklist and stop any future use of @ commands and so may not be desirable !
 
Back
Top