Re: SOLVED: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Hi All,

It was possible to solve the issue with much help from Jerry and Paul.

1. Bootstrap Loader as printed in the Dilog Documentation is wrong and 
was fixed.


Here is the fixed and running version:

Device name = MS New =
Beginning address = 001000 New =
Last byte address = 001400 New =
Start address = 001000 New =
Highest Unit number = 1 New =
Device Description = TSV05 New =
Enter ROM ODT

xx/ = open word location xx if address even, byte if odd
RETURN = close location
. or LF = close location and open next
- = close location and open previous

ROM ODT> 001000/012700
ROM ODT> 001002/172520
ROM ODT> 001004/012701
ROM ODT> 001006/172522
ROM ODT> 001010/005011
ROM ODT> 001012/105711
ROM ODT> 001014/100376
ROM ODT> 001016/012710
ROM ODT> 001020/001064
ROM ODT> 001022/105711
ROM ODT> 001024/100376
ROM ODT> 001026/012710
ROM ODT> 001030/001104
ROM ODT> 001032/105711
ROM ODT> 001034/100376
ROM ODT> 001036/012710
ROM ODT> 001040/001104
ROM ODT> 001042/105711
ROM ODT> 001044/100376
ROM ODT> 001046/005711
ROM ODT> 001050/100421
ROM ODT> 001052/012704
ROM ODT> 001054/001102
ROM ODT> 001056/005000
ROM ODT> 001060/005007
ROM ODT> 001062/046523
ROM ODT> 001064/140004
ROM ODT> 001066/001074
ROM ODT> 001070/00
ROM ODT> 001072/10
ROM ODT> 001074/001116
ROM ODT> 001076/00
ROM ODT> 001100/16
ROM ODT> 001102/00
ROM ODT> 001104/140001
ROM ODT> 001106/00
ROM ODT> 001110/00
ROM ODT> 001112/001000
ROM ODT> 001114/00
ROM ODT> 001116/00

Boot Process:
Message 04 Entering Dialog mode

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B MS0

Trying MS0MSBOOT V05.04
▒*


2. The issues I had after the Bootstrap was fixed where related to my 
cable, where I had overall three Pins with bad/no contact depending on 
the cable movement.


Outcome:
Type a command then press the RETURN key: B MS0
Trying MS0
001116
@

.dir ms0:
?DIR-F-Error reading directory

COPY MS0: NL:
?PIP-F-Directory input error MS0:


2.1 Debugging via:

Examine 1116 +7:

@001116/100022
@001120/12
@001122/00
@001124/000310
@001126/01
@001130/10
@001132/00
@001134/00
Extended Status 0 at 001124 seams to be OK, as 000310 can be mapped to: motion, 
on-line, phase-encoded drive
Extended Status 1 at 001126 seams to be not OK, as 1 means read data Parity 
error

Related Pin's:
Connector P1: 14
Connector P2: 8, 32


So I'm quite happy to have a running Pertec 1/2" drive.

Again many thanks and Greetings
Ulrich

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

I missed a Line:

@17772522/100210

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Hi Paul,

I have changed the values. Tape turns and I get the following after less 
than a second.


ROM ODT> 001000/012700
ROM ODT> 001002/172520
ROM ODT> 001004/012701
ROM ODT> 001006/172522
ROM ODT> 001010/005011
ROM ODT> 001012/105711
ROM ODT> 001014/100376
ROM ODT> 001016/012710
ROM ODT> 001020/001066  001064
ROM ODT> 001022/105711
ROM ODT> 001024/100376
ROM ODT> 001026/012710
ROM ODT> 001030/001106  001104
ROM ODT> 001032/105711
ROM ODT> 001034/100376
ROM ODT> 001036/012710
ROM ODT> 001040/001106  001104
ROM ODT> 001042/105711
ROM ODT> 001044/100376
ROM ODT> 001046/005711
ROM ODT> 001050/100421
ROM ODT> 001052/012704
ROM ODT> 001054/001102
ROM ODT> 001056/005000
ROM ODT> 001060/005007
ROM ODT> 001062/046523
ROM ODT> 001064/140004
ROM ODT> 001066/001074
ROM ODT> 001070/00
ROM ODT> 001072/10
ROM ODT> 001074/001116
ROM ODT> 001076/00
ROM ODT> 001100/16
ROM ODT> 001102/00
ROM ODT> 001104/140001
ROM ODT> 001106/00
ROM ODT> 001110/00
ROM ODT> 001112/001000
ROM ODT> 001114/00
ROM ODT> 001116/00
ROM ODT> 001120/00
ROM ODT>

