readme.txt

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

   2) Or, ensure that there is at least one device driver (for example,
      ANSI.SYS) loaded in your CONFIG.SYS file AFTER the ATDOSXL.SYS
      driver but BEFORE the DRVSPACE.SYS driver.


5. MICROSOFT BACKUP, DEFRAG AND ANTI-VIRUS
==========================================

5.1 Microsoft Anti-Virus
------------------------
Before cleaning a program file, make sure you have a backup copy of it.
If you clean a program file, and the program is corrupted, reinstall the
program. If Anti-Virus again detects a virus, there is a chance the
detection is in error; contact your software vendor to determine if an
updated version of the program is available.

5.2 Running Microsoft Backup for MS-DOS under Windows
-----------------------------------------------------
You should not run Backup for MS-DOS while Windows is running.  Use
Backup for Windows instead (Backups created using Backup for Windows
can be restored using Backup for MS-DOS).  If you do not have Backup
for Windows installed, see "Installing Anti-Virus, Backup, and Undelete
after Setup" in the "Getting Started" chapter of the Microsoft MS-DOS 
USER'S GUIDE.

5.3  Backup for Windows stops running at the end of the compatibility test
--------------------------------------------------------------------------
If Backup for Windows stops running at the end of the Compatibility
Test, you might be loading an incompatible third-party backup driver
in your SYSTEM.INI file. Carry out the following procedure.

NOTE  This procedure disables your third-party backup program.

1. Open your SYSTEM.INI file, and locate the [386Enh] section.

2. Determine whether any of the following lines are included in this
   section:

   DEVICE=FASTBACK.386
   DEVICE=VFD.386
   DEVICE=CPBVXD.386
   DEVICE=VIRWT.386

3. If you find any of these lines, add a semicolon (;) to the front
   of the line.

4. Save the file, restart Windows, and run Backup for Windows again.

5.4  Running Microsoft Backup with TI4000 and Gateway NOMAD computers
---------------------------------------------------------------------
To avoid a conflict between the Turbo feature and Microsoft Backup
for Windows or MS-DOS, add a /L0 switch to the DEVICE command in
your CONFIG.SYS that loads the BATTERY.PRO file. Or, before you
run Microsoft Backup, type SETPOWER /L0 at the command prompt.

5.5 Using MS-DOS 6.22 Backup to Restore MS-DOS 6 or 6.2 Backups
---------------------------------------------------------------
Like earlier versions of MS-DOS Backup, the Backup programs included 
with MS-DOS version 6.22 support data compression during backup. 
However, the MS-DOS 6.22 Backup programs use a different compression
format from earlier versions of Backup.

Because of this, MS-DOS 6.22 Backup for Windows (MWBACKUP.EXE) cannot 
restore compressed backups created by MS-DOS 6 or 6.2 Backup. To
restore such backups, use the version of Backup that created them, or
use MS-DOS 6.22 Backup for MS-DOS (MSBACKUP.EXE).

MS-DOS 6.22 Backup for MS-DOS (MSBACKUP.EXE) can restore earlier compressed
backups only if your system is running DoubleSpace (that is, if DBLSPACE.BIN
is loaded in memory). Otherwise, MSBACKUP.EXE cannot restore older backups;
to restore such backups, use the version of Backup that created them.

Both MSBACKUP.EXE and MWBACKUP.EXE can successfully restore 6 and 6.2 
backups made without data compression. If you unchecked the Compress 
Backup Data box in the Backup Options dialog before you backed up, you 
should have no problems restoring your data using the MS-DOS version 6.22 
Backup programs.

Restoring a Previous Version of Microsoft Backup
------------------------------------------------
When you run MS-DOS 6.22 Setup, it installs the 6.22 version of the 
Backup program(s). The following procedures explain how to re-install 
the MS-DOS 6 or 6.2 version of Backup for MS-DOS. The procedure you 
use differs depending on the size of your MS-DOS 6 or 6.2 disks. 
(The commands in these procedures assume that your Setup disks are 
in drive A and your MS-DOS files are located in the C:\DOS directory; 
if the disks or MS-DOS files are in a different drive or location, 
adjust the commands accordingly.)

If you have MS-DOS 6.2 disks (either 1.2 MB or 1.44 MB disks) or
MS-DOS 6 disks (1.2 MB disks only):

1. Insert Setup Disk 1 in drive A.

2. Type the following commands:

   COPY A:*.OVL C:\DOS
   EXPAND A:MSBACKUP.EXE C:\DOS
   EXPAND A:MSBACKUP.HLP C:\DOS
   EXPAND A:MSBCONFG.HLP C:\DOS

If you are using MS-DOS 6 disks (1.44 MB disks only):

1. Insert Setup Disk 2 in drive A.

2. Type the following commands:

   EXPAND A:MSBACKUP.EXE C:\DOS
   COPY A:*.OVL C:\DOS

3. Insert Setup Disk 3 in drive A.

