<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:314602667;
mso-list-type:hybrid;
mso-list-template-ids:2007639406 1614561900 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Recent versions of the simh PDP11 will correctly auto size (RL01 vs RL02) disk containers that have or don’t have the DEC STD 144 bad block table at the end of the drive as long as the disk image has an RT11 file system on it. If it has an RT11 file system that fact will be reported.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The prompt “Overwrite last track? [N]” is actually asking a question about whether the DEC STD 144 bad block table should be written. The default of “[N]” will create a 0 sized container file on simh v3.x and before. On simh 4.x, the container file will be created to the full size of the respective drive without regard to the answer to the “Overwrite last track? [N]” question.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Maybe the message:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>?DUP-F-Size function failed<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Happens when an empty container is provided (without a DEC STD 144 bad block info)…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Mark<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Simh [mailto:simh-bounces@trailing-edge.com] <b>On Behalf Of </b>Henk Gooijen<br><b>Sent:</b> Wednesday, February 12, 2020 1:39 PM<br><b>To:</b> simh@trailing-edge.com<br><b>Subject:</b> Re: [Simh] Initializing disks (triggered by the "Something Strange with RK05" chain<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal><span lang=NL>Yes, rt11dat and rt11run looks like RL01 “disks”, and rtv53_rl.dsk is an RL02 (and IIRC the distribution disk).<o:p></o:p></span></p><p class=MsoNormal><span lang=NL>Maybe you can add the following command after SET CPU and before the ATTACH RL statements.<o:p></o:p></span></p><p class=MsoNormal><span lang=NL>SET RL0 RL01<o:p></o:p></span></p><p class=MsoNormal><span lang=NL>SET RL1 RL02<o:p></o:p></span></p><p class=MsoNormal><span lang=NL>SET RL2 RL01<o:p></o:p></span></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal><span lang=NL>Then ATTACH them. But if I am right, you will need two empty RL02 disks, because when you boot<br>from the RL1: you probably end up in the installation procedure which want to create a backup disk<br>and a “working copy” disk (and store the distribution disk in a safe place </span><span lang=NL style='font-family:"Segoe UI Emoji",sans-serif'>😊</span><span lang=NL><o:p></o:p></span></p><p class=MsoNormal><span lang=NL>As said, from DBIT you can get an empty RL02 image.<o:p></o:p></span></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal><span lang=NL>Best to make (in Windows / Linux) a copy of the 3 files, and then proceed.<o:p></o:p></span></p><p class=MsoNormal><span lang=NL>If the rt11dat,dsk is indeed empty, it will not hurt to try<o:p></o:p></span></p><p class=MsoNormal><span lang=NL>.INIT /BADBLOCK RL2:<o:p></o:p></span></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span lang=NL>Van: </span></b><span lang=NL><a href="mailto:kjhall55@gmail.com">Ken Hall</a><br><b>Verzonden: </b>woensdag 12 februari 2020 21:09<br><b>Aan: </b><a href="mailto:SimH@trailing-edge.com">simh@trailing-edge.com</a><br><b>Onderwerp: </b>Re: [Simh] Initializing disks (triggered by the "Something Strange with RK05" chain<o:p></o:p></span></p></div><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal>Going by the size of the disk image files, I believe there’s a mix. These are downloaded disk images I pulled (literally) years ago, DL0 seems to be RL01, while DL1 is RL02:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>5235200 Dec 21 2011 rt11dat.dsk<o:p></o:p></p><p class=MsoNormal>5235200 Feb 12 12:18 rt11run.dsk<o:p></o:p></p><p class=MsoNormal>10475520 May 10 2006 rtv53_rl.dsk<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The one I’m trying to initialize is rt11dat.dsk, it’s “empty”. The other two read/access just fine, but I’ve never tried to initialize them<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Startup cmd file is:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>SET CPU 1M<o:p></o:p></p><p class=MsoNormal>ATTACH RL0 rt11run.dsk<o:p></o:p></p><p class=MsoNormal>ATTACH RL1 rtv53_rl.dsk<o:p></o:p></p><p class=MsoNormal>ATTACH RL2 rt11dat.dsk<o:p></o:p></p><p class=MsoNormal>SET RL2 BADBLOCK<o:p></o:p></p><p class=MsoNormal>BOOT RL0<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think that “BADBLOCK” option came from some suggestion way back, like I said, it’s been a long time since I touched this.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Simh <<a href="mailto:simh-bounces@trailing-edge.com">simh-bounces@trailing-edge.com</a>> <b>On Behalf Of </b>Henk Gooijen<br><b>Sent:</b> Wednesday, February 12, 2020 2:27 PM<br><b>To:</b> <a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br><b>Subject:</b> Re: [Simh] Initializing disks (triggered by the "Something Strange with RK05" chain<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=NL>See below …<o:p></o:p></span></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span lang=NL>Van: </span></b><span lang=NL><a href="mailto:kjhall55@gmail.com">Ken Hall</a><br><b>Verzonden: </b>woensdag 12 februari 2020 18:30<br><b>Aan: </b><a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br><b>Onderwerp: </b>[Simh] Initializing disks (triggered by the "Something Strange with RK05" chain<o:p></o:p></span></p></div><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal>I’ve played with RT11 on and off over the years, but the one thing I’ve never been able to do is properly initialize an empty disk. If I create a DL2: for example, and try to run initialize on it, I get back:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>.dir dl2:<o:p></o:p></p><p class=MsoNormal>?DIR-F-Error reading directory<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>.init dl2:<o:p></o:p></p><p class=MsoNormal>DL2:/Initialize; Are you sure? YES<o:p></o:p></p><p class=MsoNormal>?DUP-F-Size function failed<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This seems similar to the issues Henk Gooijen has been having with RK05’s, and it’s been so long since I’ve dealt with the real hardware I don’t recall exactly how this is supposed to work, but it seems to me it should just “work”.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Has anyone found a solution to this?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I can check that tomorrow. Maybe that is the reason you can download<o:p></o:p></p><p class=MsoNormal>an empty but initialized RL02 image (zipped) from DBIT.<o:p></o:p></p><p class=MsoNormal>If RT11 cannot figure out the size (5 MB or 10 MB / RL01 or RL02), maybe<o:p></o:p></p><p class=MsoNormal>the command (in SIMH) .SET RL0 RL02 helps. You specify that RL0 is an<br>RL02. Likewise, you can say .SET RL0 RL01. On a real PDP-11 with RL drives<br>the system will recognize what type RL01 or RL02 is connected/loaded.<br>You can have a mix of RL01 and RL02 drives on one RL11 controller.<o:p></o:p></p><p class=MsoNormal>The .SET RLx RL01 (or RL02) command is not of RT11, but of SIMH. Give it a try <span style='font-family:"Segoe UI Emoji",sans-serif'>😊</span> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For the write protect command for the RK drives, this is probably also a<br>SIMH command. .SET RK0 WRITEENABLE *<b>is</b>* in SIMH (as is .SET RK0 LOCKED).<o:p></o:p></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p><p class=MsoNormal><span lang=NL><o:p> </o:p></span></p></div></div></body></html>