KDJ11-B Setup mode
Press the RETURN key for Help
Type a command then press the RETURN key: 14

Save boot into the EEPROM

Are you sure ?  0=No,   1=Yes
Type a command then press the RETURN key: 1

Writing the EEPROM  - Please wait

KDJ11-B Setup mode
Press the RETURN key for Help
Type a command then press the RETURN key: 1
Exit

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B MS0


Trying MS0
001116
@

Many Greetings

Ulrich


Am 10.08.2017 um 19:50 schrieb Paul Koning:


On Aug 10, 2017, at 1:03 PM, Ulrich Tagge > wrote:


Hi Paul,

Yes it's an 11/84 so 22Bit.

I corrected 1050 to 100421 and have now these outcome.

ROM ODT> 001000/012700
ROM ODT> 001002/172520
ROM ODT> 001004/012701
ROM ODT> 001006/172522
ROM ODT> 001010/005011
ROM ODT> 001012/105711
ROM ODT> 001014/100376
ROM ODT> 001016/012710
ROM ODT> 001020/001066
ROM ODT> 001022/105711
ROM ODT> 001024/100376
ROM ODT> 001026/012710
ROM ODT> 001030/001106
ROM ODT> 001032/105711
ROM ODT> 001034/100376
ROM ODT> 001036/012710
ROM ODT> 001040/001106
ROM ODT> 001042/105711
ROM ODT> 001044/100376
ROM ODT> 001046/005711
*ROM ODT> 001050/100421*
ROM ODT> 001052/012704
ROM ODT> 001054/001102
ROM ODT> 001056/005000
ROM ODT> 001060/005007
ROM ODT> 001062/046523
ROM ODT> 001064/140004
ROM ODT> 001066/001074
ROM ODT> 001070/00
ROM ODT> 001072/10
ROM ODT> 001074/001116
ROM ODT> 001076/00
ROM ODT> 001100/16
ROM ODT> 001102/00
ROM ODT> 001104/140001
ROM ODT> 001106/00
ROM ODT> 001110/00
ROM ODT> 001112/001000
ROM ODT> 001114/00
ROM ODT> 001116/00
ROM ODT>

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B MS0


Trying MS0
001116
@17772522/103206


That's better.  The documentation you pointed to says that's "special 
condition" and "termination code 3" which is "function reject", for 
example bad function code.


It turns out that's caused by additional errors in the original 
document.  I suspect they changed the source code on page 3-2 but 
didn't bother running it through the assembler again; instead they 
just changed one line and forgot others.  Amazingly sloppy work.


The issue is that the symbols PKT1 and PKT2 don't match the octal 
values shown in the "assembly" listing.  You need location 1020 to be 
001064, and you need 1030 and 1040 to be 001104.


There is also an error in the source code, where it says "NUM+2" but 
the comment says "NUM+20".  The assembly listing says NUM+20 also, so 
I'll assume that is correct.  It's just a register that's passed to 
the boot block code, I don't know if it cares.


paul

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Paul Koning via cctalk]

> On Aug 10, 2017, at 3:15 PM, Ulrich Tagge  wrote:
> 
> I missed a Line:
> 
> @17772522/100210

According to the manual, that says special condition, and termination code 4.  
Which is "recoverable error".  What that means isn't clear from the register.

It appears you need to look at the extended status in the message buffer 
(starting at 1116 in memory); the layout of the message buffer is on page 4-3, 
and the detailed description of the words in there (it actually calls it 
"message packet") start on page 4-8.  Take a look at that documentation and 
what you have in memory.

paul

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Hi Paul,

Yes it's an 11/84 so 22Bit.

I corrected 1050 to 100421 and have now these outcome.

