OSDev.org

The 1.44MB FAT32 floppy disk.

Compatible with Windows (XP and above) and Linux as a FAT32 file system as a mounted image or real floppy disk.
Fully compatible with the MS FAT32 specification.

Would anyone care to explain what the point is here?

Hi,

onlyonemac wrote:Would anyone care to explain what the point is here?

Mikegonta made a BIOS extender for protected mode and implemented a FAT32 driver for MikeOS. He shows off that Windows XP can read a physical floppy formatted with FAT32, and then he is showing MikeOS booting from the floppy. Curiously, the floppy has 32 MB capacity.


Regards,
glauxosever

glauxosdever wrote:Mikegonta

Mike Gonta

.... made a BIOS extender for protected mode

Indeed I did, it's called SudoBIOS. In this case however, the MikeOS is 16-bit real mode.
I'll be releasing the 32-bit protected mode version soon.

.... and implemented a FAT32 driver for MikeOS.

Actually, the FAT32 driver is exactly the same as the simple MikeOS FAT12 driver, merely adapted for FAT32 and simplified.

He shows off that Windows XP can read a physical floppy formatted with FAT32,

I'm sure all versions of Windows since can read/write it as well, (Windows98 and DOS can't, but probably due to assumptions
they make concerning floppy disks) the XP machine was simply at hand and I don't presently have a USB floppy drive.

.... and then he is showing MikeOS booting from the floppy.

Also boots and runs from Qemu/Bochs and a USB flash drive on real hardware.

Curiously, the floppy has 32 MB capacity.

The floppy disk (and image) are limited to 1.44 MB, however since Windows will not recognize a FAT32 volume smaller than
32.5 MB some technical trickery was employed.

That's why floppy disks are usually formatted with fat12.

Techel wrote:That's why floppy disks are usually formatted with fat12.

And, that's why the beginner is still using a FAT12 image to start off with.
The MikeOS FAT32 driver is actually simpler than the original FAT12 driver (which I merely modified and simplified).
Say goodbye to FAT12 (and FAT16) and hello to FAT32.

PS. It's not a joke and the floppy disk is real - the image (and basic format) will boot and run from a USB flash drive
on real hardware and work in Qemu/Bochs.

But why hacking with fat32 on floppy disks if you could also use fat12?

Techel wrote:But why hacking with fat32 on floppy disks if you could also use fat12?

Why hack on FAT12 when you can use FAT32?

PS. It has absolutely nothing to do with floppy disks - that was only to get your attention.

Ok, my attention was successfully grabbed
Do what you want to.

Techel wrote:But why hacking with fat32 on floppy disks if you could also use fat12?

Because it sounds really cool!

onlyonemac wrote:

Techel wrote:But why hacking with fat32 on floppy disks if you could also use fat12?

Because it sounds really cool!

The really cool thing is the adaption of the MikeOS FAT12 to FAT32.
The FAT12 floppy disk (image) has long since been the mainstay of the simple OS and standalone system.
Now an even simpler FAT32 system is available.

Well congratulations. You just increased filesystem overhead to some 20% of your actual disk space. I'm sure it was worth it

Hi,

Combuster wrote:Well congratulations. You just increased filesystem overhead to some 20% of your actual disk space. I'm sure it was worth it

Fun facts:

• For FAT12 for a 1440 KiB volume you get 2880 clusters, so that one "cluster allocation table" costs 2880*1.5 = 4320 bytes, which (rounded up to the nearest sector) consumes 4608 bytes or 0.31% of the disk.
• For FAT32 the minimum volume size is 65525 (512-byte) clusters and for this case one "cluster allocation table" costs 65525*4 = 262100 bytes, which (rounded up to the nearest sector) consumes 262144 bytes or 17% of the disk.
• FAT typically uses 2 "cluster allocation tables" (where the second is for redundancy, which is important for floppy where read errors are far more common). The total space consumed by both cluster allocation tables for FAT12 is 0.625% of a 1440 KiB floppy, and FAT32 total space consumed by both cluster allocation tables is a massive 35.5% of a 1440 KiB disk.
• Because the minimum volume size for FAT32 is larger than 1440 KiB (it's roughly 32 MiB) the extra sectors/clusters that can't exist have be marked as faulty, so the majority of the 35.5% consumed by cluster allocation tables is used to convince an OS not to use sectors that don't exist.

mikegonta wrote:The really cool thing is the adaption of the MikeOS FAT12 to FAT32.

I disagree. A "really cool" thing would be an OS that doesn't have the massive security and performance problems caused by using (any version of) FAT for storing critical files needed for booting.


Cheers,

Brendan

Combuster wrote:Well congratulations. You just increased filesystem overhead to some 20% of your actual disk space. I'm sure it was worth it

It certainly was considering the space savings in the MikeOS-4.5 FAT32 (16-bit real mode) FAT32 driver which uses no 32-bit variables
in any form (instructions, registers, combined registers or memory).

Brendan wrote:I disagree. A "really cool" thing would be an OS that doesn't have the massive security and performance problems caused by using (any version of) FAT for storing critical files needed for booting.

Since when was MikeOS about security anyway? It's about a low-level operating system that's easy to understand and hack around with (and on).