Floppy speed

mark_k · 04 September 2016, 20:11

Just wondering, are all floppy speed options (turbo, 200/400/800%) supposed to work OK with the ROM trackdisk.device code?

Because I got log messages like this with an NTSC A1000, Kick/WB 1.1, floppy drive speed 400% config:
disk raw write: image file's track 80 is too small (12668 < 12798)!
disk raw write: image file's track 84 is too small (12668 < 12798)!
disk raw write: image file's track 92 is too small (12668 < 12798)!
disk raw write: image file's track 80 is too small (12668 < 12798)!

Toni Wilen · 10 September 2016, 09:10

It is "save image" (which is extended adf) having too small reserved sector size. NTSC needs a bit more space (slightly higher clock but same rotation speed = about 130 more raw bits can fit on disk if system is NTSC) but save image creator always used PAL size unless emulation was already started and in NTSC mode.

It should have always created largest possible size that Amiga can write.

mark_k · 10 September 2016, 16:23

Ah OK. As a workaround, could you save the last 12668 bytes of the data written to the ext.ADF? Since the first bytes written are the gap that would at least allow "normal" disk formats to still work.

Toni Wilen · 10 September 2016, 21:46

Quote:

Originally Posted by mark_k

Ah OK. As a workaround, could you save the last 12668 bytes of the data written to the ext.ADF? Since the first bytes written are the gap that would at least allow "normal" disk formats to still work.

Why not just re-create the save image file? It would be empty anyway in this case

mark_k · 10 September 2016, 21:56

Could some users have "PAL-only" extended ADF files (not necessarily automatically-created save images) which would otherwise not work correctly when used with an NTSC config? Or does the Create Custom Disk button always create full-size files?

04 September 2016, 20:11	#1
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,336	Floppy speed Just wondering, are all floppy speed options (turbo, 200/400/800%) supposed to work OK with the ROM trackdisk.device code? Because I got log messages like this with an NTSC A1000, Kick/WB 1.1, floppy drive speed 400% config: disk raw write: image file's track 80 is too small (12668 < 12798)! disk raw write: image file's track 84 is too small (12668 < 12798)! disk raw write: image file's track 92 is too small (12668 < 12798)! disk raw write: image file's track 80 is too small (12668 < 12798)!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
force global floppy speed	DaveMB	support.FS-UAE	16	26 October 2013 07:59
Floppy Drive Emulation Speed and available memory	Supamax	support.WinUAE	20	13 October 2009 06:12
Floppy Drive Emulation Speed...	DamienD	support.WinUAE	7	12 September 2005 17:32
Floppy Speed	BenniP	support.WinUAE	13	14 June 2004 20:58
WinUAE Floppy Speed	Critter	support.WinUAE	2	25 November 2003 14:52

10 September 2016, 09:10	#2
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,506	It is "save image" (which is extended adf) having too small reserved sector size. NTSC needs a bit more space (slightly higher clock but same rotation speed = about 130 more raw bits can fit on disk if system is NTSC) but save image creator always used PAL size unless emulation was already started and in NTSC mode. It should have always created largest possible size that Amiga can write.

10 September 2016, 16:23	#3
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,336	Ah OK. As a workaround, could you save the last 12668 bytes of the data written to the ext.ADF? Since the first bytes written are the gap that would at least allow "normal" disk formats to still work.

10 September 2016, 21:56	#5
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,336	Could some users have "PAL-only" extended ADF files (not necessarily automatically-created save images) which would otherwise not work correctly when used with an NTSC config? Or does the Create Custom Disk button always create full-size files?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)