Re: [hatari-devel] HD drive & partition limits

[Thomas Huth <th.huth@xxxxxx>]

Am Sun, 29 Jun 2014 19:00:15 +0200
schrieb Adam Kłobukowski <adamklobukowski@xxxxxxxxx>:

> W dniu 26.06.2014 19:17, Eero Tamminen pisze:
> > Hi,
> >
> > On torstai 26 kesäkuu 2014, Adam Klobukowski wrote:
> >>> According to HD driver FAQ:
> >>>          http://hddriver.seimet.de/en/faq.html
> >>>
> >>> ST/STE HW limit is 1GB:
> >>> "With the ACSI bus of the ST/STE mass storage devices with a
> >>> capacity > 1 GiB can only be used with their full capacity with
> >>> suitable host adapters or
> >>> memory card adapters."
> >>
> >> I hoped  Hatari already emulates those 'suitable' host adapters.
> >
> > No.  Everything Hatari emulates is listed in the documentation:
> > http://hg.tuxfamily.org/mercurialroot/hatari/hatari/raw-
> > file/tip/doc/manual.html#Features
> >
> > If you're considering contributing emulation for host adapter(s)
> > to Hatari, please go ahead! :-)
> >
> > (I don't think anybody of current developers has interest
> > on that, so it needs to come from outside.)
> >
> >
> >>>> I think I tried 1GB too.
> >>>
> >>> What sized partitions you used?
> >>
> >> 256MB
> >>
> >>> Partition max size limits are following for different TOS
> >>> versions:
> >>> - TOS >= 4.x: 1024MB
> >>> - TOS >=1.04:  512MB
> >>> - older TOS:   256MB
> >>>
> >>> Did you make *really* sure that partition content was using
> >>> correct FAT16 format?  Note also that some TOS versions corrupt
> >>> data on drives with VFAT directory entries.
> >>>
> >>> MiNT & MagiC support FAT32 & ext2 partitions which don't have
> >>> these limits, but you need to boot them from smaller FAT16
> >>> partition on C:.
> >>
> >> I ws not even close to trying to use VFAT. Usually everything got
> >> corrupted after I wrote first files on partition.
> >
> > What you used to format the partition?
> 
> AHDI 5

I just tried to create a hard disk image with 256 MB partitions with
AHDI here, too, but AHDI even crashed during boot with such big
partitions. It works when I use a partition that is a little bit
smaller, so I guess this is a bug in AHDI?

> I'm trying to run STVidPLay, it completly bypases driver and calls
> ACSI by itself.

I tried to install that on my HD image, too, but with AHDI it only says
"unable to determine file location" or so. It works fine when I install
the (demo version of) HDDriver, though. Quite impressive to see such
movies on a stock (emulated) ST :-)

 Thomas