4. Type the following commands:

   COPY A:*.OVL C:\DOS
   EXPAND A:MSBACKUP.HLP C:\DOS
   EXPAND A:MSBCONFG.HLP C:\DOS

   These commands copy Backup's files from drive A to the C:\DOS 
   directory. If Setup Disk 1 is in drive B, or if your MS-DOS files 
   are located in a directory other than C:\DOS, you should adjust
   the commands accordingly.

5.6 Microsoft Defragmenter
--------------------------
If you received the "Insufficient Memory" message from Microsoft
Defragmenter, use the MEM command to determine how much conventional,
upper, and extended (XMS) memory is available. In addition to using
all available conventional memory, Defragmenter can make use of up
to 384K of extended memory and 12K of upper memory.

To increase available memory, carry out the procedures in "An MS-DOS
program displays an out-of-memory message" in the chapter "Diagnosing
and Solving Problems" in the MICROSOFT MS-DOS USER'S GUIDE.

If less than 384K of extended memory is available, carry out
the procedures in "Freeing Extended Memory" in the "Making More
Memory Available" chapter in the MICROSOFT MS-DOS USER'S GUIDE.


6. THIRD-PARTY PROGRAMS
=======================

6.1 4DOS and NDOS
-----------------
4DOS and NDOS are compatible with MS-DOS 6.  However, to use some of the
new features in MS-DOS 6.22 (such as MemMaker, the LOADHIGH /L switch,
DIR compression switches, and the ability to bypass startup commands),
contact JP Software to obtain 4DOS 4.02 or later, or Symantec to obtain
Norton Utilities 7.0 or later.
 
If you use multiple configurations, 4DOS or NDOS will not automatically
run your AUTOEXEC.BAT file unless you include a /P on the SHELL line in
your CONFIG.SYS file.
 
To use MS-DOS 6.22 Help instead of 4DOS or NDOS Help, start it by using
COMMAND /C HELP, or define a 4DOS or NDOS alias to run HELP.COM from
your MS-DOS 6.2 directory.

6.2 Above Board 286 and Above Board Plus Installation
    Programs
-----------------------------------------------------
Do not use an Above Board installation program dated May 1989
or earlier until you disable programs that use extended memory,
such as SMARTDrive or RAMDrive. You might lose data if you leave
these programs enabled. After you have installed Above Board,
you can reenable these programs.

6.3 CodeView
-----------
CAUTION  Using versions 3.0 to 3.13 of the CodeView CV.EXE
file may cause data loss if your system has an 80386 memory
manager (such as EMM386.EXE) and device drivers or programs
that use extended memory. To determine which version you
have, type CV.EXE at the command prompt.

6.4 Colorado Tape Backup
------------------------
If you receive a message that you have two versions of the
VFINTD.386 file loaded, you probably need to edit your
SYSTEM.INI file. To do so, carry out the following procedure:

1. Open your SYSTEM.INI file and locate the [386Enh] section.
   You should see two lines similar to the following:

   DEVICE=C:\TAPE\CMSDTAPE.386
   DEVICE=C:\DOS\VFINTD.386

2. If you plan to use your Colorado Tape Backup program, add a semi-
   colon (;) before the DEVICE command for the VFINTD.386 file. If you
   plan to use Microsoft Backup, add a semi-colon before the DEVICE
   command for the CMSDTAPE.386 file.

3. Save the file, and restart Windows.

6.5 Fastback Plus
-----------------
If you have a version of Fifth Generation Systems Fastback Pluse earlier
than 3.0, use the LOADFIX command before running Fastback Plus or the
Fastback Plus installation program to ensure that you don't lose data. To
do so, type the following at the command prompt:

LOADFIX FB.EXE

or

LOADFIX FBINSTAL.EXE

6.6 Norton Desktop for Windows 2.0
----------------------------------
Setup adds a second Tools menu which contains Microsoft Backup and
Antivirus commands (if you installed these Windows programs),
as well as a Compression Info command (if DoubleSpace or DriveSpace 
is installed).

If you use compress the drive that contains SmartCan, you might 
experience system problems afterward. To correct this, reinstall 
Norton Desktop for Windows.

For information about using Norton AntiVirus in conjunction with
DoubleSpace or DriveSpace, see the following section.

6.7 Norton Utilities
--------------------
Norton Speed Disk and Norton Disk Doctor versions 8.0 and earlier will 
not run on DriveSpace drives. For an updated version of these Norton 
utilities, contact your software vendor.

The "Clear Space" option of Norton Speed Disk (prior to version 7.0)
is incompatible with DoubleSpace drives and DriveSpace drives. For 
an updated version of Norton Speed Disk, contact your software vendor.

Do not use the WipeInfo utility (prior to version 8.0) on compressed 
drives. It can cause lost clusters. If you have already used this 
option, use the SCANDISK command to fix the lost clusters.

If Norton AntiVirus is running when you compress the drive that 
contains the NAV_.SYS file, a copy of the NAV_.SYS file remains 
on the host drive. This prevents Norton AntiVirus from reporting a 
virus infection during the compression process. After the compression 
process is complete, you can safely delete the copy of NAV_.SYS on 
the host drive.

If you use the Norton Cache or Speedrive utilities, load the utility
after the DEVICE command that loads DRVSPACE.SYS. For more information,
see section 7.24.

