Re: Portlock Storage Manager?

[Ulrich Tagge via cctalk]

Hi Benjamin,

I was a Novell CNE for a longer time, and have started to work with
NetWare 2.10 (non dedicated server) with the age of 15 in 1993.

Have made my first real money with the migration of this NetWare 2.10
which was running on a small 80286 PC server to 3.12 on a Compaq
SystemPro in 1994.

Moved my last NetWare 6 Server in 2015 to OES and my last GroupWise
system to Exchange in 2017.

Portlock was a a tool I have used in the old days twice a month, but I
think they have lost their customer base, as nobody really use NetWare
traditional or NSS file systems any longer -Or?


Their website Portlock.com has gone in 2019, but I have also no clue if
they have end their business or if they simply have lost their domain.

But try to call them, the number is may be still in use.

https://web.archive.org/web/20190220183136/http://portlock.com/


Many Greetings

Ulrich

Re: RX01 wants

[Ulrich Tagge via cctalk]

Hi Fritz,
I'm interested in the RX01 Drive and equipment.
Where is the stuff located?

Many Greetings
Ulrich

IBM 360? on eBay.de

[Ulrich Tagge via cctalk]

I'm not affiliated with the seller.

https://www.ebay.de/itm/seltene-Anlage-Puma-Computer-IBM-2020/202646831828?hash=item2f2eb142d4:g:izoAAOSwhV1cpwr2=true

Re: Retarded ebay prices

[Ulrich Tagge via cctalk]

We had three HP250 Desks here in Germany over the last Years.
They have found a new Home for approx. 200.- to 250.- Euro.
This one is since months on my whatchlist, and the price is defnitly too 
high.
We had also a VAX 11/785 incl. 9-Track Tape, VT100, RA Disk Drive, ... 
... which was gone for under 1.000.- Euro (dame i had not enough space)

Re: DECstation firmware archive?

[Ulrich Tagge via cctalk]

Maybe this helps: http://home.iae.nl/users/pb0aia/vax/vs-scsi.html & 
ftp://ftp.gwdg.de/pub/vms/ka420/README.txt



On 08/03/2018 01:53 PM, Glen Slick via cctalk wrote:
/On Fri, Aug 3, 2018 at 2:26 AM, Jan-Benedict Glaw via cctalk />/
> wrote: />>/If it's of interest, I'd probably 
add a number of VAXstation dumps for />>/several machines (3100, 4000, VS II GPX, VXT). />/One interesting 
thing about MicroVAX 3100 firmware is that the M10/20 />/and the M10e/20e motherboards are the same (as far as I 
know) as the />/InfoServer 100 and 150 motherboards, just with different firmware. In />/some situations an 
InfoServer may be more useful than a MicroVAX 3100. />/They can be converted by replacing the firmware. /
Has anybody ever tried dis-assembling the 3100 ROM to
modify it to boot from bigger disks?

bill

PDP-11/23 with RL02 on - eBay US

[Ulrich Tagge via cctalk]

Just spotted this auction on eBay US Item: 263824036905
Location is: Glenview, Illinois

Not cheap, but the seller is open for offers.

Not affiliated with the seller.

Re: DEC Field Guide > equivalent available for Data General?

[Ulrich Tagge via cctalk]

Hi all,
thanks for your comments.
They has helped a lot, to understand the DG numbering schema, and will 
help identifying the modules.


Many Greetings
Ulrich

DEC Field Guide > equivalent available for Data General?

[Ulrich Tagge via cctalk]

Hi all,

is there somewhere a list of DG modules which includes also 3rd 
party/OEM, ... like it is available for DEC?


Would be good to know what the following is:

107-000621 02
107-000621 03/11
107-001632-00
107-0016320/02
107-000718-00
107-000181-04
107-000187-16
107-000187-15-30
AB020116-00
107-000621-03
107-001768-02
107-001768-03
107-0017680-1E
107-00053905
Zetaco SCZ-2
>500-453-00 K
>500-542-00 K


Many Greetings
Ulrich

Re: Maxtor full-height 5.25" drives of death

[Ulrich Tagge via cctalk]

/Here is my list. 6x RD54 (Maxtor XT2190) >2x OK, 2x Media Error, 1x 
Actuator Issue, 1x Head issue 3x RD53 (Micropolis 1325) >2x Actuator 
issue, 1x actuator issue followed by spinning issue (speed sensor?) 4x 
Seagate ST251 >4x OK 3x Seagete ST225 >3x OK 3x IBM Type 068 >3x Dead On 
the 3.5" side I have also many dead drives (<1GB capacity). Mostly 
sticky actuators and dead tantalum caps, but by now nothing I was not 
able to repair. Many Greetings Ulrich /


A tangential question out of curiosity: 
who here has 5.25" MFM drives they're 
extremely surprised are still working, 
and which model(s)?

...

- John

DEC H7750 Battery Backup Unit

[Ulrich Tagge via cctalk]

Hi All,

I have a PDP-11/24 which is connected to a H7750.
There is not much about the H7750 in the documentation of the /24, and I 
would like to know how to check the H7750 and to verify it's correct 
operation.


So schematics and documentation for the H7750 would be welcome - any 
hint how to find them?


Many Greetings

Ulrich

Re: PDP-11/73 and 11/94 update

[Ulrich Tagge via cctalk]

Hi Rod,

I have not the chance to go into the basement before Weekend, but have 
document the installation here:

http://www.pdp-11.de/index.php/pdp-11/rt11-5-4g-installation/

My 11/84 have the KDJ11-B (m8190).

Many Greetings
Ulrich

Re: PDP-11/73 and 11/94 update

[Ulrich Tagge via cctalk]

Hi Rod,

I missed this in my last reply.
You can also verify the Bootstrap code placed in the KDJ11 EEPROM, maybe 
there is an error in.


Many Greetings
Ulrich

Re: PDP-11/73 and 11/94 update

[Ulrich Tagge via cctalk]

Hi Rod,

I had an similar issue, when trying to boot a RX02 Disk created on my 
/84 on a /34a.
Have bypassed this and have installed a fresh RT11, but had no time to 
figure out the problem.
Would it of interest for you, to get RX02 Images (PDP11GUI) of my RT-11 
V5.4 G Distribution Set? With them, you could install your /94 from 
scratch, ... .


Many Greetings

Ulrich

Re: PDP-11/73 and 11/94 update

[Ulrich Tagge via cctalk]

Hi Rod,

I'm sure you are aware about, ... the /94 have a MDM card/module, where 
you can set the NPG jumper via switches. Is this set correct for all the 
slots, no mismatch in counting the small switches?

Have you checked the flat ribbon cable - I had much fun with damaged cables?
Have you tried dy0 and dy1?
Is the RX02 set to the correct mode?
The known good 8" disk, is a rx02 disk and not a rx01?

Many Greetings

Ulrich

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: RX02 *.DSK convert to PDP11GUI Image format

[Ulrich Tagge via cctalk]

Hi Glen,

a mirror is here: 
http://rtk.mirrors.pdp-11.ru/_pdp-11/shop-pdp.net/pub/tcpip/tcpip/

Please have a look onto my last reply, as the problem seams to be solved.

Many Greetings
Ulrich

Am 15.08.17 um 06:49 schrieb Glen Slick:

On Sun, Aug 13, 2017 at 9:00 AM, Ulrich Tagge via cctalk
<cctalk@classiccmp.org> wrote:

Hi all,

maybe someone can help.
I would like to install TCP/IP on my RT-11 system.
After a short search I have found the following, which I would use:
http://www.classiccmp.org/PDP-11/RT-11/freeware/decus11/110939/rthtml/tcpget.htm
But the images are in DSK format, but I can't write them with PDP11GUI,
which is the only way I have at the moment.

