> On Aug 3, 2017, at 4:28 PM, Ulrich Tagge via cctalk <cctalk@classiccmp.org>
> wrote:
>
> 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.
>
Hi Ulrich,
You’ve made pretty good progress.
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.
> *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
What version of RT11 do you have? The later versions would show the
CSR that the hander is set to.
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.
>
>
>
> 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, …
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
The set the CSR that you are using
set du csr=160340
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
You should then be able to install and load the handler.
install du
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
Device Status CSR Vector(s)
------ ------ --- ---------
DU Resident 172150 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
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
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
