Nice! Real hardware! One day I'll get my 11/53 back up. Are you
giving guest access and/or offering accounts? And do you have
Fortran? :)
Regards,
Mark
On Sun, Feb 16, 2014 at 2:52 PM, Peter Lothberg <roll at stupi.se> wrote:
With (a lot) of help from Johnny I have a RSX11 box on HECnet. It's a
11/53, 1.5M memory, SCSI disk and tape on CMD controller and delqua.
(It's in Sunnyvale).
$set host krylbo
[Attempting a connection, connect OK, ]
[Remote host is a RSX-11M+ system]
[TYPE ^\,<RET> to return to node SOL]
Connected to "KRYLBO"
log 10,2
Password:
RSX-11M-PLUS V4.6 BL87 [1,54] System KRYLBO
16-FEB-14 16:45 Logged on Terminal RT0: as PLT1
Good Afternoon
*****************************************************************
* *
* Welcome to RSX-11M-PLUS *
* *
* Version 4.6 Base level 87 *
* This is file LB:[1,2]LOGIN.TXT *
* *
*****************************************************************
Last interactive login on Friday, February 14, 2014 07:40:49 (RT0:)
NCP>show exec char
Node characteristics as of 16-FEB-14 16:50:52
Executor node = 59.55 (KRYLBO)
Identification = RSXBURK, Management version = 4.2.0
Host = 59.55 (KRYLBO), Loop count = 1
Loop length = 40, Loop with = Mixed
Incoming timer = 15, Outgoing timer = 30
NSP version = 4.0.0
Maximum links = 10, Delay factor = 32
Delay weight = 2
Inactivity timer = 30, Retransmit factor = 5
Routing version = 2.0.0, Type = Endnode IV
Maximum circuits = 1
Incoming proxy = Disabled
Outgoing proxy = Disabled
Segment buffer size = 576
NCP>show kno cir
Known circuits summary as of 16-FEB-14 16:51:06
Circuit = QNA-0
State = On
Adjacent node = 59.57 (E825GW)
NCP>
-P
Dave McGuire skrev 2013-12-24 05:14:
On 12/23/2013 10:46 PM, Johnny Billquist wrote:
Ahh, got it. I have a bru64k.tap file that I think came from the same
place. If you have a brusys.tap file, would you please send me a copy?
I can't seem to find that anywhere.
Did you try booting the BRU64K tape? Sounds like that should be a BRUSYS
system as well.
Not sure what the correct name is. I know it by BRUSYS, but there might
be some slight difference between the 11M and M+ standalone BRU, or it
might just be different versions of the same.
BRU64K also rings some bell, so I think I've seem that name as well.
I booted it. It seems BRU64K does not support MU: devices. The
"regular" BRUSYS does. I don't know what other differences there may be.
BRU64K "might" be able to fit into a system with merely 64 k RAM... (And
might be older than your other BRU immage ...)
Ok. I was mainly concerned about the stuff fitting...I'm assuming
4.2/4.3 are larger than 4.1. 4.1 was the last version I ran.
I've found the relevant sections of the documentation and am reading
it now.
Excellent.
Progress! I've restored the DL installation set under simh, moved the
RL02 disk images over to a (real) VAX, written them to RL02 packs, and
am running a sysgen on a (real) PDP-11/24. It's midway through the
assembly of the executive. I took a crappy phone pic:
http://www.neurotica.com/misc/pdp1124-rsx-sysgen-20131223.jpg
(yes, that bottom RL02 really is dirty...I'll clean it soon)
I wish I still had that tape, but sadly it was lost many years ago.
Distribution tape for 4.1? I thought you had 4.3 anyway, so what would
you use 4.1 for?
I wouldn't...but it was a pristine, original DEC RSX-11M distribution
tape, and those don't exactly grow on trees.
Thank you Johnny. I'm sure I will have other questions as I become
reacquainted with RSX.
No problems. Feel free to ask anything.
Thank you!
First question: I'd like to try to get DECnet running on this system,
if possible, to get it on HECnet. I've never run DECnet under RSX
before. I could put a DEUNA in the machine, but I am running short of
slots. I have a DELUA, but I don't recall sysgen asking about DELUAs.
Are they compatible at the driver level? Meaning, if I re-do my sysgen
to include a DEUNA driver, will that work with a DELUA?
-Dave
As I remember the SYSGEN/NETGEN task, the controller intended for DECnet
should NOT be taken into SYSGEN at all, but later, at the totally
separate task of performing NETGEN once Your OS. is up and running, it
should be included there. So, no need to redo your SYSGEN when playing
with different Ethernet cards.
BTW: DELUA replaced DEUNA...
/Gvran -SM6NNC
With (a lot) of help from Johnny I have a RSX11 box on HECnet. It's a
11/53, 1.5M memory, SCSI disk and tape on CMD controller and delqua.
(It's in Sunnyvale).
$set host krylbo
[Attempting a connection, connect OK, ]
[Remote host is a RSX-11M+ system]
[TYPE ^\,<RET> to return to node SOL]
Connected to "KRYLBO"
log 10,2
Password:
RSX-11M-PLUS V4.6 BL87 [1,54] System KRYLBO
16-FEB-14 16:45 Logged on Terminal RT0: as PLT1
Good Afternoon
*****************************************************************
* *
* Welcome to RSX-11M-PLUS *
* *
* Version 4.6 Base level 87 *
* This is file LB:[1,2]LOGIN.TXT *
* *
*****************************************************************
Last interactive login on Friday, February 14, 2014 07:40:49 (RT0:)
NCP>show exec char
Node characteristics as of 16-FEB-14 16:50:52
Executor node = 59.55 (KRYLBO)
Identification = RSXBURK, Management version = 4.2.0
Host = 59.55 (KRYLBO), Loop count = 1
Loop length = 40, Loop with = Mixed
Incoming timer = 15, Outgoing timer = 30
NSP version = 4.0.0
Maximum links = 10, Delay factor = 32
Delay weight = 2
Inactivity timer = 30, Retransmit factor = 5
Routing version = 2.0.0, Type = Endnode IV
Maximum circuits = 1
Incoming proxy = Disabled
Outgoing proxy = Disabled
Segment buffer size = 576
NCP>show kno cir
Known circuits summary as of 16-FEB-14 16:51:06
Circuit = QNA-0
State = On
Adjacent node = 59.57 (E825GW)
NCP>
-P
Dave McGuire skrev 2013-12-24 05:14:
On 12/23/2013 10:46 PM, Johnny Billquist wrote:
Ahh, got it. I have a bru64k.tap file that I think came from the same
place. If you have a brusys.tap file, would you please send me a copy?
I can't seem to find that anywhere.
Did you try booting the BRU64K tape? Sounds like that should be a BRUSYS
system as well.
Not sure what the correct name is. I know it by BRUSYS, but there might
be some slight difference between the 11M and M+ standalone BRU, or it
might just be different versions of the same.
BRU64K also rings some bell, so I think I've seem that name as well.
I booted it. It seems BRU64K does not support MU: devices. The
"regular" BRUSYS does. I don't know what other differences there may be.
BRU64K "might" be able to fit into a system with merely 64 k RAM... (And
might be older than your other BRU immage ...)
Ok. I was mainly concerned about the stuff fitting...I'm assuming
4.2/4.3 are larger than 4.1. 4.1 was the last version I ran.
I've found the relevant sections of the documentation and am reading
it now.
Excellent.
Progress! I've restored the DL installation set under simh, moved the
RL02 disk images over to a (real) VAX, written them to RL02 packs, and
am running a sysgen on a (real) PDP-11/24. It's midway through the
assembly of the executive. I took a crappy phone pic:
http://www.neurotica.com/misc/pdp1124-rsx-sysgen-20131223.jpg
(yes, that bottom RL02 really is dirty...I'll clean it soon)
I wish I still had that tape, but sadly it was lost many years ago.
Distribution tape for 4.1? I thought you had 4.3 anyway, so what would
you use 4.1 for?
I wouldn't...but it was a pristine, original DEC RSX-11M distribution
tape, and those don't exactly grow on trees.
Thank you Johnny. I'm sure I will have other questions as I become
reacquainted with RSX.
No problems. Feel free to ask anything.
Thank you!
First question: I'd like to try to get DECnet running on this system,
if possible, to get it on HECnet. I've never run DECnet under RSX
before. I could put a DEUNA in the machine, but I am running short of
slots. I have a DELUA, but I don't recall sysgen asking about DELUAs.
Are they compatible at the driver level? Meaning, if I re-do my sysgen
to include a DEUNA driver, will that work with a DELUA?
-Dave
As I remember the SYSGEN/NETGEN task, the controller intended for DECnet
should NOT be taken into SYSGEN at all, but later, at the totally
separate task of performing NETGEN once Your OS. is up and running, it
should be included there. So, no need to redo your SYSGEN when playing
with different Ethernet cards.
BTW: DELUA replaced DEUNA...
/Gvran -SM6NNC
Many thanks.
I think we all have created a library of tape tools over the years. I'll put on my todo this to get my set together.
As for the OSX lack of mtio.h - i've just pulled it from FreeBSD and never had an issue - obviously there is not driver. I 100% agree -- it does seems nuts and I've b*tched at my friends at Apple about it a few times. Another thing I have on my todo list is try to slide the drivers back into an hackintosh i had running on a vm in a system that has an old DEC/Adaptec PCI card in it that I still use for SCSI tapes. That said, when I have needed the tape I've just used the BSD driver on the base system.
Clem
On Sun, Feb 16, 2014 at 5:51 AM, Johnny Billquist <bqt at softjar.se> wrote:
Since from time to time, I get questions about the different tape image formats that exists, as well as how to read/write tapes from Unix, I decided to publish a set of small programs I initially write many, many years ago. In the process of cleaning things up to make them more presentable, I also made them more flexible. The odd person might have seen these programs in earlier reincarnations from me at some point in time.
Anyway, I have a set of four programs, that a few people might find useful, if they play on Unix systems.
tpr - reads from a physical tape and creates an image on disk
tpw - reads an image from disk and writes it to a physical tape
tpc - copy/convert a disk image
tpx - examine/verify a disk image
These programs will handle both .tpc images (2 byte record length headers) and .tap images (4 byte record length headers and footers).
The programs tries to automatically identify the format of the file, but you can also force a format.
They are still extremely simple and stupid programs, and have very little error handling, or help. Feel free to ask if you have questions. Suggestions, as well as patches are also welcome.
The files can be found under ftp://ftp.update.uu.se/pub/pdp11/tptools.tar
(And yes, I know they will not compile under OSX - Apple in their infinite wisdom have dropped support for tapes, and thus mtio.h no longer is around, and their man-pages also have big holes around tapes, where plenty of references from other man-pages exists... tpc and tpx is easy to fix for OSX though, but you're out of luck as far as tpr and tpw goes...)
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
Since from time to time, I get questions about the different tape image formats that exists, as well as how to read/write tapes from Unix, I decided to publish a set of small programs I initially write many, many years ago. In the process of cleaning things up to make them more presentable, I also made them more flexible. The odd person might have seen these programs in earlier reincarnations from me at some point in time.
Anyway, I have a set of four programs, that a few people might find useful, if they play on Unix systems.
tpr - reads from a physical tape and creates an image on disk
tpw - reads an image from disk and writes it to a physical tape
tpc - copy/convert a disk image
tpx - examine/verify a disk image
These programs will handle both .tpc images (2 byte record length headers) and .tap images (4 byte record length headers and footers).
The programs tries to automatically identify the format of the file, but you can also force a format.
They are still extremely simple and stupid programs, and have very little error handling, or help. Feel free to ask if you have questions. Suggestions, as well as patches are also welcome.
The files can be found under ftp://ftp.update.uu.se/pub/pdp11/tptools.tar
(And yes, I know they will not compile under OSX - Apple in their infinite wisdom have dropped support for tapes, and thus mtio.h no longer is around, and their man-pages also have big holes around tapes, where plenty of references from other man-pages exists... tpc and tpx is easy to fix for OSX though, but you're out of luck as far as tpr and tpw goes...)
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
On Sat, 15 Feb 2014, Mark Abene wrote:
I gave up trying to make sense out of <mail>mailer-relay-info.txt.
Even MM's source code is vague at best. I ultimately made no changes
in TOPS-20 at all, and just created a rule in my router's iptables to
intercept all outgoing mail from TOPS-20 and divert it to a single
mail server. If you have a linux-based router, I can give you the
proper iptables incantation to do the same.
Cisco at this end, I can probably figure out a redirect rule easily enough.
-Mark
On Sat, Feb 15, 2014 at 2:15 AM, Cory Smelosky <b4 at gewt.net> wrote:
Hello all,
I saw earlier Mark A. was working on email craziness with TOPS-20. I need
to do the same, however I already have the groundwork in place. All I need
to do is tell it to relay all email to postfix over IP. It automatically
relays to my mailserver.
Where's the configuration manual for email located? One has to exist. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
I gave up trying to make sense out of <mail>mailer-relay-info.txt.
Even MM's source code is vague at best. I ultimately made no changes
in TOPS-20 at all, and just created a rule in my router's iptables to
intercept all outgoing mail from TOPS-20 and divert it to a single
mail server. If you have a linux-based router, I can give you the
proper iptables incantation to do the same.
-Mark
On Sat, Feb 15, 2014 at 2:15 AM, Cory Smelosky <b4 at gewt.net> wrote:
Hello all,
I saw earlier Mark A. was working on email craziness with TOPS-20. I need
to do the same, however I already have the groundwork in place. All I need
to do is tell it to relay all email to postfix over IP. It automatically
relays to my mailserver.
Where's the configuration manual for email located? One has to exist. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Hello all,
I saw earlier Mark A. was working on email craziness with TOPS-20. I need to do the same, however I already have the groundwork in place. All I need to do is tell it to relay all email to postfix over IP. It automatically relays to my mailserver.
Where's the configuration manual for email located? One has to exist. ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Thanks Peter, I've been peering with Dave McGuire doing DECnet over
GRE on an emulated cisco 7206 in dynamips/dynagen. Other than burning
a lot of CPU cycles versus a much simpler Johnny-bridge, it works
quite well. :)
I'm GLGMSH (61.150) on HECnet, or gilgamesh.phiber.com on the Internet
if anyone is looking for a reliable TOPS-20 Panda system to hang out
on. Full e-mail, HECnet and Internet access.
-Mark
On Fri, Feb 14, 2014 at 11:32 AM, Peter Lothberg <roll at stupi.se> wrote:
For HECnet I'm just running a plain old fashioned Johnny-bridge. :)
I take it HECnet peers are lacking in the U.S.?
I have a cisco box with DEcnet tunnels attached to a core bbox of a
major backboone in Reston VA, but no "johnny box".
-P
For HECnet I'm just running a plain old fashioned Johnny-bridge. :)
I take it HECnet peers are lacking in the U.S.?
I have a cisco box with DEcnet tunnels attached to a core bbox of a
major backboone in Reston VA, but no "johnny box".
-P
On 5 February 2014 09:17, Mark Wickens <mark at wickensonline.co.uk> wrote:
On 05/02/2014 08:00, Cory Smelosky wrote:
On Wed, 5 Feb 2014, Google wrote:
On 5 Feb 2014, at 05:26, Cory Smelosky <b4 at gewt.net> wrote:
So, my VAXstation 4000/60 shut off and I had difficulty getting it to turn back on. Seems like a not-to-abnormal situation, right? PSU's getting old or overheating protection kicked in? That's not the weird part!
It may have overheated, I do know power switches can get flakey in VS4000s but the symptoms tend to be it won't turn OFF not on't turn ON but I guess if the switch is not contacting correctly it could be that too. the switch isn't, as far as I can tell, directly controlling the current, it is in some kind of latch circuit that unlatches when you flick it to 'OFF'. I think it's an early 'soft-power' implementation.
I moved the UPS further away. Very possible it got bumped and got too close to the UPS.
Full explanation:
http://dectec.info/vaxstation-4000-power-switch-issues-and-cleaning/
Thanks!
Also talk to Mark Wickens, he's had a few issues with 4000/90 PSUs.
When I rebooted the system...it had decided it was suddenly /2015/ and all the licenses expired. I've heard of systems resetting to the past when something happens...but NEVER the future!
That is odd, but Mark W remarked on my blog about one PSU failing and spiking his 4000/90 so badly it fried several parts, it's possible it could have upskittled the TOY clock?
Fans would click for a second and then kick right back off. It stopped doing that until I removed all the drives. Plugged 'em back in after opening the PSU to look for obvious faults and found none. Everything is working fine now...Strange.
I had a hard disk taken out by a power spike. I also had firmware corruption that required reflashing the EEPROM, but I don't remember if that was related to the PSU. They draw 30 watts when switched 'off' so it's definitely worth turning them off when not in use. Twitching fans might indicate over-current protection kicking in. I know one thing however - switched mode PSU experts are few and far between!
Don't I know it! I think that if you want to collect vintage hardware you either need a tame PSU repair man, or you need to start learning. I don't have such a person to hand, or at least not one I want to ask too often anyway, so I need to learn. This is happening a bit, but I am very slow, and I need more test equipment, like the ESR meter that has been suggested.
Regards
Rob
