DriveSpace Real-Mode Driver May Not Be Removed from Memory

ID: Q134364


The information in this article applies to:


SYMPTOMS

The real-mode memory (conventional or upper) used by DriveSpace (Drvspace.bin or Dblspace.bin) may not be reclaimed when you start Windows. This may cause problems with MS-DOS-based programs that require more conventional memory than is available.

Normally, Drvspace.bin (or Dblspace.bin) is unloaded from memory when the 32-bit DriveSpace driver (Drvspacx.vxd) is initialized at Windows 95 startup.


CAUSE

This problem can occur for any of the following reasons:


RESOLUTION

To resolve this problem, use one or more of the following methods:


MORE INFORMATION

The real-mode DriveSpace driver (Drvspace.bin or Dblspace.bin) is normally unloaded from memory when the 32-bit DriveSpace driver (Drvspacx.vxd) is initialized at Windows startup. This frees conventional memory for running MS-DOS-based programs.

The real-mode DriveSpace driver is required for accessing compressed drives when Windows is not running. If you have an MS-DOS-based program that requires MS-DOS mode, you may need to do one of the following:

Additional query words: winboot.ini dynload VxD


Keywords          : kbenv winplus win95 win98 
Version           : 95
Platform          : WINDOWS 
Issue type        : kbprb 

Last Reviewed: January 21, 1999