Re: [hatari-devel] Fsfirst issue with GEMDOS drive

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On 14.9.2024 10.12, Uwe Seimet wrote:
> When running Fsfirst on an existing file on a GEMDOS drive error -49 is
> reported, even though the file is present.

This should be fixed now (thanks to example code, and hint from Christian).


This is logged:
> GEMDOS 0x4E Fsfirst("D:\HDDRUTIL\TEST.IMG", 0x7) at PC 0x16040BC
> GEMDOS: D:\HDDRUTIL\TEST.IMG -> host: /home/us/TT/D/HDDRUTIL/TEST.IMG
> GEMDOS 0x4F Fsnext() at PC 0x16040BC
>
> Note that I do not call Fsnext, only Fsfirst, but Fsnext is also logged.

Logging is also fixed.


> The file does not have any special permissions:
>
> -rw-rw-r-- 1 us users 15728640 Sep 14 08:48 TEST.IMG
>
> This happends regardless of the file attributes I pass to Fsfirst.

It was regression from my previous fix, and happens only if FA_VOLUME is 
used in _previous_ Fsnext() calls.

Thanks for reporting!


	- Eero