
README.TXT

++++++++++++++++++++++++++++++++++++++++++
This is a BETA version of README.TXT. 
Work is still in progress.
++++++++++++++++++++++++++++++++++++++++++

NOTES ON MS-DOS 6
===========================

This file provides important information not included in the
Microsoft MS-DOS User's Guide or in MS-DOS Help.

Look through the following table of contents to determine
whether your software or hardware is included.

If you have questions about procedures or commands mentioned
in this file, you will probably find answers in the
Microsoft MS-DOS User's Guide or, if you have installed 
MS-DOS 6, in MS-DOS Help.

The following topics are discussed in this file:

1. Notes on Setup
   1.1 Bernoulli Drive
   1.2 SpeedStor
   1.3 Columbia Data Products Device Driver
   1.4 Incompatible Hard Disk or Device Driver
   1.5 WYSE Partition
   1.6 286 Accelerator Card
   1.7 AT&T 6300 Computer
   1.8 Western Digital SCSI Hard-Disk Controller
   1.9 Toshiba with a Hard RAM Disk 
   1.10 Apricot XEN-S Computer
   1.11 4DOS
   1.12 LapLink
   1.13 Dell DOS 3.30
   1.14 Tandy with ROM DOS
   1.15 You have OS/2 on your computer
   1.16 Setup displays the "Your computer uses a disk-compression
        program that is incompatible with Setup" message
   1.17 You deleted files from the directory that Setup needs
        to install the optional programs
   1.18 Running Setup if Your Computer Uses Windows NT
   1.19 Setup detects that your computer has a non-MS-DOS 
        partition, and your computer uses Windows NT
   1.20 Setup detects that your computer uses DR-DOS
   1.21 Installing MS-DOS on a Drive Other Than C
   1.22 Bypassing the Uninstall Disk When You Run Setup

   
2. Notes on Memory Management
   2.1 386MAX (5.11 or Earlier)
   2.2 All Computers Inc. Expanded-Memory Driver
       (ALLEMM4.SYS)
   2.3 Intel Expanded-Memory Driver (EMM.SYS)
   2.4 XMAEM.SYS and XMA2EMS.SYS
   2.5 When you run Windows, MS-DOS indicates that your 
       display driver uses the monochrome address range
   2.6 MemMaker does not restart after the "MemMaker will now
       restart your computer to test the new memory configuration"
       screen
   2.7 4DOS is incompatible with MemMaker

   MemMaker stuff to follow
3. Notes on Windows
   3.1 Windows/286 2.1
   3.2 "High Memory Area in Use" Message (Windows/386 2.1)
   3.3 "Cannot run Windows in standard mode" Message
   3.4 Windows Setup does not detect Workgroup Connection
   3.5 Anti-Virus for Windows does not run in Windows 3.0 real mode
   3.6 Your computer uses a Windows 3.0 permanent swap file
4. Making Your Hardware Compatible with MS-DOS 6
   4.1 Acer 1100/33 and CTRL+ALT+DEL
   4.2 Amstrad Systems and KEYB.COM
   4.3 Apricot Qi 386 Systems
   4.4 AT&T Computer with an VDC 750 Display Adapter Card
   4.5 Compaq EXTDISK.SYS Driver
   4.6 Corel System Disk Drivers
   4.7 External Floppy Disk Drives
       * Nth
       * Procomm
       * Sysgen
   4.8 Hardcard
   4.9 Inboard 386/PC
   4.10 NCR VGA BIOS
   4.11 Olivetti System with a CGA Video Board
   4.12 Toshiba T3100SX
   4.13 Western Digital VGA Card
   4.14 XGA and EMM386.EXE
   4.15 Zenith Computer
   4.16 Zeos 486 and Task Swapper
5. Making Your Network Compatible with MS-DOS 6
   5.1  Your computer has network software and Setup
        referred you to the README.TXT file
   5.2  MS-DOS Shell and Networks 
   5.3  3+Share
   5.4  Artisoft LANtastic
   5.5  AT&T StarGroup (non-LAN Manager) 
   5.6  Banyan VINES
   5.7  DEC Pathworks and PCSA
   5.8  Farallon PhoneNet Talk Version 2.02 or Earlier
   5.9  IBM PC LAN
   5.10 IBM DOS LAN Requester Version 1.30 or Earlier
   5.11 Microsoft LAN Manager and 100-Percent Compatible
        Networks
   5.12 Microsoft MS-Net and 100-Percent Compatible
        Networks
   5.13 Net/One PC  
   5.14 Novell Networks
   5.15 PC-NFS 3.0
   5.16 Sitka TOPS
   5.17 TCS 10Net or DCA 10Net
6. Using Applications with MS-DOS 6
   6.1 4DOS
   6.2 Above Board 286 and Above Board Plus Installation
       Programs
   6.3 Amload
   6.4 AutoCAD release 10
   6.5 AUTORUN.EXE
   6.6 CodeView
   6.7 Defrag
   6.8 Easel 6.0
   6.9 Everex QIC-02 Tape Software
   6.10 Fastback
   6.11 GeoWorks
   6.12 Hyperdisk cannot find Shadow RAM 
   6.13 LINK.EXE: Unexpected Error Messages
   6.14 Lotus 1-2-3 versions 3.0 and 3.1
   6.15 Manifest
   6.16 Microsoft CD-ROM Extensions
   6.17 NDOS
   6.18 Norton Desktop for Windows 2.0
   6.19 Paintbrush
   6.20 Paradox 3.5
   6.21 PC Tools
   6.22 PC-Kwik Disk Accelerator
   6.23 PeachTree Complete III
   6.24 Pklite
   6.25 ProKey Plus
   6.26 Sidekick 2.0
   6.27 Soft-ICE
   6.28 Software Carousel
   6.29 Task Swapper and Asynchronous I/O
   6.30 Ventura Publisher
   6.31 WordPerfect WPINFO.EXE 5.1
   6.32 WordPerfect Office 3.0
   6.33 XTreeNet
7. Troubleshooting DoubleSpace
   7.1 Converting Your Disk-Compression Program to DoubleSpace
   7.2 DoubleSpace Setup indicates that your computer is 
       running an incompatible disk-caching program
   7.3 You attempt to mount a compressed floppy disk, and MS-DOS
       displays an error message
   7.4 Your uncompressed drive runs out of disk space
   7.5 Your computer runs out of disk space while compressing
       a drive
   7.6 TBD
   7.7 TBD
   7.8 TBD
   7.9 TBD
   7.10 Removing DoubleSpace From Your Computer
   7.11 Setting up Stacker Over DoubleSpace


1. README CONVENTIONS
=====================

1. NOTES ON SETUP
=================

1.1 Bernoulli Drive
-------------------
Disk Caching with Bernoulli Drive

For information about disk caching with a Bernoulli drive, 
see the chapter "Diagnosing and Solving Problems" of the 
Microsoft MS-DOS User's Guide.

Fixed Drive and Bernoulli Removable Drive

If your computer has a fixed disk drive, the fixed disk drive should
be used to boot your computer. The ROM on the Iomega PC2B or PC4B
adapter should be disabled. Refer to the Host Adapter Installation
guide for more information.

Bernoulli OAD and RCD Drivers

All versions of Iomega OAD drivers are compatible with MS-DOS 6.
The OAD drivers began shipping in May 1992

If you are using an Iomega RCD driver, such as RCD.SYS or RCD4.SYS,
you need at least version 4.7 for a PC2 adapter or version 6.2 for
a PC4 adapter. If you have an Iomega PC0 adapter (A10-20.COM) or a
PC3B adapter (RCD3.SYS), you will need a new adapter card. Contact
Iomega Customer Service for more information.

If you have problems installing MS-DOS 6 on a bootable 
Bernoulli drive, and you are using the new Iomega OAD driver, disable 
the driver in the CONFIG.SYS file before running Setup. To disable the 
driver, open your CONFIG.SYS file with any text editor and type "rem" 
and a space in front of the command that loads the driver. The command 
line should look something like this:

REM DEVICE=C:\OADDOS\DOSOAD.SYS

Save the file and restart your computer by pressing CTRL+ALT+DEL. Then
Run Setup again. If you cannot set up  MS-DOS, contact 
Iomega Customer Service for more information.

If you are able to set up MS-DOS, remove the "rem" from
the command line that loads the OAD driver, save the file, and
restart your computer.

     
1.2 SpeedStor
----------------------------------
If you have a SpeedStor partition on your computer, Setup 
probably referred you to this section for one of the following
reasons:

* Setup could not find in your CONFIG.SYS file a command 
  for the device driver that supports your SpeedStor partition. 
  If this is the case, add the command line to your CONFIG.SYS 
  file, restart your computer, and run Setup. For more information 
  about adding the command line to your CONFIG.SYS file, see your 
  SpeedStor documentation.

