Creating Big FAT32 partitions in Windows XP


Recommended Posts

Windows XP doesn't let you format a partition with FAT32 if it is bigger than 32GB. This is obviously to force you to use NTFS. But if, like me, you want a big partition that can be read by many OSes including Windows, Linux and OSX then you have to use FAT32.

To do this, first you must create your partition, it is probably best to use windows disk management to do this.

Right click on My Computer and select Manage. Then select Disk Management from the left. Now find some unallocated space on one of your disks. Right click on the unallocated space and select New Partition.

Press next, select primary partition. Press next, enter the size of your new partition, the number that's in there by default is the ammount of unallocated space on your disk and thus the maximum size for the partition. Press next, select a drive letter of your choice (it can be changed later). Press next, select do not format this partition. Then press next and then finish.

Now you have a new partition that is not yet formatted.

To format the big partition with FAT32 you have to use Linux mkdosfs for Windows NT/2K/XP. There might be other ways, but this is what I used and it worked perfectly. You can download mkdosfs from here: http://www.mager.org/mkdosfs/

Download mkdosfs.zip and extract it.

mkdosfs.exe is a command line program so when you extract it put it somewhere easy to access like C:. Now, press start then run and type cmd. Now, assuming you put mkdosfs.exe on C: type C:\mkdosfs

That should give you instruction on how to use the program. If it doesn't then you haven't typed in the path of the program correctly.

To format a partition you must type this into cmd:

C:\mkdosfs -F 32 -n <partition name> -v <drive letter>

Where <partition name> is a name of your choice for your new partition and <drive letter> is the drive letter of the partition you want to format. *Don't get the drive letter wrong!*

Once you have typed that in and pressed enter, the program should give you some information about your new partition like this:

mkdosfs 2.8 (28 Feb 2001)

Win32 port by Jens-Uwe Mager

\\.\<drive letter> has 255 heads and 63 sectors per track,

logical sector size is 512,

using 0xf8 media descriptor, with 390716865 sectors;

file system has 2 32-bit FATs and 8 sectors per cluster.

FAT size is 380816 sectors, and provides 48744400 clusters.

Volume ID is 4149e22c, volume label <partition name> .

It will be unresponsive while it formats the drive, but it only took about 30 seconds to format my 200GB partition.

Note the -F 32 part of the command. mkdosfs can format FAT12 and FAT16 partitions with the relevant command. If you don't include -F 32 then mkdosfs will use either FAT12 or FAT16 so make sure you do put that bit on.

So there you go, now you have a FAT32 partition bigger than 32GB that can be read and written to by many OSes and you didn't even have to leave Windows XP (Y)

Edited by BobMarley

Only during the setup portion.

Disk Management does not let you format a partition with FAT32 if it's bigger than 32GB.

but can that program work its wonders on serial ATA drives of 200GB, that would be lovely

Yes, it was a 200GB SATA drive that I used it on :)

None really. The only benefit is the cross platform support. If you only use windows, use NTFS.

Cross platform support?? Linux and OSX both can "READ" ntfs just fine..

I see no point in using FAT32 as a filesystem - unless your using a OS that does not support NTFS.. And who is stilling use 9x?

Cross platform -- then why not just ext2 or 3? XP can read/write to ext2/3

http://www.fs-driver.org/index.html

And so can OSX..

http://sourceforge.net/projects/ext2fsx/

FAT32 is an antiquated file system used by antiquated OSs -- move forward people ;) And I agree with roadwarrior -- if your going to be using other OSs anyway -- why not just create the filesystem with one of them?

Cross platform support?? Linux and OSX both can "READ" ntfs just fine..

I see no point in using FAT32 as a filesystem - unless your using a OS that does not support NTFS.. And who is stilling use 9x?

Cross platform -- then why not just ext2 or 3? XP can read/write to ext2/3

http://www.fs-driver.org/index.html

And so can OSX..

http://sourceforge.net/projects/ext2fsx/

FAT32 is an antiquated file system used by antiquated OSs -- move forward people ;) And I agree with roadwarrior -- if your going to be using other OSs anyway -- why not just create the filesystem with one of them?

Exactly!! :whistle:

Cross platform support?? Linux and OSX both can "READ" ntfs just fine..

But they can't write to NTFS, which is half the issue! Fat32 is still needed. Don't believe me? Get an ipod and try to use it on both Mac and windows with it formatted in anything other than fat32.

Cross platform support?? Linux and OSX both can "READ" ntfs just fine..

I see no point in using FAT32 as a filesystem - unless your using a OS that does not support NTFS.. And who is stilling use 9x?

