Re: [hatari-devel] Duplicate drive image file issue

[ Thread Index | Date Index | More Archives ]

Hi Roger,

Yes, I'm sure, because if I avoid the locking issue by applying the
change (i.e. using the image file for ACSI instead of IDE) in a single
step in the UI, everything is fine.

Best regards


> On 3 Nov 2019 at 8:17, Uwe Seimet wrote:
> > 
> > For IDE HD 0 I have configured a drive image to be used. When I select
> > the same image file for ACSI HD 0 and reset Hatari, Hatari reports
> > "Locking HD file for writing failed" and TOS only sees IDE HD 0, but not
> > HD ACSI 0. So far, so good.
> > Now I eject the file for IDE HD 0, so that the image file is configured
> > for ACSI HD 0 only. After rebooting there is no HD available for TOS
> > at all, even though ACSI HD 0 is the only drive configured with an image
> > file. Looks as if Hatari has not noticed that there is no image file
> > conflict
> > anymore but still ignores the (only) assigned image.
> > 
> Are you sure this is not a byte-swapping problem?  My ACSI image and IDE image 
> are byte-swapped with respect to each other.
> Roger

Mail converted by MHonArc 2.6.19+