Re: [hatari-devel] REGRESSION: Creating and Reading HD floppies in Hatari 1.7

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On sunnuntai 21 heinäkuu 2013, Bob Carpenter wrote:
> On Atari-Forum, someone reported a problem creating HD floppies and
> reading them in Hatari. DD floppies worked fine. He was using TOS 3.06
> in TT emulation mode. However, I recreated the problem in ST mode using
> TOS 2.06. When you attempt to read the floppy that you created, you get
> a "Data on the disk in drive A: may be damaged" error.

Thanks for reporting this.  I can reproduce this.

Opening the disk goes OK, but trying e.g. to show its information fails.
With EmuTOS, disk info is shown, but it's bogus, it claims disk size
to be GBs, not 1.44MB.


> Of course, that
> is assuming you inserted the disk into drive A. To be sure, I tried
> inserting the floppy I created into drive B:, but I received the same
> error.
> 
> I used the Hatari "Create Blank Floppy" menu item in order to create the
> floppy. However, the forum poster also used mkdosfs on his Kubuntu system
> and could not read the floppy in Hatari.

I tested both methods and Hatari fails to read both of them.  Problem
happens also with ED (2.88 MB, 36 sector) floppies, not just HD.


> He said this worked on 1.6.

floppy.c hasn't been modified in the meanwhile, so it's probably the new,
more accurate FDC code.  To get HD floppies working on the real HW, one
needed to provide double rate [1] floppy step motor.  Maybe same is needed
now with the new FDC code?

Nicolas, any comments?


There's no HW for detecting HD floppies, so they probably need to be
identified by their sector count (18 for HD, 36 for ED, that's all
that needs to be supported as those are what Hatari creates).


> Here is the original Atari-Forum link in case you are interested:
> http://www.atari-forum.com/viewtopic.php?f=51&t=25184&p=234683#p234683


	- Eero

[1] In my ST, that required one rusty NAND chip and few wires
    (despite chip's legs being rusty, it was working at least
     couple of years ago when I last tested it).