* Your CONFIG.SYS file has a DEVICE=HARDRIVE.SYS line in it.
  If this is the case, carry out the following procedure:
   1. Use the EXPAND command to expand and copy the SSTOR.SYS
      file to your hard disk. Make sure you copy the SSTOR.SYS
      file to the same path as the HARDRIVE.SYS file.
      
      See the PACKING.LST file on Setup Disk 1 for the location 
      of the SSTOR.SYS file on the Setup disks and for instructions
      on how to expand and copy it to your hard drive.

   2. Replace the DEVICE=HARDRIVE.SYS file with a DEVICE=SSTOR.SYS 
      command. For example, if the command that loaded the
      HARDRIVE.SYS file was "DEVICE=C:\SSTOR\HARDRIVE.SYS", you
      would replace it with the following:

      DEVICE=C:\SSTOR\SSTOR.SYS

   3. Restart your computer by pressing CTRL+ALT+DEL.

   4. To make sure you can access your hard drive, type the following
      at the command prompt:

      dir

   5. Insert Setup Disk 1 in drive A or B, and type the following 
      at the command prompt:
         
      a:setup

      or

      b:setup

If you have a Novell or Xenix partition, see the chapter
"Diagnosing and Solving Problems" of the Microsoft
MS-DOS User's Guide.

If your system is an IBM PS/2 or has MicroChannel
architecture, contact your software vendor for disk-
partitioning software that is compatible with MS-DOS 6.


1.3 Columbia Data Products Device Driver
----------------------------------------
If you use a Columbia Data Products device driver, carry 
out the following procedure:

1. Remove the DEVICE=SSTBIOS.SYS and DEVICE=SSTDRIVE.SYS
   commands from your CONFIG.SYS file before running
   Setup.

2. Restart your system.

3. Run Setup.

4. Reinstall the device drivers by returning the DEVICE=
   commands to your CONFIG.SYS file and restarting your
   system.
      
1.4 Incompatible Hard Disk or Device Driver
-------------------------------------------
If Setup referred you to this section, and no other section
in section 1 of this README.TXT file is relevant to your
system, you have a partition that is incompatible with MS-
DOS 6. You must delete the partition from your hard disk.
See "Using Fdisk to Configure Your Hard Disk" in the chapter
"Diagnosing and Solving Problems" of the Microsoft MS-DOS
User's Guide. Make sure you back up the files on your hard
drive before deleting your partition.

1.5 WYSE Partition
------------------
If you have partitions created by WYSE DOS 2.11 or 3.1,
you must delete them from your hard disk before running
Setup. See "Using Fdisk to Configure Your Hard Disk" in the  
chapter "Diagnosing and Solving Problems" of the
Microsoft MS-DOS User's Guide. Make sure you back up the files 
on your hard drive before deleting your partition.

1.6 286 Accelerator Card
------------------------
If your system includes a 286 accelerator card, Setup may
not be able to determine the amount of extended memory you
have and may incorrectly install MS-DOS 6. If this occurs,
disable the card before running Setup. If you can't disable
the card, install MS-DOS 6 manually, as described in the
chapter "Diagnosing and Solving Problems" of the Microsoft
MS-DOS User's Guide. 

1.7 AT&T 6300 Computer
---------------------- 
If you use an AT&T 6300 computer and your ROM BIOS is
version 1.20 or earlier, contact your vendor for a ROM BIOS
upgrade. The ROM BIOS version number is displayed when you
start your computer.

1.8 Western Digital SCSI Hard-Disk Controller
---------------------------------------------
If you are using a Western Digital WD 7000 FASST or AT/XT
SCSI controller with hard-disk ROM version 3.35 or earlier,
contact Columbia Data Products Customer Services for an
upgrade before installing MS-DOS 6. The ROM version number
is displayed when you start your computer.

1.9 Toshiba with a Hard RAM Disk
--------------------------------
These instructions apply to Toshiba models T1200, T1600,
T1200XE and T1000LE.

To use the hard RAM disk, carry out the following procedure
before installing MS-DOS 6:

1. Back up your hard RAM disk.

2. Using the Toshiba Setup program, delete the hard RAM
   disk by allocating zero kilobytes to it. All data on
   the hard RAM disk will be lost.
  
3. Restart your system.

4. Install MS-DOS 6.

5. Use the Toshiba Setup program to reinstall the hard RAM
   disk.

6. Run FDISK, change to drive 2, and create a primary DOS
   partition. Quit FDISK.
  
7. Use the FORMAT command to format drive D.

1.10 Apricot XEN-S Computer
---------------------------
To install MS-DOS 6 on an Apricot XEN-S computer, carry
out the following procedure:

1. Remove the DEVICE=AEMM386.SYS command from your
   CONFIG.SYS file.

2. Restart your system.

3. Run Setup.

4. Put the DEVICE=AEMM386.SYS command back in your
   CONFIG.SYS file and restart your system.
      
1.11 4DOS
---------
To use 4DOS with MS-DOS 6, contact JP Software to obtain
an updated version of 4DOS if you have a version that is
less than 4.01.

1.12 LapLink
-------------
If you use Traveling Software LapLink, disable the LapLink
device driver before you install MS-DOS 6. The driver 
conflicts with the Setup program. Once you install MS-
DOS 6, reenable the LapLink driver.

1.13 Dell DOS 3.30
------------------
Some Dell DOS 3.30 installations were done with a utility
called AFORMAT, which creates and formats multiple 32 MB
partitions. These extended partitions become invisible with
MS-DOS 6 unless you run a utility called FIXPART before or
after upgrading to MS-DOS 6. Contact Dell to obtain the
FIXPART utility.

1.14 Tandy with ROM DOS
-----------------------
Contact your hardware manufacturer for information about
upgrading a Tandy computer with ROM DOS to MS-DOS 6. This
applies to the following models: 1000HX, 1000SL, 1000SL2,
1000TL, 1000TL2, 1000TL3, 2500XL, 2500XL2.

1.15 You have OS/2 on your computer
-----------------------------------
If you have OS/2 on your computer, and the Microsoft 
MS-DOS User's Guide referred you to the README.TXT
file, carry out one of the following procedures.
The procedure you use depends on the configuration of
your computer. 

The following sections are divided into "If You Have Neither
OS/2 Dual Boot Nor OS/2 Boot Manager," "If You Have OS/2
Dual Boot with DOS or OS/2 Boot Manager with DOS," and "If
You Have OS/2 Boot Manager Without DOS."

If You Have Neither OS/2 Dual Boot Nor OS/2 Boot Manager

If you want to remove OS/2 from your computer but want 
to save the data on your hard disk first, carry out the 
following procedure when Setup displays the screen about 
reconfiguring your system.

To remove OS/2 and save the data on your computer:

1. When Setup displays a screen about OS/2, press F3 to 
   quit Setup.

2. When Setup prompts you to confirm that you want to 
   quit Setup, remove the Setup disk from drive A.

3. Press F3 again.

4. Restart your computer using OS/2.

5. Back up the data files you want to keep onto floppy 
   disks by using the COPY command.

Caution
Do not remove OS/2 system files from your hard disk. 
If you delete OS/2 system files, you will not be able to 
install MS-DOS on your computer.

6. Reinsert Setup Disk 1 in drive A (the startup drive).

7. Restart your computer by pressing CTRL+ALT+DEL.

8. When Setup displays the screen about OS/2, choose to 
   remove OS/2.

9. After you finish setting up MS-DOS, copy the data files 
   you saved in step 5 from the floppy disks back onto your 
   hard disk.

If You Have OS/2 Dual Boot with DOS or OS/2 Boot Manager
with DOS

When Setup detects OS/2, it displays an "OS/2 Partition 
Detected" or an "OS/2 Files Detected" screen. If Setup 
displayed the "Non-MS-DOS Partition Detected" screen, carry out
procedure 1. If Setup displayed the "OS/2 Files Detected"
screen, carry out procedure 2.

Procedure 1 To remove OS/2 and save the data on your 
computer:

1. When Setup displays the "Non-MS-DOS Partition Detected" 
   screen, choose the "Continue Setup" option.

2. After you set up MS-DOS 6, make sure you can access 
   your hard disk.

3. Insert Setup Disk 1 in drive A or B.

4. Back up the data files you want to keep onto floppy 
   disks or a network drive.

5. Read the following sections in "Using Fdisk to Configure
   Your Hard Disk" in the chapter "Diagnosing and Solving
   Problems." Carry out all the procedures that appear in these 
   sections:

   o "Making a Startup Disk"

   o "Deleting Non-MS-DOS Partitions"

   o "Deleting Logical Drives"

   o "Deleting an Extended MS-DOS Partition"

   o "Creating a Primary MS-DOS Partition"

   o "Formatting Your Hard Disk"

6. Restart Setup. To do so, insert Setup Disk 1 in drive 
   A or drive B, and then type the following at the command 
   prompt:

   a:setup

   or

   b:setup

7. After you configure your hard disk, copy the files you 
   saved in step 4 back onto it.

Procedure 2 To remove OS/2 and save the data on your 
computer:

Note
If you have a version of OS/2 other than version 2.0, 
the names of the OS/2 files and directories on your 
hard disk may differ from those that appear in this 
procedure.

Caution
Do not remove MS-DOS program files from your computer. 
If you delete your current MS-DOS program files, you will 
not be able to install MS-DOS 6.

1.  When Setup displays the "OS/2 Files Detected" screen, 
    choose the "Exit Setup" option.

2.  Back up the data files you want to keep onto floppy 
    disks or a network drive.

3.  If your Setup disks are compatible with drive A, insert
    Setup Disk 1 in drive A, and restart your computer by
    pressing CTRL+ALT+DEL. After Setup displays the first
    screen, press F3 twice to exit Setup.

    If your Setup disks are not compatible with drive A,
    insert Setup Disk 1 in drive B, and type the following 
    at the command prompt: 
   
    b:setup /f

    Follow the instructions on your screen. After Setup is
    finished, restart your computer by inserting the startup
    disk in drive A and pressing CTRL+ALT+DEL.
 
4.  Make drive C the current drive by typing the following 
    at the command prompt:

    c:

5.  One by one, make each of the OS/2 directories and 
    subdirectories current by using the CD command, and 
    then delete all the files in them by using the DEL 
    command. For example, to make the SYSTEM subdirectory in
    the OS2 directory current and delete all the files in it, 
    you would type the following at the command prompt:
   
    cd \os2\system
    del *.*

    If the SYSTEM directory has any subdirectories, delete 
    the files in the subdirectories, too.

6.  After you have deleted all files in these subdirectories, 
    delete the subdirectories by using the RD command. For 
    example, to delete the SYSTEM subdirectory in the OS2 
    directory, you would type:

    rd c:\os2\system

7.  After you have deleted all subdirectories in the OS2, 
    PSFONTS, SPOOL, NOWHERE, and OS!2_2.0_D directories, 
    delete all files in these directories by using the DEL 
    command.

8.  Delete the OS2, PSFONTS, SPOOL, NOWHERE, and OS!2_2.0_D 
    directories by using the RD command.

9.  Move to another disk or directory all the OS/2 files in 
    your root directory except the following:

    EA DATA.SF
    OS2lDR.MSG
    OS2lDR
    OS2KRNl
    OS2BOOT
    WP DATA. SF

10. Type CD to return to the root directory of drive C.

11. You must change the attributes of the five files listed 
    in step 9. To do so, type the following at the command
    prompt:

    a:\attrib -h -s -r c:\e*.*
    a:\attrib -h -s -r c:\o*.*
    a:\attrib -h -s -r c:\w*.*

12. To delete the files whose attributes you changed, type 
    the following:

    del e*.*
    del o*.*
    del w*.*

13. Return to the root directory the files that you moved in 
    step 9.

14. Remove disks from all floppy disk drives, and then restart 
    your computer by pressing CTRL+ALT+DEL.

15. Insert Setup Disk 1 in drive A or drive B.

16. Run Setup again by typing the following at the command prompt:

    a:setup

    or

    b:setup

If You Have OS/2 Boot Manager Without DOS

To remove OS/2 and save the data on your hard disk:

1. When Setup displays the screen about OS/2, choose 
   the "Exit Setup and see `Getting Started'" option.

2. Back up the data files you want to keep onto floppy 
   disks or a network drive by using the COPY command.
   
3. Reinsert Setup Disk 1 in drive A (the startup drive).

4. Restart your computer by pressing CTRL+ALT+DEL.

5. When Setup displays the screen about OS/2, choose 
   the "Remove OS/2 and reconfigure your hard disk" 
   option.

6. After you finish setting up MS-DOS, copy the data files 
   you saved in step 2 from the floppy disks back onto your
   hard disk.

1.16 Setup displays the "Your computer uses a disk-compression
     program that is incompatible with Setup" message
--------------------------------------------------------------
If Setup indicated that your computer has an incompatible
disk-compression program, carry out the following procedure
to install MS-DOS:

1. Exit Setup.

2. Back up the files on your hard disk.

3. If your Setup disks are compatible with drive A, insert
   Setup Disk 1, and restart your computer by pressing 
   CTRL+ALT+DEL. After Setup displays the first screen,
   exit Setup by pressing F3 twice.

   If your Setup disks are not compatible with drive A, 
   insert Setup Disk 1 in drive B, and type the following
   at the command prompt:

   b:setup /f

   Follow the instructions on your screen. After Setup is
   finished, restart your computer by inserting your startup
   disk in drive A, and pressing CTRL+ALT+DEL.

4. Type A:FORMAT C: /S to reformat your startup drive and 
   transfer the MS-DOS 6 system files.

5. Remove your Setup or startup disk from drive A, and 
   restart your computer by pressing CRTL+ALT+DEL.

6. Insert Setup Disk 1 in drive A or B, and type A:SETUP or
   B:Setup at the command prompt.

7. After Setup is complete, type DBLSPACE, and follow the
   instructions on your screen.

   For more information on DoubleSpace, see the chapter
   "Freeing Disk Space."

8. After you have installed DoubleSpace, restore the files
   you backed up. Make sure not to restore older versions of
   MS-DOS files over your MS-DOS 6 files.

1.17 You deleted files from the directory that Setup needs
     to install the optional programs
----------------------------------------------------------
If you typed "busetup /e" at the command prompt, Setup displayed
the "Setup did not find the files it needs in the directory
specified" message, and you think you deleted the files from
your hard disk, carry out the following procedure.

1  Insert Setup Disk 1 in drive A or B.

2  Type the following at the command prompt:

   A:SETUP /E

   or

   B:SETUP /E

   Setup copies the files back to your hard disk and configures
   them for use with Windows.

1.18 Running Setup if Your Computer Uses Windows NT
---------------------------------------------------
   
TBD
   
1.19 Setup detects that your computer has a non-MS-DOS 
     partition, and your computer uses Windows NT
------------------------------------------------------

TBD

1.20 Setup detects that your computer uses DR-DOS     
-------------------------------------------------

TBD

1.21 Installing MS-DOS on a Drive Other Than C 
----------------------------------------------

TBD

1.22 Bypassing the Uninstall Disk When You Run Setup
----------------------------------------------------
To keep Setup from creating an Uninstall Disk, run Setup
with the /G switch, as in the following example:

a:setup /g

or 

b:setup /g

NOTE
If you have a version of MS-DOS earlier than 5.0, and you use
the /G switch, Setup will not prompt you to update your network
files.


2. NOTES ON MEMMAKER AND MEMORY MANAGEMENT
==========================================

2.1 386MAX (5.11 or Earlier)
----------------------------
If you have used the SETVER command to report a different
version number to a program you are loading into the upper
memory area with 386LOAD.COM or MAXHI.COM, also use the
SETVER command to report that number to 386LOAD.COM or
MAXHI.COM. For information about the SETVER command, type
HELP SETVER at the command prompt after you have installed
MS-DOS 6.

The new version number is reported to all programs loaded by
386LOAD.COM and MAXHI.COM.

MAXHI.COM programs supplied with versions of 386MAX earlier
than 5.0 are incompatible with MS-DOS 6.

2.2 All Computers Inc. Expanded-Memory Driver (ALLEMM4.SYS)
----------------------------------------------------------
Version 2.5 or later of the All Computers expanded-memory
driver (ALLEMM4.SYS) is compatible with MS-DOS 6
HIMEM.SYS. Contact All Computers to get an updated driver.

2.3 Intel Expanded-Memory Driver (EMM.SYS)
------------------------------------------
If you use Intel's EMM.SYS driver with Aboveboard, use
EMM.SYS version 4.0 revision D or later. If you have an
earlier version, contact Intel for a free upgrade.

2.4 XMAEM.SYS and XMA2EMS.SYS
-----------------------------
Setup disables the CONFIG.SYS commands that load XMAEM.SYS
and XMA2EMS.SYS. If your system uses both drivers, replace
the commands with a DEVICE=EMM386.EXE command in your
CONFIG.SYS file.

If your system includes an XMA card, remove the REM command
that precedes the DEVICE=XMA2EMS.SYS command in your
CONFIG.SYS file.

2.5 When you run Windows, MS-DOS indicates that your display 
    driver uses the monochrome address range
------------------------------------------------------------
If your computer uses a Windows 3.0 display driver, you need
to modify your SYSTEM.INI file to make the driver compatible
with the MS-DOS 6 EMM386 memory manager. Carry out the 
following procedure:

1. Open your SYSTEM.INI file by using any text editor.

2. Find the [386enh] section.

3. Add a DEVICE= line for the MONOUMB.386 file. For example, if
   DOS is your MS-DOS directory, add the following line:

   DEVICE=C:\DOS\MONOUMB.386

4. Save the file.

5. Restart your computer by pressing CTRL+ALT+DEL.

6. Run Windows again.

2.6 MemMaker does not restart after the "MemMaker will now restart
    your computer to test the new memory configuration" screen
------------------------------------------------------------------
If your AUTOEXEC.BAT file contains a command (other than the CALL
command) that starts a batch program, MemMaker might not restart 
after it displays this screen. If this happens carry out the 
following procedure.

* Type the following at the command prompt:

   find /i "memmaker" autoexec.bat >t.bat

   Then type the following at the command prompt:

   t.bat

   MemMaker should restart normally.

2.7 4DOS is incompatible with MemMaker
--------------------------------------
4DOS does not recognize the \L parameter with the 
LOADHIGH (LH) command. Because MemMaker uses the
the \L parameter with the LH command to optimize
your computer's memory, you may experience problems
if you use MemMaker with 4DOS.


Other MemMaker stuff TBD

3. NOTES ON WINDOWS
===================

3.1 Windows/286 2.1
-------------------
If you run Windows/286 2.1 with MS-DOS 6, use PIF Editor
to specify a value of 128 in the KB Required option for
COMMAND.COM. For information about using PIF Editor and PIF
options, see the Microsoft Windows User's Guide.

3.2 "High Memory Area in Use" Message (Windows/386 2.1)
------------------------------------------------------
You cannot run Windows/386 2.1 when MS-DOS 6 is loaded
into the high memory area. Also, the MS-DOS 6 versions of
SMARTDRV.EXE and RAMDRIVE.SYS are not compatible with
Windows/386 2.1. To run Windows/386 2.1 with MS-DOS 6, use
the versions of SMARTDRV.EXE and RAMDRIVE.SYS that came with
Windows and remove the DOS=HIGH command, if any, from your
CONFIG.SYS file.

3.3 "Cannot run Windows in standard mode" Message
-------------------------------------------------
If you have a DEVICE=EMM386.EXE command that includes the
RAM or NOEMS switch in your CONFIG.SYS file, you cannot run
Windows 3.0 in standard mode. Either remove the RAM or NOEMS
switch or run Windows in real or enhanced mode. (If you
remove RAM or NOEMS, you won't be able to load programs and
device drivers into the upper memory area. If you include
RAM or NOEMS, you won't be able to run Windows in standard
mode.)

NOTE: Using EMM386 may reduce the amount of extended memory
available to Windows and cause Windows to try to start in
standard mode. To prevent this, reduce the amount of
extended memory that other device drivers use. For example,
if you are using SMARTDrive, try setting the MinCacheSize
parameter to 0.

3.4 Windows Setup does not detect Workgroup Connection
------------------------------------------------------
If you install the MS-DOS 6 Workgroup Connection and
Windows 3.1 Setup does not detect your network, carry out 
the following procedure:

1. If you have successfully installed Windows 3.1, exit
   Windows and make your Windows directory current. Then
   type SETUP at the command prompt.

   If you haven't successfully installed Windows 3.1, run
   Setup and choose Custom installation.

2. When Setup displays the screen listing your computer's
   hardware and software components, choose the Network
   option.

3. Select Microsoft Network (or 100% compatible) if you want
   basic redirector support. Select Microsoft LAN Manager
   (version 2.0 Enhanced) if you have full redirector
   support.

4. Press ENTER. When Setup displays an informational screen,
   press ENTER again.

5. When Setup displays the software and hardware components screen
   again, press ENTER, and follow the instructions on your screen.

3.5 Anti-Virus for Windows does not run in Windows 3.0 real mode 
----------------------------------------------------------------
If your computer is running Windows 3.0 in real mode, you cannot 
run Anti-Virus for Windows.

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

1. Make sure the SPATCH.EXE program is on your hard disk. If it
   isn't, expand it from the Setup disks. For the location of the
   file on the Setup disk, view the PACKING.LST file on Setup Disk
   1. For information about using the EXPAND command, type
   HELP EXPAND at the command prompt.

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.

4. MAKING YOUR HARDWARE COMPATIBLE WITH MS-DOS 
==================================================

4.1 Acer 1100/33 and CTRL+ALT+DEL
---------------------------------
If you have an Acer 1100/33 computer with an Award BIOS,
you may not be able to restart your system by using
CTRL+ALT+DEL. Contact Acer for a ROM BIOS upgrade.

4.2 Amstrad Systems and KEYB.COM
--------------------------------
If your Amstrad system has a ROM BIOS version earlier than
1.4, and you can't use your keyboard after loading KEYB.COM,
contact your vendor for a ROM BIOS upgrade.

4.3 Apricot Qi 386 Systems
--------------------------
If your Apricot Qi 300 fails to start while loading
EMM386.EXE, contact Apricot for a ROM BIOS upgrade.

Some Apricot Qi660 and Qi900 computers may not work if
MS-DOS 6 is loaded into the high memory area. Run MS-DOS
6 in conventional memory, or contact Apricot Computers for
more information.

4.4 AT&T Computer with an VDC 750 Display Adapter Card
-----------------------------------------------------
Before using the MS-DOS Shell Task Swapper on an AT&T
computer with a VDC 750 display adapter card, remove the
DEVICE=EGA.SYS command from your CONFIG.SYS file.

4.5 Compaq EXTDISK.SYS Driver
-----------------------------
Compaq EXTDISK.SYS driver version 3.00 or later is
compatible with MS-DOS 6. Contact your vendor for an
upgrade.

4.6 Corel Systems Disk Drivers
------------------------------
If your Corel Systems disk driver doesn't work correctly,
contact your vendor for an upgrade.

4.7 External Floppy Disk Drives
-------------------------------
If you can't use your Nth, Procomm, or Sysgen external
floppy disk drive, contact your vendor for an update.

4.8 Hardcard
------------
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.
   
   See your Hardcard II manual to determine which address
   space to exclude. Type HELP EMM386.EXE at the command
   prompt for more information about the exclude switch.
   
   b) Hardcard 40 or Passport
   
   If you are using Hardcard 40 or a Passport removable
   disk, and you have a DEVICE command for PLUSDRV.SYS in
   your CONFIG.SYS file, carry out the following procedure
   before upgrading to MS-DOS 6:
   
   1. Disable or remove the DEVICE command for PLUSDRV.SYS
      command line in your CONFIG.SYS file.
   2. Run MS-DOS 6 Setup.
   3. Reenable or return the DEVICE command for PLUSDRV.SYS
      in your CONFIG.SYS file. Make it the last line in the
      file.

4.9 Inboard 386/PC
-------------------

The Inboard 386/PC is incompatible with the EMM386 memory
manager that comes with MS-DOS 6. Do not load EMM386 in your
CONFIG.SYS file and do not run MemMaker.

4.10 NCR VGA BIOS
-----------------
If you have an NCR VGA BIOS and can't switch between screens
when running MS-DOS Shell or QBasic, see your NCR manual for
information about making your VGA BIOS PS/2 compatible.

4.11 Olivetti System with a CGA Video Board
-------------------------------------------
An Olivetti system with a CGA video board may not scroll
correctly. Add the /S switch to the DEVICE=ANSI.SYS command
in your CONFIG.SYS file.

4.12 Toshiba T3100SX
--------------------
Toshiba T3100SX computer's suspend/resume feature is
incompatible with EMM386.EXE. Either disable the feature or
do not use EMM386.EXE.

4.13 Western Digital VGA Card
-----------------------------
If you have a Western Digital VGA card and are using
RAMBIOS.EXE and RAMBIOS.SYS, load RAMBIOS.SYS before
ANSI.SYS and DISPLAY.SYS in your CONFIG.SYS file, and
RAMBIOS.EXE before GRAPHICS.COM in your AUTOEXEC.BAT file.

4.14 XGA and EMM386.EXE
-----------------------
If you use an XGA display with EMM386.EXE, you may need to
exclude certain memory ranges with the EMM386 exclude switch
(x=). To determine which memory ranges to exclude, use the
reference disk that came with your computer to view the
memory map.

For more information about the exclude switch, type
HELP EMM386.EXE at the command prompt.

4.15 Zenith Computer
--------------------
To use the GRAPHICS command with a Zenith computer, set the
STACKS command in your CONFIG.SYS file to at least
STACKS=9,256. For information about the STACKS command, type
HELP STACKS at the command prompt.

4.16 Zeos 486 and Task Swapper
------------------------------
If you have a Zeos 486 computer with a Mylex BIOS, you may
not be able to use Task Swapper in MS-DOS Shell. Contact
Zeos for a ROM BIOS upgrade.

5. MAKING YOUR NETWORK COMPATIBLE WITH MS-DOS 6
=================================================
If your network works with MS-DOS 5, no changes are
required to make it compatible with MS-DOS 6.

5.1 Your computer has network software and Setup
    referred you to the README.TXT file
------------------------------------------------

If Setup displayed the "You have specified that your
computer is connected to a network" screen, your computer
might be running an older version of network software
that is incompatible with MS-DOS 6. Check the sections 
below for your network software. If you don't find
instructions for making your network compatible
with MS-DOS 6, you should obtain an upgrade of your 
network software from your network vendor, install the 
upgraded network files, and then run Setup again. 

After you have upgraded your network software,
if Setup still displays the "You have specified
that your computer is connected to a network" screen,
choose the Continue option. Your network should work 
correctly with MS-DOS 6.

As an alternative to upgrading your network software, you 
can install Workgroup Connection, which is network software
that comes with MS-DOS 6 and is fully integrated with MS-DOS 6.
For instructions, see the chapter "Workgroup Connection" in
the Microsoft MS-DOS User's Guide.

