The Format Dialog in Windows NT

Legacy Windows format dialog & modern replacements

• Many appreciate the original NT-era format dialog as simple, clear, and still “good enough,” especially compared to more “elegant” modern UIs.
• Others note a newer disk/formatting UI exists under Settings → Storage → Disks & volumes; it matches modern themes and integrates some Disk Manager functions, but lacks graphical disk layout views and still uses MB for sizes.
• Some lament loss of other classic utilities’ UIs (e.g., the old defragmenter block view).

Temporary solutions becoming permanent

• Widely repeated theme: “temporary” solutions often become effectively permanent if they work and reduce the urgency to replace them.
• Stories from large enterprises: production systems full of stacked “temporary fixes” and intern-written “POCs” that became core components.
• Debate over whether this is a failure (technical debt) or efficient engineering if the solution lasts decades without major issues.

FAT32 32GB limit and filesystem choices

• Commenters confirm experimentally and via leaked source that the 32GB FAT32 limit is enforced below the UI level (shared by format.com, diskpart, Disk Management).
• Some argue the limit likely came later (Windows 2000), not in the original NT4 dialog, and speculate it may have been used to push users toward NTFS.
• Discussion of FAT32 vs exFAT:
  • FAT32 is widely compatible but limited to 4GB files; useful for older or embedded devices and retro gaming hardware.
  • exFAT removes practical size limits and is natively supported on major OSes, but has patent history, some device gaps, and reports of macOS driver reliability issues.
  • Large FAT32 volumes formatted on Linux/*BSD work fine in Windows despite the Windows-side creation limit.

Debate over the original developer’s role & credibility

• Some commenters praise the developer’s historical contributions and storytelling; others argue they exaggerate their role (e.g., claiming credit for FAT32 size decisions or ZIP support).
• Evidence from old installers and vendor sites indicates Windows Zip folders use a third‑party compression library, with the Windows work being the shell/Explorer integration rather than the compression engine itself.
• A detailed subthread surfaces a past state legal case over a registry-cleaner/“security” product company the developer ran, and whether that permanently undermines trust.
• Counterarguments emphasize that legal penalties were paid, the issue is public, and perpetual condemnation is unfair if there’s no sign of reoffending.

Source leaks, verification, and memory

• Commenters use leaked NT4/NT5/XP source (now mirrored on GitHub) to verify dates and responsibilities for the format dialog and FAT32 behavior.
• There’s acknowledgement that human memory is unreliable, especially for decades-old events retold many times; some misstatements may be honest misremembering rather than intentional deceit.

UI/UX and tooling comparisons

• Several contrast Windows’ discoverable, kid-friendly “right-click → Format…” with Unix-like mkfs workflows, which are powerful but riskier and require more prior knowledge.
• Graphical Linux tools (e.g., GNOME disks, partitioners) are mentioned as higher-level, safer alternatives.
• Broader frustrations about modern enterprise tools (e.g., Salesforce for ticketing) underscore an appreciation for older, more focused systems like Remedy.

Views on “do it right” vs perfectionism

• Some argue you shouldn’t ship until you’re “proud” of the solution; others warn this can degrade into perfectionism and shipping paralysis.
• A recurring compromise view: “good enough” is acceptable if problems are minor and resources are better spent on more impactful improvements.