  
1. Difference Between DEFRAG and DBLSPACE /DEFRAGMENT
There are two ways to defragment a DoubleSpace drive: you can run DBLSPACE /DEFRAGMENT, or you can run Microsoft Defragmenter (DEFRAG.EXE).
More Information:
Files stored on DoubleSpace drives become fragmented just as they do on physical drives.
Running DEFRAG.EXE
Microsoft Defragmenter (DEFRAG.EXE) makes files contiguous by making virtual clusters contiguous. For example, a DoubleSpace drive would change from
  
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
   C:               [1123156-1-13-5-1-2-3-1521--123------- ]
  
to:
  
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
   C:               [111112222333344455556---------------- ]
  
  
Note   In this example, each number represents a piece of a file. For example, each "1" indicates a piece of file 1.
  
Running DBLSPACE /DEFRAGMENT
DBLSPACE /DEFRAGMENT moves data within the compressed volume file (CVF) so that all the free space is at the end. Files aren't made contiguous; they are simply placed in one group at the front of the drive. Using the same example, the file would change from 
  
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
   C:               [1123156-1-13-5-1-2-3-1521--123------- ]
  
to:
  
H:\DBLSPACE.000: [121354213221134----------- ]
   C:               [1123156-1-13-5-1-2-3-1521--123------- ]
  
Running DBLSPACE /DEFRAGMENT /F
DBLSPACE/DEFRAG/F moves all the used sectors to the end of the CVF. Using the same example, the file would change from
  
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
   C:               [1123156-1-13-5-1-2-3-1521--123------- ]
  
to:
  
H:\DBLSPACE.000: [-----------121354213221134 ]
   C:               [1123156-1-13-5-1-2-3-1521--123------- ]
  
  
Note   When you run DBLSPACE with the /DEFRAGMENT parameter, it may not make all of the unused sectors contiguous; this is why the /F switch exists. If you cannot resize a DoubleSpace drive because it is too fragmented, you must defragment the drive with DBLSPACE /DEFRAGMENT and then with Defragmenter. 
  
To do this: 
 1.	Run DBLSPACE to defragment the CVF.
 2.	Move all the sectors to the end of the disk by typing the following at the MS-DOS command prompt:
  
dblspace /defragment /f 
  
 3.	Run Defragmenter with the /F parameter by typing the following at the MS-DOS command prompt:
  
defrag /f
  
	This should move all of the data to the end of the CVF and then back to the front. All of the unused sectors should then be contiguous.
  
Fully Optimizing Your DoubleSpace Drive
If you type DEFRAG to defragment a DoubleSpace drive, Defragmenter runs DBLSPACE /DEFRAGMENT when it has completed. Once both types of defragmentation have been done, the sample file appears  similar to the following:
  
H:\DBLSPACE.000: [121354213221134----------- ]
   C:               [111112222333344455556---------------- ]
  
Note that files are contiguous on the virtual drive (drive C) but not within the CVF. Free space is contiguous in both places. 
2. MemMaker Doesn't Optimize Batch Files in AUTOEXEC.BAT
If a third-party memory manager has optimized memory by using specific loading programs or parameters within batch files, the following error message is displayed after you run MemMaker:
  
Bad Command or Filename
  
  
Note   You may also receive error messages from the third-party expanded memory manager (EMM) if commands such as LOADHI (from QEMM) are called. 
  
More Information:
Some third-party memory managers optimize one or more levels deep in batch files called from the AUTOEXEC.BAT file, trying to load programs in upper memory. MemMaker does not analyze software called from batch files within the AUTOEXEC.BAT file, but instead treats the whole batch file as one entity and attempts to load it in upper memory.
If you receive error messages because commands specific to third-party EMMs are still in your batch files, edit the files and remove the third-party specific information.
For example, if you have the following QEMM command in a batch file called from the AUTOEXEC.BAT file, you receive the following error message after you run MemMaker:
  
LOADHI /R:2 doskey /insert
  
To work around this problem, remove the QEMM-specific information. For example:
  
doskey /insert
  
3. Troubleshooting MS Backup and MS Backup for Windows
If you encounter problems running Microsoft Backup for MS-DOS or Microsoft Backup for Windows, use the steps in the following section to correct the problems.
Common problems caused by incorrect system configuration include the following:
·	Microsoft Backup appears to stop responding (hang) when run from the MS-DOS command prompt in Windows.
·	Microsoft Backup for Windows causes Windows to close, leaving the MS-DOS command prompt displayed on the screen.
·	Windows reports that the DMA buffer size needs to be increased to 64.
·	Microsoft Backup fails the compatibility test.
  
Troubleshooting Microsoft Backup for Windows and Microsoft Backup
 1.	Microsoft does not recommend or support running the MS-DOS-based version of Microsoft Backup (MSBACKUP.EXE) with Windows. If you choose to do this, you should create a program information file (PIF) with the following settings for Microsoft Backup:
  
Display Usage: Full Screen
Execution:  Exclusive
  
 2.	Your CONFIG.SYS file should include the following settings (the values shown are minimums):
  
FILES=30
BUFFERS=30
STACKS=9,256
  
 3.	The DMABufferSize= line should be set to at least 32 in the [386Enh] section of the SYSTEM.INI file. In some situations, the DMA  buffer size needs to be set to 40 (either in the SYSTEM.INI file, or using EMM386.EXE, or both).
 4.	If you are using MSBACKUP.EXE in Windows or the Windows version of Microsoft Backup  MWBACKUP.EXE), you should place the following line in your SYSTEM.INI file if Setup did not install it:
  
device=c:\dos\vfintd.386
  
	If you omit this line, MWBACKUP displays an error message.
  