6.8 PC Tools
------------
If PC Shell does not show all of the files or directories on your drive, 
quit PC Shell immediately and contact Central Point Software for an update. 

CAUTION: Do not attempt to use PC Shell on that drive; severe data 
	 loss might occur. This problem affects both compressed and 
	 non-compressed drives. 

The DISKFIX /SCAN option in PC Tools can cause lost clusters on
DriveSpace and DoubleSpace drives. Avoid using this option. (If you 
have already used this option, use ScanDisk to fix the lost clusters.)

The COMPRESS command of PC Tools versions 6.0 and 5.5 
is incompatible with DoubleSpace and DriveSpace.

6.9  QEMM's Stealth DoubleSpace Feature
---------------------------------------
The Stealth DoubleSpace feature of QEMM versions 7.03 and 7.04 are 
fully compatible with MS-DOS 6.22; these versions are available to all 
QEMM 7 users through online services such as CompuServe, BIX, and the 
QuarterDeck BBS, as well as directly from QuarterDeck Office Systems.

The Stealth DoubleSpace driver (ST-DBL.SYS) included with version 7.02 is 
compatible with DoubleSpace, but not with DriveSpace, DEFRAG.EXE or 
automounting compressed floppies. If you use QEMM version 7.02, obtain an 
update from one of the online services listed above or from QuarterDeck 
Office Systems.

The Stealth DoubleSpace driver (ST-DBL.SYS) included with version 7.01 is 
incompatible with MS-DOS 6.22 (both DriveSpace and DoubleSpace). If you use 
QEMM version 7.01 and your system does not start, see the following section.

If you use the Stealth DoubleSpace feature of QEMM version 7.01
---------------------------------------------------------------
The Stealth DoubleSpace feature of QEMM 7.01 is incompatible with 
MS-DOS 6.22. If you are running DoubleSpace and use the Stealth DoubleSpace 
feature of QEMM version 7.01, your computer will not start properly. 

To work around this problem, press F8 when your computer starts.
Answer Y to all prompts except the following:  

    DEVICE=C:\QEMM\ST-DBL.SYS [Y/N]?

When MS-DOS displays this prompt, answer N. (The pathname for
ST-DBL.SYS may be different on your computer.) After your computer 
starts, edit your CONFIG.SYS file and make the following changes:

 * Disable the DEVICE command for ST-DBL.SYS by using the REM command.
 
 * If you use DoubleSpace, add a DEVICE command for DBLSPACE.SYS.
   For example:

   DEVICE=C:\DOS\DBLSPACE.SYS /MOVE

   (If you use DriveSpace, add a DEVICE command for DRVSPACE instead.)
   
   
6.10  Johnson Computer Systems PC-Vault and PC-Vault Plus
---------------------------------------------------------
If you use version 4.6 or earlier of the PC-Vault or PC-Vault Plus 
hard disk protection system, do not use the Maximum Floppy
Boot Protection option if you use DoubleSpace or DriveSpace.

In these versions of PC-Vault and PC-Vault plus, the Maximum Floppy 
Boot Protection option is incompatible with DoubleSpace and DriveSpace,
and may cause data loss. If your version of PC-Vault or PC-Vault Plus
is earlier than 4.6, contact Johnson Computer Systems for an upgrade.

6.11  AddStor Double Tools 
--------------------------
AddStor's Double Tools version 1.0 and 1.2 work only with DoubleSpace;
they do not work with DriveSpace.

AddStor's Double Tools version 1.0 works with MS-DOS 6.22 DoubleSpace
as long as you do not install AddStor's enhanced DoubleSpace drivers.
When you install Double Tools version 1.0, do not check the "Install 
enhanced DoubleSpace drivers" box. If you do, Double Tools will replace the 
MS-DOS 6.22 DBLSPACE.BIN file with the Double Tools version of DBLSPACE.BIN, 
which is compatible only with MS-DOS 6.0. The next time you start your 
computer, it will display the message "Wrong DBLSPACE.BIN version" and 
none of your compressed drives will be mounted. 

If you are using Double Tools version 1.0 or 1.2 with the enhanced
DoubleSpace driver installed, you will not be able to run MS-DOS 6.22
Setup. To solve this problem, run Double Tools' DTCONFIG.EXE program
and choose the "Microsoft" (version 1.0) or "Standard" (version 1.2)
option. Then save your changes, exit from DTCONFIG, and run MS-DOS 
6.22 Setup again.


7. DRIVESPACE
=============
MS-DOS 6.22 includes DriveSpace compression software. DriveSpace appears
similar to DoubleSpace, which was included with MS-DOS 6 and 6.2. The
main difference is that DriveSpace stores compressed data in a different
format from DoubleSpace. 

Note: If you upgraded from MS-DOS 6 or MS-DOS 6.2, you can still use
      DoubleSpace with MS-DOS 6.22. (If you upgraded from MS-DOS 5 or 
      earlier, you do not have DoubleSpace on your system.)

7.1 Converting DoubleSpace Drives to DriveSpace