FAT12 DOS HD not working

[raidersan]

DIM fails when trying to create a DOS FAT12 HD image ("fail to create image")
It works if FAT16 or FAT32 is selected

[geraldholdsworth]

It seems I made a boo boo…kind of. Hard drives should ideally be FAT16 or FAT32. When DIM creates the images, it uses a set sector size of 512 bytes. This means that a maximum capacity for FAT12 should be about 31MB. Now, I could play around with sector sizes to get bigger capacities for FAT12, but why not just use FAT16? For now, I’ll reduce the minimum size for FAT12 HDD to 10MB and reduce the maximum size to 30MB. FAT16 and FAT32 will remain as is. From: raidersan ***@***.***> Reply to: geraldholdsworth/DiscImageManager ***@***.***> Date: Monday 20 January 2025 at 01:45 To: geraldholdsworth/DiscImageManager ***@***.***> Cc: Subscribed ***@***.***> Subject: [geraldholdsworth/DiscImageManager] FAT12 DOS HD not working (Issue #35) DIM fails when trying to create a DOS FAT12 HD image ("fail to create image") It works if FAT16 or FAT32 is selected — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[raidersan]

That makes sense. I believe I need FAT12 for MTCP netdrive images, that’s what I understood anyway, and it failed to recognise FAT16 images I tried. But there might have been another problem with my setup that actually would have failed on all images. Once the picomem/MTCP bug is resolved, I will try again with FAT16

[geraldholdsworth]

This should now be fixed with 1.47.5

I did consider fiddling with the sector size to allow bigger sizes, but the Microsoft White Paper warns against using any other value other that 512 bytes per sector. So, I've left it fixed at 512 bytes for now.