4. Using MemMaker with Multiple Configurations
You can use MemMaker with multiple configurations, but doing so requires that you create separate configuration files to run MemMaker. The "MS-DOS User's Guide" for version 6.0 explains this procedure in detail in Chapter 6 (pages 151 to 154).
This article explains why these separate configuration files are necessary.
More Information:
MemMaker removes all references to memory managers, the FILES= statement, the BUFFERS= statement, and the DOS= statement. It then adds the following statements at the top of the CONFIG.SYS file: 
  
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE <settings>
buffers=<setting>
files=<setting>
dos=umb
lastdrive=<setting>
FCBS=<setting>
  
[Everything else remains in the same order]
  
Note   The <setting> and <settings> are determined by MemMaker for your specific installation and configuration.
  
Because of this design, MemMaker cannot work with configuration files containing Multi-Config sections that reference multiple memory managers or have different memory configurations.
MemMaker also uses a program called SIZER.EXE to determine memory requirements for device drivers and terminate-and-stay-resident (TSR) programs. MemMaker analyzes the contents of the entire CONFIG.SYS and AUTOEXEC.BAT files (regardless of Multi-Config headings) to calculate the optimum memory configuration for your system. Because the files are viewed as a single unit, each individual configuration will not be optimized after you run MemMaker.
5. Converting Stacker Compressed Removable Disks
To convert a Stacker-compressed floppy disk, you must have approximately 900K of free disk space on the removable disk. To convert a Stacker-compressed removable media disk (such as Bernoulli disks and removable optical disks) you must have approximately 1 megabyte (MB) of free disk space on the removable disk. The free disk space can be either at the end of the Stacker volume file (SVF) or on the uncompressed portion of the disk.
If you do not have enough free disk space to compress a removable disk and you cannot remove any files to create more free disk space (or the disk capacity is less than 900K [360K or 720K]), use the procedure below (which was taken from the README.TXT file).
More Information:
DoubleSpace requires 900K free disk space so it can create a 512K DoubleSpace compressed volume file (CVF). DoubleSpace also requires 400K-500K free disk space so it can internally unfragment a highly fragmented SVF. 
If DoubleSpace cannot convert a Stacker-compressed volume file due to disk space limitations, do the following:
 1.	Insert the floppy disk in drive A or B.
 2.	Move the STACVOL.DSK file to the host drive on your hard disk. If you don't know which drive is your host drive, start DoubleSpace by typing DBLSPACE at the command prompt and choosing the Info command from the Drive menu. Exit DoubleSpace.
	When you move the file, change its extension to .001. For example if the floppy disk is in drive A, and your host drive is drive D, type the following at the command prompt:
  
move a:\stacvol.dsk d:\stacvol.001
  
	If you have insufficient disk space, start DoubleSpace by typing DBLSPSACE at the command prompt, and choose Change Size from the Drive menu. Make the size of the uncompressed drive large enough to contain the Stacker-compressed volume file.
 3.	If are using Stacker version 2.0, delete the STACKER.DRV file on the floppy disk. If you are using Stacker version 3.0, delete the STACKER.EXE and README.STC files.
 4.	Covert the compressed volume file to DoubleSpace format, as in the following example:
  
dblspace /convstac=d:\stacvol.001
  
	After DoubleSpace converts the file it will mount it.
 5.	Make sure your floppy disk is in drive A or B and then compress it by choosing the Existing Drive command from the Compress menu in DoubleSpace. Follow the instructions on your screen.
	DoubleSpace mounts the floppy drive after it finishes compressing the floppy disk.
 6.	Exit DoubleSpace.
 7.	Use the XCOPY command to copy all the files on the new compressed  drive on your hard disk to the compressed floppy disk. For example, if the compressed drive is J, and the floppy disk is in drive A, type the following at the command prompt:
  
xcopy j:\*.* a: /s
  
 8.	Delete the compressed drive on your hard disk. For example, if your compressed drive is J, type the following at the command prompt:
  
dblspace /delete j:
  
	To confirm the deletion, type "Y" (without the quotation marks).
  
6. DoubleSpace Err Msg: 'Not Enough Conventional Memory...'
If you start your computer using the interactive startup option in order to free enough memory to run the DoubleSpace Stacker conversion option, you may receive the following error message after DoubleSpace restarts your computer:
  
Not enough conventional memory
  
More Information:
When you start your computer and press the F8, F5, or SHIFT key to free enough conventional memory to run the DoubleSpace Stacker converter, you must also use the interactive startup option when DoubleSpace restarts your computer. If you do not use this option, you will not have enough memory to complete the conversion. 
If you use the F5 key to bypass the CONFIG.SYS and AUTOEXEC.BAT files, the only directory in the PATH environment variable is C:\DOS; therefore, DoubleSpace cannot start Stacker.
Workaround
To work around this situation, either use the F8 key to bypass some of your device drives before and during the Stacker conversion process, or remark out (REM) some of the device drivers and terminate-and-stay-resident (TSR) programs in your CONFIG.SYS file. 
7. MemMaker Doesn't Remove All References to QEMM
MemMaker removes all references to QEMM. However, if one of your QEMM statements in the CONFIG.SYS file does not have an equal sign (=), MemMaker ignores it; the driver is not loaded by MemMaker, nor is it removed from the CONFIG.SYS file. If this occurs, you may receive an error message from MemMaker stating that another expanded memory manager (EMM) is already running.
To work around this problem, edit your CONFIG.SYS file with a text editor such as MS-DOS Editor and put equal signs in your DEVICE commands.
8. DoubleSpace Err Msg: Drive is Too Fragmented to Resize
When you try to resize a DoubleSpace drive, you may receive the following error message
  
Drive C is too fragmented to resize. Before resizing drive C,
  
