Re: [hatari-devel] Drive image byteswap confusion

[Uwe Seimet <Uwe.Seimet@xxxxxxxxx>]

I just noticed that the actual byte order Hatari uses appears to depend
on the TOS version. Can it be that when running TOS 4.04 the resulting
byte order differs from the one used with TOS 3.06?

> Hi,
> 
> > Am Fri, 18 Oct 2019 21:11:40 +0200
> > schrieb Uwe Seimet <Uwe.Seimet@xxxxxxxxx>:
> > 
> > > This looks wrong to me. When byteswapping is configured to be off,
> > > it's actually enabled and Hatari reports:
> > 
> > There is no real right and wrong here. It always depends on where you've
> > imaged your disk, the original disk layout, and your expectations.
> 
> I'm afraid this is still not clear to me. I created a new image with
> 
> dd if=/dev/zero of=some_image_file ...
> 
> When byteswapping is switched off and I partition this image (assigned
> to a Hatari IDE drive), the byte order is not what it would have been with
> a real Atari with standard IDE interface. Instead, the resulting byte
> order is the one used by ACSI/SCSI.
> 
> > Anyway, we can not simply change the meaning here without causing much
> > more confusion. I'd suggest to simply use the "Auto" setting and stop
> > worrying about this.
> 
> "Auto" may be fine when dealing with existing images. But I often want
> to create a new bootable (with a real Atari) image with Hatari. In such
> a case it's important to have full control of the byte order. Otherwise
> you end up with different results, depending on the original byte order
> of the image.
> 
> Best regards
> 
> Uwe
> 
>