ROM ODT> 001000/012700
ROM ODT> 001002/172520
ROM ODT> 001004/012701
ROM ODT> 001006/172522
ROM ODT> 001010/005011
ROM ODT> 001012/105711
ROM ODT> 001014/100376
ROM ODT> 001016/012710
ROM ODT> 001020/001066
ROM ODT> 001022/105711
ROM ODT> 001024/100376
ROM ODT> 001026/012710
ROM ODT> 001030/001106
ROM ODT> 001032/105711
ROM ODT> 001034/100376
ROM ODT> 001036/012710
ROM ODT> 001040/001106
ROM ODT> 001042/105711
ROM ODT> 001044/100376
ROM ODT> 001046/005711
*ROM ODT> 001050/100421*
ROM ODT> 001052/012704
ROM ODT> 001054/001102
ROM ODT> 001056/005000
ROM ODT> 001060/005007
ROM ODT> 001062/046523
ROM ODT> 001064/140004
ROM ODT> 001066/001074
ROM ODT> 001070/00
ROM ODT> 001072/10
ROM ODT> 001074/001116
ROM ODT> 001076/00
ROM ODT> 001100/16
ROM ODT> 001102/00
ROM ODT> 001104/140001
ROM ODT> 001106/00
ROM ODT> 001110/00
ROM ODT> 001112/001000
ROM ODT> 001114/00
ROM ODT> 001116/00
ROM ODT>

Commands are Help, Boot, List, Setup, Map and Test.
Type a command then press the RETURN key: B MS0


Trying MS0
001116
@17772522/103206

Many Greetings

Ulrich



Am 10.08.2017 um 18:51 schrieb Paul Koning:

Does the console on your machine do 22 bit addressing?  You may need to ask for 
the CSR by its full 22 bit address, so 17772522.  The number you showed looks 
suspiciously like a powerup selftest memory check pattern.


Please excuse, maybe my understanding is wrong: Does this mean content of 
address 001050 should be 100421 instead of 100422?

Yes, that's what I meant.  Otherwise it branches to the first word of the 
message buffer, and if that's non-zero it wouldn't halt but do something 
different and probably rather strange.

paul

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Hi Jerry,
I have now also checked the content, and it is exactly what I have saved 
to the ROM.


Many Greetings
Ulrich


Am 10.08.2017 um 15:01 schrieb Jerry Weiss:



The first thing I would do is check the contents of 1000-1116 after 
the halt occurs

against the what you have in the eeprom.
Jerry
j...@ieee.org 

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Paul Koning via cctalk]

> On Aug 10, 2017, at 1:03 PM, Ulrich Tagge  wrote:
> 
> Hi Paul,
> 
> Yes it's an 11/84 so 22Bit.
> 
> I corrected 1050 to 100421 and have now these outcome.
> 
> ROM ODT> 001000/012700
> ROM ODT> 001002/172520
> ROM ODT> 001004/012701
> ROM ODT> 001006/172522
> ROM ODT> 001010/005011
> ROM ODT> 001012/105711
> ROM ODT> 001014/100376
> ROM ODT> 001016/012710
> ROM ODT> 001020/001066
> ROM ODT> 001022/105711
> ROM ODT> 001024/100376
> ROM ODT> 001026/012710
> ROM ODT> 001030/001106
> ROM ODT> 001032/105711
> ROM ODT> 001034/100376
> ROM ODT> 001036/012710
> ROM ODT> 001040/001106
> ROM ODT> 001042/105711
> ROM ODT> 001044/100376
> ROM ODT> 001046/005711
> ROM ODT> 001050/100421
> ROM ODT> 001052/012704
> ROM ODT> 001054/001102
> ROM ODT> 001056/005000
> ROM ODT> 001060/005007
> ROM ODT> 001062/046523
> ROM ODT> 001064/140004
> ROM ODT> 001066/001074
> ROM ODT> 001070/00
> ROM ODT> 001072/10
> ROM ODT> 001074/001116
> ROM ODT> 001076/00
> ROM ODT> 001100/16
> ROM ODT> 001102/00
> ROM ODT> 001104/140001
> ROM ODT> 001106/00
> ROM ODT> 001110/00
> ROM ODT> 001112/001000
> ROM ODT> 001114/00
> ROM ODT> 001116/00
> ROM ODT>
> 
> Commands are Help, Boot, List, Setup, Map and Test.
> Type a command then press the RETURN key: B MS0
> 
> 
> Trying MS0
> 001116
> @17772522/103206

