SMS 1000 aka PDP-11/73

OK, I've powered on both of the systems with the PDP-11/73 processor boards in it. I now know that they are apparently "SMS 1000" machines, but I've been able to find nothing on it on the net, except for a web page that has a picture of one in a 'tower' case http://staff.motiv.co.uk/~kevan/collection/manufacturer-sms/1000.html Mine is in a rack mount case though. It has 5 buttons and a small alphanumeric LED display that gives some system info when the system is powering up. I'm quite honestly not sure how to proceed. I've connected a laptop running TELIX for VT100 emulation. This gave me some trouble initially, but it started working once I added a "Null Modem" adapter I had (trust me you don't want to see the console cable I put together with three adapters). The display and buttons are layed out like this. +-----------------------------+ | DISPLAY | +-----------------------------+ +------+------+------+------+ | MENU | < | > | * | +--+---+---+--+---+--+---+--+ | RE | RUN | WRT | | START | HALT | PROT | +-------+------+------+ On the one with the 5.25" floppy I get the following when it comes up. SMS 1000 BOOTSTRAP 256KW MEMORY 11/73 CPU BOOTABLE DEVICES: DEVICE DEVICE UNIT NAME TYPE NUMBERS DU DSA 0-15 MU TK50 0 MS TS 0 ENTER DEVICE NAME AND UNIT NUMBER: AUTO - BOOT BOOTING FROM DEVICE 0 ***THIS VOLUME DOES NOT CONTAIN A HARDWARE BOOTABLE SYSTEM *** 000034 @ On the one with the 8" I get HELLO MIKE BOOTSTRAP 256KW MEMORY 11/73 CPU BOOTABLE DEVICES: DEVICE DEVICE UNIT NAME TYPE NUMBERS DU DSA 0-15 MU TK50 0 MS TS 0 ENTER DEVICE NAME AND UNIT NUMBER: AUTO - BOOT BOOTING FROM DEVICE 1 BOOT-U-CI/O error 000724 @ I played around and they both appear to default to the correct device numbers for Hard Drives. It gives me a *** DEVICE NOT IN SYSTEM *** if I try to access MU0 or MS0. Well, MU0 is no surprise, I know it doesn't have a TK50 in it, but I've no idea what the TS is, or how I would, or if I could boot from floppy. The 'C' in BOOT-U-CI/O error is actually a wierd c like character with a little squiggely under it. I'm assuming the first simply doesn't have an OS, and that the second has some sort of hardware problem, most likely a dead Hard Drive. I've tried to ensure that all the connections on both are good. I've learned that typing in 173000G at the @ prompt will get me back to the "ENTER DEVICE NAME AND UNIT NUMBER:" and that I can then specify a device instead of letting it go with it's own choice. Does anyone have any suggestions as to what I can do at this point? I'm guessing not much until I can scrounge an OS from somewhere. Is it possible to attach the RL02's from the /44 and see if I can boot off of those? What kind of a card does it take to interface with a RL02? Zane | Zane H. Healy | UNIX Systems Adminstrator | | healyzh(a)ix.netcom.com (primary) | Linux Enthusiast | | healyzh(a)holonet.net (alternate) | Classic Computer Collector | +----------------------------------+----------------------------+ | For Empire of the Petal Throne and Traveller Role Playing, | | see http://www.dragonfire.net/~healyzh/ | | For the collecting of Classic Computers with info on them. | | see http://www.dragonfire.net/~healyzh/museum.html |