5.2 MS-DOS Shell and Networks
-----------------------------
Most network software won't work correctly if you start it
from a MS-DOS Shell command prompt. Start your network
before starting MS-DOS Shell.

5.3 3+Share
-----------

If your network software is 3+Share, contact Microsoft Product 
Support Services. For information about contacting Microsoft 
Product Support Services, see the "Welcome" section of the
Microsoft MS-DOS User's Guide.

5.4 Artisoft LANtastic
----------------------

Before you run Setup with any version of Artisoft LANtastic, 
make sure to shut down the LANtastic server. There is no need
to shut down the redirector.

Artisoft LANtastic versions 3.02 and higher are compatible 
with MS-DOS 6.

If you are using LANtastic versions 2.5 through 3.01,
you need to type two SETVER commands at the command prompt.
The SETVER command reports to your network software the
version of MS-DOS that it was designed to run with--in this
case, version 4.0.

If you are using a LANtastic version earlier than 2.5,
contact your network vendor for an update.

To update LANtastic versions 3.01 or earlier:

1. Shut down the LANtastic server. You may leave the
   redirector running.

2. Set up MS-DOS 6 on your computer. For more information
   about installing MS-DOS 6, see "Getting Started."

   MS-DOS may display an "Incorrect DOS version" message
   when your network restarts. Ignore it.

3. Type the following command at the command prompt:

   setver server.exe 4.00

4. Restart your computer.

If you are using EMM386, you might need to exclude the
memory area used by the network adapter card. To do this,
use the x switch with the DEVICE command for EMM386.EXE in
your CONFIG.SYS file. If you are using the factory-set
defaults for the LANtastic 2Mbps adapter, include the x=d800-
dfff switch with the DEVICE command for EMM386.EXE. If this
memory region is not excluded, you might experience problems
with programs that use expanded memory.

For more information about EMM386 options, type HELP EMM386.EXE
at the command prompt after you have installed MS-DOS 6.

NOTE
The Microsoft Defrag program is incompatible with 
LANtastic network software if the server service is loaded. 
If only the redirector is loaded, the program is compatible
with LANtastic network software.

5.5 AT&T StarGroup (non-LAN Manager) 
------------------------------------
If your network software is AT&T StarGroup, you should run Setup
again, choose Continue when Setup displays the "You have
specified that your computer is connected to a network" screen,
and follow the instructions on your screen. If you cannot 
run your network software after Setup, carry out the following
procedure:

1  Type the following commands:

   SETVER SETUP.EXE 4.00
   SETVER ATTSTART.EXE 4.00

2  Restart your computer.

3  Use your StarGroup installation disks to remove the
   existing network software from your computer.

4  Reinstall StarGroup. When the StarGroup installation
   prompts you to indicate which version of MS-DOS you are
   using, choose MS-DOS version 4.0.

5.6 Banyan VINES 
----------------

Banyan VINES versions 4.1 and higher are compatible with MS-DOS 
6. You can use Banyan VINES version 4.0x with MS-DOS 6 if you
have the REDIRALL.EXE or REDIR4.EXE file in the BANYAN
directory on your hard disk.

If neither file is on your hard disk, but you have the VINES
installation disks that include one of these files, copy
the file to the directory on your hard disk that contains
network files.

If the files are not on either your hard disk or the VINES
installation disks, contact your Banyan VINES network
vendor.

If you have a VINES version earlier than 4.0, contact your
network vendor for an update.

5.7 DEC Pathworks and PCSA
--------------------------

If you have DEC PATHWORKS for DOS version 4.1,
carry out the following procedure:

1. If you are upgrading from MS-DOS version 3.3 or earlier,
   you need to update your redirector file, REDIR.EXE. Obtain
   REDIR.400 from the PATHWORKS disks or system service,
   rename it to REDIR.EXE, and place it in your DECNET
   directory.

2. Install MS-DOS 6 on your computer. For more information about 
   installing MS-DOS 6, see "Getting Started."

Version 4.0 of PATHWORKS for DOS is compatible with MS-DOS
6. However, you must take several steps to achieve this
compatibility.

To update PATHWORKS version 4.0:

1. If you are upgrading from MS-DOS version 3.3 or earlier,
   you need to update your redirector file, REDIR.EXE. Obtain
   REDIR.400 from the PATHWORKS disks or system service,
   rename it to REDIR.EXE, and place it in your DECNET
   directory.

2. Install MS-DOS 6 on your computer. For more information about 
   installing MS-DOS 6, see "Getting Started."

3. Restart your computer, but do not yet run STARTNET.BAT,
   which starts the network.

4. Type each of the following lines at the command prompt:

   setver use.exe 4.00

   setver memman.exe 4.00

   setver lad.exe 4.00

   setver show.exe 4.00

   setver netsetup.exe 4.00

5. Restart your computer, and run STARTNET.BAT.

Note: If you upgrade to PATHWORKS 4.1 from PATHWORKS 4.0,
      you must disable the SETVER commands you typed in this
      procedure. To do this after you install PATHWORKS 4.1,
      type the same commands, but replace the 4.00 with /d in
      each command.

If you are using a version of PATHWORKS or PCSA earlier than
4.0, contact your network vendor for an update. Meanwhile,
if you are using PATHWORKS or PCSA version 3.x, you can
start using MS-DOS 6 by carrying out the following
procedure.

Note: To get support for MS-DOS Task Swapper, use
      PATHWORKS for DOS version 4.1 or later.

To temporarily update PATHWORKS or PCSA version 3.x:

1. If you are upgrading from MS-DOS version 3.3 or earlier,
   you need to update your redirector file, REDIR.EXE. Obtain
   REDIR.400 from the PATHWORKS disks or system service,
   rename it to REDIR.EXE, and place it in your DECNET
   directory.

2. Install MS-DOS 6 on your computer. For more information about 
   installing MS-DOS 6, see "Getting Started." MS-DOS might display 
   a series of "Incorrect DOS version" messages when your network 
   restarts. Ignore these.

3. Type all of the following commands at the command
   prompt:

   setver use.exe 4.00
   setver emsload.exe 4.00
   setver sch.exe 4.00
   setver netsetup.exe 4.00
   setver ncp.exe 4.00
   setver dnnethat.exe 4.00
   setver lad.exe 4.00
   setver dll.dxe 4.00
   setver memman.exe 4.00
   setver dnnethld.exe 4.00
   setver show.exe 4.00

4. Restart your computer.

5.8 Farallon PhoneNet Talk Version 2.02 or Earlier
--------------------------------------------------
If your computer uses Farallo PhoneNet Talk version
2.02 or earlier, contact your network vendor for
updated network software.

5.9 IBM PC LAN
--------------
If you use IBM PC LAN 1.34 and have problems with
applications that use record locking or file locking, you
may need an updated REDIR50.EXE file included in ICO 3039.
Contact IBM Support Channel.

IBM PC LAN Program Version 1.33 or Earlier

To use MS-DOS 6 with IBM PC LAN Program (PCLP), you need
one of the following:

o IBM PCLP version 1.34 installed.

o IBM PCLP version 1.3x that has been updated to version
  1.34 by applying the appropriate IBM Corrective Service 
  Disks. Contact IBM Product Support to obtain the software 
  you need.

If you are running a PCLP version earlier than 1.30, contact
IBM for the necessary software and instructions.

To update IBM PCLP versions 1.30 through 1.34:

1. Skip to step 3 if you are upgrading from version 1.34.
   Otherwise, install the necessary IBM PCLP software by 
   following the instructions included with the Corrective 
   Service Disk(s) you received from IBM.

2. Restart your computer, and make sure the network starts.

   If the network doesn't start, quit this procedure and
   contact IBM for help.

3. Set up MS-DOS 6 on your computer. For more information
   about installing MS-DOS 6, see the chapter "Getting 
   Started."

4. Restart your computer.

   The following message appears on your screen:

   Start PC LAN Program 1.3 (Y/N)?

5. Type n, and press ENTER.

6. Type the following at the command prompt:

   setver net.com /d

7. Restart your computer.

   The following message appears on your screen:

   Start PC LAN Program 1.3 (Y/N)?

8. Type y, and press ENTER.

   Note: If, after setting up MS-DOS, your CONFIG.SYS file
         has a command for loading the IFSFUNC.EXE file,
         disable it by typing "rem" and a space in front
         of the command. Then save the file and restart
         your computer.

   Note: The Microsoft Defrag program will not run on a PCLP
         server.

5.10 IBM DOS LAN Requester Version 1.30 or Earlier
--------------------------------------------------

To use MS-DOS 6 with IBM DOS LAN Requester, you need one
of the following:

o DOS LAN Requester files that are included with OS/2 LAN
  Server version 1.30.1.

o DOS LAN Requester files that come with OS/2 LAN Server
  version 1.30, which has had IBM Corrective Service
  Diskette (CSD) 5015 applied to it.  Contact IBM Product
  Support to obtain the software you need.

If you are running a DOS LAN Requester version earlier than
1.30, contact IBM for the necessary software and
instructions.

