DriveSpace Real-Mode Driver May Not Be Removed from Memory
ID: Q134364
|
The information in this article applies to:
-
Microsoft Windows 95
-
Microsoft Plus! for Windows 95
-
Microsoft Windows 98
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:
- You booted to a command prompt, then started Windows by typing
"win." The real-mode memory used by Drvspace.bin (or Dblspace.bin)
cannot be reclaimed if you interrupt the normal Windows boot process.
- You loaded Drvspace.bin (or Dblspace.bin) in upper memory using the
following line:
devicehigh=<path>\drvspace.sys /move
The real-mode memory used by Drvspace.bin (or Dblspace.bin) cannot be
reclaimed if it is loaded into an upper memory block (UMB).
- LoadTop=0 appears in the Msdos.sys file.
A setting of 0 does not let Windows load Drvspace.bin (or
Dblspace.bin) at the top of conventional memory (just below 640K). This
prevents the unloading of Drvspace.bin (or Dblspace.bin) at Windows
startup.
- The 32-bit DriveSpace driver (Drvspacx.vxd) is not loaded.
To determine if Drvspacx.vxd is loaded, run DriveSpace, then click
About DriveSpace on the Help menu. The following table lists by product
the compression driver filenames, sizes, and versions as reported in
DriveSpace. "Dblspace.bin" can be substituted for "Drvspace.bin" in
this table.
Filename Product File Size About DriveSpace
------------------------------------------------------------------
Drvspace.bin Windows 95 71,287 Real-mode driver version 2
Drvspace.bin MS Plus! 64,135 Real-mode driver version 3
Drvspacx.vxd Windows 95 54,207 32-bit driver version 2
Drvspacx.vxd MS Plus! 61,719 32-bit driver version 3
Drvspace.bin Windows 98 68,871 Real-mode driver
Drvspacx.vxd Windows 98 57,642 32-bit driver
- Dblspace.bin remains in memory if you are using a configuration
consisting of Drvspace.ini and Dblspace.bin. In this configuration,
the Dblspace.bin file is loaded as an installable device driver and is
not transitioned to Drvspacx.vxd. If you use both Dblspace.bin and
Drvspace.bin with Drvspace.ini, Drvspace.bin is given priority and this
behavior does not occur.
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:
- Optimize conventional memory.
NOTE: As stated above, Windows cannot unload the real-mode Drive-
Space driver if it is loaded into upper memory.
- Create a special startup floppy disk. You can then use that disk to
start your computer without DriveSpace, and then run your program from
your uncompressed drive.
For more information about this procedure, see the "Freeing
Conventional Memory for Running MS-DOS Programs" section of the
Microsoft Plus! Readme file for DriveSpace and Compression Agent
(Drvspace.txt).
Additional query words:
winboot.ini dynload VxD
Keywords : kbenv winplus win95 win98
Version : 95
Platform : WINDOWS
Issue type : kbprb
|