That's better.  The documentation you pointed to says that's "special 
condition" and "termination code 3" which is "function reject", for example bad 
function code.

It turns out that's caused by additional errors in the original document.  I 
suspect they changed the source code on page 3-2 but didn't bother running it 
through the assembler again; instead they just changed one line and forgot 
others.  Amazingly sloppy work.

The issue is that the symbols PKT1 and PKT2 don't match the octal values shown 
in the "assembly" listing.  You need location 1020 to be 001064, and you need 
1030 and 1040 to be 001104.

There is also an error in the source code, where it says "NUM+2" but the 
comment says "NUM+20".  The assembly listing says NUM+20 also, so I'll assume 
that is correct.  It's just a register that's passed to the boot block code, I 
don't know if it cares.

paul

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Paul Koning via cctalk]

> On Aug 10, 2017, at 12:24 PM, Ulrich Tagge  wrote:
> 
> 
> 
> Am 10.08.2017 um 17:19 schrieb Paul Koning:
>>> On Aug 9, 2017, at 2:58 PM, Ulrich Tagge via cctalk  
>>> wrote:
>>> 
>>> 
>>> Type a command then press the RETURN key: B MS0
>>> Trying MS0
>>> 001120
>>> @
>> You're getting an I/O error halt.  That case is supposed to go to the HALT 
>> at 1114, which would mean you'd get a PC of 1116 shown in the message.
>> 
>> However... there's a bug in the bootstrap as documented in the manual.  It 
>> shows BMI HALT at 1050, but the machine code is wrong.  The displacement 
>> from the PC is 1114-1052 = 42, so the assembled instruction would be 100421. 
>>  As written, the code is a BMI MES.
>> 
>> You should examine the TS controller CSR at 172522 (TSSR) to see what error 
>> flags are set.
>> 
>>  paul
>> 
>> 
> 
> Hi Paul,
> 
> Many thanks for you Help!
> Here is the content of 172522.
> 
> Trying MS0
> 001120
> @
> @172522/052525

Does the console on your machine do 22 bit addressing?  You may need to ask for 
the CSR by its full 22 bit address, so 17772522.  The number you showed looks 
suspiciously like a powerup selftest memory check pattern.

> Please excuse, maybe my understanding is wrong: Does this mean content of 
> address 001050 should be 100421 instead of 100422?

Yes, that's what I meant.  Otherwise it branches to the first word of the 
message buffer, and if that's non-zero it wouldn't halt but do something 
different and probably rather strange.

paul

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Am 10.08.2017 um 17:19 schrieb Paul Koning:

On Aug 9, 2017, at 2:58 PM, Ulrich Tagge via cctalk  
wrote:


Type a command then press the RETURN key: B MS0
Trying MS0
001120
@

You're getting an I/O error halt.  That case is supposed to go to the HALT at 
1114, which would mean you'd get a PC of 1116 shown in the message.

However... there's a bug in the bootstrap as documented in the manual.  It 
shows BMI HALT at 1050, but the machine code is wrong.  The displacement from 
the PC is 1114-1052 = 42, so the assembled instruction would be 100421.  As 
written, the code is a BMI MES.

You should examine the TS controller CSR at 172522 (TSSR) to see what error 
flags are set.

paul




Hi Paul,

Many thanks for you Help!
Here is the content of 172522.

Trying MS0
001120
@
@172522/052525

Please excuse, maybe my understanding is wrong: Does this mean content 
of address 001050 should be 100421 instead of 100422?


Many Greetings
Ulrich

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Hi Jerry,

Welcome to the next challenge.

I have found a procedure in the RT-11 Documentation, which automatically 
creates the two tapes.
The output of the msb process is too long, so you can find them here: 
http://www.pdp-11.de/index.php/dec-devices/tsv05ts11-rt-11-and-create-magtape-distribution-set/


The creation has worked like a charm, and without any problem.

When I boot via "b ms0" I get instantly this error, but the tape doesn't 
move noticeable.


001120 is the configured Last byte address. As the code ends by 001116 I 
have set it a little big higher, which was recommended somewhere in the 
11/84 PROM documentation.