I would take a quick look at those .DSK images to see what I can make
of them, but none of the download links on that page work for me.

For example, I can't download this .DSK image. Do these links work for
other people?
ftp://shop-pdp.kent.edu/du3:/tcpip.pkg/tcpipm.dsk

Re: RX02 *.DSK convert to PDP11GUI Image format

[Ulrich Tagge via cctalk]

Hi All,

After all the replays and discussions I was more and more the 
impression, that the images couldn't be in DSK, as this would mean some 
extra work, as this format can't be created on a PDP.
To be more or less sure I have tried to open them with some DSK capable 
tool, which I had on an older 486 based PC.

The outcome was a a message which told me, that the format is not supported.

So I have tied to reach Alan via Mail, and have asked about the format, 
and that I had the hope to write the Images with PDP11GUI.
After a very short delay, I had this replay with all needed details, and 
the OK, to post it here.

So you were right about Track0...

I will test it today's evening, and report back afterwards.

Many Greetings
Ulrich

Am 14.08.17 um 20:29 schrieb Alan R. Baldwin:

Ulrich,

  The RX02 DSK images were created using the following RT-11
command file script:

 create image.dsk/allocate:988
 mount ld3: image.dsk
 init ld3:

This results in a file of 988 blocks (505,856 bytes) in
length.  The program PDP11GUI wants a file of 512,512 bytes
in length ...  So this requires an explanation -

  An RX01 or RX02 floppy disk is based on the original IBM
8" disk format of 77 tracks with 26 sectors per track and
for a Double Density RX02 has 2,002 sectors of 256 bytes each
yielding 512,512 bytes (or 1,001 blocks each 512 bytes long.)

However, DEC chose NOT to use the first track of the disk on
any RX01 or RX02 disk.  Thus 76 tracks with 26 sectors per
track for the Double Density RX02 is 1,976 sectors of
256 bytes each yielding 505,856 bytes (or 988 blocks each
512 bytes long.)

  In RT-11 the following command copies a disk file created
with the above command file directly and correctly to a real
RX02 disk:

 copy image.dsk/file dy0:/dev

as the image disk has the same size as the active part of
the RX02 disk.

  To use the PDP11GUI program you will need to prepend a file
of length 6,656 bytes to the TCP/IP files.  The file content
is inconsequential.  Copy the image file you wish to fix up
into a new location.

1)  Open up a Command Prompt Window and
move to the directory containing the image file.

2)  Make the fix up file as follows:

 fsutil file createnew hdr.bin 6656

3)  Concatenate the fix up file with the image.dsk file:

 copy /b hdr.bin /b + image.dsk /b newimage.dsk /b

The newimage.dsk file will now load into the PDP11GUI program.

Since normally the RX01/RX02 drivers don't access track 0 I don't
know what the PDP11GUI program does with those extra 6,656 bytes.

Good Luck,

Alan 

Re: RX02 *.DSK convert to PDP11GUI Image format

[Ulrich Tagge via cctalk]

Hi all,

I have tried to find a specification about the DSK Image format, but 
have only found the the following: 
http://www.cpctech.org.uk/docs/dsk.html , which looks like the focus is 
more on CPC related Disks.


Is there any detailed description somewhere in the www about the DSK format?

Many Greetings

Ulrich

Re: RX02 *.DSK convert to PDP11GUI Image format

[Ulrich Tagge via cctalk]

Am 13.08.17 um 20:34 schrieb Jerry Weiss:

On Aug 13, 2017, at 12:59 PM, Ulrich Tagge  wrote:

Hi Jerry,

I have tried with PDP11GUI, but the first message says "The image contains only 
505856 bytes, but disk has 512512 bytes".
I have written some disks, and have ignored this message, but none of them is 
readable under RT-11.
.dir dy0:
?DIR-F-Error reading directory

