On 03/16/2015 02:28 PM, Johnny Billquist wrote:
On 2015-03-16 18:32, Clement T. Cole wrote:
Yes. It should be by easy to do, although I thought Tom put the BRU
support code in there because I remember one the folks we worked
(Mital in Canada IIRC) used RSX somewhere and he had the deal with it
when then sent us tapes. But may be it was not BRU. I don't remember
as that worked started as I was leaving UCB and Tom had become the new
mr. 9-track and Thus I did not write that code (I did write the
original RT11 support with which he started).
I obviously don't know what Tom might have done. It's definitely
possible he did. But depending on when this was, it might have been
another format called DSC (Disk Save and Compress), which is what RSX
used up until V3.something. Which is, I think, almost mid-80s.
My first 11/34 came with an RSX-11M v4.2 distribution tape, which had
been kicking around there for a couple of years already, in 1986, so I'd
assume 3.x was a bit earlier than mid-80s.
-Dave
--
Dave McGuire, AK4HZ/3
New Kensington, PA
On Mon, Mar 16, 2015 at 3:55 PM, Johnny Billquist <bqt at softjar.se> wrote:
Nitpick: The 11/40 "class" machines did not have split I/D space.
Split I/D space was the 11/45,11/50,11/55 and 11/70, before we move into "modern" PDP-11s..
That's what I said - "shared I/D" as opposed to "split I/D"
On 2015-03-16 20:43, Clem Cole wrote:
On Mon, Mar 16, 2015 at 3:13 PM, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
And one of the tricks were to reduce disk seek times during a
backup. And that is done by actually not backing up files in the
logical order of the blocks in the file, but in the order they
appear on disk, which is why I said the format is slightly tricky.
That was a common trade off - the reason being that backup was done way
more often then restore. But the problem was that the a lot of the
those formats had a big issues when you had a tape error (UNIX tp and
the PDP-10 dumper formats were notorious for this problem).
Tape errors gives you problems no matter which way you cut it. The BRU format allows you to deal with the rest of the file/tape properly anyway.
But as you say a threaded format like that, you don't need a PhD to
figure it out. You just need to be careful and recognize there is a
bunch of housekeeping needed when you pull things back in. Today its a
little easier, but on an 11/40 class (shared I/D space) that would be
even more difficult, since you don't have a lot of room in active memory
to keep those tables.
Nitpick: The 11/40 "class" machines did not have split I/D space.
Split I/D space was the 11/45,11/50,11/55 and 11/70, before we move into "modern" PDP-11s...
The 11/40 is really a primitive model, where most things you even could have was optional. The basic CPU do not have an MMU, no EIS, no stack limit, not to mention that the 11/40 never even had the capability of an FPP. It had the FIS instead...
(And no I/D space, nor supervisor mode, nor 22-bit addressing.)
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 Mon, Mar 16, 2015 at 3:13 PM, Johnny Billquist <bqt at softjar.se> wrote:
And one of the tricks were to reduce disk seek times during a backup. And that is done by actually not backing up files in the logical order of the blocks in the file, but in the order they appear on disk, which is why I said the format is slightly tricky.
That was a common trade off - the reason being that backup was done way more often then restore. But the problem was that the a lot of the those formats had a big issues when you had a tape error (UNIX tp and the PDP-10 dumper formats were notorious for this problem).
But as you say a threaded format like that, you don't need a PhD to figure it out. You just need to be careful and recognize there is a bunch of housekeeping needed when you pull things back in. Today its a little easier, but on an 11/40 class (shared I/D space) that would be even more difficult, since you don't have a lot of room in active memory to keep those tables.
Clem
On 2015-03-16 19:52, Clem Cole wrote:
On Mon, Mar 16, 2015 at 2:28 PM, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
I obviously don't know what Tom might have done. It's definitely
possible he did. But depending on when this was, it might have been
another format called DSC (Disk Save and Compress), which is what
RSX used up until V3.something. Which is, I think, almost mid-80s.
Johnny,
As I said, neither do it and I don't have the code on-line to look
anymore, but given the dates you mention, DSC sounds more reasonable.
His work would have been 82/83 ish IIRC. I seem to remember that the
tapes from Mitel came from an RSX system that one of our
officemates/fellow grad students brought with him, telling us the tapes
were an RSX backup format. When we mounted them and started to poke
around, the tools we had would not work without modification. Since I
was getting ready to bug out/graduate, I remember Tom dealt with it, I
just don't remember how he did it.
Yeah. And I don't know at all how the DSC format looked like, but I believe it was simpler than BRU. One of the reasons for DEC to create BRU was to improve speed of backups. And one of the tricks were to reduce disk seek times during a backup. And that is done by actually not backing up files in the logical order of the blocks in the file, but in the order they appear on disk, which is why I said the format is slightly tricky.
This is a good example of knowing enough to be dangerous. I know a
little about RSX, but never dived in deep enough to be sure of any of
some of those details, so if you suggest that it was likely DSC, I
definitely bow to your knowledge.
:-)
That said, a quick look at:
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rsx/dec…
and, assuming no tape errors .... I suspect that it should not be that
hard to take any of the UNIX ansi tape readers that are available and
hack this format in them. Interesting to see the RAD50 stuff in there.
That takes me back to painful times.
Yeah, I have already studied that document at a great length.
The format is not hard. But the fact that you need to analyze some meta-information in order to understand where the disk blocks in the backup saveset actually fits into the restored file makes it a bit more interesting.
It also looks like the tape directory is in the front few blocks of the
tape, which was pretty typical of a number of tape formats, particularly
ones for backup. [This makes writing the tapes easier (faster) but it
also make recovery harder if you lose blocks in the directory].
Yes. Like said. It's not rocket science, but it is a bit more complicated than you might first realize.
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 Mon, Mar 16, 2015 at 2:28 PM, Johnny Billquist <bqt at softjar.se> wrote:
I obviously don't know what Tom might have done. It's definitely possible he did. But depending on when this was, it might have been another format called DSC (Disk Save and Compress), which is what RSX used up until V3.something. Which is, I think, almost mid-80s.
Johnny,
As I said, neither do it and I don't have the code on-line to look anymore, but given the dates you mention, DSC sounds more reasonable. His work would have been 82/83 ish IIRC. I seem to remember that the tapes from Mitel came from an RSX system that one of our officemates/fellow grad students brought with him, telling us the tapes were an RSX backup format. When we mounted them and started to poke around, the tools we had would not work without modification. Since I was getting ready to bug out/graduate, I remember Tom dealt with it, I just don't remember how he did it.
This is a good example of knowing enough to be dangerous. I know a little about RSX, but never dived in deep enough to be sure of any of some of those details, so if you suggest that it was likely DSC, I definitely bow to your knowledge.
That said, a quick look at: http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rsx/dec…
and, assuming no tape errors .... I suspect that it should not be that hard to take any of the UNIX ansi tape readers that are available and hack this format in them. Interesting to see the RAD50 stuff in there. That takes me back to painful times.
It also looks like the tape directory is in the front few blocks of the tape, which was pretty typical of a number of tape formats, particularly ones for backup. [This makes writing the tapes easier (faster) but it also make recovery harder if you lose blocks in the directory].
Clem
On 2015-03-16 18:32, Clement T. Cole wrote:
Yes. It should be by easy to do, although I thought Tom put the BRU support code in there because I remember one the folks we worked (Mital in Canada IIRC) used RSX somewhere and he had the deal with it when then sent us tapes. But may be it was not BRU. I don't remember as that worked started as I was leaving UCB and Tom had become the new mr. 9-track and Thus I did not write that code (I did write the original RT11 support with which he started).
I obviously don't know what Tom might have done. It's definitely possible he did. But depending on when this was, it might have been another format called DSC (Disk Save and Compress), which is what RSX used up until V3.something. Which is, I think, almost mid-80s.
BRU has been documented enough that it's not hard to write a program to extract the files from it, but it's is not totally trivial, as the files are somewhat scrambled in the saveset. I wrote a program to analyze and manipulate BRU tapes under Unix, to be able to repair tapes that had become corrupted (tape blocks scrambled).
When Tom took over he wrote a whole new program because the CAD group had had to start to deal with VMS so much and my original ANSI reader for RT11 tapes was pretty lame. When he was done, I'm pretty sure he could handle VMS save sets in his version because that what the CAD group @ DEC would use. I remember that HP used some funky format from the HP3000 which I ended up decoding using dd and some shell scripts and when never used again as we got them to switch to tar. IBM was always a different format (usually in EBCDIC). I remember once getting an ANSI labeled tape from them but in EBCDIC and broke all our tools. AT&T could also be funny. Different groups there used different tools even within UNIX so I got pretty good handling strange formats since they often sent tapes in binary and had endianness mixed in to add to the confusion. At the time, I became the go to person in Cory Hall (and often Evans folks would come to see me too) because I had spent time in a mainfra
m
e shop long before UCB and learned a lot of tricks and had a tool kit for same.
VMS backup savesets are totally incompatible with BRU savesets, though (sad). But I know I've seen Unix tools to read VMS tapes and savesets.
But both VMS and RSX use normal ANSI format tapes, so the first level of just getting to the savesets as such, is easy on Unix. Plenty of tools already exist to deal with ANSI labelled tapes.
Johnny
Somewhere I have a script called mtaapita - mag tapes are a pain in the ass - which I wrote to help pull the first few records apart and try to figure out how the tape was formatted. As I said, I used to have a pretty good collection of mag tape tools but they are not online anymore ( undoubtedly on a 9-track Unix dump tape in my basement).
Sent from my iPad
On Mar 16, 2015, at 12:25 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-03-16 14:08, Clem Cole wrote:
The format is defined in:
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rsx/dec…
and yes UNIX has tools that grok it.
Worst case it any ANSI tape reader will get the raw data off as files
with strange names and you may need a shell script to put some of the
files back together after decoding the directory.
My old housemate (and SPICE2/3 author) Tom Quarles wrote an really good
ANSI tape reader for Unix years ago. It did VMS format by default but
seem to remember he added RT11 and RSX support to it also. Since we had
to write tapes to export to those systems also.
Sadly, I used to have a directory of "magtape utilities" but I no longer
have it online. I'll try to poke around to see if I can find it next
weekend if no one else shouts out sooner.
BRU tapes are proper ANSI format tapes, so as far as that goes, the whole saveset as such can certainly be accessed with any tool that deals with ANSI tapes.
However, BRU savesets is another level, below this. To extract files from those savesets will require other software. I don't think any exists for Unix, but you can certainly write it.
Johnny
Clem
On Mon, Mar 16, 2015 at 1:05 AM, Cory Smelosky <b4 at gewt.net
<mailto:b4 at gewt.net>> wrote:
All,
Is it possible to extract files from a BRU RSX tape on UNIX, or is
the best path BRUREAD to VMS, and then zip/tar?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
--
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
below
On Mon, Mar 16, 2015 at 1:47 PM, <Paul_Koning at dell.com> wrote:
I remember the ANSI format produced by OS/360. It faintly resembled real ANSI labels, but the text was encoded in 8 bit ASCII , an IBM invention that no one else ever used before or since. I think they took regular 7 bit ASCII and moved the top bit up one so, for example, A was encoded as 0x81 rather than 0x41 as in real ASCII. After that discovery, I switched back to IBM standard labels (IBM proprietary, in EBCDIC), or more usually, unlabeled since IBM didn t do useful label processing anyway.
I think I remember getting a few of these from the IBM Cambridge folks.
On Mar 16, 2015, at 1:32 PM, Clement T. Cole <clemc at ccc.com> wrote:
... IBM was always a different format (usually in EBCDIC). I remember once getting an ANSI labeled tape from them but in EBCDIC and broke all our tools.
I remember the ANSI format produced by OS/360. It faintly resembled real ANSI labels, but the text was encoded in 8 bit ASCII , an IBM invention that no one else ever used before or since. I think they took regular 7 bit ASCII and moved the top bit up one so, for example, A was encoded as 0x81 rather than 0x41 as in real ASCII. After that discovery, I switched back to IBM standard labels (IBM proprietary, in EBCDIC), or more usually, unlabeled since IBM didn t do useful label processing anyway.
paul
Yes. It should be by easy to do, although I thought Tom put the BRU support code in there because I remember one the folks we worked (Mital in Canada IIRC) used RSX somewhere and he had the deal with it when then sent us tapes. But may be it was not BRU. I don't remember as that worked started as I was leaving UCB and Tom had become the new mr. 9-track and Thus I did not write that code (I did write the original RT11 support with which he started).
When Tom took over he wrote a whole new program because the CAD group had had to start to deal with VMS so much and my original ANSI reader for RT11 tapes was pretty lame. When he was done, I'm pretty sure he could handle VMS save sets in his version because that what the CAD group @ DEC would use. I remember that HP used some funky format from the HP3000 which I ended up decoding using dd and some shell scripts and when never used again as we got them to switch to tar. IBM was always a different format (usually in EBCDIC). I remember once getting an ANSI labeled tape from them but in EBCDIC and broke all our tools. AT&T could also be funny. Different groups there used different tools even within UNIX so I got pretty good handling strange formats since they often sent tapes in binary and had endianness mixed in to add to the confusion. At the time, I became the go to person in Cory Hall (and often Evans folks would come to see me too) because I had spent time in a mainframe shop long before UCB and learned a lot of tricks and had a tool kit for same.
Somewhere I have a script called mtaapita - mag tapes are a pain in the ass - which I wrote to help pull the first few records apart and try to figure out how the tape was formatted. As I said, I used to have a pretty good collection of mag tape tools but they are not online anymore ( undoubtedly on a 9-track Unix dump tape in my basement).
Sent from my iPad
On Mar 16, 2015, at 12:25 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2015-03-16 14:08, Clem Cole wrote:
The format is defined in:
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rsx/dec…
and yes UNIX has tools that grok it.
Worst case it any ANSI tape reader will get the raw data off as files
with strange names and you may need a shell script to put some of the
files back together after decoding the directory.
My old housemate (and SPICE2/3 author) Tom Quarles wrote an really good
ANSI tape reader for Unix years ago. It did VMS format by default but
seem to remember he added RT11 and RSX support to it also. Since we had
to write tapes to export to those systems also.
Sadly, I used to have a directory of "magtape utilities" but I no longer
have it online. I'll try to poke around to see if I can find it next
weekend if no one else shouts out sooner.
BRU tapes are proper ANSI format tapes, so as far as that goes, the whole saveset as such can certainly be accessed with any tool that deals with ANSI tapes.
However, BRU savesets is another level, below this. To extract files from those savesets will require other software. I don't think any exists for Unix, but you can certainly write it.
Johnny
Clem
On Mon, Mar 16, 2015 at 1:05 AM, Cory Smelosky <b4 at gewt.net
<mailto:b4 at gewt.net>> wrote:
All,
Is it possible to extract files from a BRU RSX tape on UNIX, or is
the best path BRUREAD to VMS, and then zip/tar?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2015-03-16 14:08, Clem Cole wrote:
The format is defined in:
http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rsx/dec…
and yes UNIX has tools that grok it.
Worst case it any ANSI tape reader will get the raw data off as files
with strange names and you may need a shell script to put some of the
files back together after decoding the directory.
My old housemate (and SPICE2/3 author) Tom Quarles wrote an really good
ANSI tape reader for Unix years ago. It did VMS format by default but
seem to remember he added RT11 and RSX support to it also. Since we had
to write tapes to export to those systems also.
Sadly, I used to have a directory of "magtape utilities" but I no longer
have it online. I'll try to poke around to see if I can find it next
weekend if no one else shouts out sooner.
BRU tapes are proper ANSI format tapes, so as far as that goes, the whole saveset as such can certainly be accessed with any tool that deals with ANSI tapes.
However, BRU savesets is another level, below this. To extract files from those savesets will require other software. I don't think any exists for Unix, but you can certainly write it.
Johnny
Clem
On Mon, Mar 16, 2015 at 1:05 AM, Cory Smelosky <b4 at gewt.net
<mailto:b4 at gewt.net>> wrote:
All,
Is it possible to extract files from a BRU RSX tape on UNIX, or is
the best path BRUREAD to VMS, and then zip/tar?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
The format is defined in: http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rsx/dec…
and yes UNIX has tools that grok it.
Worst case it any ANSI tape reader will get the raw data off as files with strange names and you may need a shell script to put some of the files back together after decoding the directory.
My old housemate (and SPICE2/3 author) Tom Quarles wrote an really good ANSI tape reader for Unix years ago. It did VMS format by default but seem to remember he added RT11 and RSX support to it also. Since we had to write tapes to export to those systems also.
Sadly, I used to have a directory of "magtape utilities" but I no longer have it online. I'll try to poke around to see if I can find it next weekend if no one else shouts out sooner.
Clem
On Mon, Mar 16, 2015 at 1:05 AM, Cory Smelosky <b4 at gewt.net> wrote:
All,
Is it possible to extract files from a BRU RSX tape on UNIX, or is the best path BRUREAD to VMS, and then zip/tar?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2015-03-16 06:05, Cory Smelosky wrote:
All,
Is it possible to extract files from a BRU RSX tape on UNIX, or is the
best path BRUREAD to VMS, and then zip/tar?
Certainly possible, but you might need to write the software first.
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
All,
Is it possible to extract files from a BRU RSX tape on UNIX, or is the best path BRUREAD to VMS, and then zip/tar?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Thanks, all up again now.
Regards
Rob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: 15 March 2015 13:34
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Johnny Please Update IP for Area 5
On 2015-03-15 10:45, Robert Jarratt wrote:
I think my IP has changed, can you restart the bridge on your side please?
Done, and yeah, seemd you had.
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 2015-03-15 10:45, Robert Jarratt wrote:
I think my IP has changed, can you restart the bridge on your side please?
Done, and yeah, seemd you had.
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
Unfortunately I am traveling and not able to make that work from here...
-Steve
On Mar 12, 2015, at 19:05, Cory Smelosky <b4 at gewt.net> wrote:
On Thu, 12 Mar 2015, Steve Davidson wrote:
Or... A telnet session to an emulator. Just need the address.
-Steve
How about disk images and a config?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 12 Mar 2015, Steve Davidson wrote:
Or... A telnet session to an emulator. Just need the address.
-Steve
How about disk images and a config?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Or... A telnet session to an emulator. Just need the address.
-Steve
On Mar 12, 2015, at 18:29, Steve Davidson <steve at davidson.net> wrote:
Help libr.
-Steve
Sent from my iPhone
On Mar 12, 2015, at 18:14, Cory Smelosky <b4 at gewt.net> wrote:
Have a librarian manual handy? I'm not too good at RT-11.
Sent from my iPhone
On Mar 12, 2015, at 21:01, Steve Davidson <steve at davidson.net> wrote:
Use the librarian to list the symbol table entries of the objs to see which ones define the symbol. Send me those names.
-Steve
Sent from my iPhone
On Mar 12, 2015, at 17:41, Cory Smelosky <b4 at gewt.net> wrote:
All,
Finally found a (maybe) working TSX+ distrib...however...
. at ld0:maktsx
.COPY IN:(TSXLNK.COM,TSGEN.MAC,TSX1.OBJ) DK:
Files copied:
IN:TSXLNK.COM to DK:TSXLNK.COM
IN:TSGEN.MAC to DK:TSGEN.MAC
IN:TSX1.OBJ to DK:TSX1.OBJ
.COPY IN:(TSTTY,TSEM2,TSEM3,TSPLAS,TSUSR).OBJ DK:
Files copied:
IN:TSTTY.OBJ to DK:TSTTY.OBJ
IN:TSEM2.OBJ to DK:TSEM2.OBJ
IN:TSEM3.OBJ to DK:TSEM3.OBJ
IN:TSPLAS.OBJ to DK:TSPLAS.OBJ
IN:TSUSR.OBJ to DK:TSUSR.OBJ
.COPY IN:(BLDTSX,BL2TSX).COM DK:
Files copied:
IN:BLDTSX.COM to DK:BLDTSX.COMIN:BL2TSX.COM to DK:BL2TSX.COM
.COPY/WAIT IN:(TSSPOL,TSLOCK,TSMSG).OBJ DK:
Mount input volume in LD0:; Continue? Y
Files copied:
Mount output volume in DU1:; Continue? Y
IN:TSSPOL.OBJ to DK:TSSPOL.OBJ
IN:TSLOCK.OBJ to DK:TSLOCK.OBJ
IN:TSMSG.OBJ to DK:TSMSG.OBJ
.COPY IN:(TSRTX,TSMIO,TSSLE,TSCLO).OBJ DK:
Files copied:
IN:TSRTX.OBJ to DK:TSRTX.OBJ
IN:TSMIO.OBJ to DK:TSMIO.OBJ
IN:TSSLE.OBJ to DK:TSSLE.OBJ
IN:TSCLO.OBJ to DK:TSCLO.OBJ
.COPY IN:(TSDBUG,TSEXC2,TSX2,TSKM2A,TSKM2B).OBJ DK:
Files copied:
IN:TSDBUG.OBJ to DK:TSDBUG.OBJ
IN:TSEXC2.OBJ to DK:TSEXC2.OBJ
IN:TSX2.OBJ to DK:TSX2.OBJ
IN:TSKM2A.OBJ to DK:TSKM2A.OBJ
IN:TSKM2B.OBJ to DK:TSKM2B.OBJ
.COPY IN:(CCL,TSXUCL,FILTIM).SAV SY:
Files copied:
IN:CCL.SAV to SY:CCL.SAV
IN:TSXUCL.SAV to SY:TSXUCL.SAV
IN:FILTIM.SAV to SY:FILTIM.SAV
.COPY IN:(DL,DM,DU,RK).TSX SY:
Files copied:
IN:DL.TSX to SY:DL.TSX
IN:DM.TSX to SY:DM.TSX
IN:DU.TSX to SY:DU.TSX
IN:RK.TSX to SY:RK.TSX
.COPY IN:(DX,DY,NL,LP).TSX SY:
Files copied:
IN:DX.TSX to SY:DX.TSX
IN:DY.TSX to SY:DY.TSX
IN:NL.TSX to SY:NL.TSX
IN:LP.TSX to SY:LP.TSX
.COPY IN:(SETSIZ.SAV,SETSIZ.COM) SY:
Files copied:
IN:SETSIZ.SAV to SY:SETSIZ.SAV
IN:SETSIZ.COM to SY:SETSIZ.COM
. at BLDTSX.COM
.MACRO TSGEN
. at BL2TSX
.R LINK
*TSX[220],TSX[90]/A/W,TSX[60]=TSGEN,TSX1/Q//
*TSTTY/O:1
*TSEM2/O:1
*TSEM3/O:1
*TSPLAS/O:1
*TSUSR/O:1
*TSSPOL/O:1
*TSLOCK/O:1
*TSMSG/O:1
*TSRTX/O:1
*TSMIO/O:1
*TSSLE/O:1
*TSCLO/O:1
*TSDBUG/O:1
*TSEXC2/O:1//
Load section:address? TSXEND:120000
Load section:address?
*TSKMON[120]=TSX2,TSX.STB/Y:40000/C
*TSKM2A/O:1/C
*TSKM2B/O:1
Boundary section? $OTABL
?LINK-W-Multiple definition of $OVRH
*^C
.COPY DK:(TSX,TSKMON).SAV SY:
Files copied:
DK:TSX.SAV to SY:TSX.SAV
DK:TSKMON.SAV to SY:TSKMON.SAV
.R TSX
?TSX-F-Fatal system error at 122664
KRE-KMON read error
Arg. value = 000000
HALT instruction, PC: 133064 (MOV R1,-(SP))
sim> examine 122664
122664: 003664
Any ideas? I followd the (sparse) 5.x manual.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Help libr.
-Steve
Sent from my iPhone
On Mar 12, 2015, at 18:14, Cory Smelosky <b4 at gewt.net> wrote:
Have a librarian manual handy? I'm not too good at RT-11.
Sent from my iPhone
On Mar 12, 2015, at 21:01, Steve Davidson <steve at davidson.net> wrote:
Use the librarian to list the symbol table entries of the objs to see which ones define the symbol. Send me those names.
-Steve
Sent from my iPhone
On Mar 12, 2015, at 17:41, Cory Smelosky <b4 at gewt.net> wrote:
All,
Finally found a (maybe) working TSX+ distrib...however...
. at ld0:maktsx
.COPY IN:(TSXLNK.COM,TSGEN.MAC,TSX1.OBJ) DK:
Files copied:
IN:TSXLNK.COM to DK:TSXLNK.COM
IN:TSGEN.MAC to DK:TSGEN.MAC
IN:TSX1.OBJ to DK:TSX1.OBJ
.COPY IN:(TSTTY,TSEM2,TSEM3,TSPLAS,TSUSR).OBJ DK:
Files copied:
IN:TSTTY.OBJ to DK:TSTTY.OBJ
IN:TSEM2.OBJ to DK:TSEM2.OBJ
IN:TSEM3.OBJ to DK:TSEM3.OBJ
IN:TSPLAS.OBJ to DK:TSPLAS.OBJ
IN:TSUSR.OBJ to DK:TSUSR.OBJ
.COPY IN:(BLDTSX,BL2TSX).COM DK:
Files copied:
IN:BLDTSX.COM to DK:BLDTSX.COMIN:BL2TSX.COM to DK:BL2TSX.COM
.COPY/WAIT IN:(TSSPOL,TSLOCK,TSMSG).OBJ DK:
Mount input volume in LD0:; Continue? Y
Files copied:
Mount output volume in DU1:; Continue? Y
IN:TSSPOL.OBJ to DK:TSSPOL.OBJ
IN:TSLOCK.OBJ to DK:TSLOCK.OBJ
IN:TSMSG.OBJ to DK:TSMSG.OBJ
.COPY IN:(TSRTX,TSMIO,TSSLE,TSCLO).OBJ DK:
Files copied:
IN:TSRTX.OBJ to DK:TSRTX.OBJ
IN:TSMIO.OBJ to DK:TSMIO.OBJ
IN:TSSLE.OBJ to DK:TSSLE.OBJ
IN:TSCLO.OBJ to DK:TSCLO.OBJ
.COPY IN:(TSDBUG,TSEXC2,TSX2,TSKM2A,TSKM2B).OBJ DK:
Files copied:
IN:TSDBUG.OBJ to DK:TSDBUG.OBJ
IN:TSEXC2.OBJ to DK:TSEXC2.OBJ
IN:TSX2.OBJ to DK:TSX2.OBJ
IN:TSKM2A.OBJ to DK:TSKM2A.OBJ
IN:TSKM2B.OBJ to DK:TSKM2B.OBJ
.COPY IN:(CCL,TSXUCL,FILTIM).SAV SY:
Files copied:
IN:CCL.SAV to SY:CCL.SAV
IN:TSXUCL.SAV to SY:TSXUCL.SAV
IN:FILTIM.SAV to SY:FILTIM.SAV
.COPY IN:(DL,DM,DU,RK).TSX SY:
Files copied:
IN:DL.TSX to SY:DL.TSX
IN:DM.TSX to SY:DM.TSX
IN:DU.TSX to SY:DU.TSX
IN:RK.TSX to SY:RK.TSX
.COPY IN:(DX,DY,NL,LP).TSX SY:
Files copied:
IN:DX.TSX to SY:DX.TSX
IN:DY.TSX to SY:DY.TSX
IN:NL.TSX to SY:NL.TSX
IN:LP.TSX to SY:LP.TSX
.COPY IN:(SETSIZ.SAV,SETSIZ.COM) SY:
Files copied:
IN:SETSIZ.SAV to SY:SETSIZ.SAV
IN:SETSIZ.COM to SY:SETSIZ.COM
. at BLDTSX.COM
.MACRO TSGEN
. at BL2TSX
.R LINK
*TSX[220],TSX[90]/A/W,TSX[60]=TSGEN,TSX1/Q//
*TSTTY/O:1
*TSEM2/O:1
*TSEM3/O:1
*TSPLAS/O:1
*TSUSR/O:1
*TSSPOL/O:1
*TSLOCK/O:1
*TSMSG/O:1
*TSRTX/O:1
*TSMIO/O:1
*TSSLE/O:1
*TSCLO/O:1
*TSDBUG/O:1
*TSEXC2/O:1//
Load section:address? TSXEND:120000
Load section:address?
*TSKMON[120]=TSX2,TSX.STB/Y:40000/C
*TSKM2A/O:1/C
*TSKM2B/O:1
Boundary section? $OTABL
?LINK-W-Multiple definition of $OVRH
*^C
.COPY DK:(TSX,TSKMON).SAV SY:
Files copied:
DK:TSX.SAV to SY:TSX.SAV
DK:TSKMON.SAV to SY:TSKMON.SAV
.R TSX
?TSX-F-Fatal system error at 122664
KRE-KMON read error
Arg. value = 000000
HALT instruction, PC: 133064 (MOV R1,-(SP))
sim> examine 122664
122664: 003664
Any ideas? I followd the (sparse) 5.x manual.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Have a librarian manual handy? I'm not too good at RT-11.
Sent from my iPhone
On Mar 12, 2015, at 21:01, Steve Davidson <steve at davidson.net> wrote:
Use the librarian to list the symbol table entries of the objs to see which ones define the symbol. Send me those names.
-Steve
Sent from my iPhone
On Mar 12, 2015, at 17:41, Cory Smelosky <b4 at gewt.net> wrote:
All,
Finally found a (maybe) working TSX+ distrib...however...
. at ld0:maktsx
.COPY IN:(TSXLNK.COM,TSGEN.MAC,TSX1.OBJ) DK:
Files copied:
IN:TSXLNK.COM to DK:TSXLNK.COM
IN:TSGEN.MAC to DK:TSGEN.MAC
IN:TSX1.OBJ to DK:TSX1.OBJ
.COPY IN:(TSTTY,TSEM2,TSEM3,TSPLAS,TSUSR).OBJ DK:
Files copied:
IN:TSTTY.OBJ to DK:TSTTY.OBJ
IN:TSEM2.OBJ to DK:TSEM2.OBJ
IN:TSEM3.OBJ to DK:TSEM3.OBJ
IN:TSPLAS.OBJ to DK:TSPLAS.OBJ
IN:TSUSR.OBJ to DK:TSUSR.OBJ
.COPY IN:(BLDTSX,BL2TSX).COM DK:
Files copied:
IN:BLDTSX.COM to DK:BLDTSX.COMIN:BL2TSX.COM to DK:BL2TSX.COM
.COPY/WAIT IN:(TSSPOL,TSLOCK,TSMSG).OBJ DK:
Mount input volume in LD0:; Continue? Y
Files copied:
Mount output volume in DU1:; Continue? Y
IN:TSSPOL.OBJ to DK:TSSPOL.OBJ
IN:TSLOCK.OBJ to DK:TSLOCK.OBJ
IN:TSMSG.OBJ to DK:TSMSG.OBJ
.COPY IN:(TSRTX,TSMIO,TSSLE,TSCLO).OBJ DK:
Files copied:
IN:TSRTX.OBJ to DK:TSRTX.OBJ
IN:TSMIO.OBJ to DK:TSMIO.OBJ
IN:TSSLE.OBJ to DK:TSSLE.OBJ
IN:TSCLO.OBJ to DK:TSCLO.OBJ
.COPY IN:(TSDBUG,TSEXC2,TSX2,TSKM2A,TSKM2B).OBJ DK:
Files copied:
IN:TSDBUG.OBJ to DK:TSDBUG.OBJ
IN:TSEXC2.OBJ to DK:TSEXC2.OBJ
IN:TSX2.OBJ to DK:TSX2.OBJ
IN:TSKM2A.OBJ to DK:TSKM2A.OBJ
IN:TSKM2B.OBJ to DK:TSKM2B.OBJ
.COPY IN:(CCL,TSXUCL,FILTIM).SAV SY:
Files copied:
IN:CCL.SAV to SY:CCL.SAV
IN:TSXUCL.SAV to SY:TSXUCL.SAV
IN:FILTIM.SAV to SY:FILTIM.SAV
.COPY IN:(DL,DM,DU,RK).TSX SY:
Files copied:
IN:DL.TSX to SY:DL.TSX
IN:DM.TSX to SY:DM.TSX
IN:DU.TSX to SY:DU.TSX
IN:RK.TSX to SY:RK.TSX
.COPY IN:(DX,DY,NL,LP).TSX SY:
Files copied:
IN:DX.TSX to SY:DX.TSX
IN:DY.TSX to SY:DY.TSX
IN:NL.TSX to SY:NL.TSX
IN:LP.TSX to SY:LP.TSX
.COPY IN:(SETSIZ.SAV,SETSIZ.COM) SY:
Files copied:
IN:SETSIZ.SAV to SY:SETSIZ.SAV
IN:SETSIZ.COM to SY:SETSIZ.COM
. at BLDTSX.COM
.MACRO TSGEN
. at BL2TSX
.R LINK
*TSX[220],TSX[90]/A/W,TSX[60]=TSGEN,TSX1/Q//
*TSTTY/O:1
*TSEM2/O:1
*TSEM3/O:1
*TSPLAS/O:1
*TSUSR/O:1
*TSSPOL/O:1
*TSLOCK/O:1
*TSMSG/O:1
*TSRTX/O:1
*TSMIO/O:1
*TSSLE/O:1
*TSCLO/O:1
*TSDBUG/O:1
*TSEXC2/O:1//
Load section:address? TSXEND:120000
Load section:address?
*TSKMON[120]=TSX2,TSX.STB/Y:40000/C
*TSKM2A/O:1/C
*TSKM2B/O:1
Boundary section? $OTABL
?LINK-W-Multiple definition of $OVRH
*^C
.COPY DK:(TSX,TSKMON).SAV SY:
Files copied:
DK:TSX.SAV to SY:TSX.SAV
DK:TSKMON.SAV to SY:TSKMON.SAV
.R TSX
?TSX-F-Fatal system error at 122664
KRE-KMON read error
Arg. value = 000000
HALT instruction, PC: 133064 (MOV R1,-(SP))
sim> examine 122664
122664: 003664
Any ideas? I followd the (sparse) 5.x manual.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Use the librarian to list the symbol table entries of the objs to see which ones define the symbol. Send me those names.
-Steve
Sent from my iPhone
On Mar 12, 2015, at 17:41, Cory Smelosky <b4 at gewt.net> wrote:
All,
Finally found a (maybe) working TSX+ distrib...however...
. at ld0:maktsx
.COPY IN:(TSXLNK.COM,TSGEN.MAC,TSX1.OBJ) DK:
Files copied:
IN:TSXLNK.COM to DK:TSXLNK.COM
IN:TSGEN.MAC to DK:TSGEN.MAC
IN:TSX1.OBJ to DK:TSX1.OBJ
.COPY IN:(TSTTY,TSEM2,TSEM3,TSPLAS,TSUSR).OBJ DK:
Files copied:
IN:TSTTY.OBJ to DK:TSTTY.OBJ
IN:TSEM2.OBJ to DK:TSEM2.OBJ
IN:TSEM3.OBJ to DK:TSEM3.OBJ
IN:TSPLAS.OBJ to DK:TSPLAS.OBJ
IN:TSUSR.OBJ to DK:TSUSR.OBJ
.COPY IN:(BLDTSX,BL2TSX).COM DK:
Files copied:
IN:BLDTSX.COM to DK:BLDTSX.COMIN:BL2TSX.COM to DK:BL2TSX.COM
.COPY/WAIT IN:(TSSPOL,TSLOCK,TSMSG).OBJ DK:
Mount input volume in LD0:; Continue? Y
Files copied:
Mount output volume in DU1:; Continue? Y
IN:TSSPOL.OBJ to DK:TSSPOL.OBJ
IN:TSLOCK.OBJ to DK:TSLOCK.OBJ
IN:TSMSG.OBJ to DK:TSMSG.OBJ
.COPY IN:(TSRTX,TSMIO,TSSLE,TSCLO).OBJ DK:
Files copied:
IN:TSRTX.OBJ to DK:TSRTX.OBJ
IN:TSMIO.OBJ to DK:TSMIO.OBJ
IN:TSSLE.OBJ to DK:TSSLE.OBJ
IN:TSCLO.OBJ to DK:TSCLO.OBJ
.COPY IN:(TSDBUG,TSEXC2,TSX2,TSKM2A,TSKM2B).OBJ DK:
Files copied:
IN:TSDBUG.OBJ to DK:TSDBUG.OBJ
IN:TSEXC2.OBJ to DK:TSEXC2.OBJ
IN:TSX2.OBJ to DK:TSX2.OBJ
IN:TSKM2A.OBJ to DK:TSKM2A.OBJ
IN:TSKM2B.OBJ to DK:TSKM2B.OBJ
.COPY IN:(CCL,TSXUCL,FILTIM).SAV SY:
Files copied:
IN:CCL.SAV to SY:CCL.SAV
IN:TSXUCL.SAV to SY:TSXUCL.SAV
IN:FILTIM.SAV to SY:FILTIM.SAV
.COPY IN:(DL,DM,DU,RK).TSX SY:
Files copied:
IN:DL.TSX to SY:DL.TSX
IN:DM.TSX to SY:DM.TSX
IN:DU.TSX to SY:DU.TSX
IN:RK.TSX to SY:RK.TSX
.COPY IN:(DX,DY,NL,LP).TSX SY:
Files copied:
IN:DX.TSX to SY:DX.TSX
IN:DY.TSX to SY:DY.TSX
IN:NL.TSX to SY:NL.TSX
IN:LP.TSX to SY:LP.TSX
.COPY IN:(SETSIZ.SAV,SETSIZ.COM) SY:
Files copied:
IN:SETSIZ.SAV to SY:SETSIZ.SAV
IN:SETSIZ.COM to SY:SETSIZ.COM
. at BLDTSX.COM
.MACRO TSGEN
. at BL2TSX
.R LINK
*TSX[220],TSX[90]/A/W,TSX[60]=TSGEN,TSX1/Q//
*TSTTY/O:1
*TSEM2/O:1
*TSEM3/O:1
*TSPLAS/O:1
*TSUSR/O:1
*TSSPOL/O:1
*TSLOCK/O:1
*TSMSG/O:1
*TSRTX/O:1
*TSMIO/O:1
*TSSLE/O:1
*TSCLO/O:1
*TSDBUG/O:1
*TSEXC2/O:1//
Load section:address? TSXEND:120000
Load section:address?
*TSKMON[120]=TSX2,TSX.STB/Y:40000/C
*TSKM2A/O:1/C
*TSKM2B/O:1
Boundary section? $OTABL
?LINK-W-Multiple definition of $OVRH
*^C
.COPY DK:(TSX,TSKMON).SAV SY:
Files copied:
DK:TSX.SAV to SY:TSX.SAV
DK:TSKMON.SAV to SY:TSKMON.SAV
.R TSX
?TSX-F-Fatal system error at 122664
KRE-KMON read error
Arg. value = 000000
HALT instruction, PC: 133064 (MOV R1,-(SP))
sim> examine 122664
122664: 003664
Any ideas? I followd the (sparse) 5.x manual.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
All,
Finally found a (maybe) working TSX+ distrib...however...
. at ld0:maktsx
.COPY IN:(TSXLNK.COM,TSGEN.MAC,TSX1.OBJ) DK:
Files copied:
IN:TSXLNK.COM to DK:TSXLNK.COM
IN:TSGEN.MAC to DK:TSGEN.MAC
IN:TSX1.OBJ to DK:TSX1.OBJ
.COPY IN:(TSTTY,TSEM2,TSEM3,TSPLAS,TSUSR).OBJ DK:
Files copied:
IN:TSTTY.OBJ to DK:TSTTY.OBJ
IN:TSEM2.OBJ to DK:TSEM2.OBJ
IN:TSEM3.OBJ to DK:TSEM3.OBJ
IN:TSPLAS.OBJ to DK:TSPLAS.OBJ
IN:TSUSR.OBJ to DK:TSUSR.OBJ
.COPY IN:(BLDTSX,BL2TSX).COM DK:
Files copied:
IN:BLDTSX.COM to DK:BLDTSX.COMIN:BL2TSX.COM to DK:BL2TSX.COM
.COPY/WAIT IN:(TSSPOL,TSLOCK,TSMSG).OBJ DK:
Mount input volume in LD0:; Continue? Y
Files copied:
Mount output volume in DU1:; Continue? Y
IN:TSSPOL.OBJ to DK:TSSPOL.OBJ
IN:TSLOCK.OBJ to DK:TSLOCK.OBJ
IN:TSMSG.OBJ to DK:TSMSG.OBJ
.COPY IN:(TSRTX,TSMIO,TSSLE,TSCLO).OBJ DK:
Files copied:
IN:TSRTX.OBJ to DK:TSRTX.OBJ
IN:TSMIO.OBJ to DK:TSMIO.OBJ
IN:TSSLE.OBJ to DK:TSSLE.OBJ
IN:TSCLO.OBJ to DK:TSCLO.OBJ
.COPY IN:(TSDBUG,TSEXC2,TSX2,TSKM2A,TSKM2B).OBJ DK:
Files copied:
IN:TSDBUG.OBJ to DK:TSDBUG.OBJ
IN:TSEXC2.OBJ to DK:TSEXC2.OBJ
IN:TSX2.OBJ to DK:TSX2.OBJ
IN:TSKM2A.OBJ to DK:TSKM2A.OBJ
IN:TSKM2B.OBJ to DK:TSKM2B.OBJ
.COPY IN:(CCL,TSXUCL,FILTIM).SAV SY:
Files copied:
IN:CCL.SAV to SY:CCL.SAV
IN:TSXUCL.SAV to SY:TSXUCL.SAV
IN:FILTIM.SAV to SY:FILTIM.SAV
.COPY IN:(DL,DM,DU,RK).TSX SY:
Files copied:
IN:DL.TSX to SY:DL.TSX
IN:DM.TSX to SY:DM.TSX
IN:DU.TSX to SY:DU.TSX
IN:RK.TSX to SY:RK.TSX
.COPY IN:(DX,DY,NL,LP).TSX SY:
Files copied:
IN:DX.TSX to SY:DX.TSX
IN:DY.TSX to SY:DY.TSX
IN:NL.TSX to SY:NL.TSX
IN:LP.TSX to SY:LP.TSX
.COPY IN:(SETSIZ.SAV,SETSIZ.COM) SY:
Files copied:
IN:SETSIZ.SAV to SY:SETSIZ.SAV
IN:SETSIZ.COM to SY:SETSIZ.COM
. at BLDTSX.COM
.MACRO TSGEN
. at BL2TSX
.R LINK
*TSX[220],TSX[90]/A/W,TSX[60]=TSGEN,TSX1/Q//
*TSTTY/O:1
*TSEM2/O:1
*TSEM3/O:1
*TSPLAS/O:1
*TSUSR/O:1
*TSSPOL/O:1
*TSLOCK/O:1
*TSMSG/O:1
*TSRTX/O:1
*TSMIO/O:1
*TSSLE/O:1
*TSCLO/O:1
*TSDBUG/O:1
*TSEXC2/O:1//
Load section:address? TSXEND:120000
Load section:address?
*TSKMON[120]=TSX2,TSX.STB/Y:40000/C
*TSKM2A/O:1/C
*TSKM2B/O:1
Boundary section? $OTABL
?LINK-W-Multiple definition of $OVRH
*^C
.COPY DK:(TSX,TSKMON).SAV SY:
Files copied:
DK:TSX.SAV to SY:TSX.SAV
DK:TSKMON.SAV to SY:TSKMON.SAV
.R TSX
?TSX-F-Fatal system error at 122664
KRE-KMON read error
Arg. value = 000000
HALT instruction, PC: 133064 (MOV R1,-(SP))
sim> examine 122664
122664: 003664
Any ideas? I followd the (sparse) 5.x manual.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
And done!
Sorry for the noise everyone!
Reason for change: Modified Tunnel52: Cory Smelosky (Area 9)
"dynamic_ip" changed from "true" to false"
-brian
On Mar 11, 2015, at 10:30 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Wed, 11 Mar 2015, Brian Hechinger wrote:
Or perhaps not. DNS was saying 139 but it had 132 in the db. I ve manually set it to 139 in the db. If that doesn t settle it down I ll mark you as static.
That'd explain things. ;)
Good thing it's a 2851 that can take it!
Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 15.1(4)M8, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 07-Mar-14 08:19 by prod_rel_team
Cisco 2851 (revision 1.0) with 473088K/51200K bytes of memory.
Processor board ID FHK1050F1JN
4 FastEthernet interfaces
2 Gigabit Ethernet interfaces
1 Serial interface
1 ATM interface
1 terminal line
1 Virtual Private Network (VPN) Module
DRAM configuration is 64 bits wide with parity enabled.
239K bytes of non-volatile configuration memory.
125440K bytes of ATA CompactFlash (Read/Write)
Description: LAN :: Link to switch
Internet address is 10.10.0.1/16
MTU 9000 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full Duplex, 1Gbps, media type is T
output flow-control is XON, input flow-control is XON
Waiting for the gig of RAM to arrive!
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
