Re: DSSI Disks

Anders Magnusson <[email protected]> Mon, 4 May 2026 09:37:34 +0200
Newsgroups gmane.os.netbsd.ports.vax
Message-ID <[email protected]>
Den 2026-05-04 kl. 08:55, skrev Johnny Billquist:
> On 2026-05-04 03:06, Andrew Ball wrote:
>>    ASB> set rq3 rf35
>>       > attach rq3 disk3.img
>>
>>    PK> You can do that, but it's not required (unless you're creating a
>>      > new container in which case the name implies the size). My point
>>      > was that attaching an existing image file should default the
>>      > type, though of course you can then override it if you want.
>>
>>      Interesting!  I had no idea that was optional.  That might explain
>> why simh3 didn't seem to understand what I was trying to do. Perhaps
>> it's an open-simh 4 thing.
>
> Yes. You don't have to say anything about type. It's used by simh to 
> have a size for creating the new disk. And that's close to all simh 
> uses it for. It might present different names in MSCP also, but as 
> we've been discussing now, this is somewhat broken in simh.
>
> And yes, v3 of simh are just knows even a little less about types. 
> Which is why you were getting those errors.
May note here as well that some third-party cards might present the disk 
type as just anything.
For example; an Emulex MSCP-emulating SCSI card I had always presented 
the disks as RA81, independent of size and type.

-- R