Many Greetings
Ulrich
The first thing I would do is check the contents of 1000-1116 after 
the halt occurs

against the what you have in the eeprom.

1120 is not a location I would expect this to halt, so either there is 
a problem in
loading the the eeprom bootstrap or perhaps the first records of the 
tape are being loaded.

Do you see any tape motion?

For RT-11, you need to load device specific files at the beginning of 
the tape.
The tape primary and secondary bootstrap which load the monitor, need 
to be first.
The following (rough) example is for  MS:  @1600BPI and the RT11SJ 
monitor.


   Ini/Que/Vol/File:MBOT16.BOT MS:
   Cop MSBOOT.BOT MS:/Pos:-1
   Cop MDUP.MSMS:/Pos:-1
   Cop SWAP.SYS   MS:/Pos:-1
   Cop RT11SJ.SYS MS:/Pos:-1
   Cop MS.SYS MS:/Pos:-1
 Cop DU.SYS MS:/Pos:-1
   Cop MDUP.SAV   MS:/Pos:-1
   Cop PIP.SAVMS:/Pos:-1
   Cop DUP.SAVMS:/Pos:-1

… + other OS files.


Jerry
j...@ieee.org 

Re: PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Jerry Weiss via cctalk]

> On Aug 9, 2017, at 1:58 PM, Ulrich Tagge via cctalk  
> wrote:
> 
> Hi All,
> I have some trouble to get the Bootstrap for an Dilog DU142 (TS11) Controller 
> running on my PDP-11/84.
> The bootstrap on page 3-2 of the following documentation was used: 
> http://bitsavers.informatik.uni-stuttgart.de/pdf/dilog/2120-0090-1_DU142_Jul87.pdf
> That's, what I have saved to the 11/84 PROM:
> 
> Type a command then press the RETURN key: 13
> Edit/create an EEPROM boot
> Type CTRL Z to exit or press the RETURN key for No change
> 1741 Bytes free in the EEPROM
> Device name = MSNew =
> Beginning  address  = 001000New =
> Last byte address   = 001120New =
> Start address   = 001000New =
> Highest Unit number = 1 New =
> Device Description  = TSV05 New =
> Enter ROM ODT
> 
> xx/ = open word location xx if address even, byte if odd
> RETURN  = close location
> . or LF = close location and open next
> -   = close location and open previous
> 
> ROM ODT> 001000/012700
> ROM ODT> 001002/172520
> ROM ODT> 001004/012701
> ROM ODT> 001006/172522
> ROM ODT> 001010/005011
> ROM ODT> 001012/105711
> ROM ODT> 001014/100376
> ROM ODT> 001016/012710
> ROM ODT> 001020/001066
> ROM ODT> 001022/105711
> ROM ODT> 001024/100376
> ROM ODT> 001026/012710
> ROM ODT> 001030/001106
> ROM ODT> 001032/105711
> ROM ODT> 001034/100376
> ROM ODT> 001036/012710
> ROM ODT> 001040/001106
> ROM ODT> 001042/105711
> ROM ODT> 001044/100376
> ROM ODT> 001046/005711
> ROM ODT> 001050/100422
> ROM ODT> 001052/012704
> ROM ODT> 001054/001102
> ROM ODT> 001056/005000
> ROM ODT> 001060/005007
> ROM ODT> 001062/046523
> ROM ODT> 001064/140004
> ROM ODT> 001066/001074
> ROM ODT> 001070/00
> ROM ODT> 001072/10
> ROM ODT> 001074/001116
> ROM ODT> 001076/00
> ROM ODT> 001100/16
> ROM ODT> 001102/00
> ROM ODT> 001104/140001
> ROM ODT> 001106/00
> ROM ODT> 001110/00
> ROM ODT> 001112/001000
> ROM ODT> 001114/00
> ROM ODT> 001116/00
> 
> That's the outcome.
> 
> Type a command then press the RETURN key: B MS0
> Trying MS0
> 001120
> @
> 
> I have also tried the native TS11 bootstraps, but they are also not working, 
> but this is more likely related to the Dilog.
> Any help would be appreciated, as I can't wait to boot from my fresh build 
> RT-11 Tapes.
> By the way, RT-11 recognized this controller, and is able to read and write 
> to the TS05 Drive.
> 
> .show de:ms
> 
> Device Status CSR Vector(s)
> -- -- --- -
> MS Installed 172522 224 300
> 
> Many Greetings
> Ulrich


