readme.txt

DOS的一些基础工具

4. Insert MS-DOS 6.22 Setup Disk 1 in drive A or drive B, and then
   type A:SETUP or B:SETUP. 


1.20  Changes to International Keyboard and Character Set Support
-----------------------------------------------------------------
MS-DOS 6.22 includes new codepage information files EGA2.CPI, 
EGA3.CPI and ISO.CPI, as well as the new KEYBRD2.SYS file, which
offers additional keyboards. MS-DOS also includes new country settings 
in COUNTRY.SYS.

For details about enhancements to the international keyboard and codepage
(character set) support, see the COUNTRY.TXT file, which is located in
the directory that contains your MS-DOS files.


2. MEMMAKER AND MEMORY MANAGEMENT
=================================

2.1 Intel Expanded-Memory Driver (EMM.SYS)
------------------------------------------
If you use Intel's EMM.SYS driver with Aboveboard, use EMM.SYS
version 4.0 revision E if you an ISA system, or EMM.SYS version 4.0
revision D if you have an MCA or other system. Contact Intel for a
free upgrade.

2.2 Running MemMaker on a Computer with PC-NFS
----------------------------------------------
If you use PC-NFS network software, carry out the following procedure
before you run MemMaker:

1. Open your MEMMAKER.INF file by using any text editor. This file is
   in the directory that contains your MS-DOS files.

2. Add the following line to the file:

   *NET

3. Save the file, and then run MemMaker.

2.3 You have a Super VGA display and want to conserve memory.
-------------------------------------------------------------
If you use Microsoft Windows on an 80386 computer with extended
memory and a Super VGA display, you can use the MONOUMB.386 file, in
conjunction with MemMaker, to conserve conventional memory for
running programs.

To conserve memory if you have a Super VGA display:

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

2. Add a DEVICE command for the MONOUMB.386 file, which is located
   in your MS-DOS directory. For example, if your MS-DOS files are in
   C:\DOS, add the following line to this section:

   DEVICE=C:\DOS\MONOUMB.386

3. Save the file, and restart your computer.
  
4. After your computer starts, run MemMaker by typing MEMMAKER at the
   command prompt.

5. Choose Custom Setup. On the Advanced Options screen, answer Yes to
   the question "Use monochrome region (B000-B7FF) for running programs?"
  
   Follow the instructions on your screen.

2.4 Using MemMaker with IBM LAN
-------------------------------
Before you run MemMaker, you might need to make adjustments to the
parameters specified for your IBM LAN support driver, DXMC0MOD.SYS. In
your CONFIG.SYS file, make sure that the DEVICE command that loads
DXMC0MOD.SYS includes one of the following before you run MemMaker:

o The first three parameters, as in the following example:

  DEVICE=C:\DXMC0MOD.SYS 400000000001,D800,1

o No parameters, as in the following example:

  DEVICE=C:\DXMC0MOD.SYS

o Some parameters and enough commas to fill in the first three
  parameters, as in the following example:

  DEVICE=C:\DXMC0MOD.SYS 400000000001,,

2.5 MemMaker and Adaptec SCSI devices
-------------------------------------
MemMaker is compatible with Adaptec SCSI devices. However, if you use
the ASPI4DOS.SYS driver to support your SCSI device, MemMaker by default
will exclude this driver from the optimization process. If you don't
use the SCSI device as your startup or boot drive, you can include the
ASPI4DOS.SYS driver in the optimization process. To do so, remove the
^ASPI4DOS entry in the MEMMAKER.INF file, and then run MemMaker.

2.6 Using MemMaker on a computer with PC Tools or PC-DOS RAMBoost
-----------------------------------------------------------------
You can use MemMaker or RAMBoost with MS-DOS, but not both at the
same time. MemMaker will prevent RAMBoost from loading, but not
remove its DEVICE= command from your CONFIG.SYS.

2.7 EMM386 detects an error in an application
---------------------------------------------
If EMM386 displays a message such as "EMM386 has detected error
#12 in an application," this indicates that the processor
has reported an exception error to EMM386. An exception error
typically occurs when an application gives the processor an
instruction under invalid or unexpected conditions. In most cases,
these errors are related to a specific program. If you are receiving
an error that does not occur with any particular application, the
error might be caused by a device driver or a memory-resident
(terminate-and-stay-resident) program.

To avoid these errors:

  o  Try to identify the program involved. One way to do this is
     to see if the error occurs when the program is not running.
     If you suspect a memory-resident program or device driver,
     try bypassing it when your computer starts.

  o  Try disabling EMM386. If a particular application is to blame,
     disabling EMM386 might allow that application to generate an
     error message. Disabling EMM386 might also change
     your memory configuration so that the error no longer occurs.

  o  Try changing the order in which you load device drivers and
     memory-resident programs. This might help because some
     errors occur only under specific memory conditions.

  o  If error 12 is occurring, this indicates that a stack is being used
     incorrectly. Try adding the following command to your CONFIG.SYS
     file:

	STACKS=18,512

  o  If error 13 is occurring, the program may be trying to use protected
     mode without cooperating with EMM386. You may need to obtain a
     VCPI-compliant version of the program, or not load EMM386 when
     using this application.

