{"id":1280,"date":"2017-08-07T21:57:13","date_gmt":"2017-08-07T19:57:13","guid":{"rendered":"http:\/\/www.pdp-11.de\/?page_id=1280"},"modified":"2024-06-02T16:23:37","modified_gmt":"2024-06-02T14:23:37","slug":"tsv05ts11-rt-11-and-create-magtape-distribution-set","status":"publish","type":"page","link":"https:\/\/www.pdp-11.de\/index.php\/dec-devices\/tsv05ts11-rt-11-and-create-magtape-distribution-set\/","title":{"rendered":"TSV05 \/ Pertec"},"content":{"rendered":"

TSV05_Maint.pdf<\/a>\u00a0 TSV05_User.pdf<\/a><\/p>\n

After I have managed to get RT-11 installed, the time is come, to look at my new Dilog DU-142 Pertec (TS11 compatible) controller, and the DEC TS05 (Cipher F880)\u00a0 9-Track Tape drive.<\/p>\n

Don’t spend too much time to find the mostly missing Pertec Cables, build them by you own (but do it right!<\/em>)! It’s quite easy, when you have the 50 Pin Edge connector. (google is your friend)<\/p>\n

As I like the old style, I have bought an original Spectra-Strip Cable NOS from 1979. And it fits quite good. A shielded cable would be better I think, but they are so much expensive, that I was not willing to pay for them.<\/p>\n

\"\"<\/a> \"\"<\/a>\"\"<\/a>\"\"<\/a>\"\"<\/a>\"\"<\/a><\/p>\n

show dev shows, that rt11 has recognized the Dilog without reconfiguring anything -strange I was a bit prepared for my first sysgen session.<\/p>\n

.show de:ms\n\nDevice Status CSR Vector(s)\n------ ------ --- ---------\n MS Installed 172522 224 300<\/pre>\n
After this, I have started a short test, to see, if my drive reacts on any OS command.<\/p>\n
.init\/bad ms0:\nMS0:\/Initialize; Are you sure? Y\n.<\/pre>\n
As soon as I have pressed „Y“ the drive began to turn. Good sign.<\/p>\n
Now I was interested to create RT-11 Distribution Tapes, which looks like is quite simple, here is the procedure out of the DOC<\/a> (side 5-8):<\/p>\n
.assign ms0: KIT:\n\n.assign du0: BIN:\n\n.@msb\n\n.$Load Bin,Kit\n\n.$Ini\/Que\/Vol\/File:Bin:MBOT16.BOT Kit:\nMS0:\/Initialize; Are you sure? Y\nVolume ID? RT5.4G\nOwner? DIS MS 1\/2\n\n.$Cop Bin:MSBOOT.BOT Kit:\/Pos:-1\n Files copied:\nBIN:MSBOOT.BOT to KIT:MSBOOT.BOT\n\n.$Cop Bin:MDUP.AI Kit:\/Pos:-1\n Files copied:\nBIN:MDUP.AI to KIT:MDUP.AI\n........\n........\n........\n.$Cop Bin:MSCPCK.SAV Kit:\/Pos:-1\n Files copied:\nBIN:MSCPCK.SAV to KIT:MSCPCK.SAV\n\n.^C\n\n.$Ini\/Que\/Vol\/File:Bin: Kit:\nMS0:\/Initialize; Are you sure? Y\nVolume ID? RT5.4G\nOwner? DIS MS 2\/2\n\n.$Cop Bin:TRANSF.TSK Kit:\/Pos:-1\n Files copied:\nBIN:TRANSF.TSK to KIT:TRANSF.TSK\n\n.$Cop Bin:TRANSF.EXE Kit:\/Pos:-1\n Files copied:\nBIN:TRANSF.EXE to KIT:TRANSF.EXE\n......\n......\n......\n.$Cop Bin:INDEX.IMG Kit:\/Pos:-1\n Files copied:\nBIN:INDEX.IMG to KIT:INDEX.IMG\n\n.$Cop Bin:INDEX.IDX Kit:\/Pos:-1\n Files copied:\nBIN:INDEX.IDX to KIT:INDEX.IDX\n\n.^C\n\n.$Unload Bin,Kit<\/pre>\n
\n
And now the trouble began.<\/strong><\/p>\n
To boot from TS11\/TS05\/TU80 you need to type or toggle in the Bootstrap or you are in a lucky situation where you have the matching BPROM for an M9312.<\/p>\n
I’m in a not so bad position, as my PDP-11\/84 has the possibility, to add own BootStraps to the EEprom which can be added via the setup menu.<\/p>\n
So this was the first time, I have added an „own“ BootStrap and I have needed about 7 tries until I had it once correct typed in. But nothing happens, except the following message, which came instantly up.<\/p>\n
Type a command then press the RETURN key: B MS0\nTrying MS0\n001120<\/pre>\n
I had no clue what this means, except, that this was not the outcome I was expecting!<\/p>\n
After some more verification, like jumper settings, read write to tape, and so on I have decided to post it to cctalk, to find someone with detailed knowledge about.<\/p>\n
http:\/\/www.classiccmp.org\/pipermail\/cctalk\/2017-August\/037014.html<\/a><\/p>\n
Short after I have posted the bootstrap out of the Dilog Manual and the error I had, the first two replays with useful tips, explanations, and a deep understanding about these magic Assembler\/MACRO stuff came in.<\/p>\n
Jerry and Paul, were more than helpful, both have analysed the problem remotely, and found an issue in the printed Bootstrap of the Dilog Controller, which I would never had found.<\/p>\n
In short words, it looks like the printed Bootstrap was after never tested > nice work! I through such pitfalls are a sign of today’s docs, but OK, I have learned, that this seams to be not the case.<\/p>\n
Here are the addresses and values, who needs to be changed, to fix the Bootstrap loader of the Dilog DU142:<\/strong><\/p>\n
001020\/001064\n001030\/001104\n001040\/001104\n001050\/100421<\/pre>\n
Here is the complete Bootstrap, like it is now saved to the PDP-11\/84 EEPROM:<\/strong><\/p>\n
Device name = MS New =\nBeginning address = 001000 New =\nLast byte address = 001400 New =\nStart address = 001000 New =\nHighest Unit number = 1 New =\nDevice Description = TSV05 New =\nEnter ROM ODT\n\nxxxxxx\/ = open word location xxxxxx if address even, byte if odd\nRETURN = close location\n. or LF = close location and open next\n- = close location and open previous\n\nROM ODT> 001000\/012700\nROM ODT> 001002\/172520\nROM ODT> 001004\/012701\nROM ODT> 001006\/172522\nROM ODT> 001010\/005011\nROM ODT> 001012\/105711\nROM ODT> 001014\/100376\nROM ODT> 001016\/012710\nROM ODT> 001020\/001064\nROM ODT> 001022\/105711\nROM ODT> 001024\/100376\nROM ODT> 001026\/012710\nROM ODT> 001030\/001104\nROM ODT> 001032\/105711\nROM ODT> 001034\/100376\nROM ODT> 001036\/012710\nROM ODT> 001040\/001104\nROM ODT> 001042\/105711\nROM ODT> 001044\/100376\nROM ODT> 001046\/005711\nROM ODT> 001050\/100421\nROM ODT> 001052\/012704\nROM ODT> 001054\/001102\nROM ODT> 001056\/005000\nROM ODT> 001060\/005007\nROM ODT> 001062\/046523\nROM ODT> 001064\/140004\nROM ODT> 001066\/001074\nROM ODT> 001070\/000000\nROM ODT> 001072\/000010\nROM ODT> 001074\/001116\nROM ODT> 001076\/000000\nROM ODT> 001100\/000016\nROM ODT> 001102\/000000\nROM ODT> 001104\/140001\nROM ODT> 001106\/000000\nROM ODT> 001110\/000000\nROM ODT> 001112\/001000\nROM ODT> 001114\/000000\nROM ODT> 001116\/000000<\/pre>\n
So now all could be good, if I had not build the cable by my own …<\/em><\/strong><\/p>\n
With this changes it should be possible, to boot the RT-11 Tape, but I get the following error.<\/p>\n
Type a command then press the RETURN key: B MS0\nTrying MS0\n001116\n@<\/pre>\n
Paul and Jerry have debugged this remotely, and I have provided what was requested. Both were able to map this issue to a read Parity error.<\/p>\n
Here the procedure:<\/strong><\/p>\n
Examine TSSR: @17772522\/100210\n\nExamine 1116 +7:\n\n@001116\/100022
@001120\/000012
@001122\/000000
@001124\/000310
@001126\/000001
@001130\/100000
@001132\/000000
@001134\/000000<\/pre>\n
Extended Status 0 at 001124 seams to be OK, as 000310 can be mapped to: motion, on-line, phase-encoded drive<\/p>\n
Extended Status 1 at 001126 seams to be not OK, as 1 means read data Parity error<\/p>\n
The next suggestion was to read from tape (which was working some days before) and surprise I get the following output:<\/p>\n
.dir ms0:\n?DIR-F-Error reading directory\n\nCOPY MS0: NL: \n?PIP-F-Directory input error MS0:<\/pre>\n
So the extended Status 1 makes sense, as reading was no longer possible.<\/p>\n
I have checked again the drive, the coupler, the voltages, … All OK, next Morning I have started to check the cables, and surprise, I found overall three lanes without contact, or with changing state, depending on cable movement.<\/p>\n
The following Lanes were affected:<\/p>\n
Connector P1: 14\nConnector P2: 8, 32<\/pre>\n
The real Issue was maybe P2:8 as in the Doc you will find the following description: Read data bit 7 (LSB!)<\/p>\n
After this was fixed the drive works as expected means read\/write and boot from it works.<\/p>\n
.dir ms0:\n\nMDUP .AI 56 MDUP .MM 56\nMDUP .MS 56 MDUP .MT 56\nMDUP .MU 56 SWAP .SYS 27\nRT11AI.SYS 81 RT11PI.SYS 95\nRT11BL.SYS 78 RT11SJ.SYS 79\nRT11FB.SYS 93 RT11XM.SYS 107\n...\n...\n...\nLDX .SYS 8 LPX .SYS 2\nLSX .SYS 5 MMX .SYS 10\nMSX .SYS 11 MTX .SYS 9\nMUX .SYS 16 NCX .SYS 9\nNLX .SYS 2 NQX .SYS 7\nERROUT.SAV 18 MSCPCK.SAV 3\n 122 Files, 2633 Blocks<\/pre>\n
Message 04 Entering Dialog mode\n\nCommands are Help, Boot, List, Setup, Map and Test.\nType a command then press the RETURN key: B MS0\n\n\n\nTrying MS0MSBOOT V05.04\n\u2592*<\/pre>\n
So again many thanks to Paul and Jerry for their help, time and patience!<\/p>\n","protected":false},"excerpt":{"rendered":"
TSV05_Maint.pdf\u00a0 TSV05_User.pdf After I have managed to get RT-11 installed, the time is come, to look at my new Dilog DU-142 Pertec (TS11 compatible) controller, and the DEC TS05 (Cipher F880)\u00a0 9-Track Tape drive. Don’t spend too much time to find the mostly missing Pertec Cables, build them by you own (but do it right!)! […]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":492,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1280","page","type-page","status-publish","hentry","odd","post-seq-1","post-parity-odd","meta-position-left-outer-pullout","fix"],"_links":{"self":[{"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/pages\/1280","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/comments?post=1280"}],"version-history":[{"count":40,"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/pages\/1280\/revisions"}],"predecessor-version":[{"id":3233,"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/pages\/1280\/revisions\/3233"}],"up":[{"embeddable":true,"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/pages\/492"}],"wp:attachment":[{"href":"https:\/\/www.pdp-11.de\/index.php\/wp-json\/wp\/v2\/media?parent=1280"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}