To update IBM DOS LAN Requester version 1.30:

1. Upgrade your DOS LAN Requester software to version
   1.30.1 by following the instructions included with IBM
   Corrective Service Disk 5015.

2. Restart your computer and make sure the network starts.

   If the network doesn't start, quit this procedure and
   contact IBM for help.

3. Set up MS-DOS 6 on your computer. For more information
   about installing MS-DOS 6, see the chapter "Getting 
   Started."

4. Restart your computer.

   The following message appears on your screen:

   Start DOS LAN Requester (Y/N)?

5. Type n, and press ENTER.

6. Type the following at the command prompt:
 
   setver net.com /d

7. Restart your computer.

   The following message appears on your screen:

   Start DOS LAN Requester (Y/N)?

8. Type y, and press ENTER.

   Note: If, after setting up MS-DOS, your CONFIG.SYS file
         has a command for loading the IFSFUNC.EXE file,
         disable it by typing "rem" and a space in front
         of the command. Then save the file and restart
         your computer.

5.11 Microsoft LAN Manager and 100-Percent Compatible
     Networks
-----------------------------------------------------
If you are running any version of Microsoft LAN Manager
or a 100-Percent Compatible network, you should upgrade 
to Workgroup Connection. For information on installing 
Workgroup Connection, see the chapter "Workgroup Connection" 
in the Microsoft MS-DOS User's Guide.

5.12 Microsoft MS-Net and 100-Percent Compatible
     Networks
------------------------------------------------
If you are running any version of Microsoft MS-Net
or a 100-Percent Compatible network, you should upgrade 
to Workgroup Connection. For information on installing 
Workgroup Connection, see the chapter "Workgroup Connection" 
in the Microsoft MS-DOS User's Guide.

5.13 Net/One PC
---------------
If Ungermann-Bass Net/One PC does not load with MS-DOS 6,
do one of the following:
                              
*    Contact your vendor to get an updated LOADNIU.EXE file.
*    Put a UBPAUSE command between the LOADNIU and XNSBIOS
     lines of the MSNET.INI file.
*    Issue network commands from a batch file that includes a
     PAUSE command between the LOADNIU and XNSBIOS lines.
     
5.14 Novell Networks
--------------------
Contact your vendor for a version of the Novell shell which
is compatible with MS-DOS 6.

If your network software uses NETX.COM, you should obtain
version 3.26 or later for use with MS-DOS 6.

If you have a NetWare version earlier than 2.1, or your network
software uses any of the following files, contact your network
vendor:

NET3.COM
NET4.COM
XMSNET3.EXE
XMSNET4.EXE
EMSNET3.EXE
EMSNET4.EXE

If you can't use Task Swapper in MS-DOS Shell when running
a Novell network, contact your network vendor.

If you can't load MS-DOS 6 on your remote-boot workstation,
contact Novell for the RPLFIX.COM file.

If you run LOGIN.EXE, MAP.EXE, and SESSION.EXE from MS-DOS
Shell or while MS-DOS Shell is running, a search path is not
added to the existing path. Use these programs before starting
MS-DOS Shell.

If you use the Novell login program to set the COMSPEC
variable after starting MS-DOS 6, and you can't
reload the COMMAND.COM file, edit the SHELL command line
in your CONFIG.SYS file. Make sure the path to
COMMAND.COM points to the root directory and remove the
c:\dos\ parameter that follows the path, if one exists.

For example, suppose your SHELL command line looks like
this:

    SHELL=C:\DOS\COMMAND.COM  C:\DOS\  /P  /E:512

Change it to look like this:

    SHELL=C:\COMMAND.COM  /P  /E:512

Or contact your Novell vendor to get a new login program.

