Re: DSSI Disks
Johnny Billquist <[email protected]> Mon, 4 May 2026 08:55:29 +0200
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Organization | SoftJAR AB |
| Message-ID | <[email protected]> |
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.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: [email protected] || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol