readme.txt

Dos6.22安装软件,现在使用Dos的朋友不是很多了,希望能大家一些方便.

a network drive.

7.15 DriveSpace and PC-Vault
-----------------------------
See section 6.10.
  
7.16 Maximum size of a compressed drive
---------------------------------------
The maximum size for a DriveSpace compressed drive is 512 megabytes (MB).
For example, if you compress a disk drive that is 600 MB, the resulting
DriveSpace drive will be no larger than 512 MB. To compress the rest of
the disk drive, run DriveSpace, and choose Create New Drive from the 
Compress menu. Make the new compressed drive as large as possible.
(If your drive is very large, you might need to create several new 
compressed drives in order to compress the entire drive.)

7.17  DriveSpace could not mount a drive due to problems with the drive
-----------------------------------------------------------------------
If the message "DriveSpace could not mount drive X due to problems
with the drive" (in which X is the drive letter) appears when you start
your computer, then the internal organization of the drive has problems
that prevent the drive from being used. DriveSpace stores each
compressed drive in a special file called a compressed volume file (CVF).
The CVF is a file with the hidden, system, and read-only attributes; it
is stored on an uncompressed drive.

To use the compressed drive again, you need to run ScanDisk on that
drive's compressed volume file, and then restart your system. The
error message includes the name of the compressed volume file on which
you need to run ScanDisk (for example, C:\DRVSPACE.000).

To fix this problem for a compressed drive other than drive C:

  o  Type the SCANDISK command specified by the DriveSpace error
     message. For example, SCANDISK D:\DRVSPACE.001. (If MS-DOS cannot
     find the SCANDISK program, see the following procedure.)

To fix this problem for compressed drive C, or if MS-DOS cannot find
the SCANDISK program:

1. Insert Setup Disk 1 in drive A (or B) of your computer.

2. Change to the drive that contains Setup Disk 1.

3. To start ScanDisk, type the SCANDISK command as specified by
   the DriveSpace error message. For example, SCANDISK C:\DRVSPACE.000.
   When ScanDisk displays dialogs describing any problems, choose
   the Fix It button.

4. After ScanDisk has finished, remove the floppy disk and restart
   your computer.

7.18  DriveSpace finishes installation, but you cannot access your Hardcard
----------------------------------------------------------------------------
See section 4.2, part C.

7.19  You receive a DoubleGuard Alarm message
---------------------------------------------
If a DoubleGuard Alarm message appears, DoubleGuard has detected that
an application has damaged memory that DriveSpace was using. DoubleGuard
halts your computer to prevent any further damage to your data. 

Normally, each program "owns" a separate area of memory, and does not use
memory that another program is already using. However, a few programs
contain programming errors that cause them to inadvertently use memory
belonging to another program. If such a program inadvertently uses
memory belonging to DriveSpace, that program could write its own
data over the data DriveSpace was storing there. Since the data that
DriveSpace stores in memory usually includes files you are currently
using, this could cause damage to your data. 

DriveSpace's DoubleGuard safety-checking feature detects when another
program has violated DriveSpace's memory, and immediately shuts down
your computer to minimize the chance of data loss. (If further disk
activity were to occur instead, you could lose some or all of the 
data on your drive, since the data DriveSpace has in memory is probably
invalid due to damage by the other program.)

If you receive a DoubleGuard Alarm message, do the following:

1. Restart your computer by turning the power switch off and then 
   on again.

2. Type the following at the command prompt:

     SCANDISK /ALL

   This runs ScanDisk on all your drives to detect and correct any
   problems that might have been caused by the program that
   violated DriveSpace's memory.

3. Make a note of which program, if any, you were running when the
   DoubleGuard Alarm occurred. That program is probably (but not
   necessarily) the program that caused the DoubleGuard Alarm.
   If you receive additional DoubleGuard Alarms, take notes about
   what you were doing and see if you can detect a pattern.

7.20  A compressed drive is currently too fragmented to mount
-------------------------------------------------------------
If you receive the message "Compressed drive X is currently too
fragmented to mount" (in which X is the drive letter) when your
computer starts, or if DriveSpace displays the message "The
X:\DRVSPACE.nnn file is too fragmented to mount," then DriveSpace
cannot mount the drive because its compressed volume file is stored in
too many fragments on your hard disk. (DriveSpace stores each
compressed drive in a special file called a compressed volume file (CVF).
The CVF is a file with the hidden, system, and read-only attributes, and
is stored on an uncompressed drive.)

To correct this problem, increase the MaxFileFragments setting in your
DRVSPACE.INI file. DriveSpace displays the "too fragmented to mount"
error messages because the number of CVF file fragments exceeds this
setting. Follow these steps:

