Re: DSSI Disks
Paul Koning <[email protected]> Sun, 3 May 2026 14:42:20 -0400
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail=_ABD45EC5-B631-4658-83F9-666047FEC98D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On May 3, 2026, at 1:19=E2=80=AFPM, Johnny Billquist <[email protected]> = wrote: >=20 > On 2026-05-03 19:03, Andrew Ball wrote: >> ASB> I notice that ra0 and ra1 are reported as the wrong type of >> > drive (RF31 instead of RF35). >> JB> The names are basically just strings returned from the >> > simulator. They have no relevance beyond being just a string >> > that you can print out. >> > >> > Size/capacity similarly is reported as what the actual = capacity >> > is, without any regards to names. >> > >> > So this is all just cosmetic, and it's a thing that you need = to >> > fix in the simulator if you want it to say something else. >> Thanks Johnny (and thanks Michael for the correction). I'll try >> some other disk types to submit a more helpful report to the = open-simh >> people. RF71 works:- >> ra3 at mscpbus0 drive 3: RF71 >> ra3: no disk label: size 781440 sectors >=20 > I wasn't even aware that simh could report "RF71". simh have been = pretty stubborn on not accepting that it should be an arbitrary string, = and have just a few fixed values hardcoded in the code. (Atleast when I = last checked.) >=20 > But honestly, I would just ignore this "problem". Like I said - it's = very much just a cosmetic thing. I would have thought the "type" is chosen based on the disk image size, = but judging by the examples given that isn't the case. I wonder why = not. And yes, technically it's a string that should be configurable to = anything the MSCP protocol can convey. But it would be nice if at least = it produced identifiers matching the media size. paul --Apple-Mail=_ABD45EC5-B631-4658-83F9-666047FEC98D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"content-type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;"><br = id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote = type=3D"cite"><div>On May 3, 2026, at 1:19=E2=80=AFPM, Johnny Billquist = <[email protected]> wrote:</div><br = class=3D"Apple-interchange-newline"><div><meta charset=3D"UTF-8"><span = style=3D"caret-color: rgb(0, 0, 0); font-family: LucidaConsole; = font-size: 12px; font-style: normal; font-variant-caps: normal; = font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none; float: none; display: inline !important;">On 2026-05-03 19:03, = Andrew Ball wrote:</span><br style=3D"caret-color: rgb(0, 0, 0); = font-family: LucidaConsole; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;"><blockquote type=3D"cite" style=3D"font-family: = LucidaConsole; font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; orphans: auto; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;"> ASB> I notice that ra0 and ra1 = are reported as the wrong type of<br> > = drive (RF31 instead of RF35).<br> JB> The names are = basically just strings returned from = the<br> > simulator. They have no = relevance beyond being just a = string<br> > that you can print = out.<br> ><br> &nbs= p;> Size/capacity similarly is reported as what the actual = capacity<br> > is, without any regards = to = names.<br> ><br> &n= bsp;> So this is all just cosmetic, and it's a thing that you need = to<br> > fix in the simulator if you = want it to say something else.<br> Thanks Johnny = (and thanks Michael for the correction). I'll try<br>some other = disk types to submit a more helpful report to the open-simh<br>people. = RF71 works:-<br>ra3 at mscpbus0 drive 3: RF71<br>ra3: no disk = label: size 781440 sectors<br></blockquote><br style=3D"caret-color: = rgb(0, 0, 0); font-family: LucidaConsole; font-size: 12px; font-style: = normal; font-variant-caps: normal; font-weight: 400; letter-spacing: = normal; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none;"><span style=3D"caret-color: rgb(0, 0, 0); = font-family: LucidaConsole; font-size: 12px; font-style: normal; = font-variant-caps: normal; font-weight: 400; letter-spacing: normal; = text-align: start; text-indent: 0px; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; = text-decoration: none; float: none; display: inline !important;">I = wasn't even aware that simh could report "RF71". simh have been pretty = stubborn on not accepting that it should be an arbitrary string, and = have just a few fixed values hardcoded in the code. (Atleast when I last = checked.)</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: = LucidaConsole; font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none;"><br style=3D"caret-color: rgb(0, 0, 0); font-family: = LucidaConsole; font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none;"><span style=3D"caret-color: rgb(0, 0, 0); font-family: = LucidaConsole; font-size: 12px; font-style: normal; font-variant-caps: = normal; font-weight: 400; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none; float: none; display: inline !important;">But honestly, I would = just ignore this "problem". Like I said - it's very much just a cosmetic = thing.</span></div></blockquote><br></div><div>I would have thought the = "type" is chosen based on the disk image size, but judging by the = examples given that isn't the case. I wonder why = not.</div><div><br></div><div>And yes, technically it's a string that = should be configurable to anything the MSCP protocol can convey. = But it would be nice if at least it produced identifiers matching = the media size.</div><div><br></div><div><span class=3D"Apple-tab-span" = style=3D"white-space:pre"> = </span>paul</div><div><br></div><br></body></html>= --Apple-Mail=_ABD45EC5-B631-4658-83F9-666047FEC98D--