defragment it by typing DEFRAG.EXE /H /Q <x>: at the MS-DOS command prompt where <x> is the drive letter of the compressed drive.
Running DEFRAG /H /Q C: does not correct this problem; you still cannot resize the DoubleSpace drive.
This error can occur if the drive is too fragmented or if a program (such as MIRROR or Norton Image) places a hidden file at the end of the DoubleSpace drive.
More Information:
If the problem is not being caused by a delete tracking program (such as MIRROR), and DEFRAG /H /Q C: does not correct the problem, edit the DBLSPACE.INI file and increase the MaxFileFragments setting. 
To do this:
 1.	Remove the Read-Only, System, and Hidden file attributes on the DBLSPACE.INI file. For example, if drive H is your host drive, type the following at the MS-DOS command prompt and press ENTER:        
  
attrib h:\dblspace.ini -r -s -h
  
 2.	Using MS-DOS Editor, edit the DBLSPACE.INI file and increase the value for MaxFileFragments - 2000 is a good number to try. 
 3.	Save the DBLSPACE.INI file and quit MS-DOS Editor.
 4.	Use the ATTRIB command to reset the file attributes on DBLSPACE.INI. For example, if your host drive is drive H, type thefollowing command and press ENTER:
  
attrib h:\dblspace.ini +r +s +h2. 
  
 5.	Restart your computer and try to resize the drive.
  
Delete Tracking Programs
This problem can also occur if a program (such as MIRROR or Norton Image) creates a file at the end of the drive. MIRROR, for example, creates a file called MIRORSAV.FIL; Norton Image creates a file called IMAGE.IDX. 
Since this file has read-only, hidden, and system file attributes set, it cannot be moved when you run Defragmenter (DEFRAG.EXE or Defrag). To allow Defrag to move the hidden system file, remove the file attributes, then use Defrag with the /Q and /H switches. For example, type "DEFRAG /Q /H C:" (without the quotation marks) at the MS-DOS command prompt and then press ENTER.
  
Note   If you do not use MIRROR or Norton Image, it is possible that another program has placed a file with its system attribute set near the end of the drive.
  
To search for hidden files on your drive, type the following at the MS-DOS command prompt:
  
dir /s /ah /p
  
To search for hidden SYSTEM files on your drive, type the following at the MS-DOS command prompt:
  
dir /s /as /p
  
  
Note   Since MIRORSAV.FIL may exist on the host drive, you should  log on to H: and do a DIR /AH /S to look for these hidden system files. 
  
You can use the ATTRIB command to remove the file attributes on the file. For example, if you have the MIRROR file on drive C, issue the following command at the MS-DOS command prompt:
  
attrib -r -a -s -h c:\mirorsav.fil
  
After you run Defrag with the parameters suggested in the error message, you should be able to resize the DoubleSpace drive.
The Norton products included here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
9. MSAV: Cleaning Boot-Sector Viruses from Compressed Drives
Microsoft Anti-Virus may detect a  boot sector virus (such as STONED or Michelangelo) but may fail to clean it. This problem can occur for two reasons:
·	The boot sector virus is on your DoubleSpace-compressed drive and  your host drive. 
·	All of the virus code is not being overwritten
  
More Information:
The Boot Sector Virus is on Your DoubleSpace-Compressed Drive and Your Host Drive.
Boot-sector viruses are activated when you start your computer from the infected drive (usually drive C) and alter MS-DOS startup code located in the boot sector of your hard disk. DoubleSpace drives do not actually have MS-DOS startup code to corrupt; however, if a virus is detected on a compressed drive, it is likely that the host drive is also infected.
You can detect and clean viruses from all local drives by using the following command:
  
msav /c /l
  
The /C switches causes Microsoft Anti-Virus to scan and clean the disk. The /L switches causes Microsoft Anti-Virus to scans all local drives except A and B.
All of the Virus Code is Not Being Overwritten
When a boot sector virus infects a hard disk, it moves the original boot sector information to another location on the disk and replaces it with virus code. Microsoft Anti-Virus finds the original boot sector information and uses it to overwrite the virus code. If the original boot sector information is incomplete or has been damaged in some way, all of the virus code may not be overwritten. When Microsoft Anti-Virus scans the drive and finds the remnant of the virus code it report it as a virus.
Workaround if CHKDSK reports 655,360 Total Bytes Memory
If the Total Bytes Memory reported by MS-DOS CHKDSK is 655,360 bytes, the virus is not active, and the following steps should be taken to clean the remnant of the virus code from the drive:
 1.	Back up all data on all partitions on the hard drive. You might want to use the Microsoft Backup Compare feature to ensure that all files have been backed up successfully.
 2.	If the infected hard drive was partitioned with MS-DOS FDISK, the virus remnant may be cleaned by running FDISK with the /MBR  parameter. This will refresh the Master Boot Record and overwrite any remaining virus code. Turn the computer off and then back on after this procedure.
	Warning   You should not use FDISK/MBR if :
·	the disk was partitioned using Storage Dimensions' SpeedStor utility with the /Bootall option
·	more than 4 partitions exist
·	certain dual-boot programs are in use
  
	For more information, query on the following words in the Microsoft Knowledge Base:
  
FDISK /MBR REWRITES MASTER BOOT RECORD
  
 3.	Microsoft Anti-Virus to determine whether the procedure eliminated the remaining virus code.
  
