On Sat, 14 Feb 2015, Peter Lothberg wrote:
Put the Panda20 monitor on it ans se if it boots.=20
Getting that on there will be a bit of a challenge however.
The MRC's Panda distribution that runs under the KLH-10 emulator,
configure a tape drive to write to file. Make yourself a completek
boot/distribution tape. Write it to you SCSI tape drive, Johnny had a
program. Put the drive on the SC-40 and tell ot to boot from the tape.
Does the permissions system implement any special locking requiring me to drop to mini-EXEC from tape to backup the PS?
SCSI tape is identified with a response to SCSI INQUIRY (or is it INQUIRE?) correct? Does the NSP implement a command to list the devices on a specific SCSI channel? I THINK I boot from tape by setting source to the tape drive?
I would do this with a copy of your boot-disk, as I don't remember how
the console processor file-system got there.. Think it's simular to
how it's done on a KS2020. (A file with the FE system and a pointer in
the home-block).
Yeah, obviously I'll be making a copy. ;)
-P
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Put the Panda20 monitor on it ans se if it boots.=20
Getting that on there will be a bit of a challenge however.
The MRC's Panda distribution that runs under the KLH-10 emulator,
configure a tape drive to write to file. Make yourself a completek
boot/distribution tape. Write it to you SCSI tape drive, Johnny had a
program. Put the drive on the SC-40 and tell ot to boot from the tape.
I would do this with a copy of your boot-disk, as I don't remember how
the console processor file-system got there.. Think it's simular to
how it's done on a KS2020. (A file with the FE system and a pointer in
the home-block).
-P
Sent from my iPhone
On Feb 14, 2015, at 02:17, Peter Lothberg <roll at Stupi.SE> wrote:
Interesting that it's brought out to RJ45 connectors though!
I thought copper FDDI was a mini-DIN? Was that a Cisco-specific
implementation?
The DIN connector is to control the bypass. CDDI is a RJ45 connector.
Ahhhhh.
(And 100M ended up using a very simular line encoding)
Thanks, that helps.
The DFxxx are KL10 cpu diagnostics, BIN are code for the chanel-cpu's
Glad I have diagnostics at least, if they are just KL10 diags there should
be a DEC reference of what diag = what.
Yes; xxKAA is the basic instruction test for a PDP10, DBKAA for
example runs on a KI10...
Thanks.
In you directory there is no operating system, it can still be on the
the disk in the OS file-system, but you need to teach the boot to look
at that drive..
Good thing EDDT works!
...no idea how to break back to NSP though...or anything about the
bootloader.
Control \
Thanks.
Do you have more than 1 drive?
No, my disk bays were empty.
Disk bay? Take another picture, please.
External CompuServe-manufactured enclosures. SCSI string with connectors, don't have the cable for connecting to distribution panel though.
As those are just 512-byte-sector ones I believe you said...those are easy
enough to image. I'd just need to give Gerry a ring so I can swing by
with a VAX or something that'll accept a SCSI drive.
Does the microcode/boot drive operate as a MASSBUS emulator, or is it also
SCSI brought out directly? (That one would POSSIBLY be documented
though...unlike the other stuff. So TOPS-20 could be made to work on
that)
Kindof... There are several operating modes, Standard T10, Standard
T20, 25 bit physical address T10, 30 Bit virtual adress Tops20.
That's very helpful, would be a good starting point.
Unless there is something special with the CS boxes, it will start off
pretending to be a normal KL10-B-E with masbuss..
Okay. Thanks for the info.
Put the Panda20 monitor on it ans se if it boots.
Getting that on there will be a bit of a challenge however.
Need to get a compatible tape drive so I can do anything real.
basically any SCSI tape works, a DLT, A DAT a 9trk....
That's easy enough to do then. Just need to find a working drive.
-P
Interesting that it's brought out to RJ45 connectors though!
I thought copper FDDI was a mini-DIN? Was that a Cisco-specific
implementation?
The DIN connector is to control the bypass. CDDI is a RJ45 connector.
(And 100M ended up using a very simular line encoding)
The DFxxx are KL10 cpu diagnostics, BIN are code for the chanel-cpu's
Glad I have diagnostics at least, if they are just KL10 diags there should
be a DEC reference of what diag = what.
Yes; xxKAA is the basic instruction test for a PDP10, DBKAA for
example runs on a KI10...
In you directory there is no operating system, it can still be on the
the disk in the OS file-system, but you need to teach the boot to look
at that drive..
Good thing EDDT works!
...no idea how to break back to NSP though...or anything about the
bootloader.
Control \
Do you have more than 1 drive?
No, my disk bays were empty.
Disk bay? Take another picture, please.
As those are just 512-byte-sector ones I believe you said...those are easy
enough to image. I'd just need to give Gerry a ring so I can swing by
with a VAX or something that'll accept a SCSI drive.
Does the microcode/boot drive operate as a MASSBUS emulator, or is it also
SCSI brought out directly? (That one would POSSIBLY be documented
though...unlike the other stuff. So TOPS-20 could be made to work on
that)
Kindof... There are several operating modes, Standard T10, Standard
T20, 25 bit physical address T10, 30 Bit virtual adress Tops20.
Unless there is something special with the CS boxes, it will start off
pretending to be a normal KL10-B-E with masbuss..
Put the Panda20 monitor on it ans se if it boots.
Need to get a compatible tape drive so I can do anything real.
basically any SCSI tape works, a DLT, A DAT a 9trk....
-P
On Sat, 14 Feb 2015, Peter Lothberg wrote:
http://i.imgur.com/ZmLpwhV.jpg
So you have a CDDI (fddi over copper) interface and 3 SCSI ports.
Interesting that it's brought out to RJ45 connectors though!
I thought copper FDDI was a mini-DIN? Was that a Cisco-specific implementation?
http://i.imgur.com/KYl73d8.jpg
BOOT40.EXE tell me about hung SCSI devices (Shocker, none plugged in).
BTSCFC Can't find any channels
Can't tell if I'm missing a drive the rest of the OS would be on.
I think that "boot40" tells it to boot from chan4/drive0.
That makes sense.
The DFxxx are KL10 cpu diagnostics, BIN are code for the chanel-cpu's
Glad I have diagnostics at least, if they are just KL10 diags there should be a DEC reference of what diag = what.
In you directory there is no operating system, it can still be on the
the disk in the OS file-system, but you need to teach the boot to look
at that drive..
Good thing EDDT works!
...no idea how to break back to NSP though...or anything about the bootloader.
Do you have more than 1 drive?
No, my disk bays were empty.
As those are just 512-byte-sector ones I believe you said...those are easy enough to image. I'd just need to give Gerry a ring so I can swing by with a VAX or something that'll accept a SCSI drive.
Does the microcode/boot drive operate as a MASSBUS emulator, or is it also SCSI brought out directly? (That one would POSSIBLY be documented though...unlike the other stuff. So TOPS-20 could be made to work on that)
Need to get a compatible tape drive so I can do anything real.
-P
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
RH channels:
LOGICAL ACTUAL TYPE MISCELLANEOUS
5 CHN1 EI
0 CHN0 SI MASK=0x03
1 CHN2 SI MASK=0x03
7 CHN3 CI PORT#=0x3
http://i.imgur.com/ZmLpwhV.jpg
So you have a CDDI (fddi over copper) interface and 3 SCSI ports.
http://i.imgur.com/KYl73d8.jpg
BOOT40.EXE tell me about hung SCSI devices (Shocker, none plugged in).
BTSCFC Can't find any channels
Can't tell if I'm missing a drive the rest of the OS would be on.
I think that "boot40" tells it to boot from chan4/drive0.
The DFxxx are KL10 cpu diagnostics, BIN are code for the chanel-cpu's
In you directory there is no operating system, it can still be on the
the disk in the OS file-system, but you need to teach the boot to look
at that drive..
Do you have more than 1 drive?
-P
On Thu, 12 Feb 2015, Peter Lothberg wrote:
Cory,
When you have sorted out the console thing, do:
NSP>show cpu assIGNMENT
CPU0 has the following channels assigned:
No IU channels
RH channels:
LOGICAL ACTUAL TYPE MISCELLANEOUS
5 CHN1 EI
0 CHN0 SI MASK=0x03
1 CHN2 SI MASK=0x03
7 CHN3 CI PORT#=0x3
http://i.imgur.com/ZmLpwhV.jpg
DTEs:
LOGICAL ACTUAL TYPE MISCELLANEOUS
0 FE PRIVILEGED
and
NSP>dir
http://i.imgur.com/KYl73d8.jpg
BOOT40.EXE tell me about hung SCSI devices (Shocker, none plugged in). BTSCFC Can't find any channels
Can't tell if I'm missing a drive the rest of the OS would be on.
-P
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Grounding issue sorted. Trying diagnostics.
Booting compuserve monitor complains about file not found. Could be on a disk I don't have.
Sent from my iPhone
On Feb 13, 2015, at 01:37, Cory Smelosky <b4 at gewt.net> wrote:
On Fri, 13 Feb 2015, Paul_Koning at Dell.com wrote:
On Feb 12, 2015, at 12:41 PM, Johnny Billquist <bqt at softjar.se> wrote:
...
Start with just 7 bits no parity. Try both one and two stop bits. Then move on from there.
7 bits no parity is something I ve never seen. I would start with 8 bits no parity, one stop bit unless it s 110 bps. 7 bits with parity, that does come up on a few occasions. But while I ve seen 8 and 5 and even 6 bit serial comms used, I can t think of any 7 bits in the wild.
Looking like it's some grounding issue somewhere. Waiting until someone with better eyes had physical access and can trace it out...due to no schematics unless Peter has some.
paul
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2015-02-13 15:36, Paul_Koning at Dell.com wrote:
On Feb 13, 2015, at 9:06 AM, Clem Cole <clemc at ccc.com
<mailto:clemc at ccc.com>> wrote:
I agree, I never saw _/correctly/_ configured systems with anything
less than 8 bits. 7 with parity (8 total) as Paul said,
was pretty standard. particularly on modems. Early UNIX tty drivers
used to assume it and pretty much always AND 0x7F with the input
character.
Not only that, but some (BSD 2.9?) put out text with 0x80 ORed into the
output stream, which messes up modern terminal emulators.
It's still there in 2.11BSD, until the last (unofficial) patch set I sent out a few years ago which removed it.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
