Microsoft KB Archive/104726: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 68: | Line 68: | ||
To work around this situation: | To work around this situation: | ||
# Ensure the floppy disk drives are empty and reboot your computer. | # Ensure the floppy disk drives are empty and reboot your computer. | ||
# When the | # When the "Starting MS-DOS..." prompt is displayed, press F5. | ||
# Run Microsoft Defragmenter (Defrag). | # Run Microsoft Defragmenter (Defrag). | ||
# Restart you computer. | # Restart you computer. |
Latest revision as of 09:43, 20 July 2020
Article ID: 104726
Article Last Modified on 11/18/1999
APPLIES TO
- Microsoft MS-DOS 6.2 Standard Edition
- Microsoft MS-DOS 6.22 Standard Edition
This article was previously published under Q104726
This information applies to both Microsoft DoubleSpace and Microsoft DriveSpace. For MS-DOS 6.22, use DRVSPACE in place of DBLSPACE for commands and filenames.
SYMPTOMS
When DoubleSpace restarts your computer to increase the DBLSPACE.INI MaxFileFragments setting (because your DoubleSpace-compressed drive is too fragmented to mount), your computer becomes trapped in an endless loop.
CAUSE
This problem occurs when a DoubleSpace-compressed drive on your hard disk drive is too fragmented to mount and you are booting your computer from a floppy disk (typically in drive A).
DoubleSpace modifies the DBLSPACE.INI file on the host drive for the overly fragmented DoubleSpace-compressed drive; DoubleSpace does not consider which drive is the boot drive.
RESOLUTION
To work around this situation:
- Ensure the floppy disk drives are empty and reboot your computer.
- When the "Starting MS-DOS..." prompt is displayed, press F5.
- Run Microsoft Defragmenter (Defrag).
- Restart you computer.
Additional query words: 6.20 6.22 stuck
Keywords: KB104726