2.8  MemMaker no longer aggressively scans upper memory by default
------------------------------------------------------------------
By default, the MS-DOS 6.22 version of MemMaker does not scan upper
memory aggressively. Instead, the MemMaker option "Scan the upper 
memory area aggressively?" is set to No, and MemMaker limits its search 
for available UMBs to memory addresses C600 through EFFF. In contrast,
the MS-DOS 6 version of MemMaker did scan upper memory aggressively 
by default: in addition to scanning memory in the C600-EFFF range, 
it also scanned addresses in the range F000 through F7FF. 

To make more memory available for running programs, run MemMaker in 
Custom mode and change the "Scan the upper memory area aggressively?" 
option to Yes. (Note that, on some computers, putting UMBs in this 
range prevents the computer from starting properly.)

Note: If you last ran MemMaker with the "Scan the upper memory
      area aggresively" option set to Yes, then the next time
      you run MemMaker, it leaves that option set to Yes.


3. WINDOWS
==========

3.1 Your computer uses a Windows 3.0 permanent swap file.
---------------------------------------------------------
If your computer uses a Windows 3.0 permanent swap file, run
the SPATCH.BAT program to make the swap file compatible with MS-DOS 6.
To do so, carry out the following procedure:

1. Copy the SPATCH.BAT file to your hard disk. To determine the location of
   the file on the Setup disks, view the PACKING.LST file on Setup Disk
   1.

2. Type the following at the command prompt:

   SPATCH [DRIVE]:[PATH]SWAPFILE.EXE
  
   For the DRIVE and PATH parameters, specify the location of
   your SWAPFILE.EXE file.

3. Follow the instructions on your screen.

   The program modifies the SWAPFILE.EXE for use with MS-DOS 6
   and saves a backup copy as SWAPFILE.SAV. After you have confirmed
   the file works correctly, you can delete the SWAPFILE.SAV file.

3.2 Using compressed floppy disks with Windows File Manager
-----------------------------------------------------------
If you are using compressed floppy disks with automounting enabled,
you might encounter error messages or other problems while using File 
Manager. To work around these problems, press the F5 key twice.

For example, if you change from a compressed to an uncompressed floppy
disk, the drive button for the compressed floppy disk's host drive 
remains until you press the F5 key twice.


4. HARDWARE COMPATIBILITY WITH MS-DOS
=====================================

4.1 Compaq EXTDISK.SYS Driver
-----------------------------
The Compaq EXTDISK.SYS driver version 3.00 or later is
compatible with MS-DOS 6. If you have a version earlier
than 3.00, contact your vendor for an upgrade.

4.2 Hardcard
------------
If you upgraded your system from MS-DOS 6 or 6.2, your system
uses its Hardcard drive as its startup drive, and you want to use 
DoubleSpace on that drive, see section 7.18. For additional 
Hardcard information, see the following:

a) Hardcard II

   If you can't use Plus Development Hardcard II or Hardcard
   II XL when running EMM386.EXE, specify the exclude (x=)
   switch to prevent EMM386 from conflicting with the card's
   BIOS address.

   To configure EMM386, run MemMaker.

b) Hardcard 40 or Passport

   If you are using Hardcard 40 or a Passport removable
   disk, and you have a DEVICE command in your CONFIG.SYS file
   for PLUSDRV.SYS, disable or remove the DEVICE command.
   Then run MS-DOS 6.22 Setup. After Setup is complete, reenable or
   restore the DEVICE command for PLUSDRV.SYS. Make it the last line
   in the file.

c) If you upgraded your system from MS-DOS 6 or 6.2, installed 
   DoubleSpace on your Hardcard, and are now unable to access your 
   newly compressed drive, try the following:

   1) Add a DRVSPACE /MOUNT command to your AUTOEXEC.BAT file to mount
      the compressed volume file on the Hardcard every time you start
      your computer.

   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.

4.3 Toshiba
-----------
If you used the MS-DOS 5.0 version of EMM386 before you ran
Setup, and you use the Power Management function, use
the VRESUME program or device driver to avoid problems with
the Resume feature. Carry out the following procedure:

1. Make sure the VRESUME.COM or VRESUME.SYS file is on your hard disk.
   To load the TSR, add a command for VRESUME.COM to your AUTOEXEC.BAT file.
   To load the device driver, add a command for the VRESUME.SYS file to
   your CONFIG.SYS file.

2. Save the file, and restart your computer.

   NOTE  For information about using VRESUME with Windows 3.0, see the
   WRESUME.TXT file on your Toshiba MS-DOS 5.0 disks.

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