So I think the DSK format is different from the one PDP11GUI uses.
In the documentation I have seen, that the format is the same as SimH uses.
Image file format
Every DEC disk or tape is logically represented as a linear list of “blocks”. 
The block size differs between 128 byte and 1024 bytes. Reading and writing is 
based on block numbers.
The file format is that of SimH: a file image is just a stream of blocks.
Kermit would be a possibility, and I will try it later on.

Many Greetings
Ulrich


DEC OS’es typically do not do anything with track 0 on an RX02, and start with 
track 1.  I can only guess that PDP11GUI is trying to use the entire disk.

If there is an option to start at track 1 or skip the first 30 (?) blocks, that 
might work.


Note that ?DIR–F–Error reading directory is a hardware error.
Bad data would instead cause a ?DIR–F–Invalid directory.
You are right, and it looks like, that in the process of image writing, 
and reading my DY0: died.

Tested again with DY1: and the outcome is now ?DIR-F-Invalid directory

I have send a Mail to Joerg yesterday evening, and have asked about 
PDP11GUI and the possibility to write DSK images, now waiting for the 
outcome.


Many Greetings
Ulrich
  


Regards,
Jerry

Re: RX02 *.DSK convert to PDP11GUI Image format

[Ulrich Tagge via cctalk]

Hi Jerry,

I have tried with PDP11GUI, but the first message says "The image 
contains only 505856 bytes, but disk has 512512 bytes".
I have written some disks, and have ignored this message, but none of 
them is readable under RT-11.

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

So I think the DSK format is different from the one PDP11GUI uses.
In the documentation I have seen, that the format is the same as SimH uses.
>>
*Image file format*
Every DEC disk or tape is logically represented as a linear list of 
“blocks”. The block size differs between 128 byte and 1024 bytes. 
Reading and writing is based on block numbers.

The file format is that of SimH: a file image is just a stream of blocks.
>>

Kermit would be a possibility, and I will try it later on.

Many Greetings
Ulrich

Am 13.08.2017 um 19:25 schrieb Jerry Weiss:

On Aug 13, 2017, at 11:00 AM, Ulrich Tagge via cctalk <cctalk@classiccmp.org> 
wrote:

Hi all,

maybe someone can help.
I would like to install TCP/IP on my RT-11 system.
After a short search I have found the following, which I would use: 
http://www.classiccmp.org/PDP-11/RT-11/freeware/decus11/110939/rthtml/tcpget.htm
But the images are in DSK format, but I can't write them with PDP11GUI, which 
is the only way I have at the moment.
I like the PDP11GUI implementation and way, as there is nothing more you need 
as a PDP and a RX02, which is in most cases available.

Someone here, who has the equipment, time and mind to write the DSK files onto 
RX02 followed by an new image via PDP11GUI?
Or is there any other suitable way for me?



Hi Ulrich,

I haven’t used PDP11GUI, but you should be able to use it write the DSK files 
from PC to an RX02.   Did you
encounter some problem?Alan has provided images which are RX02 sized.  This 
site has the latest distribution
http://shop-pdp.net/rthtml/tcpip.php

Otherwise - check this site for a copy of kermit - 
http://www.columbia.edu/kermit/pdp11.html
Note especially, the bootstrap process for RT-11.  You basically copy the files 
as text down to the machine.
Then you compile a macro program to convert the .HEX file to a program. That 
minimal
kermit will then allow you load other data and programs, including the full 
featured Kermit-11.

I’ve used this process myself using any basic terminal emulator.
Paste the text via either an editor or using COPY TT: to DK:FILE.TXT  
(terminate with a CONTROL-Z).

Jerry
j...@ieee.org

RX02 *.DSK convert to PDP11GUI Image format

[Ulrich Tagge via cctalk]

Hi all,

