FAT32 drive on GPT (Miscellaneous)
> For GPT entries, there is no distinction between FAT and NTFS partitions.
> Both have partition type EBD0A0A2-B9E5-4433-87C0-68B6B72699C7.
In GPT, these are all classified as "Microsoft Basic Data" (which also covers exFAT). Even though there are plenty of bits to distinguish between the various partition types (way more than the single byte provided by MBR) MS decided for some reason to ignore that capability.
> If the non-FAT partitions do not get a drive letter assigned at boot, there
> is no way to reformat a such partition under FreeDOS with a FAT filesystem,
> at least with the format utility currently provided by FreeDOS.
>
> Perhaps this behaviour should be configurable?
In my USB program, by default it only assigns drive letters to compatible (FAT-formatted) partitions. To identify what's in the partition, though, it can't use the GPT entry. It must look at the data in the first sector (volume boot record) of the partition to see what's actually there (if anything).
This is different than MBR, where you can (at least theoretically) tell how a partition/volume is _supposed_ to be formatted (even if it hasn't yet been formatted) by the partition type value in the MBR.
The USB program also has a command-line option to mount non-compatible partitions (like NTFS or exFAT or non-formatted partitions) as drive letters so they can (at least theoretically) be (re)formatted by a DOS program. Of course, that's a dangerous thing to do unless you're _really_ sure you know what you're doing.
It seems like it might also be possible to create a FORMAT program that doesn't require a drive letter as input. I know there are some partition managers that will format the partitions they create (FDISK doesn't do that). Maybe that's the better approach, but it seems like it would also be possible to create a "smarter" FORMAT program that could make up for some of the shortcomings in FDISK?
Complete thread:
- FAT32 drive on GPT - CandyMan, 30.08.2023, 18:15 (Miscellaneous)
- FAT32 drive on GPT - RayeR, 30.08.2023, 20:21
- FAT32 drive on GPT - bretjohn, 31.08.2023, 01:27
- FAT32 drive on GPT - tom, 31.08.2023, 10:31
- FAT32 drive on GPT - boeckmann, 31.08.2023, 14:52
- FAT32 drive on GPT - tom, 01.09.2023, 17:32
- FAT32 drive on GPT - CandyMan, 31.08.2023, 18:27
- FAT32 drive on GPT - tom, 01.09.2023, 17:24
- FAT32 drive on GPT - CandyMan, 01.09.2023, 19:11
- FAT32 drive on GPT - boeckmann, 01.09.2023, 19:29
- FAT32 drive on GPT - tom, 01.09.2023, 22:52
- FAT32 drive on GPT - CandyMan, 02.09.2023, 00:14
- FAT32 drive on GPT - bretjohn, 02.09.2023, 03:39
- FAT32 drive on GPT - boeckmann, 02.09.2023, 12:54
- FAT32 drive on GPT - ecm, 02.09.2023, 14:07
- FAT32 drive on GPT - boeckmann, 02.09.2023, 15:17
- FAT32 drive on GPT - ecm, 02.09.2023, 14:07
- FAT32 drive on GPT - tom, 02.09.2023, 21:51
- FAT32 drive on GPT - boeckmann, 02.09.2023, 12:54
- FAT32 drive on GPT - RayeR, 02.09.2023, 21:14
- FAT32 drive on GPT - tom, 01.09.2023, 22:52
- FAT32 drive on GPT - 0ffer, 02.01.2024, 20:05
- FAT32 drive on GPT - ecm, 03.02.2024, 19:08
- FAT32 drive on GPT - boeckmann, 01.09.2023, 19:29
- FAT32 drive on GPT - CandyMan, 01.09.2023, 19:11
- FAT32 drive on GPT - tom, 01.09.2023, 17:24
- FAT32 drive on GPT - RayeR, 02.09.2023, 21:19
- FAT32 drive on GPT - boeckmann, 31.08.2023, 14:52
- FAT32 drive on GPT - mceric, 30.08.2023, 22:54
- FAT32 drive on GPT - RayeR, 30.08.2023, 20:21