Cross platform -- then why not just ext2 or 3? XP can read/write to ext2/3

http://www.fs-driver.org/index.html

...

FAT32 is an antiquated file system used by antiquated OSs -- move forward people ;) And I agree with roadwarrior -- if your going to be using other OSs anyway -- why not just create the filesystem with one of them?

First of all, those FS Drivers are poorly made, do not work too well, and cause issues when formatting drives / noticing drives. Secondly; what if the person formats with something such as ResierFS? Support is lacking even-moreso in that. FAT32 is just a known, well used standard is cross-platform. The having LInux and such write to it, is a plus aswell.

So, moving forward for those other OSes is not an option. :unsure:

Sure, it sucks; but it helps when running a server, or something old. I should know, I just started doing so and have found this to be a crux problem.

And I agree with roadwarrior -- if your going to be using other OSs anyway -- why not just create the filesystem with one of them?

Because you can format it with Windows XP fine like I have shown in this guide. I don't understand you people, I created this because I like to pass on information in the hope that it will be useful. What is the point of posting here about how bad FAT32 is or why you shouldn't do it?

To those that said thanks, you're welcome :)

  • 1 month later...

Hmm, didn't work out very well. Here's what happens:

C:\>mkdosfs -v -F 32 -n USB1 G:

mkdosfs 2.8 (28 Feb 2001)

Win32 port by Jens-Uwe Mager <[email protected]>

mkdosfs: unable to get length for '\\.\G:'

What might be wrong?

How did you make the partition G:? If the partition is already formatted then that might not work, I don't know since i've never tried it. Try deleting the partition using Windows Disk Management and then follow the guide to make another one.

To all those saying that FAT32 is really inefficient on big drives, Microsoft has really exagerated the facts. On my music partition I have 60GB of data that is about 10,000 1-10MB files. The extra data that the FAT32 innefiency has created is about 20MB. I'm not complaining at that.

The only real downside is the 4GB file size limit and lack of security features. Everything else has been exagerated by Microsoft.

Edited by BobMarley
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
    • It is when it's a desktop in my house though for a PC that's lightly used and not really important when it is. If it was a laptop, it would be a different story. The real solution is varied and begins starting at post #22 in that thread.
    • Win11Debloat 2026.06.14 by Razvan Serea Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience. It can remove pre-installed bloatware apps, disable telemetry, remove intrusive interface elements and much more. The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the option to make changes to other Windows users. All changes made by Win11Debloat can be easily reversed, and most removed apps can be restored via the Microsoft Store. A full guide on how to undo the changes is available here. Win11Debloat features: Below is an overview of the key features and functionality offered by Win11Debloat. Please refer to the wiki for more information about the default settings preset. Remove a wide variety of preinstalled apps. Click here for more info. Disable telemetry, diagnostic data, activity history, app-launch tracking & targeted ads. Disable tips, tricks, suggestions & ads across Windows. Disable Windows location services & app location access. Disable Find My Device location tracking. Disable 'Windows Spotlight' and tips & tricks on the lock screen. Disable 'Windows Spotlight' desktop background option. Disable ads, suggestions and the MSN news feed in Microsoft Edge. Hide Microsoft 365 ads on the Settings 'Home' page, or hide the 'Home' page entirely. Disable & remove Microsoft Copilot. Disable Windows Recall. Disable Click to Do, AI text & image analysis tool. Prevent AI service (WSAIFabricSvc) from starting automatically. Disable AI Features in Edge. Disable AI Features in Paint. Disable AI Features in Notepad. Disable the Drag Tray for sharing & moving files. Restore the old Windows 10 style context menu. Turn off Enhance Pointer Precision, also known as mouse acceleration. Disable the Sticky Keys keyboard shortcut. Disable Storage Sense automatic disk cleanup. Disable fast start-up to ensure a full shutdown. ...and more. Once you’ve downloaded the Win11Debloat file (Get.ps1), just follow these quick steps: Locate the Get.ps1 script file. Right-click the file and select Run with PowerShell from the context menu. If prompted by User Account Control (UAC), select Yes to grant the script the necessary administrative permissions. Win11Debloat 2026.06.14 changes: This is a minor release that hopefully addresses the false positives in Windows Defender and Bitdefender that prevented users from downloading and/or running Win11Debloat. Refactor Get-RegFileOperations.ps1 to address false positives by @Raphire in #626 Add logging around WinGet app retrieval and increase timeout to 20s by @Raphire Download: Win11Debloat 2026.06.14 | Open Source View: Win11Debloat Home Page | Screenshots 1| 2 Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!