The first thing I would do is check the contents of 1000-1116 after the halt 
occurs
against the what you have in the eeprom.

1120 is not a location I would expect this to halt, so either there is a 
problem in
loading the the eeprom bootstrap or perhaps the first records of the tape are 
being loaded.
Do you see any tape motion?

For RT-11, you need to load device specific files at the beginning of the tape.
The tape primary and secondary bootstrap which load the monitor, need to be 
first.
The following (rough) example is for  MS:  @1600BPI and the RT11SJ monitor.

   Ini/Que/Vol/File:MBOT16.BOT MS: 
   Cop MSBOOT.BOT MS:/Pos:-1
   Cop MDUP.MSMS:/Pos:-1
   Cop SWAP.SYS   MS:/Pos:-1
   Cop RT11SJ.SYS MS:/Pos:-1
   Cop MS.SYS MS:/Pos:-1
   Cop DU.SYS MS:/Pos:-1
   Cop MDUP.SAV   MS:/Pos:-1
   Cop PIP.SAVMS:/Pos:-1
   Cop DUP.SAVMS:/Pos:-1

… + other OS files. 


Jerry
j...@ieee.org

PDP-11/84 Bootstrap for TSV05 (Dilog DU142)

[Ulrich Tagge via cctalk]

Hi All,
I have some trouble to get the Bootstrap for an Dilog DU142 (TS11) 
Controller running on my PDP-11/84.
The bootstrap on page 3-2 of the following documentation was used: 
http://bitsavers.informatik.uni-stuttgart.de/pdf/dilog/2120-0090-1_DU142_Jul87.pdf

That's, what I have saved to the 11/84 PROM:

Type a command then press the RETURN key: 13
Edit/create an EEPROM boot
Type CTRL Z to exit or press the RETURN key for No change
1741 Bytes free in the EEPROM
Device name = MSNew =
Beginning  address  = 001000New =
Last byte address   = 001120New =
Start address   = 001000New =
Highest Unit number = 1 New =
Device Description  = TSV05 New =
Enter ROM ODT

xx/ = open word location xx if address even, byte if odd
RETURN  = close location
. or LF = close location and open next
-   = close location and open previous

ROM ODT> 001000/012700
ROM ODT> 001002/172520
ROM ODT> 001004/012701
ROM ODT> 001006/172522
ROM ODT> 001010/005011
ROM ODT> 001012/105711
ROM ODT> 001014/100376
ROM ODT> 001016/012710
ROM ODT> 001020/001066
ROM ODT> 001022/105711
ROM ODT> 001024/100376
ROM ODT> 001026/012710
ROM ODT> 001030/001106
ROM ODT> 001032/105711
ROM ODT> 001034/100376
ROM ODT> 001036/012710
ROM ODT> 001040/001106
ROM ODT> 001042/105711
ROM ODT> 001044/100376
ROM ODT> 001046/005711
ROM ODT> 001050/100422
ROM ODT> 001052/012704
ROM ODT> 001054/001102
ROM ODT> 001056/005000
ROM ODT> 001060/005007
ROM ODT> 001062/046523
ROM ODT> 001064/140004
ROM ODT> 001066/001074
ROM ODT> 001070/00
ROM ODT> 001072/10
ROM ODT> 001074/001116
ROM ODT> 001076/00
ROM ODT> 001100/16
ROM ODT> 001102/00
ROM ODT> 001104/140001
ROM ODT> 001106/00
ROM ODT> 001110/00
ROM ODT> 001112/001000
ROM ODT> 001114/00
ROM ODT> 001116/00

That's the outcome.

Type a command then press the RETURN key: B MS0
Trying MS0
001120
@

I have also tried the native TS11 bootstraps, but they are also not 
working, but this is more likely related to the Dilog.
Any help would be appreciated, as I can't wait to boot from my fresh 
build RT-11 Tapes.
By the way, RT-11 recognized this controller, and is able to read and 
write to the TS05 Drive.


.show de:ms

Device Status CSR Vector(s)
-- -- --- -
 MS Installed 172522 224 300

Many Greetings
Ulrich