Recent Posts41
OsX86 Hackintosh (Intel / AMD) / Re: even if u have no PCIE slots SIL3124 on PCI133 still benefits OSX TIGER+
« Last post by chrisNova777 on April 06, 2026, 11:57:18 PM »whats the max size for fat32 partition under windows 9x
Gemini said
Under Windows 9x (specifically Windows 95 OSR2, Windows 98, and Windows Me), the theoretical and practical limits for FAT32 partitions are shaped by the architectural constraints of the era.
The Standard Partition Limit
While the FAT32 file system itself can theoretically support volumes up to 2TB, Windows 9x has a practical ceiling of 127GB (or approximately 137,438,953,472 bytes).
This limitation isn't strictly a "FAT32" issue, but rather a result of the 28-bit LBA (Logical Block Addressing) used in the standard IDE/ATA drivers of the time. Once you exceed 127GB, the addressing system runs out of bits to map sectors, which can lead to catastrophic data corruption as the system "wraps around" and begins overwriting the beginning of the disk.
Key Constraints and Factors
Scandisk and Defrag: Even if you use third-party drivers to bypass the 127GB limit, the built-in Windows 9x utilities like Scandisk and Disk Defragmenter are 16-bit applications. They typically struggle or crash on partitions larger than 32GB or 64GB because they cannot handle the massive amount of cluster information in memory.
Cluster Size: FAT32 uses clusters to manage data. On a large partition, a 32KB cluster size is standard. If the partition is too large, the number of clusters becomes too high for the 16-bit FAT tables to track efficiently under 9x.
The 32GB "Format" Limit: While Windows 9x can read and write larger partitions, Windows 2000 and XP introduced an artificial 32GB limit when formatting new FAT32 partitions to encourage users to switch to NTFS. To create a 120GB FAT32 partition for a Windows 98 build, you generally need to use the 98 FDISK utility or a third-party tool.
Recommended Best Practice
For maximum stability on vintage hardware, it is generally recommended to keep partitions at or below 32GB. If you are using a larger drive (like an 80GB or 120GB HDD), splitting it into several 32GB logical drives ensures that Scandisk and other system tools remain functional and prevents the "out of memory" errors common in late-90s DOS-based environments.
You said
whats the max size of afat32 partition under windows 98SE when connected to a SIL3124 card
Gemini said
When using a Silicon Image SiI3124 controller on Windows 98SE, you are stepping outside the standard IDE/ATA limitations, but you still face the architectural ceilings of the operating system itself.
The 128GB Threshold
The primary hurdle for Windows 98SE is the 28-bit LBA (Logical Block Addressing) limit. Standard Windows 98SE drivers cannot "see" or safely address storage space beyond 128GB (137GB decimal).
While the SiI3124 chip itself is a professional-grade SATA II controller that supports 48-bit LBA (allowing for Terabytes of storage), the Windows 9x driver is the bottleneck.
With standard drivers: You should not exceed a 120GB partition. Attempting to use a larger drive or partition will result in "wrap-around" data corruption once the 128GB mark is passed.
With 48-bit LBA Patches: If you use a third-party patch (such as the well-known Rudolph Loew's patch), Windows 98SE can theoretically handle FAT32 partitions up to 2TB.
Critical Constraints for the SiI3124
Even if you patch the OS to see the full size of a modern SATA drive, there are two major "soft" limits to consider for a stable build:
1. The Scandisk/Defrag Memory Wall
The 16-bit versions of SCANDISK.EXE and DEFRAG.EXE included with 98SE will fail on very large partitions.
32GB to 64GB: Usually the "sweet spot" for stability.
127GB+: Scandisk will likely report "Out of Memory" errors because it cannot track the massive number of clusters in a FAT32 table of that size.
2. The PCI Bus Saturation
The SiI3124 is a fast SATA II controller, but when plugged into a standard 32-bit PCI slot (like those on an ASUS P5PE-VM), it is capped at a theoretical maximum of 133MB/s.
While the card supports NCQ and Hot-Plug, using a massive partition (e.g., 500GB) doesn't provide a speed advantage; it only increases the time the system spends "thinking" during boot-up or disk repair cycles.
Recommendation for Your Setup
For a high-performance Windows 98SE build using that specific card:
Primary Partition: Keep your boot partition (C:) at 32GB. This ensures all native 98SE utilities work perfectly.
Extended Partitions: If you have a larger SATA drive, use FDISK (or a tool like Partition Magic) to create additional logical drives (D:, E:, etc.) in 32GB or 64GB chunks.
Total Disk Size: If you haven't patched the system for 48-bit LBA, do not use a physical drive larger than 120GB, regardless of how many partitions you make.
Gemini said
Under Windows 9x (specifically Windows 95 OSR2, Windows 98, and Windows Me), the theoretical and practical limits for FAT32 partitions are shaped by the architectural constraints of the era.
The Standard Partition Limit
While the FAT32 file system itself can theoretically support volumes up to 2TB, Windows 9x has a practical ceiling of 127GB (or approximately 137,438,953,472 bytes).
This limitation isn't strictly a "FAT32" issue, but rather a result of the 28-bit LBA (Logical Block Addressing) used in the standard IDE/ATA drivers of the time. Once you exceed 127GB, the addressing system runs out of bits to map sectors, which can lead to catastrophic data corruption as the system "wraps around" and begins overwriting the beginning of the disk.
Key Constraints and Factors
Scandisk and Defrag: Even if you use third-party drivers to bypass the 127GB limit, the built-in Windows 9x utilities like Scandisk and Disk Defragmenter are 16-bit applications. They typically struggle or crash on partitions larger than 32GB or 64GB because they cannot handle the massive amount of cluster information in memory.
Cluster Size: FAT32 uses clusters to manage data. On a large partition, a 32KB cluster size is standard. If the partition is too large, the number of clusters becomes too high for the 16-bit FAT tables to track efficiently under 9x.
The 32GB "Format" Limit: While Windows 9x can read and write larger partitions, Windows 2000 and XP introduced an artificial 32GB limit when formatting new FAT32 partitions to encourage users to switch to NTFS. To create a 120GB FAT32 partition for a Windows 98 build, you generally need to use the 98 FDISK utility or a third-party tool.
Recommended Best Practice
For maximum stability on vintage hardware, it is generally recommended to keep partitions at or below 32GB. If you are using a larger drive (like an 80GB or 120GB HDD), splitting it into several 32GB logical drives ensures that Scandisk and other system tools remain functional and prevents the "out of memory" errors common in late-90s DOS-based environments.
You said
whats the max size of afat32 partition under windows 98SE when connected to a SIL3124 card
Gemini said
When using a Silicon Image SiI3124 controller on Windows 98SE, you are stepping outside the standard IDE/ATA limitations, but you still face the architectural ceilings of the operating system itself.
The 128GB Threshold
The primary hurdle for Windows 98SE is the 28-bit LBA (Logical Block Addressing) limit. Standard Windows 98SE drivers cannot "see" or safely address storage space beyond 128GB (137GB decimal).
While the SiI3124 chip itself is a professional-grade SATA II controller that supports 48-bit LBA (allowing for Terabytes of storage), the Windows 9x driver is the bottleneck.
With standard drivers: You should not exceed a 120GB partition. Attempting to use a larger drive or partition will result in "wrap-around" data corruption once the 128GB mark is passed.
With 48-bit LBA Patches: If you use a third-party patch (such as the well-known Rudolph Loew's patch), Windows 98SE can theoretically handle FAT32 partitions up to 2TB.
Critical Constraints for the SiI3124
Even if you patch the OS to see the full size of a modern SATA drive, there are two major "soft" limits to consider for a stable build:
1. The Scandisk/Defrag Memory Wall
The 16-bit versions of SCANDISK.EXE and DEFRAG.EXE included with 98SE will fail on very large partitions.
32GB to 64GB: Usually the "sweet spot" for stability.
127GB+: Scandisk will likely report "Out of Memory" errors because it cannot track the massive number of clusters in a FAT32 table of that size.
2. The PCI Bus Saturation
The SiI3124 is a fast SATA II controller, but when plugged into a standard 32-bit PCI slot (like those on an ASUS P5PE-VM), it is capped at a theoretical maximum of 133MB/s.
While the card supports NCQ and Hot-Plug, using a massive partition (e.g., 500GB) doesn't provide a speed advantage; it only increases the time the system spends "thinking" during boot-up or disk repair cycles.
Recommendation for Your Setup
For a high-performance Windows 98SE build using that specific card:
Primary Partition: Keep your boot partition (C:) at 32GB. This ensures all native 98SE utilities work perfectly.
Extended Partitions: If you have a larger SATA drive, use FDISK (or a tool like Partition Magic) to create additional logical drives (D:, E:, etc.) in 32GB or 64GB chunks.
Total Disk Size: If you haven't patched the system for 48-bit LBA, do not use a physical drive larger than 120GB, regardless of how many partitions you make.