1. Change to the root directory of your startup drive. (If your
   startup drive is compressed, change to that drive's host drive.)

2. Type the following command:

     TYPE DRVSPACE.INI

3. Note the current value for the MaxFileFragments setting.

4. Use the DRVSPACE /MAXFILEFRAGMENTS command to specify a higher value.
   For example, if MaxFileFragments is currently set to 128, you might
   type the following command:

     DRVSPACE /MAXFILEFRAGMENTS=200

5. Restart your computer. DriveSpace should now be able to mount
   the drive.

If DriveSpace still cannot mount the drive, follow these steps:

1. Run ScanDisk to check the reliability of your hard disk by typing the
   following at the command prompt:

      SCANDISK /ALL /SURFACE

2. Restart your computer. If DriveSpace still cannot mount the drive,
   proceed to step 3.

3. Remove the Read-Only, System, and Hidden file attributes on the
   DRVSPACE.<XXX> file. For example, if the file is H:\DRVSPACE.000,
   type the following at the command prompt:

       ATTRIB H:\DRVSPACE.000 -R -S -H

4. Run Microsoft Defragmenter (Defrag) by typing DEFRAG at the
   command prompt.

5. Use the ATTRIB command to reset the file attributes on DRVSPACE.<XXX>.
   For example, if the file is H:\DRVSPACE.000, type the following at
   the command prompt:

       ATTRIB H:\DRVSPACE.000 +R +S +H

6. Restart your computer again. DriveSpace should now be able to mount
   the compressed drive.

7.21  You receive the message "Your computer is running with an
      incompatible version of DBLSPACE.BIN" 
----------------------------------------------------------------
If you try to run the MS-DOS 6 version of DBLSPACE.EXE with MS-DOS 6.2,
it displays the following message:

  Your computer is running with an incompatible version of DBLSPACE.BIN.
  You must update DBLSPACE.BIN on the root directory of drive @.

DBLSPACE.EXE has detected that its version number does not match that 
of your MS-DOS 6.2 DBLSPACE.BIN. To correct this problem, you need to
update this copy of the DBLSPACE.EXE file.

When you run MS-DOS 6.22 Setup, it updates the DBLSPACE.EXE file in
the directory that contains your MS-DOS files. If there are other
copies of DBLSPACE.EXE elsewhere on your disk -- for example, in the root
directory of your host drive -- Setup does not update those additional
copies. To update them yourself, use the COPY /Y command to copy the 
MS-DOS 6.22 version of DBLSPACE.EXE over the older versions. (The MS-DOS
6.22 version of DBLSPACE.EXE is located in the directory that contains
your MS-DOS files.)

7.22  Using the DRVSPACE command after bypassing DRVSPACE.BIN
-------------------------------------------------------------
If you bypass DRVSPACE.BIN when you start your computer (by pressing
CTRL+F5 or CTRL+F8), then the DRVSPACE command may not work as
expected:

 * Usually, if DriveSpace is installed, typing DRVSPACE runs the
   DriveSpace program. However, if you type DRVSPACE when 
   DRVSPACE.BIN is not loaded, DriveSpace Setup starts instead. 
   If this happens, quit DriveSpace Setup. 

 * If you type the DRVSPACE /MOUNT command, it reports that there
   are no more drive letters for DriveSpace to use. (DriveSpace
   cannot mount a compressed drive unless DRVSPACE.BIN is loaded.)

To use DriveSpace or your compressed drives, restart your computer
without bypassing DRVSPACE.BIN.

7.23  Removing the write-protection from a compressed floppy disk
-----------------------------------------------------------------
If you are using a compressed floppy disk that is write-protected
and Automounting is enabled, the disk will remain write-protected
until it is unmounted -- even if you remove the write-protect tab 
from it.

To remove the write protection, use either of the following methods:

 * Unmount the floppy disk by using the DRVSPACE /UNMOUNT command, 
   and then try using the disk again (this will automatically 
   remount it). For example, if the disk is in drive B, you would
   type DRVSPACE /UNMOUNT B: and then try using the disk again.
   (If Windows is running, you can't use the DRVSPACE /UNMOUNT
   command. In that case, use the following method.)

 * Insert a different floppy disk in the drive and access it (for
   example, carry out the DIR command on it). This automatically
   unmounts the compressed floppy disk that was previously in the
   drive.) Then, reinsert the compressed floppy disk and try using
   it again (this will automatically remount it).

NOTE  If you are using DriveSpace and mount an unconverted DoubleSpace 
      floppy disk, the disk will be mounted with write-protected.
      The only way to remove the write protection on such a disk is
      to convert it to DriveSpace format; for information on converting
      it, see section 7.1.

7.24  Automounting and Norton disk-caching utilities
----------------------------------------------------
If you use a Norton disk-caching utility such as Norton Cache 
(NCACHE2.EXE) or Norton Speedrive (SPEEDRV.EXE) make sure the 
utility is loaded after the DEVICE command for DRVSPACE.SYS. 
If you load one of these utilities before DRVSPACE.SYS, 
DriveSpace's automounting feature will not work.