maybe someone can help.
I would like to install TCP/IP on my RT-11 system.
After a short search I have found the following, which I would use: 
http://www.classiccmp.org/PDP-11/RT-11/freeware/decus11/110939/rthtml/tcpget.htm
But the images are in DSK format, but I can't write them with PDP11GUI, 
which is the only way I have at the moment.
I like the PDP11GUI implementation and way, as there is nothing more you 
need as a PDP and a RX02, which is in most cases available.


Someone here, who has the equipment, time and mind to write the DSK 
files onto RX02 followed by an new image via PDP11GUI?

Or is there any other suitable way for me?

Many 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)

[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)

[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 <cctalk@classiccmp.org> 
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 

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

Re: RL drive bulkhead connector

[Ulrich Tagge via cctalk]

Each drive has this adapter internally at the flat ribbon cable, so if 
you have a spare drive you could think about using them.
I have done this also, but my drive was damaged by water, so it was ok 
for me to cannibalize the adapter.
It's also possible to go direct from the controller to the drive with a 
flat ribbon cable, but I have not done this, and think that the original 
cable is shielded, ... .


Many Greetings
Ulrich

Re: WTB: RX02 Floppy Disks

[Ulrich Tagge via cctalk]

Output:
.SET DU CSR=17760340
?DU-W-Patch handler bootstrap, put CSR at 3264

As you may have already learned, use only 16bit addresses for this.

Hi Jerry,

Thanks, you found the failure! (it's always the same with Copy and Paste).
After I have corrected this to 160340 and afterwards all was running 
fine, and I was able to INIT the Disk.
A format was still not possible, but I think this is normal and works as 
designed?!


Last step was to set the adapter CSR to the MSCP default, to bypass 
further issues due to the non default CSR.
As there is at the moment no plan for additional MSCP adapter in this 
PDP, it will be fine.


After this change I was needed to restore the original DU.SYS, as 
booting was not possible, and a SYSGEN is by now not an option. (will 
look at it later on, to understand a bit more about)

>>
?BOOT-U-▒Conflicting SYSGEN options
>>

Now I have managed to boot from the SCSI disk, which is a great result.

>>>
Trying DU0

Starting system from DU0


RT-11SJ (S) V04.00I

.SET TT QUIET
?KMON-F-File not found SY:RTPRES.SAV
?KMON-F-File not found SY:DATE.SAV
?KMON-F-Illegal device VW:
?KMON-F-Illegal device BS:
?KMON-F-Illegal device HC:

.DIR

US.SYS 7  26-Nov-91  TT.SYS 2  26-Nov-91
DL.SYS 4  26-Nov-91  DU.SYS 4  26-Nov-91
RK.SYS 3  26-Nov-91  DY.SYS 4  26-Nov-91
DX.SYS 3  26-Nov-91  LP.SYS 2  26-Nov-91
SC.SYS 5  26-Nov-91  HC.SYS 5  26-Nov-91
BS.SYS 3  26-Nov-91  VW.SYS 2  26-Nov-91
NL.SYS 2  26-Nov-91  LS.SYS 2  26-Nov-91
SCMEV .SYS 5  26-Nov-91  SCVS11.SYS 4  26-Nov-91
SCEVA .SYS 4  26-Nov-91  LPMEV .SYS 2  26-Nov-91
LPLXY .SYS 2  26-Nov-91  LPSID .SYS 2  26-Nov-91
LPEVA .SYS 2  26-Nov-91  MS.SYS10  26-Nov-91
MM.SYS 9  26-Nov-91  HC7221.SYS 4  26-Nov-91
HC7220.SYS 5  26-Nov-91  HC722T.SYS 5  26-Nov-91
US460 .SYS 7  26-Nov-91  US410 .SYS 7  26-Nov-91
HC7580.SYS 5  26-Nov-91  HC7550.SYS 5  26-Nov-91
HC7475.SYS 5  26-Nov-91  HC722C.SYS 5  26-Nov-91
SCMPR .SYS 5  26-Nov-91  DUORG .SYS 4  26-Nov-91
STARTS.COM 1  26-Nov-91  PIP   .SAV23  26-Nov-91
DIR   .SAV17  26-Nov-91  DUP   .SAV41  26-Nov-91
RESORC.SAV15  26-Nov-91  FORMAT.SAV19  26-Nov-91
SWAP  .SYS25  26-Nov-91  RT11SJ.SYS65  26-Nov-91
CHKPNT.SYS   412  09-Aug-94
 43 Files, 763 Blocks
 58469 Free blocks
>>


So next step is to look at a newer RT11 version, and try to install all 
from scratch.


Again many thanks!
Have a nice Weekend
Ulrich

Re: WTB: RX02 Floppy Disks

[Ulrich Tagge via cctalk]

Hi Jerry,

You’ve made pretty good progress.

Yes with the right input and help this can happen. ;-)
And all the help is much appreciated!


If you haven’t already, Google for and look at the manual for the SQ739. I 
think you will find that most of the
commands for the on-board diagnostics are the same.  The unibus controller will 
have a
different layout and perhaps a physical vector switch, but you should be able 
to sort out the differences.

Not done by now, but is now noted and on the plan for the weekend, I'm 
also interested to know about the jumper settings as there are some of them.


What version of RT11 do you have?  The later versions would show the
CSR that the hander is set to.

Its: RT-11SJ (S) V04.00I ... quite old.

  


You mention a RC25.  Is that on another machine? If you have two MSCP
controllers in the same backplane (KLESI? + SU723) then that is more complex.

My guidance below assumes the SU723 and a bootable RX02 device are
the only disks.  Do not follow if you have two MSCP controllers installed.
That's the right assumption, I have two /84 one with lesi and working 
RC25 where I have created the Floppy disks, and a playground mostly 
empty, but now equipped with SCSI and RX211.

The address 160340 is not what is normally expected “standard” CSR for a MSCP.
Its is easy to change the handler address.

First make a copy of the DU.SYS handler to preserve it.

copy/sys du.sys duorg.sys

Done

The set the CSR that you are using

set du csr=160340

Output:
.SET DU CSR=17760340
?DU-W-Patch handler bootstrap, put CSR at 3264


Try vector address 154 first, unless you know the board is configured 
differently.
It appears already set for this, but here is how you change it.

set du vector=154

Output:
.SET DU VECTOR=154

.

You should then be able to install and load the handler.

 install du

Output:
.INSTALL DU
.

 load du

Output:
.LOAD DU


Depending on the DU handler, it is possible to map a large MSCP image to 
multiple
partitions.  If the handler installs, try the following.  It show a basic 
mapping.
Single controller, single drive and in this case 8 partitions.   The first 
partition
should be the same as below.  An RZ22 would normally only have space
sufficient for 1 partition.

 show de:du

 DeviceStatus   CSR Vector(s)
-- --   ----
  DU Resident172150   154

  DU0: is set PORT =  0, UNIT =  0, PART =  0
  DU1: is set PORT =  0, UNIT =  0, PART =  1
  DU2: is set PORT =  0, UNIT =  0, PART =  2
  DU3: is set PORT =  0, UNIT =  0, PART =  3
  DU4: is set PORT =  0, UNIT =  0, PART =  4
  DU5: is set PORT =  0, UNIT =  0, PART =  5
  DU6: is set PORT =  0, UNIT =  0, PART =  6
  DU7: is set PORT =  0, UNIT =  0, PART =  7

Output:
.SHOW DE:DU
?KMON-F-Illegal command
.SHOW DEV:DU
?KMON-F-Illegal command

(RT11 Version to old?)


.SHOW DEV

Device  Status   Vector
---
  US  Not installed  410
  DL  Not installed  160
  RK  Not installed  220
  DY  Resident   264
  DX  Not installed  264
  LP  146676 200 204
  SC  143332 000
  HC  Not installed  330 334
  BS  Not installed  300 304
  VW  Not installed  270 274
  NL  Installed  000
  LS  Installed  200 204
  MS  Not installed  224
  MM  Not installed  224
*  DU  141440 154*

So something happens and we have a first progress.


Since you already did a SCSI format from the controller or if the drive
was previously formatted, you will not need to repeat this. The RT11 FORMAT
command does NOT support this as an MSCP device.  Note: the handler can be
configured to more partitions and disk space than actually exist on the drive.

You can examine the contents of the drive to see if it readable.

 dump/term du0:/end:1
Dump is unfortunately not available on my disk by now, but will add 
them, when I have moved the RX02 back to the other PDP.

If the handler loads but doesn’t access the drive, check the vector address 
first.

Once you are sure the contents are not needed, you can try an initialize.


Good luck.

Jerry
j...@ieee.org


Is it maybe better to start with a newer version of RT11?
In the meantime I have managed to test RX02 Imaging with Joeg Hoppe's 
PDP11GUI. Works perfect and looks like a great tool.
If I load the MSCP driver via PDP11GUI and use address 160340 I can also 
dump the DU0 (RZ22) disk to my PC, so it seams to be working.


I have not found a newer RX02 RT11 Distribution Set by now, do you have 
some tip were I can find and download one?  Google doesn't return any 
rx02 files, only ready to use images for 

Re: WTB: RX02 Floppy Disks

[Ulrich Tagge via cctalk]

Hi All,
All my 8" SSDD /SSSDdisks are non formatted, which was the reason for my 
initial troubles.
Nevertheless, my IBM System /23 (Type 5324) can format disks in three 
different formats:


_1. IBM System /23 Format_
512 Bytes per Sector
Possible Disk: SSSD, SSDD, DSDD

_2. Standard Format_
128 Bytes per Sector
Possible Disk: SSSD, SSDD

_3. H- Format_
258 Bytes per Sector
Possible Disk: DSDD

_So option 2_ was the right one, also when nothing in the docs point to 
the IBM 3740 format.
After booting the System/23 with the inserted maintenance Disk VOL002 
the formatter program can be started with the following command: link 
prepare



By now I have 20 RX02 Disks formatted, and was also able to create a 
bootable RT11 Disk via my running RT11 installation on my RC25.

It is RT-11SJ (S) V04.00I ...
>>>
.FORMAT DY1:
DY1:/FORMAT-Are you sure?Y
?FORMAT-I-Formatting complete
<<<
>>>
.INIT/BAD DY1:
DY1:/Initialize; Are you sure? Y
?DUP-I-No bad blocks detected DY1:
<<<

Next step would be to install RT11 on my SCSI Disk, which is presented 
through a Dilog SU726A as MSCP Device 0 (Address 160340 (will be 1760340 
on my PDP-11/84)) to the system.
Disk is an DEC RZ22 and was also formatted and mapped, through the Dilog 
"BIOS" (Jumper J14 in to boot Maintenance Address ... and @175000g 
followed by FT)
Now it looks like I need the SU726A manual, as I have no clue as which 
device RT11 should recognize the Dilog, I assume DU0: but RT11 doesn't 
load the Device.



*SHOW DEV*

Device  Status   Vector
---
  US  Not installed  410
  DL  Not installed  160
  DU  Not installed  154
  RK  Not installed  220
  DY  Resident   264
  DX  Not installed  264
  LP  146676 200 204
  SC  143332 000
  HC  Not installed  330 334
  BS  Not installed  300 304
  VW  Not installed  270 274
  NL  Installed  000
  LS  Installed  200 204
  MS  Not installed  224
  MM  Not installed  224
*
**.DIR*

SWAP  .SYS25  26-Nov-91  RT11SJ.SYS65  26-Nov-91
US.SYS 7  26-Nov-91  TT.SYS 2  26-Nov-91
DL.SYS 4  26-Nov-91  DU.SYS 4  26-Nov-91
RK.SYS 3  26-Nov-91  DY.SYS 4  26-Nov-91
DX.SYS 3  26-Nov-91  LP.SYS 2  26-Nov-91
SC.SYS 5  26-Nov-91  HC.SYS 5  26-Nov-91
BS.SYS 3  26-Nov-91  VW.SYS 2  26-Nov-91
NL.SYS 2  26-Nov-91  LS.SYS 2  26-Nov-91
SCMEV .SYS 5  26-Nov-91  SCVS11.SYS 4  26-Nov-91
SCEVA .SYS 4  26-Nov-91  LPMEV .SYS 2  26-Nov-91
LPLXY .SYS 2  26-Nov-91  LPSID .SYS 2  26-Nov-91
LPEVA .SYS 2  26-Nov-91  MS.SYS10  26-Nov-91
MM.SYS 9  26-Nov-91  HC7221.SYS 4  26-Nov-91
HC7220.SYS 5  26-Nov-91  HC722T.SYS 5  26-Nov-91
US460 .SYS 7  26-Nov-91  US410 .SYS 7  26-Nov-91
HC7580.SYS 5  26-Nov-91  HC7550.SYS 5  26-Nov-91
HC7475.SYS 5  26-Nov-91  HC722C.SYS 5  26-Nov-91
SCMPR .SYS 5  26-Nov-91  CHKPNT.SYS   412  09-Aug-94
STARTS.COM 1  26-Nov-91  PIP   .SAV23  26-Nov-91
DIR   .SAV17  26-Nov-91  DUP   .SAV41  26-Nov-91
RESORC.SAV15  26-Nov-91  FORMAT.SAV19  26-Nov-91
 42 Files, 759 Blocks
 215 Free blocks


Any Hint how I get RT11 load the correct device so that I can format and 
init the SCSI Disk?
Is maybe Someone here with an Manual of the Dilog? A SU723 could be also 
helpful, ... .


Many Greetings
Ulrich

Re: WTB: RX02 Floppy Disks

[Ulrich Tagge via cctalk]

Hi All,

Have managed to find and pick a bunch of SSSD 8" Disks in my basement, 
and have formatted them now via the IBM /23.
Over the weekend I try the next step,and will "format" them under RT11. 
So fingers crossed, that my only running RT11 system, installed on an 
DEC RC25, will still boot.


Many Greetings
Ulrich

Re: WTB: RX02 Floppy Disks

[Ulrich Tagge via cctalk]

Hi All,

Looks like I was wrongly under the impression, that there is no way to 
reformat, disks to work in an RX02.
I have two working IBM System /23 with 8" Floppy drives, which can 
format also in IBM3740.
So when I have understood it correct, it could be worth to simply format 
an 8" SSSD Disk in 3740 format, followed by:

".FORMAT DY0:"

".INITIALIZE/BADBLOCKS DY0:"

under RT11 which will end up in an RX02 formatted disk - Correct?

Many Greetings
Ulrich

WTB: RX02 Floppy Disks

[Ulrich Tagge via cctalk]

Hi all,

I'm interested on RX02 Disks, and would be happy to get some of them, to 
create RT11 installation and diagnostic disks.
I know there are RX01/02 emulators available, but I would like to use 
the original way and equipment.

Destination would be Germany.

Many Greetings
Ulrich

S: Dilog SU726A Documentation

[Ulrich Tagge via cctalk]

Hi All,

Is someone here, who has the documentation for an Dilog SU726A Rev. C, 
Unibus SCSI Controller?


Looks like the documentation is not on the Web, as google doesn't return 
any helpful link, and Bitsavers miss it also.


Many Greetings

Ulrich

Re: UNIBUS RK611 (RK06/RK07) controller available

[Ulrich Tagge via cctalk]

Hi Noel,

I'm really interested to get a Backplane and Board Set (RK611), for my 
two RK7 drives.


I think we are not on the same continent, but I'm willing to spend some 
bucks for shipping, ... .


So happy to hear from you.

Many Greetings
Ulrich