| Re: [hatari-devel] ACSI: READ/WRITE (10) incorrectly evaluate block number |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] ACSI: READ/WRITE (10) incorrectly evaluate block number
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Sun, 27 Oct 2013 11:01:48 +0100
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1382868108; l=658; s=domk; d=seimet.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=h7eqL3RUASbks5BXXYer3E95KDo=; b=Ttr7taF0DEP6iUv3jc8t4/315NWUoSErVq2UYQMrTnVgFCa6pw7pvw/M3+8YwdpkgGO qbyL6D81JKnqdmJBEPXDmMPDjqWieuRNu0ZwAilkPniPQYOxFW4A5dehDXLnmjgfhoDr/ FZJ8VEXWFRiG96JWlpCp/9rm+FlsGju8FHE=
Hi Thomas,
> > As far as I can tell the ACSI emulation code tries to determine the
> > drive size from the root sector content, which is not correct. There
> > might have been (old) partitioning software that once placed the total
> > number of sectors there, but this is not standardized and also would
> > not help for unpartitioned drives.
> > I would expect fstat() or something similar to be used in order to
> > derive the number of blocks from the image file size.
>
> Ok, good hint, thanks, I've fixed this now, too.
Yes, this works fine now, thank you. Reading beyond the last sector is
not yet rejected, though.
Take care
Uwe