How to load drvspace high?
Rob Laddish
some disk space back. :-) I noticed that dos windows under w95 have
the drivespace/doublespace (sp?) driver loaded high, but all of my
boot into dos icons cause me to boot dos with the driver loaded low.
There is no entry in my config files to load the driver, which makes
sense because the config.sys & autoexec.bat files are probably on
the compressed drive. My problem is that this driver is ~80k and takes
up way too much conventional memory and many things won't run anymore.
I suppose that I could create a boot disk, but they're quite a pain.
Does anyone know how to load the compressed disk driver into high
memory for pure dos boots?
Thanks for any help,
Rob
------------------------------------------------------------------------
Robert Laddish, Hewlett-Packard (Santa Rosa) ro...@sr.hp.com 707-577-3767
"A hundred thousand lemmings can't be wrong." ... Author unknown
------------------------------------------------------------------------
trueba
>==========Rob Laddish, 10/5/95==========
>
>I bought w95 & the plus pack, and I'm using the disk compression to get
>some disk space back. :-) I noticed that dos windows under w95 have
>the drivespace/doublespace (sp?) driver loaded high, but all of my
>boot into dos icons cause me to boot dos with the driver loaded low.
>There is no entry in my config files to load the driver, which makes
>sense because the config.sys & autoexec.bat files are probably on
>the compressed drive. My problem is that this driver is ~80k and takes
>up way too much conventional memory and many things won't run anymore.
>I suppose that I could create a boot disk, but they're quite a pain.
>
>Does anyone know how to load the compressed disk driver into high
>memory for pure dos boots?
>
I have a question here that I've asked before and it has, so
far, gotten no response whatsoever. What causes the Drivespace
driver to load in either conventional or upper memory at ANY
time? I used Drivespace from the Windows 95 install and the new
Drivespace 3 from the Plus! pack. If used it to compress my one
and only hard drive on my system. I ran full compression and not
just compressing the free space. At no time, when doing a mem
from a DOS prompt do I see it loaded in either conventional or
upper memory. To check it out, someone else in our office
compressed his drive with Drivespace 3 and got the same results:
no sign of Drivespace in either conventional or upper memory.
Obviously, there is some reason for the discrepancies here, but
what is it?
Ramesh Viswanathan
: I have a question here that I've asked before and it has, so
: far, gotten no response whatsoever. What causes the Drivespace
: driver to load in either conventional or upper memory at ANY
: time? I used Drivespace from the Windows 95 install and the new
: Drivespace 3 from the Plus! pack. If used it to compress my one
: and only hard drive on my system. I ran full compression and not
: just compressing the free space. At no time, when doing a mem
: from a DOS prompt do I see it loaded in either conventional or
: upper memory. To check it out, someone else in our office
: compressed his drive with Drivespace 3 and got the same results:
: no sign of Drivespace in either conventional or upper memory.
: Obviously, there is some reason for the discrepancies here, but
: what is it?
The Following KB article form Microsoft, provides a good insight.
------
DriveSpace Real-Mode Driver May Not Be Removed from Memory
ARTICLE ID: Q134364
The information in this article applies to:
- Microsoft Windows 95
- Microsoft Plus! for Windows 95
SYMPTOMS
The real-mode memory (conventional or upper) used by DriveSpace
(Drvspace.bin or Dblspace.bin) may not be reclaimed when you start
Windows 95. 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 95 by typing
"win."
The real-mode memory used by Drvspace.bin (or Dblspace.bin) cannot be
reclaimed if you interrupt the normal Windows 95 boot process by
pressing F8 at the "Starting Windows 95" message, selecting Command
Prompt Only from the Windows 95 Startup menu, and then typing "win" to
start Windows 95.
- 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 95 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 Plus! 64,135 Real-mode driver version 3
Drvspacx.vxd Windows 95 54,207 32-bit driver version 2
Drvspacx.vxd Plus! 61,719 32-bit driver version 3
RESOLUTION
To resolve this problem, use one or more of the following methods:
- Start Windows 95 normally (do not boot to a command prompt, then start
Windows 95 by typing "win").
- Change the command in the Config.sys file from
devicehigh=<path>\drvspace.sys /move
to:
device=<path>\drvspace.sys /move
NOTE: The syntax of this command is different if you use a third-party
memory manager (such as Qualitas 386MAX or QuarterDeck QEMM).
- Remove LoadTop=0 from the Msdos.sys file. For information about editing
the Msdos.sys file, please see the following article in the Microsoft
Knowledge Base:
ARTICLE-ID: Q118579
TITLE : Contents of the Windows 95 Msdos.sys File
- Rename the Drvspacx.vxd file in the Windows\System\Iosubsys folder and
then use the procedure below that applies to your configuration:
If Microsoft Plus! for Windows 95 Is Not Installed
--------------------------------------------------
1. Run Windows 95 Setup again.
2. Choose "Restore Windows files that are changed or corrupted" when
you are prompted.
If Microsoft Plus! for Windows 95 Is Installed
----------------------------------------------
1. Click the Start button, point to Settings, and then click Control
Panel.
2. Double-click the Add/Remove Programs icon.
3. On the Install/Uninstall tab, click Microsoft Plus! For Windows 95,
and then click Add/Remove.
4. When Setup begins, click Reinstall.
Manually Extract Drvspacx.vxd from the Original Disks or CD-ROM
---------------------------------------------------------------
Manually extract the Drvspacx.vxd file from the original Windows 95 or
Plus! disks or CD-ROM. If Plus! is installed, be sure to extract the
Drvspacx.vxd file from the Plus! disks or CD-ROM, not from the Windows
95 disks or CD-ROM.
For more information about the Extract tool, type "extract" (without
quotation marks) at a command prompt, or see the following article in
the Microsoft Knowledge Base:
ARTICLE-ID: Q129605
TITLE : Using the Windows 95 Extract Tool (Extract.exe)
NOTE: The Drvspacx.vxd file for Windows 95 is located in the
Win95_09.cab file on disk 9 of the original disks, or in the
Win95_09.cab file on the CD-ROM.
The Drvspacx.vxd file for Plus! is located in the Plus_1.cab file on
disk 1 of the original disks, or in the Plus_1.cab file on the CD-ROM.
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 95 cannot unload the real-mode DriveSpace
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).
KBCategory: kbenv
KBSubcategory: wpp95 win95 winplus
Additional reference words: 95 winboot.ini dynload VxD
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1995.
--
Ramesh Viswanathan *************** ClubWin Member ***************
Siemens Corporate Research, 755 College Road East, Princeton NJ 08540-6668
#include <standard_disclaimer.h>
Rob Laddish
: I have a question here that I've asked before and it has, so
: far, gotten no response whatsoever. What causes the Drivespace
: driver to load in either conventional or upper memory at ANY
: time? I used Drivespace from the Windows 95 install and the new
: Drivespace 3 from the Plus! pack. If used it to compress my one
: and only hard drive on my system. I ran full compression and not
: just compressing the free space. At no time, when doing a mem
: from a DOS prompt do I see it loaded in either conventional or
: upper memory.
Weird. I ran drivespace from the plus pack and fully compressed my
only hard drive, and both DOS windows in W95 and reboots into DOS
show drivespace running.
Btw, others sent me help, it appears that running drvspace /move in your
config.sys moves most of it to high memory. Thanks! I also used the I
option in emm386 to use extra space. Unfortunately, I'm now at ~550K
free in a dos booted window, but it's much better than 500K as before!
Thanks again,