Workaround if CHKDSK reports less than 655,360 Total Bytes Memory
If CHKDSK reports less than 655,360 Total Bytes Memory, the virus may still be active -- proceed as follows:
 1.	Boot from a write-protected system disk, known to be free of virus infection (such as your original MS-DOS 6 Upgrade Setup disk 1.
	Note   While the 1.2 MB (5.25 inch) floppy disks are write protected, the 1.44 (3.5 inch) floppy disks are not. If you have the 1.44 inch floppy disks, you should slide with write protect tab so the write protect whole is open on all your disks. Be sure you scan the floppy disks to ensure they are not infected. If they are, order new disk from Microsoft Consumer Sales at: (800) 426-9400.
 2.	Put disk 3 of either the 1.2 MB (5.25 inch) or 1.44 (3.5 inch) disk set in drive A.
 3.	Change to the MS-DOS prompt at drive A and run Microsoft Anti-Virus. For example, type the following at the MS-DOS command prompt, pressing ENTER after each line:
  
a:
msav c: /c /l
  
 4.	Remove the floppy disk drive from drive A and restart your computer.
 5.	Scan all hard drives to ensure the virus has been removed.
	Note   The new location of the original boot sector information may be different for each boot sector virus.  Microsoft Anti-Virus can therefore clean only the boot sector viruses on the Microsoft Anti-Virus Virus List.
  
Which Boot Sector Is Executed During Startup?
If drive C is uncompressed, its boot sector is run during system startup. If drive C is compressed, the boot sector of its host drive is run.
What the Boot Sector Does
MS-DOS 5.0 and 6.0 boot sector startup code does the following: 
·	Confirms that the system files (IO.SYS and MSDOS.SYS) are the first two files in the root directory of the drive.
·	Loads and executes the first three sectors of the IO.SYS file.
	The boot sector is executed by the master boot record (MBR). If you have more than one partition, the MBR determines which one to run using the partition table.
  
How Boot Sector Viruses Get on a Compressed Volume File (CVF)
If a drive is infected before you install DoubleSpace, some boot virus information may be replicated on the DoubleSpace CVF. Although it cannot affect the system from the DoubleSpace volume, the signatures may still be detected here. To correct this, clean both the host drive and DoubleSpace-compressed drive.
10. FastTips: DoubleSpace Q&A
 1.	Q. How can I receive the Stacker(R) Conversion Disk?
	A. You can order the "Conversion Disk for Users of Stacker" by sending in $10 and the Conversion Disk Offer coupon from your "Microsoft MS-DOS 6 User's Guide." Unfortunately, we cannot make this conversion tool available electronically. For more information on the MS-DOS 6 Stacker Conversion tool, call Microsoft Sales and Service at (800) 228-7007.
 2.	Q. Why does DoubleSpace create a drive identified by the letter H when I have drives A, B, and C only?
	A. To avoid conflicts with existing drives, DoubleSpace examines the existing drive assignments during installation to find the highest drive letter currently in use. It then skips the next four letters and assigns the fifth letter to the new DoubleSpace drive.
	For example, if your computer has two floppy disk drives (A and  B) and a hard disk drive (C), DoubleSpace locates the highest letter (C); skips drive letters D, E, F, and G; and then assigns drive letter H for its own use. 
	For more information, refer to the "Freeing Disk Space" chapter in the "Microsoft MS-DOS 6 User's Guide."
 3.	Q. I am currently using a third-party disk-compression software package and now want to convert to DoubleSpace. How can I do this?
	A. To convert to a DoubleSpace drive, use the following steps: 
 1.	Install the MS-DOS 6 Upgrade if you haven't already done so.
 2.	Back up your program and data files on all drives using Microsoft Backup or a third-party utility.
 3.	Create a bootable MS-DOS floppy disk. To do this, insert the original MS-DOS 6 Setup Disk 1 in either drive A or drive B, type the following command, and then press ENTER
  
drive:setup /f
  
	where "drive" is the floppy disk drive containing Setup Disk 1.
	Important   After you type the above command and Setup prompts you to insert a disk to create the startup floppy disk, you MUST create that disk in drive A. Also, be sure that you choose to install on drive A.
 4.	Verify that the disk you have just created is bootable by inserting the disk in drive A and pressing CTRL+ALT+DEL. If your system starts up, continue with the next step. If it does not, reboot from your hard disk and repeat step 3 until you have created a bootable floppy disk.
 5.	Format the drive with the compressed volume file (CVF). To do this, type the following command at the A: prompt and then press ENTER
  
format drive:
  
	where "drive" is the floppy disk drive containing the CVF.
	Note   If you are formatting drive C, use the /s switch with the format command to make the hard disk bootable.
 6.	If you formatted a drive other than C, skip to step 7. If you formatted drive C, you must reinstall the MS-DOS 6 Upgrade. To do this, insert Setup Disk 1 in drive A or drive B, type the following command, and then press ENTER 
  
drive:setup
  
	where "drive" is the floppy disk drive containing Setup Disk 1.
	Follow the steps on the screen to install the MS-DOS 6 Upgrade.
	Note   If you used Microsoft Backup for MS-DOS to back up your compressed drive, be sure to reinstall Backup for MS-DOS when Setup prompts you to do so. (You need this program to restore your backup disks.)
 7.	Install DoubleSpace. To do this, type "dblspace" at the MS-DOS command prompt, press ENTER, and then follow the steps on the screen.
	Note   For more information on DoubleSpace, refer to the "Freeing Disk Space" chapter in the "Microsoft MS-DOS 6 User's Guide" or type "help dblspace" (without the  quotation marks) at the MS-DOS command prompt and press ENTER. For more information on Microsoft Backup, refer to the "Managing Your System" chapter in the "Microsoft MS-DOS 6 User's Guide."
 8.	Restore the files from your backup disks by using Microsoft Backup or your third-party backup utility. If you are using a third-party backup utility, you must install the software onto the hard disk. Refer to the manufacturer's documentation for the procedure to do this.
  
 4.	Q. I installed DoubleSpace and now each time I enter Microsoft Windows I receive the error "Corrupt Swapfile Warning." I have set up my permanent swap file many times, but I continue to receive this error. How can I correct this problem?
	A. In this case, the error "Corrupt Swapfile Warning" probably means your permanent swap file is being created on a DoubleSpace compressed volume. Windows cannot create a permanent swap file on a compressed volume. To correct this problem, set the permanent swap file to a noncompressed drive.
	Windows contains code to detect and avoid compressed volumes created with third-party software. However, Windows cannot detect compressed volumes created with DoubleSpace because Windows' release predates the release of DoubleSpace.
	For more information, refer to the "Freeing Disk Space" chapter in the "Microsoft MS-DOS 6 User's Guide," or type "help dblspace" (without the quotation marks) at the MS-DOS command prompt and press ENTER.
 5.	Q. I am trying to run Windows 3.0 in real mode so that I can change my permanent swap file with SWAPFILE.EXE. Every time I try, I receive the error message "Unsupported DOS version; upgrade to DOS version 3.1 or higher." What causes this error?
	A. This is an incorrect message. To correct this problem, run the  SPATCH.BAT file, which is located on your original MS-DOS 6 Upgrade disks.
  
11. FastTips: MemMaker Q&A
 1.	Q. How can I free conventional memory on my computer?
	A. You can optimize your computer memory use automatically by running the MS-DOS 6.0 MemMaker program. There are some restrictions on using MemMaker to optimize your system memory.  MemMaker works on 80386 and 80486 computer systems only; it does not work on 80286 or 8088 systems. It works with the MS-DOS HIMEM.SYS and EMM386.EXE memory-management utilities only; it does not work with third-party utilities, such as Qemm(TM) and 386MAX(R).
	MemMaker reviews your CONFIG.SYS and AUTOEXEC.BAT files and then optimizes them by loading terminate-and-stay-resident (TSR) programs and installable device drivers into the memory area between 640 kilobytes (K) and 1 megabyte (MB), which is called the upper memory area (UMA). Before you run MemMaker, verify that all device drivers are being loaded properly and that any hardware they control is also functioning correctly. To run MemMaker, type "memmaker" (without the quotation marks) at the MS-DOS command prompt, and press ENTER. 
	Read each screen and follow the instructions listed. During this process you are prompted to choose either Express Setup orCustom Setup. We recommend using the express mode of MemMaker Setup initially. Setup prompts you to verify that your applications require expanded memory. If you are unsure, refer to your software documentation.
	MemMaker reboots your machine twice while it determines the optimal configuration. When it has chosen a configuration, a screen reports how much memory was available before you ran MemMaker and how much is available now. If the displayed memory is not what you expect or need, press the ESC key to undo changes made by MemMaker.
	If you accepted the changes made by MemMaker and now want to undo them, type "memmaker /undo" (without the quotation marks) at the MS-DOS command prompt, and then press ENTER.
	For more information about MemMaker, please refer to the "Managing Your System" chapter of the "Microsoft MS-DOS 6 User's Guide."
 2.	Q. After MemMaker rebooted my computer, the computer stopped responding ("hung"). How can I correct this problem?
	A. MemMaker tries to use UMA locations that it determines are free. If your machine hangs, note any error messages that are displayed, then restart your computer. MemMaker detects that your computer is being restarted before the optimization is complete and displays a screen listing possible reasons for the interruption and instructions for resuming or quitting the optimization. Accept the default options to continue.
	For more information regarding MemMaker, please refer to the"Making More Memory Available" chapter of the "Microsoft MS-DOS 6 User's Guide."
 3.	Q. After running MemMaker, some programs on my computer no longer function properly. How can I correct this problem?
	A. Some programs and device drivers are not designed to be loaded into the UMA. If you have such a program, it cannot work correctly when loaded into the UMA. To correct this problem, you must change how the program is loaded, thus changing where it will be loaded in memory. Two procedures for doing this follow.
	If the program is being loaded from the CONFIG.SYS file with a DEVICEHIGH command, open the CONFIG.SYS file in an ASCII text editor, such as MS-DOS Editor, and change the line for the device driver to read device instead of devicehigh. Save the file, quit the text editor, and then reboot your computer by pressing CTRL+ALT+DEL.
	If the program is being loaded in the AUTOEXEC.BAT file, open the AUTOEXEC.BAT file in an ASCII text editor and remove the LOADHIGH (LH) command for that program. Save the file, quit the text editor, and then reboot your computer by pressing CTRL+ALT+DEL.
	For more information on the LOADHIGH and DEVICEHIGH commands, refer to the "Microsoft MS-DOS 6 User's Guide" or type "help loadhigh" or "help devicehigh" (without the quotation marks) at      the MS-DOS command prompt. Also, check the documentation that comes with your application for details on memory location and usage.
 4.	Q. I am using the Multi-config commands and I want to optimize my system. Are there any special precautions I should take?
	A. MemMaker views the CONFIG.SYS and AUTOEXEC.BAT files as a single unit. When you run MemMaker, it removes all references to memory managers and the FILES, BUFFERS, and DOS commands. It then adds the following commands to the top of the CONFIG.SYS file:
  
device=c:\dos\himem.sys
device=c:\dos\emm386.exe settings
buffers=setting
files=setting
dos=umb
lastdrive=setting
fcbs=setting
  
	Note   The setting values for BUFFERS, FILES, lastdrive, and EMM386.EXE are determined by MemMaker based on your configuration.
	Because of this design, MemMaker cannot optimize CONFIG.SYS and AUTOEXEC.BAT files that use Multi-config commands.
	To optimize multiple configurations using MemMaker, you must have separate configuration files for each item on your multiple configuration menu, and run MemMaker on each set of files. This is a complex process. Refer to the "Making More Memory Available" chapter of the "Microsoft MS-DOS 6 User's Guide" to clarify how to use MemMaker with multiple configurations.
	For more information on the multiple configuration commands, refer to the "Configuring Your System" chapter of the "Microsoft MS-DOS 6 User's Guide."
	For more information on MemMaker, refer to the "Making More Memory Available" chapter of the "Microsoft MS-DOS 6 User's  Guide."
 5.	Q. After optimizing my system with MemMaker, I receive the error  message "Bad command or filename." How can I correct this problem?
	A. This error message indicates that MS-DOS cannot find a file or program. Check the drive, path, and filenames to verify that the filenames and locations are accurate. This error may occur if MemMaker changes programs loaded by a third-party memory manager. MemMaker does not support the use of third-party  memory managers, and all such references in the AUTOEXEC.BAT and CONFIG.SYS files should be replaced with the corresponding  MS-DOS memory manager or command.
	For more information on MemMaker, refer to the "Making More Memory Available" chapter of the "Microsoft MS-DOS 6 User's Guide."
  
12. Microsoft Anti-Virus Cannot Remove Stoned Virus
Microsoft Anti-Virus can detect the "Stoned 4" virus but may not be able to remove it. To remove the Stoned virus, use the Fdisk program to replace the master boot record (MBR). For example, type "fdisk  /mbr" (without the quotation marks) at the MS-DOS command prompt and then press ENTER. 
Warning   Do not use Fdisk with the /MBR parameter if your hard disk partitioning and/or access software stores information in the MBR. 
13. Novell Login Drive Not Available After Installing DoubleSpace
After you install Microsoft DoubleSpace, the drive letter F (normally used by Novell NetWare) may be in use.  To work around this problem, you can either use a different drive letter for your login drive, or adjust DoubleSpace so that it uses a different drive letter for its host drive.
You can avoid this problem if you make sure your NetWare software is loaded before you run DoubleSpace to compress your drives.
More Information:
If your usual NetWare drive letter is not available, one of the following should correct the problem:
·	If your CONFIG.SYS file has a DEVICEHIGH=C:\DOS\DBLSPACE.SYS command, make sure it is placed before any RAMDrive statements.  Changing the order of the RAMDrive and DBLSPACE.SYS lines in the CONFIG.SYS file changes the "Last drive reserved for DoubleSpace's use:" setting in the DBLSPACE.INI file, freeing up an additional drive letter.
·	Run DBLSPACE at the MS-DOS command prompt and increase the "Last drive reserved for DoubleSpace's use:" setting. 
·	If neither of the options above correct the problem, you will have to edit the DBLSPACE.INI file to manually change the host drive letter. To do this:
 1.	Change to the host drive (for example H).
 2.	Use the ATTRIB command to change the file attribute on the DBLSPACE.INI file.
	For example:
  
attrib h:\dblspace.ini -s -h -r
  
 3.	Edit the DBLSPACE.INI file with a text editor, such as MS-DOS Editor.
 4.	Change the LastDrive setting to the letter you want to be the host drive. For example, if you have only one hard disk drive (C), you should use D for the host drive so that F will be available for your Novell login drive. To do this, change the FirstDrive and LastDrive statements to read as follows:
  
FirstDrive=D
LastDrive=D
  
 5.	Change the first parameter in the ActivateDrive line to the same letter you used in step 4.
	Warning   Do not change the second parameter (represented by "xx") in the following example:
	Before change:     ActivateDrive=H,xx
	After change:      ActivateDrive=D,xx
	Warning   If you use a drive letter that is used by a physical device (such as drive A), for the N value, the system may stop responding (hang) or continually reboot when you restart it. 
 6.	Save your changes and quit the text editor.
 7.	Reset the system, hidden, and read-only attributes on the DBLSPACE.INI file. For example:
  
attrib h:\dblspace
.ini +s +h +r
  
 8.	If you are using Microsoft Windows, edit the [386enh] section of your SYSTEM.INI file and change the PermSwapDOSDrive setting to the correct drive. For example:
  
PermSwapDOSDrive=D
  
 9.	Restart your computer (press CTRL+ALT+DEL).
  
  
14. Your Computer Fails the Microsoft Backup Compatibility Test .
Your computer may fail the Microsoft Backup compatibility test for the following reasons:
·	The floppy drive controller card does not support direct memory access (DMA).
·	A software compatibility problem exists in MS-DOS.
·	You are using a third-party virtual device driver (VxD) in Windows.
·	The floppy disk is not properly seated.
·	The floppy disks you are using are failing.
·	You are loading APPEND.EXE, causing the following error message:
·	The file <filename> does not exist. The file cannot be compared.
·	You are running POWER.EXE.
  
Troubleshooting the MS-DOS-Based Version of Microsoft Backup
If you are running the MS-DOS-based version of Microsoft Backup, start your computer with the Clean Start function key (F5) and try the compatibility test again. If it the test fails again, follow the instruction in the "Manual Backup to Path Test" section below.
Troubleshooting Microsoft Backup for Windows. If you are running Microsoft Backup for Windows:
 1.	Run File Manager and format a floppy disk to see if you are having problems formatting floppy disks from Windows.  
 2.	Try running Windows in standard mode and then running the compatibility test.
	If the compatibility test works in standard mode but does not work  in 386 enhanced mode, remove any virtual device drivers (VxDs) that may conflict with VFINTD.386. For example, tape backup VxDs may   conflict with VFINTD.386.
	The following software VxDs (loaded in the [386enh] section of the SYSTEM.INI file) can cause the compatibility test to fail:
  
DEVICE=MYABU.386
DEVICE=FASTBACK.386
DEVICE=VFD.386
DEVICE=CPBVXD.386
DEVICE=VIRWT.386
DEVICE=CMSTAPE.386
DEVICE=CMSTAPED.386
DEVICE=CMSDTAPE.386
DEVICE=ABACKUP.386
  
	Note   Backup for Windows may fail by either dropping to the MS-DOS command prompt, blanking the screen, or hanging the system when it reaches 99% completion.
  
Manual Backup to Path Test
If the compatibility test fails, you will not be able to backup to drive A or B using the specific drive  options. Instead, you will have to backup to the MS-DOS path.
When you back up to the MS-DOS path, all your floppy disks must be formatted before you begin backing up. This feature (backing up to the MS-DOS path) is implemented in Microsoft Backup to provide maximum compatibility with the various hardware being produced.
When you back up to the MS-DOS path, all your floppy disks must be formatted before you begin backing up.
To test backing up to the MS-DOS path, do the following:
 1.	Start Microsoft Backup or Microsoft Backup for Windows.
 2.	Choose the Select Files Button and select approximately 2 MB of files--enough that all the files will not fit on one floppy disk.
	For more information on selecting files, see the Selecting Files For Backup Help topic.
 3.	After you have selected approximately 2 MB of files, choose the OK button.
 4.	In the Backup To box, select MS-DOS Path.
 5.	In the Backup To text box, type "A:\" or "B:\" (without the quotation marks) and then choose the Start Backup button.
 6.	Change the disk in the floppy disk drive when you are prompted to do so.
 7.	When Microsoft Backup has completed the backup, choose the OK button.
 8.	Choose the Compare button.
 9.	Choose the Select Files Button and select the files you backed up.
10.	Choose the Start Compare button.
	If the compare successfully completes, you can safely backup to the MS-DOS path.
  
15. Windows Fails to Run in Enhanced Mode After Running MemMaker .
If Windows fails to run in 386 enhanced mode after you run MemMaker, you may be having problems with a poorly behaved terminate-and-stay- resident (TSR) program, or MemMaker may be using a setting that is too aggressive. To troubleshoot this problem:
 1.	Use the interactive startup option (press the F8 function key when the message "Starting MS-DOS..." appears on your screen).
 2.	As you process your CONFIG.SYS file, select Yes to load HIMEM.SYS and then No to not load EMM386.EXE.
 3.	After responding No to EMM386, press the ESC key to load all the remaining device drivers.
 4.	Start Windows and confirm that it starts properly. If it does not, you are having problems unrelated to MemMaker.
 5.	Exit Windows and run MemMaker.
 6.	Choose to run in Custom Setup, and then choose No when you are asked if MemMaker should "Scan the upper memory area aggressively?"
 7.	Press ENTER to accept the defaults to all other options.
 8.	After MemMaker completes its optimization, run Windows and confirm that it works correctly.
 9.	If you are still having problems with Windows, use the MS-DOS Editor to add the X=A000-EFFF parameter to the device= command for EMM386.EXE in the CONFIG.SYS file and then restart your computer.
	If the problem goes way, narrow down exclude (X=) range.
  
16. Optimizing DoubleSpace on Your Computer
When you use DoubleSpace to double your hard disk space, the following my occur:
·	You may have less conventional memory because the DoubleSpace component (DBLSPACE.BIN) requires 43 kilobytes (K) of memory
·	You may incur a slight (3% to 5%) performance degradation
  
More Information:
You can mitigate these problems with the following steps:
 1.	If you are using Microsoft Windows, set the TEMP environment  variable to the host drive.
a.	Type "dblspace /list" (without the quotation marks) at the MS-DOS command prompt and then press ENTER to determine which drive is the host drive.
b.	Use the DIR command to determine if you have at least 2 megabytes (MB) free disk space on the host drive. If you do not, see the section titled "Using DoubleSpace to Manage Compressed Drives" in the "User's Guide" for instructions on decreasing the size of  the compressed volume file (CVF). If you receive the message
	"Drive X is too fragmented to resize," see section 7.14 in the README.TXT file.
c.	Change to the host drive and create a TEMP directory. For example, if your host drive is drive H, type the following at the MS-DOS command prompt, pressing ENTER after each line:
  
h:
md \temp
  
d.	Using MS-DOS Editor, edit the AUTOEXEC.BAT file and change the SET TEMP statement to point to the TEMP directory on the host drive. For example:
  
set temp=h:\temp
  
  
 2.	If you are using a 386 or higher machine, run MemMaker after you run DoubleSpace to ensure you are freeing as much conventional memory as possible. If you have a VGA display adapter, run MemMaker in custom mode and choose Yes when prompted to use the monochrome region to obtain an additional 32K of upper memory block (UMB) space. If you have a Super VGA video display adapter, you can use the monochrome region, but you need to load the MONUMB.386 file if you use Microsoft Windows. For specific instructions, see section 2.3 of the README.TXT file.
 3.	If you are using a 286 machine and low on conventional memory, you may want to consider purchasing a third-party memory manager to load device drivers, terminate-and-stay-resident (TSR) programs, and the DoubleSpace component (DBLSPACE.BIN) in the upper memory area (UMA).  Two such products are QRAM (from QuarterDeck) and MOVE'EM (from Qualitas). On some, but not all, 286 systems, these products provide UMB space. Consult with the manufacturer for details on system compatibility.
 4.	If you are using a 286 or higher machine and have more than 1 MB of  memory, ensure you are loading SMARTDrive. 
 5.	If you are unable to run a particular application (such as an  MS-DOS-based game) due to insufficient memory, you may want to move that software to the host drive and create a startup disk for drive A that does not contain the DoubleSpace component (DBLSPACE.BIN).  To do this:
a.	Type "dblspace /list" (without the quotation marks) at the MS-DOS  command prompt and then press ENTER to determine which drives are uncompressed or host drives.
b.	Use the XCOPY command to copy the software directory to the host  drive. For example, if H is your host drive, type "xcopy c:\dir\*.*  h:\dir\*.*  /s" (without the quotation marks) at the MS-DOS command      prompt and then press ENTER.
c.	Create a startup (boot) disk in drive A with the SYS command. For example, type "sys c: a:" (without the quotation marks) at the MS-DOS command prompt and then press ENTER.
d.	Type "deltree a:\dblspace.bin" (without the quotation marks) at the MS-DOS command prompt and then press ENTER to remove the DoubleSpace component.
e.	Confirm that all your files were copied to the host drive. 
f.	Using MS-DOS Editor, create CONFIG.SYS and AUTOEXEC.BAT files on drive A and include any TSRs or device drivers required by the software. You should also add a PATH statement to include the       software directory. 
	Note   If you are using a host drive, remember that the drive letter will be different when you start the computer without the DoubleSpace component (DBLSPACE.BIN).
g.	Restart the system with the new startup disk in drive A and run the software to ensure you have configured the system correctly. 
	Note   Your compressed drive will not be accessible when you restart your computer from this floppy disk. The data on your drive is not lost; it will be accessible when you restart your computer from the       hard disk.
h.	If everything is working correctly, restart your computer from the hard disk and delete the software directory from the compressed drive. For example, type "deltree /y c:\dir" (without the quotation       marks) at the MS-DOS command prompt and then press ENTER.
  
 6.	Some applications either implicitly (such as Microsoft Mail version 3.0) or explicitly (such as Paradox) encrypt data files. This enryption removes any patterns in the data, rendering it incompressible. Storing these files on a DoubleSpace drive does not save any disk space and increases file write time because DoubleSpace does the work of trying to compress the file, but cannot. These types of files, if updated often, should be stored on a uncompressed or host drive.
	The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
  
17. Setting the LASTDRIVE Command to Work with a Novell Network
If you set the LASTDRIVE variable to Z and are using a Novell network, the following error message may be displayed:
invalid drive specification
To work around this problem, set LASTDRIVE to something other than Z.
More Information:
A Novell network sets its network drive to the first drive letter not taken by MS-DOS. For example, if LASTDRIVE is equal to H, the network drive is assigned to I.
If LASTDRIVE is set to Z, MS-DOS has taken all the drive letters; therefore, none are available for the network. 
Novell networks are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
18. DoubleSpace Setup Hangs During First Reboot
If you run DoubleSpace Setup and your computer stops responding (hangs) during the first reboot or your computer hangs when you boot from a floppy disk that contains DBLSPACE.BIN (such as the Uninstall disk or the MS-DOS 6 Upgrade Disk 1), it may be because the ROM BIOS on your computer failed when DBLSPACE.BIN called interrupt 1AH. 
This problem occurs on the following computers:
·	Sharp models 6781, 6785, and 6881
·	Canon C-200 M-50
·	Computers using a Microsolutions Compaticard
  
  
Note   The above list may not be complete.
  
When this problem occurs, your system hangs before the DoubleSpace compression process begins. Because no data is ever moved to a DoubleSpace compressed volume file (CVF), no data is lost.
To work around this problem, do the following:
 1.	Restart your computer from an MS-DOS system disk that does not contain DBLSPACE.BIN.
 2.	Delete the DBLSPACE.* files from the root directory of your hard disk.
	For example, type the following at the MS-DOS command prompt and press ENTER:
  
deltree /y c:\dblspace.*
  
 3.	Edit your AUTOEXEC.BAT file and remove any DoubleSpace commands.
 4.	Edit your CONFIG.SYS file and remove the following line:
  
devicehigh=c:\dos\dblspace.sys /move
  
 5.	Remove any floppy disks from your disk drives and restart your computer.
 6.	Follow this procedure to modify DBLSPACE.BIN so that it does not make the INT 1A ROM BIOS call.
	Use Debug to load DBLSPACE.BIN into memory. At the MS-DOS prompt type the following command and press ENTER: 
  
debug c:\dos\dblspace.bin
  
	Press ENTER after typing the following commands:
  
DEBUG               COMMAND
PROMPTS             TO ENTER    COMMENTS
-------             --------    --------
-                    e c7ea      Edit C7EA
nnnn:C7EA CD.        90          Replace INT opcode with NOP
-                    e c7eb      Edit C7EB
nnnn:C7EB 1A.        90          Replace 1A INT number w/ NOP
-                    w           Write the file back to disk
Writing 0C80E bytes
-                    q           Quit Debug
  
 7.	Run DoubleSpace Setup again.
  
More Information:
When DBLSPACE.BIN loads, it makes a call to Interrupt 1AH (Function B0H, Subfunction 01H) to check for the presence of a ROM-based MRCI provider. On systems that do not have a ROM-based MRCI provider, the ROM BIOS must process the INT 1Ah call and indicate that the function was not successful. Microsoft has found that with some ROM BIOS chip sets the stack becomes corrupted when this function call is processed.
The Debug procedure removes the INT 1AH call from DBLSPACE.BIN. On systems with no ROM-based MRCI provider this does not alter the performance of DoubleSpace. The Debug procedure should not be performed on systems that have a ROM-based MRCI provider. 
  
Note   At this time, no ROM-based MRCI providers are available on the market. 
  
19. Determining Which Files to Back Up When You Use DoubleSpace
When you use DoubleSpace, you should back up the files on your compressed volume, not the compressed volume file (CVF) on the host drive. For example, if you have compressed drive C and DoubleSpace has created the host drive as drive H, you should back up all your files on drive C and any data files left on drive H. You do not need to back up any DBLSPACE.<nnn> files (for example, DBLSPACE.000) on the host drive.
This allows you to restore single files from drive C if necessary. If you back up only the  DBLSPACE.<nnn> file(s) you can restore only an entire drive. This could be a problem because all change to all files (on the compressed drive) since the last backup are overwritten when you restore the DBLSPACE.<nnn> file. 
For more information on DoubleSpace terminology, run DoubleSpace, choose Contents from the Help menu, and then select Understanding DoubleSpace Terms.


 