7.25  Undelete utilities and DriveSpace
----------------------------------------
DriveSpace cannot compress or uncompress drives while an undelete 
utility (for example, Microsoft Undelete's Delete Sentry or Norton's
SmartCan) is running. To compress or uncompress a drive, you will need 
to temporarily disable the undelete utility. Follow these steps:

1. Purge any previously deleted files to conserve disk space. If you 
   are using Microsoft Delete Sentry, type the following at the command 
   prompt:

   UNDELETE /PURGE

   Carry out this command on each drive you plan to compress or uncompress. 
   If you will be uncompressing a drive, you should also purge deleted 
   files from that drive's host drive. To purge deleted files from a 
   drive other than the current drive, specify the drive letter after
   the UNDELETE /PURGE command (for example, UNDELETE /PURGE E:).

   If you use a different undelete utility, see that utility's 
   documentation for information about purging deleted files.

2. Edit your AUTOEXEC.BAT file and use the REM command to disable 
   the command that starts the undelete utility. (For example, if 
   you use Delete Sentry, disable the UNDELETE /S command.)

3. Restart your computer.

4. Try again to compress or uncompress the drive.

5. When you have finished compressing or uncompressing, edit your 
   AUTOEXEC.BAT file, reenable the command that starts the undelete
   utility, and then restart your computer again.

7.26  Creating an Emergency Startup Disk for DriveSpace Systems
----------------------------------------------------------------
To create an MS-DOS 6.22 startup disk if you use DriveSpace:

1. If you are upgrading from MS-DOS 6.0, install MS-DOS 6.22 in the 
   directory that contains your previous version of MS-DOS. 
   
2. To create a startup floppy disk, run Setup again by typing the following 
   command:

   SETUP /F

   Setup installs MS-DOS 6.22 on the floppy disk. The resulting startup disk
   does not include DRVSPACE.BIN, since MS-DOS 6.22 does not include 
   DriveSpace.

3. Add the DRVSPACE.BIN file to the floppy disk by copying it from the
   directory that contains your MS-DOS files. For example, if your MS-DOS
   directory is C:\DOS and the floppy disk is in drive A, you would type:

   COPY C:\DOS\DRVSPACE.BIN A:

Note: If you are upgrading from MS-DOS 6 but need to install to the 
      floppy disk without first installing MS-DOS 6.22 on your hard disk, 
      you can skip Step 1. However, the resulting startup disk will include 
      MS-DOS 6 DoubleSpace rather than MS-DOS 6.2 DoubleSpace. When you 
      start your computer using such a startup disk, you will receive a 
      message from DoubleSpace; to continue, just press ENTER.

7.27 If ScanDisk Cannot Check or Repair a DoubleSpace Volume File
-----------------------------------------------------------------
MS-DOS 6.22 ScanDisk can check DoubleSpace drive or volume files only 
if DoubleSpace is installed. If you try to check or repair a DoubleSpace 
volume file and DBLSPACE.BIN is not loaded into memory, ScanDisk displays 
an error message like the following:

   ScanDisk cannot check or repair DoubleSpace volume file C:\DBLSPACE.001.

The cause of the problem might be one of the following:

 *  You upgraded to MS-DOS 6.22 from MS-DOS version 5 or earlier. In this
    case, you cannot use ScanDisk to check DoubleSpace drives.

 *  DoubleSpace is installed on your system, but you started your
    computer from a floppy disk or by pressing CTRL+F5 or CTRL+F8. If this 
    is the case, remove any floppy disks from your drives, restart your 
    computer, and try running ScanDisk again. 
    
If DoubleSpace is not installed, you will need to load DBLSPACE.BIN
in order to check and repair the DoubleSpace drive.

To load DoubleSpace:

1. Type the following at the command prompt, and then press ENTER:

	REM >> C:\DBLSPACE.INI        
	
   This command creates a new DBLSPACE.INI file, if one does not already
   exist.
	
2. Restart your computer, and then try running ScanDisk again.

3. If DoubleSpace still did not load, copy the DBLSPACE.BIN file from your
   MS-DOS directory to the root directory of drive C. For example, if your
   MS-DOS files are in the C:\DOS directory, you would type the following:

	COPY C:\DOS\DBLSPACE.BIN C:\

4. Restart your computer, and then try running ScanDisk again.

5. If DoubleSpace still did not load, try copying the DBLSPACE.BIN file    
   from MS-DOS 6.2 Setup Disk 1 or from the Uninstall disk you created
   when upgrading from MS-DOS 6 or 6.2. For example, if the disk is
   in drive A, you would type:

	COPY A:\DBLSPACE.BIN C:\

6. Restart your computer, and then try running ScanDisk again.