If you are having problems using Microsoft Undelete on 
a Novell network, use the MAP ROOT command in conjunction
with the delete-sentry method of protection. (If you have
Novell Netware version 2.15c or older, obtain the most
recent MAP.EXE file from your network vendor.) For example,
you would use the following MAP ROOT syntax (normally
specified in the server's login script):

MAP ROOT F:=COUNT/SYS:USERS/JOEB

where F is the network drive letter, COUNT is a file server name,
SYS is the volume name, USERS is a subdirectory of volume SYS, and
JOEB is the root for a network user. On JOEB's computer, the
AUTOEXEC.BAT would contain the following syntax:

UNDELETE /SF

where /S specifies the delete-sentry method of protection and F
specifies a network drive to be protected. The AUTOEXEC.BAT should
specify /S[drive] for each drive to be protected.

5.15 PC-NFS 3.0
---------------
If you use PC-NFS 3.0 with MS-DOS Shell, MS-DOS Shell may
display more drives than you have currently enabled. To
prevent this, use the PC-NFS /d switch to specify the number
of drives you are using. For more information, see your PC
NFS documentation.

If you can't use the COPY or XCOPY command on PC-NFS 3.01,
contact your vendor to get an updated version of the
PCNFS.SYS device driver.

5.16 Sitka TOPS
----------------
If your computer uses Sitka TOPS version earlier than 3.0,
contact your network vendor for an update.

Sitka TOPS version 3.0 is compatible with MS-DOS 6. If you
have any problems running this network software with MS-DOS
6, contact your network vendor.

If your system is a TOPS workstation, the MS-DOS Shell MOVE
command may not work.

Don't use the LOADHIGH command with a TOPS network.
  
5.17 TCS 10Net or DCA 10Net 
---------------------------
DCA 10Net Plus Versions 4.20 (20) and later, and DCA
10Net versions 3.3 (41) and later are compatible with
MS-DOS 6. If you have an earlier version, contact
your network vendor for an update.

If you are running a compatible version of 10Net Network 
Software, disable the network software, and then run MS-DOS 6 
Setup. After you install MS-DOS 6, reenable your network
software.

NOTE
The Microsoft Defrag program is incompatible with 
10Net network software if the server service is loaded. 
If only the redirector is loaded, the program is compatible
with 10Net network software.

6. USING APPLICATIONS WITH MS-DOS 6
===================================

6.1 4DOS
--------

With older versions of 4DOS, you might have problems
running MS-DOS Help if you use 4DOS as your SHELL.
If you don't use 4DOS as your SHELL, you might have
problems running 4DOS's help system.

To avoid a conflict between help systems, upgrade to
the most recent version of 4DOS. Or, to use MS-DOS 
Help with your older version of 4DOS, use the
COMMAND /C HELP command. 

6.2 Above Board 286 and Above Board Plus Installation
    Programs
----------------------------------------------------

CAUTION: The Intel Above Board installation program that
         shipped before May 1989 tests extended memory in a
         way that can corrupt extended memory.

Before using an Above Board installation program prior to
May 1989, make sure you haven't loaded software such as
SMARTDrive or RAMDrive that uses extended memory.  After the
Above Board has been installed, other software using
extended memory is unaffected.

6.3 Amload
---------
If you can't use the Apricot Computer Amload program,
use the following LOADFIX command:

   LOADFIX amload.exe

For information about the LOADFIX command, type
HELP LOADFIX at the command prompt.

6.4 AutoCAD release 10
---------------------
To run AutoCAD release 10 for MS-DOS, contact Autodesk for a
patch file. No patch is needed for AutoCAD386.

6.5 AUTORUN.EXE
--------------
If you can't use Mountain Network Solutions AUTORUN.EXE, a
tape-drive backup program, contact your vendor for an
upgrade.

6.6 CodeView
-----------
CAUTION: Using versions 3.0 to 3.13 of the CodeView CV.EXE
file may cause data loss if your system has a 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.

This problem has been fixed in CodeView version 3.14. Call
Microsoft C Support to get this version.

6.7 Defrag
----------
If run Defrag and MS-DOS still displays out-of-memory messages after
you have followed the procedures in "An MS-DOS program displays
an out-of-memory message" in the chapter "Diagnosing and Solving
Problems" of the Microsoft MS-DOS User's Guide, your computer
might have too many files for Defrag to reorganize the files on
your hard disk. For Defrag to work correctly, you might need to 
delete some files or move them to a floppy disk or a network drive.

6.8 Easel 6.0
------------
Interactive Images Easel 6.0 is incompatible with the
DOS=HIGH and EMM386 commands. Contact your vendor for an
update.

6.9 Everex QIC-02 Tape Software
-------------------------------
If you are running Everex QIC-02 Tape Software version 4.08,
you should use the SETVER command to make the software 
compatible with MS-DOS 6. To do so, type the following at
the command prompt:

SETVER TAPE.EXE 5.00

6.10 Fastback
-------------
If you have a version of Fifth Generation Systems Fastback
earlier than 3.0, you must use the LOADFIX command before
running Fastback or the Fastback installation program. Type
the following:

LOADFIX FB.EXE

or

LOADFIX FBINSTAL.EXE

For information about the LOADFIX command, type HELP LOADFIX
at the command prompt.

6.11 GeoWorks
-------------
If you have a version of GeoWorks (PC/GEOS) earlier than
1.2, use the SETVER command to report version number 4.01 to
the GEOS.EXE file. Type the following:

SETVER GEOS.EXE 4.01

Do not run the installation program for GeoWorks Ensemble
when MS-DOS Shell Task Swapper is active.

Use the Exclusive Tasking option when running GeoWorks
Ensemble with Windows.

6.12 Hyperdisk cannot find Shadow RAM
-------------------------------------

By default, EMM386 reserves the E000-EFFF area of memory for programs
that run in upper memory. However, to load Hyperdisk into Shadow RAM
memory, Hyperdisk must have access to this area of memory.

To Hyperdisk the area of memory it needs:

1   Open your CONFIG.SYS file with any text editor.

2   Add the following to the command line that loads EMM386:

    x=E000-EFFF

    For example, suppose your EMM386 command line is the following:

    DEVICE=C:\DOS\EMM386.EXE

    Modify it so that it looks like the following:

    DEVICE=C:\DOS\EMM386.EXE x=E000-EFFF

6.13 LINK.EXE: Unexpected Error Messages
----------------------------------------
If you get unexpected error messages while linking programs,
make sure you don't have an old version of LINK.EXE in your
DOS directory or path.

LINK.EXE is not supplied with MS-DOS 6.

6.14 Lotus 1-2-3 versions 3.0 and 3.1
-------------------------------------
If Lotus 1-2-3 no longer runs properly, or it prevents you from opening
large files, there could be several causes:

o You might not have enough extended (XMS) memory available. You need at
  least 384K (393,216 bytes) of available memory.

o You are using MS-DOS Shell, and Task Swapper is enabled.

o Your expanded-memory emulator (such as EMM386) isn't set up to work with
  Lotus 1-2-3.

Carry out the following procedures in order. If the first procedure doesn't
solve the problem, try the next one.

Increase available extended memory

Before you can make more extended memory available, you must determine how
much extended memory is being used.

To determine how much extended memory is being used:

* At the command prompt, type the following:

  mem

  The command displays your computer's memory configuration, including
  the amount of XMS memory used and free. You need at
  least 393,216 bytes of XMS memory free to run Lotus 1-2-3.

To make more extended memory available:

o Make sure your computer has as much physical extended memory as the
  program needs. If you do not have enough physical extended memory, you
  may want to contact your hardware vendor to determine how you can add
  more to your computer.

o Make sure your CONFIG.SYS file contains a DEVICE command for the
  HIMEM.SYS extended memory manager (or another memory manager that
  conforms to the XMS specification). Most programs need an extended
  memory manager to use extended memory. For more information about
  HIMEM.SYS, type HELP HIMEM.SYS at the command prompt.

o If your CONFIG.SYS file includes a DEVICE command for RAMDrive or
  EMM386, these programs could be using too much of your extended memory.
  If so, reduce the amount of memory that is specified by editing the
  DEVICE command for each driver. For more information about editing the
  DEVICE commands in your CONFIG.SYS file, see the chapter "Freeing More
  Memory" of the Microsoft MS-DOS User's Guide.

o Make sure your CONFIG.SYS and AUTOEXEC.BAT files don't start unnecessary
  programs that use extended memory. For more information about
  modifying your CONFIG.SYS and AUTOEXEC.BAT files, see "Streamlining Your
  CONFIG.SYS and AUTOEXEC.BAT Files" in the chapter "Freeing More Memory" 
  of the Microsoft MS-DOS User's Guide.

o In your AUTOEXEC.BAT file, try disabling SMARTDRV.EXE to conserve XMS
  memory by typing REM and a space in front of the command. For example, 
  the altered line might look like this:

  rem c:\dos\smartdrv.exe

Set up EMM386 to run Lotus 1-2-3 version 3.0 or 3.1

If none of the preceding suggestions solved the problem, EMM386 is probably
set to run with the NOEMS switch, which makes expanded (EMS) memory
unavailable. Because Lotus 1-2-3 version 3.0 or 3.1 and EMM386 run in
protected mode, they need to communicate to avoid conflicts. Lotus 1-2-3 and
EMM386 can use a protocol called Virtual Control Program Interface (VCPI) to
communicate. VCPI assumes that a page of expanded memory space exists. A
page is not available if EMM386 uses the NOEMS switch. You must change the
setting.

To update the device command for EMM386:

1. Use any text editor to open your CONFIG.SYS file.

2. Locate the DEVICE command for EMM386. It should look like the
   following:

   device=c:\dos\emm386.exe noems

   If there is no DEVICE command for EMM386 in your CONFIG.SYS file, add
   one as described in the next step. Make sure the line you add appears
   after the DEVICE command for HIMEM.SYS.

3. Replace the NOEMS switch with the RAM switch.

   The correct DEVICE command for EMM386 should look like the following:

   device=c:\dos\emm386.exe ram 

   The RAM switch gives programs access to both expanded memory and the
   upper memory area.

4. Save your CONFIG.SYS file, and then quit the text editor.

5. Restart your computer by pressing CTRL+ALT+DEL.

6. Try starting Lotus 1-2-3 again.

6.15 Manifest
-------------
Versions 1.01 and later of Quarterdeck Manifest are
compatible with MS-DOS 6. If you have a version earlier
than 1.01, contact your vendor for an upgrade.

6.16 Microsoft CD-ROM Extensions
--------------------------------
Use the MSCDEX.EXE file that comes wtih MS-DOS 6.

If you load MSCDEX.EXE with a batch file or program,
make sure it loads the MSCDEX.EXE file that comes with 
MS-DOS 6. The MS-DOS Setup program copies the file
to the directory that contains your MS-DOS files.

6.17 NDOS
---------
You might have problems running MS-DOS Help if you use 
NDOS as your SHELL. If you don't use NDOS as your SHELL, 
you might have problems running NDOS's help system.

To use MS-DOS Help with NDOS, use the COMMAND /C HELP 
command. 

6.18 Norton Desktop for Windows 2.0
-----------------------------------
Setup modifies Norton Desktop for Windows by adding a
second Tools menu which contains Backup and Antivirus commands
(if you installed these Windows programs), as well as a 
DoubleSpace Info command. 

If you installed the Anti-Virus, Backup, and Undelete 
for Windows, you can add to Norton Desktop a Microsoft 
Tools group containing the programs' icons. Carry out Procedure 1 
if you have a group open and want to add to it the
Microsoft Tools group. Carry out Procedure 2 if you don't have a 
group open.

Procedure 1 To add the Microsoft Tools Group if the group window
            is open:

* Drag the file C:\DOS\WNTOOLS.GRP and drop it on the group window.

Procedure 2 To add the Microsoft Tools Group if the the group window\
            is not open:

1. Select the group into which you want the Microsoft Tools group to
   go--for example, the Main or Quick Access group.

2. From Norton Desktop for Windows, choose New from the File menu.

3. In the New dialog box, select Group as the Type.

4. In the Group File Name box, type the path to the WNTOOLS.GRP file. 
   This file is in the directory that contains your MS-DOS files. For
   example, if this directory is C:\DOS, type the following:

   C:\DOS\WNTOOLS.GRP

5. Choose OK.

6.19 Paintbrush
---------------
If you have an EGA monitor and want to run Microsoft or
ZSoft Paintbrush, you must remove the DEVICE=EGA.SYS
command from your CONFIG.SYS file. After removing the
command, you may have difficulty with screen swapping when
using Task Swapper in MS-DOS Shell.

6.20 Paradox 3.5
----------------
For information about Paradox version 3.5, see section 6.12, 
Lotus 1-2-3 versions 3.0 and 3.1. This information also
applies to Paradox 3.5.

6.21 PC Tools
-------------
The FORMAT command of PC Tools version 7.1 conflicts with
MS-DOS 6. You should use the FORMAT.EXE command that comes 
with MS-DOS 6.

The COMPRESS command of PC Tools version 6.0 is incompatible
with DoubleSpace. When running MS-DOS 6, you should use 
DEFRAG for freeing disk space because it is fully
integrated with MS-DOS 6.

6.22 PC-Kwik Disk Accelerator
-----------------------------
Do not load versions of Multisoft PC-Kwik Disk Accelerator
earlier than 2.0 into the upper memory area.

6.23 PeachTree Complete III Single-User Version
-----------------------------------------------
If you are using the single-user version of PeachTree
Complete III (batch 01 through batch 13), contact PeachTree
for an update.

There is no compatibility problem with the network version.

6.24 Pklite
-----------
Do not use Pklite to pack device drivers.

If you have a PC-Kwik cache on your system, and you can't
run a packed program, do one of the following:
   * Use the LOADFIX command to start the program.
   * Run MS-DOS 6 in conventional memory.
   * Run a version of the program that was not packed with
     Pklite.
   * Disable asynchronous reads on the PC-Kwik cache.

For information about the LOADFIX command, type HELP LOADFIX
at the command prompt.

6.25 ProKey Plus
----------------
If you have problems using a version of RoseSoft ProKey Plus
earlier than 5.0, contact your vendor for an upgrade.

ProKey Plus is incompatible with MS-DOS Editor and QBasic.

6.26 Sidekick 2.0
-----------------
If you are running MS-DOS 6 in the high memory area, use
the following LOADFIX command to start Borland Sidekick 2.0:

    LOADFIX sk2.exe

For information about the LOADFIX command, type HELP LOADFIX
at the command prompt.

6.27 Soft-ICE
-------------
When using Nu-Mega Soft-ICE, load it before loading other
drivers. Otherwise, you may lose data stored in extended
memory by drivers such as SMARTDrive.

In addition, when running Soft-ICE and SMARTDrive, do not
press CTRL+ALT+DEL until you are sure that your computer's
software has finished writing to disk. Otherwise, you might
lose data.

6.28 Software Carousel
----------------------
Software Carousel 5.01 is compatible with MS-DOS 6.
If you have an earlier version, contact SoftLogic Solutions
for an update.

If you installed HIMEMSLS.SYS, remove the
DEVICE=HIMEMSLS.SYS command from your CONFIG.SYS after
running MS-DOS 6 Setup.

To use DOSKEY, load it after you load Software Carousel into
memory.

6.29 Task Swapper and Asynchronous I/O
--------------------------------------
Some programs that perform asynchronous communications are
incompatible with MS-DOS Shell Task Swapper. Terminal-
emulation software (such as SmartCom and Procomm Plus) and
server/client software (such as Laplink and Blast) are
asynchronous communications programs. If you can't use an
asynchronous program with Task Swapper, contact your vendor
for more information, or disable Task Swapper.

6.30 Ventura Publisher
----------------------
If you can't start Ventura Publisher, make sure your Ventura
Publisher directory is within the first 70 characters of the
PATH command in your AUTOEXEC.BAT file.

6.31 WordPerfect WPINFO.EXE 5.1
-------------------------------
Some versions of the WPINFO.EXE file included with
WordPerfect 5.1 are incompatible with MS-DOS 6. Contact
your vendor for more information.

6.32 WordPerfect Office 3.0
---------------------------
Some versions of WordPerfect Office 3.0 are incompatible
with MS-DOS 6. Contact your vendor for more information.

6.33 XTreeNet
-------------
To use XTreeNet with MS-DOS Shell Task Swapper, select the program,
choose the Properties command from the File menu, choose the 
Advanced button, and select the Prevent Program Switch option. 
For more information, select the option and press F1.

7. TROUBLESHOOTING DOUBLESPACE
==============================
   
7.1 Converting Your Disk-Compression Program to DoubleSpace
-----------------------------------------------------------
If your computer uses Stacker disk-compression software, install
MS-DOS 6, and then convert it to DoubleSpace by typing DBLSPACE at 
the command prompt. If your computer uses XtraDrive disk compression, 
use its uninstallation program to remove the compression, and then
install DoubleSpace.

Note: If your version of Stacker is 1.1 or you compressed your drive
with a 4K cluster size, you cannot automatically convert your Stacker
drive; you must convert it manually, as described in the procedure
below.

If your computer does not use Stacker disk-compression software,
you can convert to DoubleSpace manually. Carry out the following
procedure.

To convert your disk-compression software to DoubleSpace manually:

1. Install MS-DOS 6 if you haven't already done so.

2. Use Microsoft Backup to back up the files on your hard disk.

3. Insert Setup Disk 1 in drive A, and restart your computer
   by pressing CTRL+ALT+DEL. When the first screen appears, press
   F3 twice to exit Setup.

   Or, create a startup disk by inserting Setup Disk in drive B,
   and typing B:SETUP /F. Follow the instructions on your screen. 
   After Setup is finished, restart your computer by inserting the 
   startup disk in drive A and pressing CTRL+ALT+DEL.

4. Use the format command to format the drive that contains the     
   file that stores all of your compressed files. If you don't know
   where this file is located, see your disk-compression
   documentation.
   
   If you are reformatting drive C, include the /S switch to transfer 
   your system files, as in the following example:

   format c: /s

   NOTE
   If you don't format drive C, remove from your CONFIG.SYS and
   AUTOEXEC.BAT files any commands that were used by your disk-
   compression software.

5. If you formatted drive C, make sure Setup Disk 1 is in drive A 
   or B, and type A:SETUP or B:SETUP at the command prompt.

    Follow the instructions on your screen.

6. Install DoubleSpace by typing DBLSPACE at the command prompt. 
   Follow the instructions on your screen. 

   For more information about DoubleSpace, see the chapter 
   "Freeing Disk Space" of the Microsoft MS-DOS User's Guide.

7. Restore the files you backed up.



7.2 DoubleSpace Setup indicates that your computer is running an
    incompatible disk-caching program
----------------------------------------------------------------    
If DoubleSpace Setup displays a message indicating your computer
is running an incompatible disk-caching program, carry out the
following procedure to install DoubleSpace:

1. Open your CONFIG.SYS file by typing EDIT C:\CONFIG.SYS
   at the command prompt.

2. Delete the line that contains the device command that loads
   your disk-caching program.

3. Make sure you have a line for the MS-DOS 6 SMARTDRV program. 
   For example, if C:\DOS is your MS-DOS directory, add the 
   following line:

   C:\DOS\SMARTDRV.EXE /DOUBLE_BUFFER

4. Save the file.

5. Open your AUTOEXEC.BAT file.

6. Make sure you have a line for the MS-DOS 6 SMARTDRV program. 
   For example, if DOS is your MS-DOS directory, add the 
   following line:

   C:\DOS\SMARTDRV.EXE /L

7. Save the file, and restart your computer by pressing
   CTRL+ALT+DEL.

8. Run DoubleSpace again.
     
7.3 You attempt to mount a compressed floppy disk, and MS-DOS
    displays an error message
-------------------------------------------------------------
If you have not installed DoubleSpace on your hard disk, and you
attempt to mount a compressed floppy disk, MS-DOS displays 
the following message:

   There are no more drive letters reserved for dblspace to use.
   To add more, use the options selection from the tools menu.

You must load DBLSPACE.BIN and create a DBLSPACE.INI file to mount
compressed floppy disks if you have not installed DoubleSpace on your
hard disk.

To correct this problem:

1. Create a C:\DBLSPACE.INI file by using any text editor. 
   DBLSPACE.INI should contain the following two lines:

   MaxRemovableDrives=2
   LastDrive=F

   Note: LastDrive= must be set to one letter higher than your last
         logical drive letter. For example, if your last drive is E:, 
         use LastDrive=F in your DBLSPACE.INI file.

2. Copy DBLSPACE.BIN from your MS-DOS directory to the root directory of
   your startup drive. For example, type the following at the command
   prompt:

   copy c:\dos\dblspace.bin c:\

3. Restart the computer.

4. You can now mount the compressed disk in your floppy drive. For
   example, if the disk is in drive A:, type the following at the
   command prompt:

   dblspace /mount a:
   
7.4 Your uncompressed drive runs out of disk space
--------------------------------------------------

TBD


7.5 DoubleSpace did not compress all of your files because
    the drive ran out of disk space
----------------------------------------------------------
If DoubleSpace indicates that it could not compress some
of the files because there was not enough disk space, carry
out the following procedure.

1. Type DBLSPACE at the command prompt.

2. To determine which drive is your uncompressed drive, choose
   Info from the Drive menu. Then choose Exit from the Drive
   menu.

3. Back up to floppy disks the files that were left uncompressed
   on the uncompressed drive.

4. Delete the files that were left uncompressed on the uncompressed
   drive.

5. Type DBLSPACE at the command prompt.

6. Choose Change Size from the Drive menu.

7. To increase the size of your compressed drive, decrease the size
   of your uncompressed drive. Choose OK.

8. Choose Exit from the Drive menu, and copy the backed-up files
   to your compressed drive. If you run out of space again, repeat
   steps 5 through 7 until the compressed drive is large enough.

7.6
---- 
TBD

Placeholder:
Your computer was unexpectedly restarted.
This apparently damaged drive X, because 
DoubleSpace can no longer mount that drive. 
Run CHKDSK /F from the command prompt, 
and then try mounting the drive 
again. For more information, see the 
DoubleSpace section of the README.TXT file.

7.7
---

TBD

Placeholder:
Your system includes removable media
that was compressed using Stacker (TM).
If you continue, DoubleSpace Setup will convert X
in Y to DoubleSpace format. If you have other
disks for Z which are also in Stacker format, you 
need to convert those disks to DoubleSpace format
before you can use them with DoubleSpace.
For more information, press F1 or see the DoubleSpace
section of the README.TXT file.

7.8
----

TBD

Placeholder:
To convert this volume, there must be at least X
MB of free space on drive Z. For information about how
to convert this volume, press F1 or see the DoubleSpace
section of the README.TXT file.

7.9
----

TBD

Placeholder:

Your computer might be running software
that is incompatible with DoubleSpace.

CAUTION: If you run DoubleSpace now, you could
lose some or all of the files on your
computer. 

Do not continue DoubleSpace until you have 
read the README.TXT file.

For more information, press F1.

7.10 Removing DoubleSpace From Your Computer
--------------------------------------------

TBD

7.11 Setting up Stacker Over DoubleSpace 
----------------------------------------

TBD
