Microsoft KB Archive/107471

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:04, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

Article ID: 107471

Article Last Modified on 9/30/1999


  • Microsoft Windows for Workgroups 3.11

This article was previously published under Q107471


When you try to open or copy a file larger than 2 megabytes (MB), you may receive one of the following error messages:

Segment Load Failure


Insufficient Memory


These errors occur if both of the following conditions exist:

  • You are using a permanent swap file without 32-bit disk access enabled. This causes paging to occur through MS-DOS.


  • You are using 32-bit file access. Since 32-bit disk access is disabled, the real-mode mapper (RMM.D32) is used to provide 32-bit file services.

These errors do not occur if the permanent swap file is on a drive with 32-bit disk access enabled or if 32-bit file access is disabled.


To work around these errors do one of the following:

  • If your hard disk controller is WD1003 compatible, enable 32-bit disk access.


  • Disable 32-bit file access.


Microsoft has confirmed this to be a problem in Microsoft Windows for Workgroups version 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Bases as it becomes available.


This size of the file needed to trigger this error is not always 2 MB. The limit is 512 multiplied by the size of the allocation unit for the drive where the target file resides. The allocation unit size is commonly 4096 bytes, thus the apparent 2 MB limit. In cases in which the allocation unit size is different, the limit is also different.

Additional query words: 3.11 errors out of memory vfat fastdisk incompatible incompatibility doesn't work not working

Keywords: KB107471