Dec 142017
| Dos 6.0 tech notes from compuserve / microsoft. | |||
|---|---|---|---|
| File Name | File Size | Zip Size | Zip Type |
| DOS6INFO.TXT | 281715 | 69225 | deflated |
Download File DOS6KB.ZIP Here
Contents of the DOS6INFO.TXT file
-=-=-=-=-=-
ARTICLE-ID:Q95997
TITLE :DELTREE: No Error Message If Directory Does Not Exist
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When the DELTREE.EXE command is executed on a directory that does not
exist, no error message is displayed and you are returned to the
MS-DOS prompt. This behavior can be misleading if you mistype a
directory name--since no error message is displayed, you may think
that the directory you were trying to delete was successfully deleted.
More Information:
If the directory you want to delete is specified correctly with the
DELTREE.EXE command, you will receive the following message:
Delete directory and all of its subdirectories?
[yn]
where is the name of the directory you want to delete.
You are required to answer "y" to delete the entire subdirectory or
"n" to cancel the operation.
For more information on the DELTREE command, type "HELP DELTREE"
(without the quotation marks) at the command prompt.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94568
TITLE :MWAV.EXE Cannot Clean FORMS Virus But MSAV.EXE Can
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If Microsoft Anti-Virus for Windows detects the FORMS virus, the following
generic message is displayed:
The virus infecting this disk has not been analyzed by Central Point
Software. As a result, the virus cannot be removed. See your "MS-DOS 6
User's Guide" for information about updating Microsoft Anti-Virus so you
can detect and remove the latest viruses.
Microsoft Anti-Virus for Windows cannot clean the FORMS virus but the
MS-DOS-based version of Microsoft Anti-Virus (MSAV.EXE) can.
More Information:
If you do not have the MS-DOS-based version of Microsoft Anti-Virus
installed, run SETUP /E to install the optional utilities. For more
information on SETUP /E, see page 4 of the "MS-DOS 6 User's Guide."
Additional reference words: 6.00 form forms
-=-=-=-=-=-
ARTICLE-ID:Q94569
TITLE :Compression Software Doesn't Load After Running MemMaker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you run MemMaker with a third-party disk compression program, such as
Stacker or SuperStor, MemMaker cannot undo the changes in the CONFIG.SYS
and AUTOEXEC.BAT files after a failed boot attempt.
More Information:
If a reboot attempt fails, MemMaker provides a Cancel button to undo
changes. MemMaker attempts to undo all changes to your CONFIG.SYS and
AUTOEXEC.BAT files on the host drive but cannot because the compressed
drive in no longer mounted.
Although MemMaker correctly detects compression on the system and verifies
that the CONFIG.SYS and AUTOEXEC.BAT files match, the problem still occurs
because CHKSTATE.SYS is loaded before the disk-compression software.
MemMaker is able to restore the files on the host drive, but not on the
compressed volume (which is swapped with the host AFTER the disk-
compression software is loaded).
To restore your computer to its previous state, copy and rename the
AUTOEXEC.UMB and CONFIG.UMB files from the host drive to the compressed
volume after you choose the MemMaker Cancel option. For example, if drive D
is the uncompressed host drive and drive C is the compressed volume, use
the following commands:
copy d:\autoexec.umb c:\autoexec.bat
copy d:\config.umb c:\config.sys
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94639
TITLE :Troubleshooting MS Backup and MS Backup for Windows
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0, 3.0a, and 3.1
--------------------------------------------------------------------
Summary:
If you encounter problems running Microsoft Backup for MS-DOS or Microsoft
Backup for Windows, use the steps in the following section to correct the
problems.
Common problems caused by incorrect system configuration include:
- Microsoft Backup appears to stop responding (hang) when run from the
MS-DOS Prompt under Windows.
- Microsoft Backup reports problems accessing the second floppy disk
drive during the compatibility test when run from MS-DOS Prompt under
Windows. Microsoft Backup either displays the following error message or
continues to ask for the first disk after you have inserted the second
one.
Diskette not properly seated.
- Microsoft Backup for Windows causes Windows to close, leaving the
command prompt displayed on the screen.
- Windows reports that the DMA buffer size needs to be increased to 64.
Troubleshooting Microsoft Backup for Windows and Microsoft Backup
-----------------------------------------------------------------
1. Microsoft does not recommend or support running the MS-DOS-based
version of Microsoft Backup (MSBACKUP.EXE) with Windows. If you choose
to do this, you should create a program information file (PIF) for
Microsoft Backup with the following settings:
Display Usage: Full Screen
Execution: Exclusive
2. Your CONFIG.SYS file should include the following settings (the values
shown are minimums):
FILES=30
BUFFERS=30
STACKS=9,256
3. The DMABufferSize= line should be set to at least 32 in the [386Enh]
section of the SYSTEM.INI file.
Additional reference words: 6.00 3.00 3.00a 3.10 win31 win3 win30 ms-dos
backup
-=-=-=-=-=-
ARTICLE-ID:Q94666
TITLE :Difficult to Use F5 & F8 Keys on Data General Computers
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Data General machines may have difficulty accepting input from the F5 and
F8 keys, which are used to bypass or step through the CONFIG.SYS and
AUTOEXEC.BAT files. You must press the F5 or F8 key immediately after
hearing the first beep from your computer BIOS at system startup. You may
have to press the F5 or F8 key many times.
On most computers, you have a few seconds to press the F5 or F8 key after
you see the "Staring MS-DOS..." prompt and hear the beep.
For more information, contact Data General.
Additional reference words: 6.00 function key keys
-=-=-=-=-=-
ARTICLE-ID:Q94722
TITLE :Running MemMaker to Optimize a Startup Floppy Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker to optimize a startup (boot) floppy disk, it
incorrectly prompts you to "Remove all floppy disks from your floppy-disk
drives and then press Enter." Although MemMaker specifically supports the
optimization of a startup floppy disk, it displays a generic prompt that
assumes you are optimizing drive C.
To work around this problem, ignore the message to remove all floppy disks,
and press ENTER to restart your computer.
More Information:
To optimize a startup floppy disk, you must run MemMaker from drive A. If
you do not, MemMaker optimizes the startup files on your hard disk drive.
To start MemMaker from drive A:
1. Change to drive A.
2. Start MemMaker. (To do this, type "memmaker" (without the quotation
marks and then press ENTER).
Note: When you run MemMaker to optimize a startup floppy disk, you must
have the following five files on the floppy disk in drive A.
CHKSTATE.SYS
EMM386.EXE
HIMEM.SYS
MEMMAKER.EXE
SIZER.EXE
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94772
TITLE :MemMaker Err Msg with Perscope: UMB's Overran List Buffer
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker detects the protected memory used by the Periscope board, but it
does not exclude the range correctly resulting in the following error
message:
UMB's overran list buffer
To work around this problem, add the x= switch to the device= line for
EMM386 to exclude the C800-CFFF range. For example:
device=c:\dos\emm386.exe x=c800-cfff
More Information:
MemMaker detects the first 24 kilobytes (K) of memory used by the Periscope
board but does not detect the last 8K. Therefore, when MemMaker adds the x=
parameter, it does not exclude a large enough range.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94775
TITLE :Disks Created by MS-DOS 6 Upgrade Using SETUP /F
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
With MS-DOS 6 Upgrade, you can create a single startup floppy disk for
drive A using the /F parameter. The contents of this disk vary based on
disk capacity.
Note: MS-DOS 6 Upgrade does NOT have the ability to install the complete
operating system (with all programs) to floppy disks.
More Information:
Floppy Disk Contents for SETUP /F:
File
Filename Attributes Disk Size
---------------------------------------------------------
360K 720K 1.2MB 1.44MB
(5.25") (3.5") (5.25") (3.5")
IO.SYS SHR X X X X
MSDOS.SYS SHR X X X X
COMMAND.COM R X X X X
DBLSPACE.BIN SHR X X X X
ATTRIB.EXE A X X X X
DEBUG.EXE A X X X X
EXPAND.EXE A X X X X
FDISK.EXE A X X X X
FORMAT.COM A X X X X
RESTORE.EXE A X X X X
SYS.COM A X X X X
CHKDSK.EXE A X X X X
EDIT.COM A X X X
QBASIC.EXE A X X X
XCOPY.EXE A X X
MSD.EXE A X X
MSAV.EXE A X X X
DBLSPACE.EXE A X X
Additional reference words: 6.00 floppy diskette
-=-=-=-=-=-
ARTICLE-ID:Q94815
TITLE :MSD Err Msg: Error Writing Bad File Number
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you attempt to print a Microsoft Diagnostics (MSD) report to an inactive
port, you receive the following error message:
Error Writing Bad File Number
To correct this problem, print to an active port.
Additional reference words: 6.00 win31 win wfw wfwg
-=-=-=-=-=-
ARTICLE-ID:Q94329
TITLE :MS-DOS 6 OEM Setup Doesn't Boot on Tandy 1000TX 286
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some Tandy 1000TX 286 computers have a 3.5-inch floppy disk drive that
can be configured as a 360K drive. If the drive has been reconfigured,
the MS-DOS 6 OEM 720K Disk 1 will not start (boot) the computer.
Workaround
----------
To work around this problem:
1. Modify or create the CONFIG.SYS file on Disk 1, and add the
following line:
DRIVPARM=/d:0 /f:2
2. Boot the system using this disk.
Setup should now run normally.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94985
TITLE :MemMaker Fails to Undo Changes to CONFIG.SYS File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If your AUTOEXEC.BAT, CONFIG.SYS, or Windows SYSTEM.INI file is marked as
read-only, MemMaker displays the following error message:
MemMaker cannot continue because it cannot gain access to the
AUTOEXEC.BAT, CONFIG.SYS, or Windows SYSTEM.INI file. Make sure the
read-only attribute for those files is not set.
To undo MemMaker's changes, press ENTER.
If your AUTOEXEC.BAT file or SYSTEM.INI file is marked read-only but the
CONFIG.SYS file is not, MemMaker does not undo the changes it made to the
CONFIG.SYS file.
To work around this problem, remove the read-only attribute on the
AUTOEXEC.BAT and/or SYSTEM.INI file and restart MemMaker. To remove the
read-only attribute on the AUTOEXEC.BAT and/or SYSTEM.INI files, use the
ATTRIB command as follows:
attrib c:\autoexec.bat -r
-and/or-
attrib c:\windows\system.ini -r
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95955
TITLE :Configuring MSCDEX for Multiple CD-ROM Drives
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft CD-ROM Extensions (MSCDEX) can control multiple CD-ROM
drives. To configure your system to do this, you must make some
adjustments to the parameters on your CD-ROM driver in the CONFIG.SYS
file and to the MSCDEX command in your AUTOEXEC.BAT file.
More Information:
MSCDEX uses the /D:MSCDxxx parameter to differentiate between the
drives. For example, the following commands assign the Creative Labs
CD-ROM driver (SBPCD.SYS) to drive m and the external CD-ROM
(TSLCDR.SYS) to drive n:
CONFIG.SYS File
---------------
device=c:\sbpro\sbpcd.sys /d:mscd001 /p:220
device=c:\scsi\tslcdr.sys /d:mscd000
AUTOEXEC.BAT File
-----------------
mscdex /d:mscd001 /l:m /d:mscd000 /l:n
Note: Because MS-DOS treats CD-ROM drives like network drives, you can
assign them to any available drive letter.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94867
TITLE :Err Msg after Running MemMaker: Double-Buffering Driver...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you have a device= statement for SMARTDRV.EXE in your CONFIG.SYS file,
but you are not using the /DOUBLE_BUFFER switch, MemMaker may change the
device= statement to devicehigh=. If so, you receive the following error
message:
Double-buffering driver cannot be loaded into a UMB.
Do not use the devicehigh command or other load-high
utilities to load Smartdrv.exe
To correct this problem, in the CONFIG.SYS file, change the devicehigh=
statement for SMARTDRV.EXE to device= and add the /DOUBLE_BUFFER switch,
then run MemMaker again.
More Information:
MemMaker recognizes and ignores the device= statement for SMARTDRV.EXE only
if you are using the /DOUBLE_BUFFER switch.
A device= statement in the CONFIG.SYS file does not load the SMARTDrive
cache; it loads only the double-buffering device driver embedded in the
SMARTDRV.EXE file. This device driver cannot be loaded into upper memory.
For more information on SMARTDrive and double buffering, query on the
following words in the Microsoft Knowledge Base:
smartdrive and double and buffer and bus and mastering
Additional reference words: 6.00 line
-=-=-=-=-=-
ARTICLE-ID:Q94891
TITLE :Why MemMaker Doesn't Work with Multi-Config Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
This article explains why MemMaker doesn't work with MS-DOS Multi-Config
files.
Important: You can use MemMaker with multiple configurations, but doing so
requires creating separate configuration files to run MemMaker. For more
information, see the "Using MemMaker with Multiple Configurations" section
in Chapter 6 of the "MS-DOS User's Guide."
More Information:
MemMaker removes all references to memory managers, the FILES= statement,
the BUFFERS= statement, and the DOS= statement. It then adds the following
statements at the top of the CONFIG.SYS file:
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE
buffers=
files=
dos=umb
lastdrive=
FCBS=
[Everything else remains in the same order]
Note: The and are determined by MemMaker for your
specific installation and configuration.
Because of this design, MemMaker cannot work with configuration files that
contain Multi-Config sections that reference multiple memory managers or
have different memory configurations.
MemMaker also uses a program called SIZER.EXE to determine memory
requirements for device drivers and terminate-and-stay-resident (TSR)
programs. MemMaker analyzes the contents of the entire CONFIG.SYS and
AUTOEXEC.BAT files (regardless of Multi-Config headings) to calculate the
optimum memory configuration for your system. Because the files are viewed
as a single unit, each individual configuration will not be optimized after
you run MemMaker.
Additional reference words: 6.00 MULTICONFIG
-=-=-=-=-=-
ARTICLE-ID:Q94940
TITLE :Interlnk Cannot Access CD-ROM Drives
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Interlnk cannot access CD-ROM drives. Interlnk accesses drives using a
block device driver. This means that Interlnk can recognize standard drives
but not network drives. Because CD- ROM drives use a network interface,
Interlnk cannot be used to access them.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95998
TITLE :SmartMon Incorrectly Reports Cache Status with DBLSPACE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The SMARTDrive Monitor (SMARTMON.EXE) provides an interface to the
performance of SMARTDrive 4.0, the disk cache included with MS-DOS 6.
If you attempt to turn on caching for a DBLSPACE drive by typing the
SMARTDRV.EXE command at the command prompt, you receive an error
message indicating that you must specify the host drive rather than
the compressed drive.
However, if you are using the SMARTDrive Monitor and you select the
compressed drive and then select the Cache Reads And Writes button,
this action is ignored and you do not receive an error message. When
SmartMon is reloaded, it defaults back to no read or write cache on
the DBLSPACE drive.
Microsoft has confirmed this to be a problem in SmartMon version 3.1.
We are researching this problem and will post new information here in
the Microsoft Knowledge Base as it becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95182
TITLE :DXMC0MOD.SYS Err Msg: Invalid Shared RAM Address
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Due to a difference in line parsing between the DEVICE and DEVICEHIGH
commands you may receive one of the following error messages when the
IBM network device driver, DXMC0MOD.SYS, loads:
Invalid shared RAM address
-or-
Invalid early token ring release
After these error messages are displayed, the DXMC0MOD.SYS device
driver does not load and the network fails to start. This occurs most
often after MemMaker has been used, and DEVICE commands have been
changed to DEVICEHIGH.
To enable your network to start and avoid these error messages, make
sure enough commas are used in the DXMC0MOD.SYS statement to act as
delimiters for the three optional parameters required by DXMC0MOD.SYS.
For example, each of the following lines cause error messages to be
displayed:
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001,D800
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS ,D800
To avoid these errors, change each line to the following:
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001,,
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001,D800,
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS ,D800,
More Information:
This problem is caused by the manner in which DEVICEHIGH parses
command lines. The DXMC0MOD.SYS device driver does not correctly
interpret the DEVICEHIGH parameter information.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95203
TITLE :Err Msg: SmartMon Unable to Save the New Cache Settings
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows Resource Kit version 3.1
--------------------------------------------------------------------
Summary:
If you used SMARTDrive Monitor (SmartMon) to change SMARTDrive's
cache settings, you may receive the following error message after
exiting SmartMon:
SmartMon is unable to save the new cache settings in the specified
batch file.
This error message is displayed when SmartMon is unable to find the
SMARTDrive command line in the AUTOEXEC.BAT file. This may be due to
the fact that SmartMon does not recognize the LH command and /L switch
when they are used together. For example, SmartMon cannot modify the
following line:
lh c:\dos\smartdrv.exe /l
To work around this problem, change the cache settings by manually
editing the AUTOEXEC.BAT file.
Microsoft has confirmed this to be a problem in SmartMon version 3.1.
We are researching this problem and will post new information here as
it becomes available.
Additional reference words: 6.00 smartdrive smartdrv monitor
-=-=-=-=-=-
ARTICLE-ID:Q95204
TITLE :MS-DOS 6.0: ANSI.SYS Turns Off Menu Colors
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are loading the ANSI.SYS driver, MS-DOS 6.0 multiple
configuration colors set with the menucolor= setting are reset to the
default colors.
More Information:
The menucolor= setting in the CONFIG.SYS file allows you to define
your menu colors. When ANSI.SYS is loaded through one of the menu
blocks, the screen colors are reset. This occurs because ANSI.SYS is a
block device for the console (CON). ANSI.SYS takes over all output to
the console and manipulates the data in an ANSI (American National
Standards Institute) format.
ANSI.SYS turns off the menu colors because it does not detect the
previous state of the CON device.
Additional reference words: 6.00 multiconfig multi-config
-=-=-=-=-=-
ARTICLE-ID:Q95288
TITLE :InterLnk Causes Extra Drive Letters in File Manager
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0, 3.0a, and 3.1
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
If Interlnk is loaded in the CONFIG.SYS file, Microsoft Windows File
Manager indicates the presence of the Interlnk drives with removable
media icons (sometimes called "floppy icons"). If Interlnk is loaded
but you don't have an active connection to another computer, you will
receive the following error message when you try to access one of the
Interlnk drives:
Error Selecting Drive
There is no disk in drive x.
Insert a disk, and then try again.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95348
TITLE :Converting Stacker Compressed Removable Disks
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
To convert a Stacker-compressed floppy disk, you must have
approximately 900K of free disk space on the removable disk. To
convert a Stacker-compressed removable media disk (such as Bernoulli
disks and removable optical disks) you must have approximately 1
megabyte (MB) of free disk space on the removable disk. The free disk
space can be either at the end of the Stacker volume file (SVF) or on
the uncompressed portion of the disk.
If you do not have enough free disk space to compress a removable disk
and you cannot remove any files to create more free disk space (or the
disk capacity is less than 900K [360K or 720K]), use the procedure
below (which was taken from the README.TXT file).
More Information:
DoubleSpace requires 900K free disk space so it can create a 512K
DoubleSpace compressed volume file (CVF). DoubleSpace also requires
400K-500K free disk space so it can internally unfragment a highly
fragmented SVF.
If DoubleSpace cannot convert a Stacker-compressed volume file due to
disk space limitations, do the following:
1. Insert the floppy disk in drive A or B.
2. Move the STACVOL.DSK file to the host drive on your hard disk. If
you don't know which drive is your host drive, start DoubleSpace by
typing DBLSPACE at the command prompt and choosing the Info command
from the Drive menu. Exit DoubleSpace.
When you move the file, change its extension to .001. For example
if the floppy disk is in drive A, and your host drive is drive D,
type the following at the command prompt:
move a:\stacvol.dsk d:\stacvol.001
If you have insufficient disk space, start DoubleSpace by typing
DBLSPSACE at the command prompt, and choose Change Size from the
Drive menu. Make the size of the uncompressed drive large enough to
contain the Stacker-compressed volume file.
3. If are using Stacker version 2.0, delete the STACKER.DRV file on
the floppy disk. If you are using Stacker version 3.0, delete the
STACKER.EXE and README.STC files.
4. Covert the compressed volume file to DoubleSpace format, as in the
following example:
dblspace /convstac=d:\stacvol.001
After DoubleSpace converts the file it will mount it.
5. Make sure your floppy disk is in drive A or B and then compress it
by choosing the Existing Drive command from the Compress menu in
DoubleSpace. Follow the instructions on your screen.
DoubleSpace mounts the floppy drive after it finishes
compressing the floppy disk.
6. Exit DoubleSpace.
7. Use the XCOPY command to copy all the files on the new compressed
drive on your hard disk to the compressed floppy disk. For example,
if the compressed drive is J, and the floppy disk is in drive A,
type the following at the command prompt:
xcopy j:\*.* a: /s
8. Delete the compressed drive on your hard disk. For example, if your
compressed drive is J, type the following at the command prompt:
dblspace /delete j:
To confirm the deletion, type "Y" (without the quotation marks).
Additional reference words: 6.00 svf cvf syquest floppy disk drive
removable media
-=-=-=-=-=-
ARTICLE-ID:Q94330
TITLE :DoubleSpace Setup Runs in Mono on Some Older 8514 Cards
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Microsoft DoubleSpace setup and configuration program
(DBLSPACE.EXE) runs in monochrome on the following 8514 video cards:
- Original IBM 8514 video cards. This behavior does not occur on
newer 8514 cards, or on ATI Ultra cards in 8514 mode.
- Paradise 8514/A cards.
This problem occurs due to a limitation of the cards, not DoubleSpace.
Additional reference words: 6.0 mono monochrome mono-chrome black and
white b&w amber dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95349
TITLE :Cannot Open More Than One File at a Time with EXPAND
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS Help contains a phrase that may be unclear. The help file
states that the filename parameter:
Specifies the location and name of a compressed file or files
The EXPAND command does not support wildcards (such as * and ?) and
cannot expand more than one file at a time.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94386
TITLE :Insufficient Memory Error Message with DBLSPACE /RATIO
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
If you run DBLSPACE /RATIO before the NET command is used in the
AUTOEXEC.BAT file, you may receive an insufficient memory error message.
This problem occurs when the network has not released the memory used
during loading because network binding has not yet occurred.
More Information:
It is not necessary to run DBLSPACE /RATIO from the AUTOEXEC.BAT file since
DoubleSpace reliably reports the amount of free disk space. However, if you
want to run DBLSPACE /RATIO from the AUTOEXEC.BAT file, run the NET START
command before you run DBLSPACE /RATIO as in the following example:
c:\windows\net start
c:\dos\dblspace /ratio
Additional reference words: 6.00 wfw wfwg
-=-=-=-=-=-
ARTICLE-ID:Q96083
TITLE :DoubleSpace Err Msg: Drive is Too Fragmented to Resize
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
When you try to resize a DoubleSpace drive and the MS-DOS 5.0 MIRROR
program is installed, you may receive the following error message
Drive C is too fragmented to resize. Before resizing drive
C, defragment it by typing DEFRAG.EXE /H /Q x: at the MS-DOS
command prompt
where x is the drive letter of the compressed drive.
Running DEFRAG /H /Q C: does not solve the problem; you still cannot
resize the DoubleSpace drive.
This problem occurs because MIRROR is creating a file called
MIRORSAV.FIL at the end of the drive. In most cases, DoubleSpace
cannot resize a drive if there is an unmovable file near the end of
the drive. Since the file has Read-only, Hidden, and System file
attributes set, it cannot be moved when you run Defragmenter
(DEFRAG.EXE).
If you do not use MIRROR, it is possible that another program has
placed a file with its System attribute set near the end of the drive.
More Information:
You can use the ATTRIB command to removed the file attributes on the
MIRROR file. For example, if the file is on drive C, issue the
following command from the MS-DOS command prompt:
attrib -s c:\mirorsav.fil
After running Defragmenter with the parameters suggested in the error
message, you should be able to resize the DoubleSpace drive.
Additional reference words: 6.00 dblspace doublespace
-=-=-=-=-=-
ARTICLE-ID:Q94387
TITLE :Setup Creates OLD_DOS.x Directory with /G & /H Switches
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Although you don't have the option to uninstall if you install Microsoft MS-
DOS 6 Upgrade using the /G and /H switches together, Setup still creates an
OLD_DOS.x directory. Because you cannot uninstall, it is safe to delete the
OLD_DOS.x directory using DELOLDOS.EXE.
More Information:
Setup /G disables the Uninstall feature of MS-DOS. Setup /H installs MS-DOS
with very few prompts for user input and cannot be used without the /G
switch.
Setup uses the OLD_DOS.x directory to create temporary CONFIG.SYS and
AUTOEXEC.BAT files when it modifies them. Setup does not copy any other MS-
DOS files to this directory when you install MS-DOS 6 Upgrade using the /G
and /H switches together.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94388
TITLE :Modifying MS-DOS Help Command Reference
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Microsoft MS-DOS 6 Help Command Reference can be customized to add site-
specific information and annotations with the HELPMAKE.EXE program supplied
with Microsoft C Compiler. Corporate sites, network administrators, and
computer consultants can modify the MS-DOS 6 Help Command Reference by
using HELPMAKE.EXE to decode and recompile the help file (HELP.HLP).
For more information on modifying help files, refer to the Microsoft C
Compiler documentation. To order Microsoft C, call Microsoft Consumer Sales
(800) 426-9400.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94411
TITLE :MemMaker Doesn't Optimize Batch Files in AUTOEXEC.BAT
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If a third-party memory manager has optimized memory by using specific
loading programs or parameters within batch files, the following error
message is displayed after you run MemMaker:
Bad Command or Filename
Note: You may also receive error messages from the third-party expanded
memory manager (EMM) if commands such as LOADHI (from QEMM) are called.
More Information:
Some third-party memory managers optimize one or more levels deep in batch
files called from the AUTOEXEC.BAT file, trying to load programs in upper
memory. MemMaker does not analyze software called from batch files within
the AUTOEXEC.BAT file, but instead treats the whole batch file as one
entity and attempts to load it in upper memory.
If you receive error messages because commands specific to third-party EMMs
are still in your batch files, edit the files and remove the third-party
specific information.
For example, if you have the following QEMM command in a batch file called
from the AUTOEXEC.BAT file, you receive the following error message after
you run MemMaker:
LOADHI /R:2 doskey /insert
To work around this problem, remove the QEMM-specific information. For
example:
doskey /insert
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95436
TITLE :Why Should I Upgrade to MS-DOS 6?
---------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
---------------------------------------------------------------------
Summary:
The MS-DOS 6 Upgrade includes the following new or enhanced features:
- Microsoft DoubleSpace
- Microsoft MemMaker
- Microsoft Backup
- Microsoft Anti-Virus
- Microsoft Undelete
- MultiConfig
- Interactive Start
- Microsoft Defragmenter
- MS-DOS Help
- Enhanced SMARTDrive
- Microsoft Diagnostics (MSD)
- Interlnk
- Enhanced Commands
This article briefly describes these enhancements and their benefits to
the user.
More Information:
Microsoft DoubleSpace
---------------------
Microsoft DoubleSpace increases your available disk space by
integrating compression into the operating system. You can use
DoubleSpace to increase available space on both hard disks and floppy
disks.
Microsoft MemMaker
------------------
Microsoft MemMaker is a memory-optimization program that makes it easy
to free conventional memory by moving device drivers and memory-resident
programs from conventional memory into the upper memory area (UMA). If
your computer has an 80386 or higher processor, you can use MemMaker to
increase available conventional memory so that programs run faster and
more efficiently.
Microsoft Backup
----------------
Microsoft Backup is a utility for backing up your hard disk drive.
MS-DOS 6 includes both Backup for MS-DOS, a program you can start from
the MS-DOS command prompt, and Backup for Windows, a program you can
use with Microsoft Windows.
Microsoft Anti-Virus
--------------------
Microsoft Anti-Virus can identify and remove more than 1000 different
computer viruses. MS-DOS 6 includes both Anti-Virus for MS-DOS, a
program you can start from the MS-DOS command prompt, and Anti-Virus
for Windows, a program you can use with Windows.
Microsoft Undelete
------------------
Microsoft Undelete enables you to choose one of three levels of
protection in case you accidentally delete a file. MS-DOS 6 includes
Undelete for MS-DOS, a program you can run from the MS-DOS command
prompt, and Undelete for Windows, a program you can use with Windows.
For more information about Undelete, see the chapter "Managing Your
System" in the MS-DOS 6 user's guide.
MultiConfig
-----------
MultiConfig allows you to define more than one configuration in your
CONFIG.SYS file. If your CONFIG.SYS file defines multiple
configurations, MS-DOS displays a menu that enables you to choose the
configuration you want to use each time you start your computer.
Interactive Start
-----------------
Interactive Start gives you the ability to bypass startup commands
when you turn on your computer. This feature allows you to choose
which CONFIG.SYS commands MS-DOS should carry out and whether MS-DOS
should run your AUTOEXEC.BAT file. By controlling the commands your
computer uses to start up, you can pinpoint problems more quickly and
easily.
Microsoft Defragmenter
----------------------
Microsoft Defragmenter reorganizes files on your hard disk to minimize
the time it takes your computer to access them.
MS-DOS Help
-----------
MS-DOS Help is a complete online reference to MS-DOS commands. The
reference includes information about how to type commands and their
parameters and switches, notes about commands, and examples of how to
use commands.
Enhanced SMARTDrive
-------------------
The SMARTDrive program included with MS-DOS 6 speeds up your computer
by using a disk cache, which stores information to be written to your
hard disk and writes it to the disk later, when system resources are
in less demand.
Microsoft Diagnostics
---------------------
Microsoft Diagnostics (MSD) gathers and displays technical information
about your computer.
Interlnk
--------
Interlnk enables you to easily transfer files between computers. With
Interlnk and a cable, you can access information on another computer
without having to use floppy disks to copy files to that computer.
Enhanced Commands
-----------------
The following commands have been added or enhanced for MS-DOS 6:
- The MOVE command moves one or more files from one directory or drive
to another. You can also use the Move command to rename directories.
- The CHOICE command allows you to prompt a user for input when
running a batch program. The CHOICE command allows you to display a
specified prompt, pause for user input, and return an error-level
parameter to the batch program.
- The DELTREE command deletes a directory and all of its files and
subdirectories.
Additional reference words: 6.00 feature summary dblspace multi-config
-=-=-=-=-=-
ARTICLE-ID:Q95494
TITLE :DoubleSpace Err Msg: 'Not Enough Conventional Memory...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you start your computer using the interactive startup option in
order to free enough memory to run the DoubleSpace Stacker conversion
option, you may receive the following error message after DoubleSpace
restarts your computer:
Not enough conventional memory
More Information:
When you start your computer and press the F8, F5, or SHIFT key to
free enough conventional memory to run the DoubleSpace Stacker
converter, you must also use the interactive startup option when
DoubleSpace restarts your computer. If you do not use this option, you
will not have enough memory to complete the conversion.
If you use the F5 key to bypass the CONFIG.SYS and AUTOEXEC.BAT files,
the only directory in the PATH environment variable is C:\DOS;
therefore, DoubleSpace cannot start Stacker.
Workaround
----------
To work around this situation, either use the F8 key to bypass some of
your device drives before and during the Stacker conversion process,
or remark out (REM) some of the device drivers and
terminate-and-stay-resident (TSR) programs in your CONFIG.SYS file.
Additional reference words: 6.00 reboot boot dblspace
-=-=-=-=-=-
ARTICLE-ID:Q94412
TITLE :AUTOEXEC File Is Not Processed Running 3rd-Party Shell
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some third-party command shells (such as NDOS) do not require the /P
switch (which specifies the command shell is permanent). As a result, if
you use a third-party shell without the /P switch, and set environment
variables from your CONFIG.SYS file or use MS-DOS 6 startup menus, your
AUTOEXEC.BAT file is not processed when you start your computer.
More Information:
Third-party command shells that do not require the /P switch check to see
if an environment has been created. If it has, they do not call the
AUTOEXEC.BAT file. If you use the MS-DOS 6 startup menu feature or you set
environment variables (such as PATH or PROMPT) in your CONFIG.SYS file, an
environment is created and the AUTOEXEC.BAT file is not processed.
Additional reference words: 6.00 NDOS 4DOS norton symantic
-=-=-=-=-=-
ARTICLE-ID:Q95495
TITLE :DblSpace Err: DoubleSpace Cannot Find STACKER.COM...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you run DoubleSpace and choose to convert a Stacker volume to a
DoubleSpace volume, and the Stacker directory is not in the PATH, you
receive the following error message:
DoubleSpace cannot find STACKER.COM in the path. This file is required
for Stacker conversion. Add the directory with STACKER.COM to the
path.
More Information:
When you convert a Stacker volume to a DoubleSpace volume, DoubleSpace
runs the STACKER.COM file to get information on Stacker drive mapping.
If the Stacker directory is not in the PATH environment variable, you
receive the above error message.
The Stacker directory can be removed from the PATH environment
variable after DoubleSpace has been installed.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94413
TITLE :Setup Checks for 6 Free Entries in the Root Directory
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system versions 5.0, 5.0a, and 6.0
--------------------------------------------------------------------
Summary:
The Microsoft MS-DOS installation program (SETUP.EXE) checks the root
directory of your startup drive (usually C) to determine if there is enough
room for MS-DOS files in the root directory. Is some cases, Setup may
incorrectly determine that enough room exists.
More Information:
You cannot have more than 512 entries (files or directories) in the root
directory of an MS-DOS partition. Setup does not allow you to install MS-
DOS Upgrade if you have 507 or more entries in the root directory
(including hidden files). This ensures that MS-DOS Setup can create at
least six entries.
In some cases, six entries is not enough. When Setup runs out of entries,
the installation cannot be successfully completed. For example, if you have
506 entries in the root directory, you are using PC-DOS, and you install MS-
DOS 6 Upgrade in a new directory, Setup cannot successfully install all the
files.
The information below lists all potential files and directories that may be
placed in the root directory and under what conditions they are installed.
Any combination of the factors listed below results in an incomplete
installation.
- WINA20.386 is copied to the root directory if your computer is capable
of running Microsoft Windows in 386 enhanced mode and you have Windows
version 3.0 installed.
- If you are using IBM PC-DOS, the files IBMBIO.COM and IBMDOS.COM are no
longer used but are not deleted. MSDOS.SYS AND IO.SYS are copied to the
root directory as two additional files.
- If you choose a new directory when you install MS-DOS, an additional
root directory entry is used.
- If AUTOEXEC.BAT and CONFIG.SYS are changed by Setup, the files
AUTOEXEC.OLD and CONFIG.OLD are created in the root directory.
- Setup creates an OLD_DOS.1 directory.
- If use the /E switch to install both the MS-DOS-based and the Windows-
based programs that ship with MS-DOS, Setup creates a WINDOWS directory.
(This does not apply to MS-DOS 5 Upgrade).
Workaround
----------
To work around this problem, remove unnecessary files from the root
directory and rerun Setup.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96029
TITLE :SPEEDCACHE PLUS Version 4.3 Not MS-DOS 6.0-Compatible
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Iomega's SPEEDCACHE PLUS version 4.3 is not compatible with Microsoft
MS-DOS 6.
SPEEDCACHE PLUS is used to decrease the access time on Bernoulli
drives. Iomega is testing SpeedCache with MS-DOS 6 and will make an
updated version available soon.
For more information, contact Iomega at (800) 546-5522.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95497
TITLE :Less Disk Space After Converting a Stacker Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you convert a drive from Stacker to DoubleSpace, DoubleSpace might
show that you have less compressed disk space than you had with
Stacker. This apparent disparity occurs because DoubleSpace is
thoroughly integrated with the MS-DOS operating system and can more
accurately estimate compressed disk space. In fact, you may actually
have more compressed disk space than you had before the conversion,
regardless of what was reported.
In addition, DoubleSpace continually updates its compressed disk space
estimates. As a result, as you work with a compressed drive,
DoubleSpace updates its estimates to reflect the actual current state
of file compression on your drive.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95532
TITLE :Deleting Unneeded Files After Converting a Stacker Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you want to save disk space after converting a Stacker volume file
(SVF) to a DoubleSpace compressed volume file (CVF), you can remove
most of your Stacker files.
More Information:
Since Stacker swaps the drive letters during the processing of the
CONFIG.SYS file, Stacker requires that the startup files (and files
called from the CONFIG.SYS file) be located on the uncompressed host
drive. Because DoubleSpace loads before CONFIG.SYS is processed
(unlike Stacker), you can delete any file (and directory) that Stacker
put on the host drive for CONFIG.SYS processing. These commonly
include files in the DOS and WINDOWS directories on the host drive.
In addition, you can delete AUTOEXEC.* and CONFIG.* on the host drive
since they only need to reside on the startup drive (C:).
The only files that must remain on the DoubleSpace host drive (of your
bootable partition) are DBLSPACE.BIN, DBLSPACE.INI, DBLSPACE.00X,
IO.SYS, MS-DOS.SYS, and your Windows permanent swap file if you have
one (386SPART.PAR). These files should have the following attributes:
System, Hidden, and Read-Only.
You can also safely remove the remarked out (REM) Stacker lines from
the CONFIG.SYS file, remove the Stacker directory from the PATH
environment variable in the AUTOEXEC.BAT file, and delete the Stacker
directory from the hard disk.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q94414
TITLE :OLD_DOS.x Directory Created Even if You Can't Uninstall
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Although you don't have the option to uninstall when you install Microsoft
MS-DOS 6 Upgrade on a system with a disk-compression program (such as
Stacker), Setup still creates an OLD_DOS.x directory. Because you cannot
uninstall, it is safe to delete the OLD_DOS.x directory using DELOLDOS.EXE.
More Information:
Setup uses the OLD_DOS.x directory to create temporary CONFIG.SYS and
AUTOEXEC.BAT files when it modifies them. Setup does not copy any other MS-
DOS files to this directory when you install MS-DOS 6 Upgrade over a disk-
compression program.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95745
TITLE :Err Msg with Iomega: 'MS-DOS 6 Cannot Be Installed...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you attempt install the MS-DOS 6 Upgrade on an Iomega Bernoulli
drive, you may receive the following error message:
MS-DOS 6 can not be installed because of an unrecognized partition.
Exit or install on floppy disks.
Iomega is currently working on new drivers for their drives that will
correct this problem.
For more information, contact Iomega at 1-800-546-5522. Microsoft will
post new information here as it becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94554
TITLE :HIMEM.SYS and EMM386.EXE Are Not Verbose by Default
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
In Microsoft MS-DOS version 6.0, HIMEM.SYS and EMM386.EXE do not display
any initialization information by default. When you start your computer, no
information is displayed by either device driver as CONFIG.SYS is
processed. To show data such as A20 handling switches and upper memory area
(UMA) information, you must add the /VERBOSE (/V) switch to each device
driver statement in the CONFIG.SYS file. For example:
DEVICE=C:\DOS\HIMEM.SYS /V
DEVICE=C:\DOS\EMM386.EXE NOEMS X=D000-D7FF /V
You can also display startup information by pressing the ALT key while your
computer is starting. This is useful for a one-time status check of these
drivers.
Note: If either device driver finds an error during initialization, it
automatically switches to verbose mode, displaying both the error and its
normal startup information.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96030
TITLE :Err Msg: 'DoubleSpace Cannot Continue...' with Bernoulli
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you set up DoubleSpace on a Bernoulli disk that has been
formatted with the Iomega Format utility, you may receive the
following error message:
DoubleSpace can not continue because an unrecognized error has
occurred.
If you choose the Yes button to continue setting up DoubleSpace, the
program reboots your computer and restores the original configuration
files--your data is not lost.
More Information:
The Iomega Format utility is provided with Bernoulli drives. For more
information on this utility, contact Iomega at (800) 546-5522.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95855
TITLE :Backup Err Msg: Not Ready Error Accessing Drive x
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You may receive the following error message when you back up
to a network drive using Microsoft Backup for Windows
Not ready error accessing drive x
where x is the letter of your network drive.
This error occurs when the network generates a timeout error, due to
the way MS-DOS creates a file for the backup. Therefore, this error
occurs more often with a slow server or when you're doing a very large
backup.
Workaround
----------
To work around this problem, either back up smaller portions of your
hard disk or increase your timeout setting for your network. If you
are using Microsoft LAN Manager version 2.1 or later, or a 100-percent
LAN Manager-compatible network, add the following statement to the
[workstation] section of the LANMAN.INI file.
SESSTIMEOUT=180
Additional reference words: 6.0 decnet ibm lan server lan manager
compatible
-=-=-=-=-=-
ARTICLE-ID:Q94555
TITLE :MemMaker: Order of Entries in the CONFIG.SYS File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker always modifies the CONFIG.SYS file so that the entries are in the
following order:
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE
buffers=
files=
dos=umb
lastdrive=
FCBS=
[Everything else in the same order it was already in]
The and are determined by MemMaker for each you
specific installation and configuration.
More Information:
MemMaker does not have a feature that allows drivers load before any of
those listed above. If there is a problem with a specific driver that needs
to be loaded before the above lines, that driver may not function until you
manually edit the CONFIG.SYS file and move the driver to where it belongs.
To work around this problem:
1. Edit the CONFIG.SYS file and comment out (REM) the device driver you
are having problems with.
2. Run MemMaker.
3. Edit the CONFIG.SYS file and remove "REM" from the device driver.
4. Return the device driver to its previous location.
Note: If the memory configuration that MemMaker created changes when you
follow this procedure, you must manually optimize your configuration.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96061
TITLE :MS-DOS Err Msg: Could Not Copy COMMAND.COM to Target...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use the SYS command (SYS.COM) to transfer the MS-DOS startup
file to another disk and COMMAND.COM is not in the root directory of
your startup drive, you receive the following error message:
Could not copy COMMAND.COM onto target disk
More Information:
Even if the COMSPEC environment variable and the SHELL= statement in
the CONFIG.SYS file point to COMMAND.COM in a different directory,
SYS.COM still looks for COMMAND.COM in the root directory of the
startup drive.
Workaround
----------
To work around this problem, copy COMMAND.COM to the root directory of
your startup drive (see your MS-DOS manual for information about
copying files). Then, set the read-only attribute with the ATTRIB
command. For example, type the following at the MS-DOS command prompt
and press ENTER:
attrib +r command.com
Additional reference words: 6.00 SYS COMMAND COMSPEC SHELL boot err
msg
-=-=-=-=-=-
ARTICLE-ID:Q95533
TITLE :Largest Possible DoubleSpace Drive Is 512 MB
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS limit for a drive using an 8K cluster size is 512 MB
(65,536 clusters at 8192 bytes per cluster). Because DoubleSpace
supports only 8K clusters, a drive compressed with DoubleSpace is
limited to 512 MB. If your compression ration is 2:1, the physical
size of the compressed value file (CVF) will be 256 MB.
Accessing data by 8K clusters (as compared with 4K or 2K clusters)
increases the speed of the disk read times (in most cases). With an 8K
cluster size, the MS-DOS kernel reads in more sectors than it would
with a smaller cluster size.
For more information on cluster sizes, query on the following words in
the Microsoft Knowledge Base:
cluster and logical and ms-dos
Additional reference words: 6.0 input/output i/o reads dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95536
TITLE :Results of DBLSPACE /CHKDSK
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The DBLSPACE /CHKDSK command evaluates errors and then sorts them into
three categories: lost clusters, cross-linked files, and other.
The "other" category indicates one or more of the following problems:
- There is a damaged extended BIOS parameter block (BPB). (This is
the BPB specific to the compressed volume file [CVF].)
- There is a damaged beginning or ending signature in the CVF.
- An entry in the MD-FAT (Microsoft DoubleSpace - file allocation
table) is corrupt (unreadable).
- The MD-FAT makes a reference to the MS-DOS FAT that is not valid.
- The sector heap offset is out of range; for example, the sector
heap is larger than the CVF or beyond the size of the logical
compressed drive.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q95557
TITLE :System Stops Responding with GAI.SYS Loaded High
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The device driver for the APPIAN Rendition IIe Video card (GAI.SYS)
cannot be loaded high.
If you are using this video card, you need to manually exclude GAI.SYS
when running MemMaker in custom mode, or modify the MEMMAKER.INF file.
To exclude the GAI.SYS device driver, edit the MEMMAKER.INF file with
a text editor such as MS-DOS Editor, and add the following line:
*GAI
More Information:
If GAI.SYS is loaded high (into upper memory) the system may stop
responding (hang) at random. This can also occur when you run the
MS-DOS Prompt icon in Windows.
Additional reference words: 6.0 uma umb devicehigh
-=-=-=-=-=-
ARTICLE-ID:Q95558
TITLE :MemMaker Doesn't Remove All References to QEMM
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker removes all references to QEMM. However, if one of your QEMM
statements in the CONFIG.SYS file does not have an equal sign (=),
MemMaker ignores it; the driver is not loaded by MemMaker, nor is it
removed from the CONFIG.SYS file. If this occurs, you may receive an
error message from MemMaker stating that another expanded memory
manager (EMM) is already running.
To work around this problem, edit your CONFIG.SYS file with a text
editor such as MS-DOS Editor and put equal signs in your DEVICE
commands.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q95559
TITLE :MemMaker Does Not Preserve Redirection Settings
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker does not preserve redirection syntax in the AUTOEXEC.BAT
file. For example, if you have C:\DOS\DOSKEY >NUL in the AUTOEXEC.BAT
file, MemMaker will change it to LH /L:x,nnnn C:\DOS\DOSKEY.
To work around this problem, edit your AUTOEXEC.BAT file and put the
>NUL statement back in after you run MemMaker.
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96087
TITLE :Bernoulli Drive Doesn't Mount with DoubleSpace Loaded
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DBSPACE.SYS is loaded in the CONFIG.SYS file before Iomega's device
driver (RCD.SYS) then the Bernoulli mount code is discarded before the
Bernoulli drives become readable.
RCD.SYS should be loaded as high as possible in the CONFIG.SYS file
and MUST be loaded before DBLSPACE.SYS.
Note: DBLSPACE.SYS does not load a device driver for DoubleSpace. It
simply moves DBLSPACE.BIN in memory.
The Iomega and Bernoulli products included here are manufactured by
vendors independent of Microsoft; we make no warranty, implied or
otherwise, regarding these products' performance or reliability.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96093
TITLE :Manifest Shows EMS Memory with NOEMS Switch
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Quarterdeck's Manifest program shows that there is expanded memory
specification (EMS) memory, even if EMM386.EXE is loaded with the NOEMS
switch. If the NOVCPI switch is added to the EMM386.EXE line in the
CONFIG.SYS file, Manifest will no longer show any EMS memory.
More Information:
EMM386.EXE is a VCPI provider even when the NOEMS switch is specified.
With VCPI support enabled, EMM386.EXE supplies an upper-memory frame
buffer for the VCPI applications to use. When an application checks for
EMS memory it may see this buffer and believe it to be an EMS page
frame, thus reporting that EMS memory is available when in actuality it
is not. When the NOVCPI switch is added, it disables this upper-memory
buffer, thus disabling what the application is seeing as EMS.
This is a functional change in MS-DOS 6.0. To make EMM386.EXE perform
like it does in earlier versions of MS-DOS, both the NOEMS switch and
the NOVCPI switch are required.
Manifest is manufactured by a vendor independent of Microsoft; we make
no warranty, implied or otherwise, regarding this product's performance
or reliability.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95560
TITLE :MemMaker Converts Some Variables to Drive Letters
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you set an environment variable in the AUTOEXEC.BAT file and then
use it to run a program, MemMaker converts the environment variable to
its true name.
For example, if your AUTOEXEC.BAT file contains these lines before you
run MemMaker
set xdrive=d
%xdrive%:\dos\doskey
they are converted to:
set xdrive=d
lh /l:xxxx d:\dos\doskey
To work around this problem, either do not set environment variables
to drive letters or directories, or modify your CONFIG.SYS and
AUTOEXEC.BAT files after you run MemMaker.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96250
TITLE :How to Remove DoubleSpace and Preserve Your Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following procedure describes how to remove DoubleSpace from your
hard disk while preserving your files. It is a lengthy procedure and
should be followed only if DoubleSpace removal is necessary. If you
need to change the size of your DoubleSpace volume, type "help
dblspace" (without the quotation marks) at the MS-DOS command prompt
and refer to the online help topic DBLSPACE /SIZE.
Note: This example assumes that you have compressed your boot drive
(C) and that your DoubleSpace host partition is H. For more
information on how DoubleSpace assigns host partitions, query on the
following words in the Microsoft Knowledge Base:
doublespace and assigns and host
If you are not removing DoubleSpace from your boot drive, skip
steps 2-7.
1. Back up all the files you want to preserve from your compressed
drive (C) by using Microsoft Backup or a third-party backup utility.
(For information on using Microsoft Backup, see Chapter 3, "Managing
Your System," in the "Microsoft MS-DOS User's Guide.")
2. When you remove DoubleSpace, what is now drive H will become drive
C, which means you will boot from drive H. To be able to boot from
drive H and restore your backup files, the DoubleSpace host partition
must contain the necessary MS-DOS system files and utilities.
Furthermore, if you stored your backup files on a network drive,
network redirectors must be available.
Determine how much free space you will need to copy the MS-DOS
files (and network redirectors) on the DoubleSpace host partition
(drive H). To do so, use the DIR command. For example, to see how
much space is needed for your MS-DOS files, type the following
command:
dir c:\dos
The output appears as follows:
...
UNFORMAT.COM
VALIDATE.COM
VSAFE.COM
XCOPY.EXE
194 file(s) 7003143 bytes
12959744 bytes free
The next-to-last line shows the number of bytes used by the files in
the DOS directory. This number is the amount of free disk space needed
to store the necessary files and utilities after DoubleSpace is
removed.
3. To free unused disk space from the DoubleSpace compressed volume,
use the /SIZE switch as follows:
dblspace /size
4. Determine how much free space there is on the DoubleSpace host
partition. To do this, change to drive H and use the DIR command. The
last line of the output from the DIR command shows the number of bytes
free on drive H. If this number is greater than the number you found
in step 2, there is enough space to copy the necessary files and
utilities, and you can proceed with step 6. If there is not enough
space on the DoubleSpace host partition, proceed to step 5.
5. Delete enough files on drive C to create the needed space you
determined during step 2. (Note: Do not delete any MS-DOS or network
files; those files must be present during this procedure.)
You can use the DELTREE command to do this. (DELTREE quickly deletes
entire directories.) For example, to remove the WORD directory and all
the files and subdirectories it contains, type the following:
deltree /y c:\word
After you delete some files, shrink the DoubleSpace volume file
again by typing the following:
dblspace /size
To find out if you've created enough free disk space, change to drive
H and use the DIR command. Again, the bytes in use and bytes free are
displayed. If the last line, "bytes free," shows enough free disk
space, continue with step 6. Otherwise, repeat step 5.
6. Copy all the MS-DOS and network files that you need (the files you
determined were necessary during step 2) to the DoubleSpace host
partition (drive H). To preserve the file and directory structure, you
can use the XCOPY command with the /S switch. For example, to copy all
the MS-DOS files into a DOS directory on H, type the following:
md h:\dos
xcopy c:\dos\*.* h:\dos /s
7. Make sure there is a copy of COMMAND.COM in the root of the
DoubleSpace host partition by typing the following:
dir h:\command.com
If COMMAND.COM is not present, copy it from the boot drive (C) with
the following command:
copy c:\command.com h:\
Repeat this step for AUTOEXEC.BAT and CONFIG.SYS files. These files
need to be in the root of the DoubleSpace host partition as well.
You now have all the files you need to boot from the uncompressed
drive and restore your backup files; you can begin removing the
DoubleSpace volume.
8. Switch to the root of the DoubleSpace host partition by typing the
following:
h:
cd\
9. Delete the DoubleSpace files by using the following command:
deltree /y dblspace.*
10. If you are removing DoubleSpace from your boot drive, open the
CONFIG.SYS file from the DoubleSpace host partition (H) in a text
editor, such as MS-DOS Editor. If you are not removing DoubleSpace
from your boot drive, open the CONFIG.SYS file from drive C. Remove
any reference to DBLSPACE.SYS. For example, change your DBLSPACE.SYS
DEVICE command to appear as follows:
rem device=c:\dos\dblspace.sys
11. Restart your computer by pressing CTRL+ALT+DEL.
12. Restore your backup files.
DoubleSpace has now been removed from your system.
Additional reference words: 6.00 howto
-=-=-=-=-=-
ARTICLE-ID:Q95599
TITLE :DblSpace Err Msg: DoubleSpace Cannot Convert Your...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you convert a Stacker volume to a DoubleSpace volume, your
Stacker compressed volume file (CVF) must have 8K clusters. If it does
not, you receive the following error:
DoubleSpace cannot convert your Stacker drives because they have a
cluster size other than 8K. To convert your Stacker drives to
DoubleSpace format, follow the instructions in the DoubleSpace
section of the README.TXT file.
More Information:
When you install Stacker version 2.0 or 3.0, you have the option of
using cluster sizes other than the 8K default.
- Stacker 2.0 supports 4K and 8K clusters
- Stacker 3.0 supports 4K, 8K, 16K, and 32K clusters
Since the conversion of a Stacker volume is done cluster by cluster,
and DoubleSpace uses 8K clusters, DoubleSpace cannot convert Stacker
volumes if they don't have 8K clusters.
Additional reference words: 6.0 err msg errmsg
-=-=-=-=-=-
ARTICLE-ID:Q95601
TITLE :Windows Error Message: Corrupt Swap File Warning
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0 and 3.1
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
Microsoft Windows versions 3.0 and 3.1 allow you to create a permanent
swap file on an MS-DOS 6.0 DoubleSpace drive. If you do this, you
receive one of the following messages when you restart Windows:
Windows 3.1:
Corrupt Swap File Warning - The permanent swap file is corrupt
Windows 3.0:
Corrupt Swap File Warning - Your swap file is corrupt
To work around this situation, delete the permanent swap file and
create a permanent swap file on your host drive.
Note: The host drive is the drive that actually contains the
DoubleSpace compressed volume file (CVF). For more information, run
DoubleSpace and choose Contents from the Help menu.
More Information:
Windows Doesn't Detect DoubleSpace
----------------------------------
Windows cannot create a permanent swap file on CVFs created by disk
compression programs such as DoubleSpace, Stacker, and SuperStor.
Since Windows does direct disk read/write operations to a permanent
swap file, the swap file must be located on a physical hard disk, not
a CVF.
Because DoubleSpace had not been developed when Windows 3.1 was
released, it was not possible to add detection code to Windows to
prevent it from installing on a DoubleSpace drive.
Additional Problems with Windows 3.0
------------------------------------
When you run Windows 3.0 in real mode (in order to run SWAPFILE.EXE),
you receive the following message:
Unsupported DOS version; upgrade to DOS version 3.1 or higher
This message is obviously incorrect. To work around this situation,
run SPATCH.BAT, which is located on your original MS-DOS 6.0 disks.
For more information on DoubleSpace, type the following at the MS-DOS
command prompt:
help dblspace
Additional reference words: 6.0 swapfile dblspace double space
dblspace.exe err msg errmsg
-=-=-=-=-=-
ARTICLE-ID:Q95856
TITLE :Uninstalling MS-DOS 6 Upgrade After Compressing a Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You cannot use the MS-DOS 6 Upgrade Uninstall disk to restore your
previous version of MS-DOS if you have compressed any of your hard
disk drives with DoubleSpace or a third-party disk-compression program
unless you remove all traces of the disk-compression software.
If you attempt to restore your previous version of MS-DOS and you have
compressed your hard disk drive with DoubleSpace, you receive the
following error:
Because you installed DoubleSpace after installing MS-DOS 6,
you cannot restore your previous version of DOS.
More Information:
If you have compressed you hard disk drive with DoubleSpace and would
like to restore your previous version of MS-DOS, query on the
following words in the Microsoft Knowledge Base and follow the
procedure in the article about removing DoubleSpace and preserving
your files:
preserve and doublespace and remove and ms-dos
After you have followed the procedure in the article, restart your
computer with the Uninstall disk in drive A.
For more information about restoring your previous version of MS-DOS,
query on the following words in the Microsoft Knowledge Base:
uninstall and no and disk and old_dos
If you have compressed your hard disk drive with a third-party disk
compression program, consult your documentation or contact the
manufacture for assistance in removing the software before running
Uninstall.
Additional reference words: 6.00 double space dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96128
TITLE :How Setup, MemMaker, and DoubleSpace Find Windows
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Setup, MemMaker, and DoubleSpace need to locate the Windows directory
on your hard disk (if you have one). To find the Windows directory,
Setup looks for the following four files:
WIN.COM
PROGMAN.INI
SYSTEM.INI
When you run SETUP /E to install the optional utilities, Setup checks
to make sure your DOS directory is in the path and looks for
DISKCOPY.COM in that directory.
MemMaker and DoubleSpace look for the following three files:
WINVER.EXE
SYSTEM.INI
WINFILE.INI
Additional reference words: 6.00 setup.exe busetup.exe memmaker.exe
dblspace dblspace.exe
-=-=-=-=-=-
ARTICLE-ID:Q95632
TITLE :DBLSPACE.INI File Settings
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
The following are valid settings for the DBLSPACE.INI file:
MaxRemovableDrives=
FirstDrive=
LastDrive=
MaxFileFragments=
ActivateDrive=
More Information:
MaxRemovableDrives=
-------------------------------------
This setting specifies the number of hard drive partitions available
to MS-DOS.
FirstDrive=
-------------------------
This setting specifies the lowest logical drive letter available for a
DoubleSpace host drive.
LastDrive=
------------------------
This setting specifies the highest logical drive letter available for
a DoubleSpace host drive.
Note: DoubleSpace loads host drives starting at LastDrive= and works
back to FirstDrive=.
MaxFileFragments=
-----------------------
MaxFileFragments is set to 2600 during installation of DoubleSpace.
After DoubleSpace is installed, each time the compressed volume file
(CVF) is changed (deleted, mounted, unmounted, resized), the
MaxFileFragments setting is changed to reflect the new number of file
fragments in all compressed volume files. The new number is a sum of
the file fragments in all CVF's plus 110.
For example, if the CVF on drive C has 6 fragments and the CVF on
drive D has 3 fragments, then maxfilefragments=119 (110+6+3). The new
value is used to allocate adequate memory the next time the CVF is
mounted. The changes in the DBLSPACE.INI file (with respect to
allocating memory) take effect after you restart your computer.
Note: The initial setting (2600) and the number added when a CVF is
changed (110) are both read from the DBLSPACE.INF file.
ActivateDrive=
--------------------------------------------------------------
This setting specifies three things:
- The first drive letter specifies which drive letter to use for the
host drive.
- The second drive letter specifies which drive to use for the
compress volume file (CVF).
- The third digit is the last number of the compress volume file
(DBLSPACE.00x). This digit indicates which DoubleSpace volume
should be mounted.
For example, "ActivateDrive=H,C0" indicates DoubleSpace was used to
compress drive C (using CIP), drive H is used for the host drive, and
the DoubleSpace file name is DBLSPACE.000.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95633
TITLE :Automating RAMDrive Compression with DoubleSpace
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
It is possible to compress a RAMDrive with DoubleSpace. However, since
the information on the RAMDrive is lost each time you restart your
computer, you have to recompress the RAMDrive each time you start your
system.
You can avoid this problem by storing the RAMDrive compressed volume
file (CVF) on your hard drive and placing two commands in your
AUTOEXEC.BAT file to copy and mount the CVF on the RAMDrive when you
start your computer.
More Information:
The compression of the RAMDrive can be automated using the following
procedure:
1. Create RAMDrive. For example, to create a 1 MB RAMDrive in extended
memory, place the following statement in your CONFIG.SYS file:
device=c:\dos\ramdrive.sys 1024 /e
2. Restart your computer to load the RAMDrive.
MS-DOS assigns the next available drive letter for the RAMDrive.
For example, if you only have one hard drive (C), the RAMDrive
is assigned the drive letter D. This procedure continues to use D:
in the examples.
3. Compress the RAMDrive using the following command:
dblspace /compress d: /reserve=.13
The /RESERVE=.13 switch isn't necessary but it gives you the most
compressed space. On a 1 MB compressed RAMDrive, you have 1.59 MB free
on the RAMDrive and .13 MB free on the host drive.
4. Change the CVF attributes so the file can be copied. For example:
attrib h:\dblspace.000 -s -h -r
This example assumes the host drive is H:. To determine your host
drive, type DBLSPACE /LIST at the MS-DOS command prompt. Write the
drive mapping information down, because you need it in step 5.
5. Copy the compressed volume file (CVF) to your hard drive.
To avoid having to recompress the RAMDrive each time you start your
computer, you must store the CVF on your hard drive. This requires
approximately 1 MB of space on your hard drive.
To copy the compressed volume file to your hard drive, type the
following at the MS-DOS command prompt:
copy h:\dblspace.000 c:\dos\ramcvf.000
Since this file cannot be compressed (it already is) you should
copy it to an uncompressed drive.
6. Add the following lines to your AUTOEXEC.BAT file so the CVF is
copied to your RAMDrive and mounted each time you start your computer.
REM Copies and Mounts CVF to RAMDrive
copy c:\dos\ramcvf.000 d:\dblspace.000
dblspace /mount=000 d: /newdrive=h:
Substitute the appropriate drive letters for C:, D:, and H:. Drive
C: should be the uncompressed drive where you store the RAMDrive
CVF, drive D: is the RAMDrive, and drive H: is the host.
7. Restart your computer. To determine if the procedure worked, type
DBLSPACE /LIST at the MS-DOS command prompt.
WARNING: Any information stored on a RAMDrive is lost when you restart
or turn off your computer. To prevent data loss, copy any file you
want to save from your RAMDrive to your hard drive before turning off
your computer.
Additional reference words: 6.0 6 compressed
-=-=-=-=-=-
ARTICLE-ID:Q96130
TITLE :How DBLSPACE.BIN Determines If It Should Stay in Memory
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you have DBLSPACE.BIN in the root directory of your startup drive
(usually C) but you do not have a compressed volume file (CVF),
DBLSPACE.BIN still loads in memory.
After DBLSPACE.BIN loads in memory, it searches for the DBLSPACE.INI
file. If it finds this file, DBLSPACE.BIN remains in memory and
continues the boot process by loading IO.SYS in memory. (It doesn't
matter whether the DBLSPACE.INI file is valid.)
If the DBLSPACE.INI file is not found, DBLSPACE.BIN does not remain
loaded in memory.
Note: The DBLSPACE.SYS command in the CONFIG.SYS file does not effect
this process.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95634
TITLE :Manual Installation Err Msg: Incompatible Partition
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
If you attempt to perform a manual installation of MS-DOS 6 Upgrade,
using the "You need to install MS-DOS manually" procedure in
Diagnosing and Solving Problems, step 3 says to use the SETUP /Q
command. However, if Setup detects you have a special master boot
record (MBR) or an incompatible partition, Setup displays the
"Incompatible partition" screen.
Workaround
----------
If you have one of the following drives and you receive this error
message, run setup with the /U and /Q switches (for example, A:SETUP
/U /Q).
- Priam
- Everex
- SpeedStor Bootall
- Micro House DrivePro
Installing the Optional Programs
--------------------------------
If you attempt to install the optional programs at a later date, you
should also use the /U switch. For example:
setup /u /e
Setup Syntax
------------
/E Installs Windows and MS-DOS optional programs.
/Q Copies MS-DOS files to a hard disk.
/U Installs MS-DOS even if Setup detects disk partitions
that might be incompatible with MS-DOS 6.
For more information of Setup switches, insert MS-DOS 6 Upgrade Setup
Disk 1 in one of your floppy disk drives, change to that drive at the
MS-DOS command prompt and type SETUP /?.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96133
TITLE :DoubleSpace Err Msg: 'Your Computer Might Be Running...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you try to install DoubleSpace while running a version of
SMARTDrive from a version of MS-DOS earlier than 6.0, the following
dialog box appears:
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.
To install DoubleSpace and avoid this error message, make sure you are
loading MS-DOS 6.0 SMARTDrive. The SMARTDrive command line in
AUTOEXEC.BAT should look similar to the following:
c:\dos\smartdrv.exe
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95635
TITLE :Using Unique Labels with Multi-Config
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
When using a Multi-Config startup menu with MS-DOS 6.0, the label
names you use in your AUTOEXEC.BAT file must be unique within the
first eight characters. This is true for all MS-DOS labels.
More Information:
For example, if your startup menu has two labels, (Emp_John_Smith and
Emp_John_Smyth) and your AUTOEXEC.BAT file has a GOTO %CONFIG%
command, MS-DOS will always jump to the :Emp_John_Smith label if it
appears before the :Emp_John_Smyth label in the AUTOEXEC.BAT file.
To workaround or avoid this problem, make sure all menu items in your
CONFIG.SYS and their corresponding labels in your AUTOEXEC.BAT file
are unique within the first eight characters.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96152
TITLE :Setup Adds MS-DOS Directory to Every PATH Statement
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 Setup adds the MS-DOS directory to every PATH statement in
your AUTOEXEC.BAT file. For example, if Setup finds the following
lines in your AUTOEXEC.BAT file
path c:\dos;c:\windows
path %path%;c:\c700\bin
it adds "c:\dos" to the second line even though the MS-DOS directory
is already present in the first line. The lines appear as follows:
path c:\dos;c:\windows
path c:\dos;%path%;c:\c700;c:\bin
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95956
TITLE :MSCDEX Doesn't Load with Trantor CD-ROM Driver
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Trantor CD-ROM driver TSLCDR.SYS (commonly used with Adaptec 1542b
SCSI cards) cannot be found in memory by MSCDEX when you have a very
large CONFIG.SYS file and you use a MS-DOS 6.0 multiple configuration
menu. As a result, MSCEDEX won't load for this device driver.
Workaround
----------
To work around this problem, decrease the size of the CONFIG.SYS file
or don't use a multiple configuration menu.
We are researching this problem and will post new information here as
it becomes available.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.0 dblspace multi-config 3rdparty
-=-=-=-=-=-
ARTICLE-ID:Q95957
TITLE :Qemm Err Msg: File Server Encountered a Critical...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use QuarterDeck's Qemm extended memory manager with Windows
in 386 enhanced mode, Windows may generate the following error message
when you run Intel's Faxability Plus for Windows:
File server encountered a critical error and terminated.
To work around this problem, disable the Stealth Mapping feature in
Qemm. For information about how to do this, See your Qemm manual
More Information:
Faxability Plus for Windows comes with the Satisfaxion Fax/Modem.
CASMGR, a terminate-and-stay-resident (TSR) program that captures the
fax and communicates with the fax/modem card, also causes this error
message.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.0 VSERVER
-=-=-=-=-=-
ARTICLE-ID:Q95808
TITLE :How to Install MS-DOS 6 Upgrade over DR-DOS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft PSS supports the installation of Microsoft MS-DOS 6 Upgrade
over Novell DR-DOS.
Much of the information in the "More Information" section of this
article section was taken from the MS-DOS 6 Upgrade README.TXT file.
More Information:
It is possible to upgrade from DR-DOS to the MS-DOS 6 Upgrade;
however, before you run the Setup program, you should first review the
following precautions and carry out those that apply to your system:
- If you have any security features, including password protection,
disable them. For more information, refer to page 187 in the
"Microsoft MS-DOS 6 User's Guide."
Warning: The MS-DOS 6 Upgrade Setup program cannot create an
Uninstall disk if your CONFIG.SYS or AUTOEXEC.BAT file is password
protected. If any of your DR-DOS system files or your DR-DOS
directory are password protected, use the DR-DOS password command
to disable the password protection before you install MS-DOS 6.
- If you have the DELWATCH delete-protection program installed on
your computer, you must disable DELWATCH and purge your deleted
files before you install MS-DOS 6. To do this, refer to pages
187-188 in the "Microsoft MS-DOS 6 User's Guide."
- If your CONFIG.SYS or AUTOEXEC.BAT file uses any conditional DR-DOS
commands (such as ? or goto), remove those commands and adjust the
order of the remaining commands accordingly.
- If your CONFIG.SYS file contains the DR-DOS chain command, remove
it and adjust the other CONFIG.SYS commands accordingly.
- If your computer uses disk compression, but drive C is not
compressed, run Setup as described in the "Getting Started" Chapter
of the "Microsoft MS-DOS 6 User's Guide." When Setup displays the
message "Your CONFIG.SYS file contains commands that are not valid
MS-DOS commands," select the Modify Original Files option.
- If your hard disk is compressed, carry out the procedure in the
section of the README.TXT file titled "Setup detects that your
computer uses DR-DOS."
- If Setup displays the message "Your computer uses a disk-
compression program and does not have enough free disk space to set
up MS-DOS," you must convert your DR-DOS 6 SuperStor (SSTOR)
compressed drive to an MS-DOS 6 DoubleSpace drive using the
procedure below. This is necessary because the DR-DOS 6 SSTOR
utility does not provide the functionality to increase the size of
your uncompressed host drive.
To run the MS-DOS 6 Setup program, do the following:
1. Use the DR-DOS Backup command to back up your program and data
files. For more information on using the DR-DOS Backup command,
refer to your DR-DOS documentation.
2. Insert the MS-DOS 6 Setup Disk 1 in drive A or B and use the setup
command with the /f switch. For example, if you insert Setup Disk 1
in drive A, type the following at the MS-DOS command prompt and
then press enter:
a:setup /f
Important: After you type the above command and Setup prompts you
to insert a disk to create the startup floppy disk, you MUST create
that disk in drive A. Also, be sure that you choose to install on
drive A.
3. Ensure the startup disk you created in step 2 is in drive A and
then restart your computer by pressing CTRL+ALT+DEL.
4. Use the MS-DOS Format command to reformat all of your drives. When
you format drive C, be sure to use the /s parameter to make the
disk bootable. To do this, type the following command at the MS-DOS
command prompt and then press enter:
format c: /s
5. To restore your program and data files, use the MS-DOS 6 restore
command (this command is located on the startup disk you created in
step 2). For example, to restore your files to from drive A to
drive C, type the following at the MS-DOS command prompt and then
press enter:
restore a: c:\*.* /s
Important: Do NOT restart your computer before proceeding to
step 6.
Note: If some of your files cannot be restored to your hard disk
because you don't have enough disk space, you need to install the
MS-DOS 6 Upgrade, run DoubleSpace to compress your hard disk, and
then restore your files. After you finish restoring your files,
continue with step 6.
6. To remove your DR-DOS files, install the MS-DOS 6 Upgrade again. To
do this, insert the MS-DOS 6 Setup Disk 1 in drive A, type setup,
and follow the instructions on your screen.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96167
TITLE :DoubleSpace Identifies Windows 3.1 in Standard Mode as Shell
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you attempt to run DoubleSpace or any of the DoubleSpace command
line functions from the MS-DOS Prompt with Windows 3.1 in standard
mode, you receive the following error message:
You are running the MS-DOS Shell. To run DoubleSpace,
you must first quit the MS-DOS Shell.
This error occurs because the code used to detect MS-DOS Shell is the
same as the code to detect Windows in standard mode, and the detection
for Shell precedes the detection for Windows.
Additional reference words: 6.00 DoubleSpace dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95814
TITLE :EMM386.EXE May Cause PS/2 to Hang with HIGHSCAN
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use the IBM Reference Diskettes version 1.31 for the PS/2 model
90 or 95, you may not be able to use the HIGHSCAN switch with
EMM386.EXE. Using HIGHSCAN may cause your system to stop responding
(hang).
This problem does not occur with Reference Diskette version 1.10.
More Information:
The newer Reference Diskette uses memory addresses in the F000-F7FF
range (although it may use additional memory elsewhere in the
upper memory area).
To workaround this problem, run MemMaker Custom Setup and choose No
when prompted to "Scan the Upper Memory Area Aggressively?"
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95816
TITLE :DBLSPACE.SYS /MOVE Is in the CONFIG.SYS File Twice
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
During installation, DoubleSpace may add more than one
"DEVICEHIGH=C:\DOS\DBLSPACE.SYS /MOVE" statement to the CONFIG.SYS
file. DoubleSpace adds this line to more than one location in the
CONFIG.SYS file if DoubleSpace determines that DBLSPACE.BIN may cause
problems for network device drivers.
More Information:
DBLSPACE.SYS /MOVE does not load a device driver for DoubleSpace.
Instead, it moves the DoubleSpace component (DBLSPACE.BIN) in memory.
Multiple instances of DBLSPACE.SYS do not use additional memory
because this device drive simple moves DBLSPACE.BIN and then unloads
itself.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95818
TITLE :Brooklyn Bridge Installation Changes CONFIG.SYS File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use an MS-DOS 6 multiple configuration menu, your CONFIG.SYS
file becomes scrambled when you install Brooklyn Bridge version 3.5.
More Information:
Installing Brooklyn Bride on a system using a multiple configuration
menu results in the following:
- All blank lines are removed.
- A screen dump (both character and attributes) is inserted into the
middle of the CONFIG.SYS file.
- DEVICE=BRIDGE1.DEV is added to an unexpected location, such as the end
of and existing CONFIG.SYS command.
The Brooklyn Bridge installation program does not give the user a
choice to update the CONFIG.SYS file - it is done automatically.
However, Brooklyn Bridge does create a backup CONFIG.SYS file called
CONFIG.OLD.
Note: This problem may apply to other versions of Brooklyn Bridge -
Microsoft has tested MS-DOS 6 with Brooklyn Bridge version 3.5 only.
Additional reference words: 6.00 multi-config
-=-=-=-=-=-
ARTICLE-ID:Q95819
TITLE :Defragmenter Err Msg: 'Insufficient Memory...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If there are too many files and directories on your hard drive, MS-DOS
Defragmenter (DEFRAG) can run out of memory. If Defragmenter runs out
of memory before beginning optimization, you will receive the
following error message:
Insufficient memory - Error Reading the FAT
Defragmenter is limited by the number of files/directories and NOT the
disk size. It is unlikely you will see this problem unless you have
more than 10,000 files/directories on your drive.
You may be able to alleviate the problem by increasing the amount of
free conventional memory and available upper memory blocks (UMBs).
More Information:
If you have freed as much conventional memory as possible and you are
using a 386 or 486 machine, try the following temporary workaround:
1. Make sure EMM386.EXE is being loaded in the CONFIG.SYS file.
2. Using an ASCII text editor such as MS-DOS Edit, add the I=A000-BF77
and NOEM parameters to the device=C:\DOS\EMM386.EXE line in the
CONFIG.SYS.
Note: The A000-B7FF range is commonly used by video cards. Unless
you have a monochrome video card, do not run any graphics
applications when you are using the I=A000-B7FF parameter.
3. Save the CONFIG.SYS file and quit the text editor.
4. Restart your computer.
5. Run Defragmenter with the /G0 switch to prevent it from running in
graphics mode. For example, you would type:
defrag /g0
Note: The switch is G and the number zero not G and the letter O.
6. Edit your CONFIG.SYS file and remove the parameters you added in
step 2.
7. Save the text file, exit the editor and restart your computer.
If, after following the above procedure, you continue to run out of
memory when you attempt to defragment your drive, the problem is most
likely occurring because you have more files than Defragmenter handle.
To optimize your disk, you will need to remove some files from your
disk. If this problem occurs frequently, you may want to consider
creating smaller partitions or multiple DoubleSpace drives on the same
partition.
Additional reference words: 6.00 dos msdos defrag raise the ceiling
dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96169
TITLE :AUTOEXEC.BAT and CONFIG.SYS Backups on Uninstall Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 Setup saves backup copies of the AUTOEXEC.BAT and
CONFIG.SYS files on the Uninstall disk that you create during
installation. No copies are saved in the boot drive of your hard disk.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95824
TITLE :Constant or Random Beeping in Windows with Anti-Virus
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If your computer makes a beeping sound randomly when you are running
Windows, or if Windows stops responding (hangs), and you are loading
Microsoft Anti-Virus, you need to load VSafe Manager (MWAVTSR.EXE).
VSafe Manager is a Windows-based terminate-and-stay-resident (TSR)
program designed to allow bidirectional communication with VSafe. For
more information on VSafe Manager, query on the following words in the
Microsoft Knowledge Base:
vsafe and manager and mwavtsr.exe
Additional reference words: 6.00 VM Beep-o-matic beep MSAV safe
-=-=-=-=-=-
ARTICLE-ID:Q96180
TITLE :VSAFE Err Msg: Program Is Trying to Write to Hard Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following pop-up dialog box may be displayed when you perform a
disk operation that writes to the disk:
VSAFE Warning
Program is trying to write to hard disk
Do you wish to continue?
You can then choose one of three options: Stop, Continue or Boot. If
you choose Stop, the following error message is displayed:
ATTENTION: A serious disk error has occurred while writing
to drive C.
(Note: If you are running MS-DOS Prompt from Windows, this error
message is displayed in a blue screen with the heading "Serious Disk
Error.")
You can now choose to retry the operation. This causes the first VSAFE
error to display again. Until you choose Continue or Boot, you are not
able to escape these recurring warning messages. If you choose
Continue, the write operation is performed. If you choose Boot, the
write operation aborts, your system restarts, and any information you
were trying to save is lost.
This problem is caused by VSAFE installed with the write-protect
option and SMARTDrive installed with write caching enabled. If you
want to use VSAFE with the write-protect option, do not enable
SMARTDrive write caching.
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here as it
becomes available.
Additional reference words: 6.00 write protect protected
-=-=-=-=-=-
ARTICLE-ID:Q96185
TITLE :Norton Speed Disk May Cause Lost Clusters with DBLSPACE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After you use any version of Symantec Norton Speed Disk prior to
version 7.0 on a compressed DoubleSpace drive, the DBLSPACE /CHKDSK
command may report a very large number of lost allocation units.
This occurs when you have set the option to Clear Unused Disk Space
and then perform a full optimization.
Solution
--------
To correct this problem, type "dblspace /chkdsk /f" (without the
quotation marks) at the MS-DOS command prompt and press ENTER.
Note: The Compress program from PCTools versions 5.5 and 6.0 may also
cause the above problem if the Clear Unused Disk Space option is set
when you perform a full optimization.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.00 PCTools Compress Speedisk Norton
dblspace DoubleSpace double space 3rdparty
-=-=-=-=-=-
ARTICLE-ID:Q95835
TITLE :What VSafe Manager (MWAVTSR.EXE) Does and How It Works
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
VSafe Manager (MWAVTSR.EXE) is a Windows-based application that allows
bidirectional communication with VSafe.
VSafe in not a Windows-based application; therefore, if you are
running Windows, the only way VSafe can inform you that there is a
problem is to cause the system to beep. When VSafe Manager is running,
VSafe can send you messages through VSafe Manager. In addition, VSafe
Manager lets you change VSafe settings while Windows is running.
More Information:
The most common problem with VSafe Manager occurs when Windows beeps
as you start it. This beeping occurs after you have upgraded Windows
because VSafe checks the files that are loading against the CHKLIST.MS
file in the loading file's directory. If they don't match, VSafe tries
to prevent the file from loading.
To work around this problem, do one of the following:
- Rescan you disk with Microsoft Anti-Virus after upgrading to create
new checksum files.
-or-
- Delete the current checksum files.
To create new checksum files:
1. From the Options menu, choose Set Options.
2. Select the Create New Checksums check box and choose the OK button.
3. Select the drive you want to scan and choose the Detect button.
To delete the checksum files:
1. Select the drive from which you want to delete the checksum files.
2. From the Scan menu, choose Delete CHKLIST Files.
3. Choose the Delete button.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96327
TITLE :Disconnected Network Drive Icon Becomes Floppy Disk Drive Icon
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system version 3.1
- Microsoft LAN Manager versions 2.1, 2.1a, and 2.2
--------------------------------------------------------------------
Summary:
Under certain circumstances, Windows File Manager may not disconnect
from a network drive correctly. After attempting to disconnect, the
network drive icon changes to a floppy disk drive icon. If you choose
the floppy icon, File Manager displays an error message stating that
no floppy disk in the drive. Until you reboot your computer, File
Manager maintains the dysfunctional floppy disk drive icon.
To work around this problem, do the following:
1. Change to your DoubleSpace host partition and use the ATTRIB
command to remove the hidden, system, and read-only attributes of
the DBLSPACE.INI file:
attrib dblspace.ini -h -s -r
2. Open DBLSPACE.INI in a text editor, such as MS-DOS Editor. You
should see two lines similar to the following (not necessarily in this
order):
LastDrive=M
ActivateDrive=H,C0
3. Change the ActivateDrive= statement's first parameter to the next
drive letter following your last physical drive letter. For example,
if you have two partitions (C and D) on one physical hard drive, set
ActivateDrive= to E.
Warning: If you use the incorrect drive letters when you edit the
ActivateDrive= line in the DBLSPACE.INI file, the system may stop
responding (hang) when you restart it.
4. Set LastDrive= to the same letter you used in step 3. As with the
previous example, if you have one physical drive and two
partitions, C and D, your DBLSPACE.INI file would include the
following lines:
LastDrive=E
ActivateDrive=E,C0
5. Save the changes you made to the DBLSPACE.INI file and use the
ATTRIB command to reset its attributes as follows:
attrib dblspace.ini +h +s +r
6. Restart your computer.
After you restart your computer, DoubleSpace uses the new drive letter
as its host partition. This results in no available drive letters
between your physical hard disk drive and the DoubleSpace host
partition to use for network redirections. You must use drive letters
following the host partition drive letter; this effectively avoids the
floppy disk drive icon problem.
Note: This procedure restricts the creation of additional DoubleSpace
compressed drives. If you later decide to create additional compressed
drives, you must change the LastDrive= statement in the DBLSPACE.INI
file to a higher letter than the one specified in ActivateDrive=. For
example, if your host drive is assigned to D, your DBLSPACE.INI file
should include the following lines:
LastDrive=E
ActivateDrive=D,C0
This gives DoubleSpace the necessary drive letter to use when it
creates another DoubleSpace compressed drive.
Steps to Reproduce Problem
--------------------------
1. Run DBLSPACE to determine the DoubleSpace host partition drive
letter.
2. Before you start Windows, use the LAN Manager command, NET USE, to
connect to a network drive, specifying a drive letter prior to the one
used by the DoubleSpace host partition.
3. Start Windows and run File Manager.
4. From the Disk menu, choose Disconnect Drive or Network Connections
(depending on your version of LAN Manager). Disconnect the network
drive you connected to in step 2.
After you close the network dialog box, the network drive icon changes
to a floppy disk drive icon. If you choose this icon, File Manager
notifies you that there is no disk in the floppy disk drive.
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here as it
becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96197
TITLE :Cannot See Dell Partitions After Upgrading to MS-DOS 6
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 5.0, 5.0a, and 6.0
--------------------------------------------------------------------
Summary:
If you install the MS-DOS 6 Upgrade on a machine running Dell DOS
version 3.3, you may be unable to access all your partitions after you
upgrade your computer.
If you have already installed the MS-DOS 6 Upgrade and you cannot see
all your partitions, restart your computer with the Uninstall disk in
drive A to uninstall MS-DOS 6.0.
Note: This information also applies to MS-DOS versions 5.0 and 5.0a.
More Information:
Workaround
----------
To work around this problem, back up your data, repartition your hard
disk drive, upgrade to MS-DOS 6, and then restore your data.
For specific instructions on repartitioning your hard disk drive
without losing data, download PD0466.EXE (for MS-DOS 5.O) or PD0771
(for MS-DOS 6.0) from the MSDL or CompuServe. These application notes
are titled as follows:
- PD0466: How Do I Repartition My Hard Disk into One Partition?
- PD0771: Repartitioning Your Hard Disk to Upgrade to MS-DOS 6.0
For more information, query on the following words in the
Microsoft Knowledge Base:
PD0466 or PD0771
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
product's performance or reliability.
Additional reference words: 3.30 5.00 5.00a 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96200
TITLE :DoubleSpace Cannot Mount Compressed Write-Protected Disk
Summary:
When you attempt to mount a DoubleSpace compressed floppy disk, you
receive the following error if the disk is write protected
DoubleSpace cannot mount drive x because the file x:\DBLSPACE.000
is not a valid compressed volume file.
where x is the floppy drive letter.
Workaround
----------
To work around this problem, remove the write protection for the
floppy disk.
More Information:
You can mount a floppy disk by running DoubleSpace or you can mount
the floppy disk with the MS-DOS DBLSPACE /MOUNT command. For example,
type the following command at the MS-DOS command prompt and press
ENTER if your floppy disk drive is drive A:
dblspace /mount a:
For more information on DoubleSpace, type "help dblspace" (without the
quotation marks) at the MS-DOS command prompt and press ENTER.
Additional reference words: 6.00 DoubleSpace dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96202
TITLE :Drive Letter Memory Use Is Listed Incorrectly in Help
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Under "Last drive reserved for Dblspace's use," MS-DOS DoubleSpace
Help incorrectly states the following:
Each drive letter uses 24K of memory: to conserve memory, decrease
this amount.
Actually, each drive letter uses 24 bytes of memory.
Additional reference words: 6.00 doc err docerr documentation error
-=-=-=-=-=-
ARTICLE-ID:Q96204
TITLE :You have a SCSI Hard Disk Drive and MemMaker Hangs
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you have an SCSI hard disk and MemMaker stops responding (hangs), a
device driver may be loading into upper memory before the SMARTDrive
double_buffer driver in the CONFIG.SYS file.
Workaround
----------
To work around this problem,
1. Restart your computer (if you haven't already done so).
2. When MemMaker prompts you for input, choose Cancel And Undo Changes.
3. Use MS-DOS Editor to add the following line to the beginning of
your CONFIG.SYS file:
device=c:\dos\smartdrv.exe /double_buffer
Note: If this line already appears in your CONFIG.SYS file, make
sure it is the first line.
4. Save your CONFIG.SYS file.
5. Try running MemMaker again.
If this does not correct the problem refer to Chapter 6 of the
"Microsoft MS-DOS 6 User's Guide" for information about
troubleshooting MemMaker.
For more information about SMARTDrive and the double_buffer driver, query
on the following words in the Microsoft Knowledge Base:
smartdrive and double_buffer
The SCSI hard drive is manufactured by a vendor independent of
Microsoft; we make no warranty, implied or otherwise, regarding this
product's performance or reliability.
Additional reference words: 6.0 load loading high umb uma devicehigh
-=-=-=-=-=-
ARTICLE-ID:Q96329
TITLE :How MemMaker Finds Current Files and Buffers Settings
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
To determine the current settings for the following four environment
variables set in the CONFIG.SYS file, MemMaker scans memory:
Buffers=
FCBS=
Files=
Lastdrive=
MemMaker searches memory instead of reading the CONFIG.SYS file
because a third-party memory manager may be loading these commands
into upper memory. This is necessary because MemMaker may not
recognize your third-party memory management loading scheme.
Additional reference words: 6.00 uma umb
-=-=-=-=-=-
ARTICLE-ID:Q95836
TITLE :BUSETUP Runs from Drive A Only
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Page 5 of the "Microsoft MS-DOS User's Guide" indicates that you can
use the BUSETUP /E command to install the optional utilities from
either drive A or drive B.
This information is incorrect, you can run BUSETUP only from drive A.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95857
TITLE :DoubleSpace Err Msg: DoubleSpace Cannot Convert Stacker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use DoubleSpace to convert a Stacker volume file (SVF) to a
DoubleSpace compressed volume, you receive the following error message
if the Stacker volume file has never been mounted:
Error: DoubleSpace cannot convert your Stacker drives because
they have a cluster size other than 8K. To convert your Stacker
drives to DoubleSpace format, follow the instructions in the
DoubleSpace section of the README.TXT file.
This error occurs regardless of the Stacker volume file cluster size
if the Stacker volume file has never been mounted. If the Stacker
volume file has been mounted and you receive this error message, you
need to convert your Stacker volume file to 8K clusters.
Workaround
----------
If your Stacker volume file has never been mounted, either mount the
Stacker volume file and then run DoubleSpace, or mount the Stacker
volume file, dismount the Stacker volume file, and then run
DoubleSpace.
Additional reference words: 6.0 unmount dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95858
TITLE :What Does BUSETUP.EXE Do?
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS 6 Upgrade
--------------------------------------------------------------------
Summary:
BUSETUP.EXE is the executable file for Bootable Upgrade Setup and is
located on Setup Disk 1 of MS-DOS 6 Upgrade.
Because Setup Disk 1 can be used to start your system and MS-DOS 6
Upgrade is licensed as an upgrade package only, BUSETUP.EXE is
designed to run only when your machine already has an operating system
installed.
When you start your computer from MS-DOS 6 Upgrade Setup Disk 1, the
AUTOEXEC.BAT file runs BUSETUP.EXE.
Additional reference words: 6.0 boot
-=-=-=-=-=-
ARTICLE-ID:Q95859
TITLE :Extra Tools Menu Added to Norton Desktop for Windows
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If Windows is installed on your computer when you run the MS-DOS 6
Upgrade Setup program, Setup installs a Tools menu in the File Manager
toolbar. If you use Norton Desktop for Windows, you have two Tools
menus after you install the MS-DOS 6 Upgrade.
This problem occurs because Norton Desktop for Windows has one Tools
menu and inherits a second one from File Manager by reading the
WINFILE.INI file.
More Information:
The two tools menus have different functions. The Tools menu in File
Manager and the Tools menu in Norton Desktop for Windows give you the
following options:
Command Description
---------------------------------
Backup Runs Microsoft Backup
Antivirus Runs Microsoft Anti-Virus
DoubleSpace Info Provides DoubleSpace statistics if you have
DoubleSpace installed
You can keep both Tools menus in Norton Desktop for Windows or you can
remove the second Tools menu by telling Norton Desktop for Windows to
ignore the add-ins section in the File Manager information file
(WINFILE.INI).
To configure Norton Desktop for Windows to ignore File Manager
add-ins, set MaxWinFileExtensions equal to zero in your NDW.INI file.
This disables all of the add-ins inherited from File Manager. For
example:
MaxWinFileExtensions=0
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95861
TITLE :RAMDRIVE.SYS Should Precede DBLSPACE.SYS in CONFIG.SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The RAMDRIVE.SYS line in the CONFIG.SYS file should precede the
DBLSPACE.SYS line or the RAMDrive will receive a different drive
designation from what it was before. This can become a problem if you
have many batch files referencing the RAMDrive. For example, if your
batch files reference drive D and it becomes drive I after DoubleSpace
is installed, your batch files will not work.
More Information:
The drives used for DoubleSpace are selected from the last available
drive rather than the first available drive. If RAMDRIVE.SYS precedes
the DBLSPACE.SYS line, then the RAMDrive's drive letter comes right
after the last physical drive. For example, if you have a drive C and a
floppy disk drive A, then the RAMDrive is assigned the letter D.
If the RAMDRIVE.SYS line comes after the DBLSPACE.SYS line,
DoubleSpace has already allocated all the drive letters between drive
C and its host drive (probably drive H) so the RAMDrive is assigned
letter I.
For information on how DoubleSpace assigns host drive letters, query
on the following words in the Microsoft Knowledge Base:
doublespace and assigns and host
For more information on RAMDrive, type "help ramdrive.sys" (without
the quotation marks) at the MS-DOS command prompt and press ENTER.
Additional reference words: 6.00 double space dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95959
TITLE :Intersvr Resets Screen Mode
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Intersvr resets the screen to 25-line mode and may not display
information on the lower part of the screen when you are loading
XANSI.SYS and using an Orchid ProDesigner IIs in 80-characters-per
line/60-lines-per-screen mode. There is no work around at this time.
This problem does not occur with ANSI.SYS and MODE.COM when they are
used with the video modes they support.
More Information:
For more information on MODE and video support, type the following at
the MS-DOS command prompt and press ENTER:
help mode (set display mode)
Intersvr is a component of the MS-DOS file transfer utility Interlnk.
For more information on Interlnk, type the following command at the
MS-DOS command prompt or see Chapter 7, "Features for Your Laptop
Computer," in the "MS-DOS 6 User's Guide":
help interlnk
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96330
TITLE :MS-DOS 6 Upgrade Does Not Update SHELL= in CONFIG.SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Unlike previous versions of Microsoft MS-DOS, when you install MS-DOS
6 Upgrade, the Shell command in the CONFIG.SYS file is not updated if
you are not using COMMAND.COM.
More Information:
If you are using a third-party shell with MS-DOS 6.0, you may have
problems with multiple-configuration menus, MemMaker, and the startup
function keys (F5 and F8).
To correct these problems, either use COMMAND.COM or contact your
third-party shell manufacturer for an updated version.
The default Shell command for MS-DOS 6 Upgrade is as follows:
shell=c:\dos\command.com c:\dos /p
If the current Shell is COMMAND.COM, Setup updates the path, keeps the
/E parameter (if there is one), and adds the /P parameter if it does
not already exist.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96331
TITLE :Stacker Err Msg: WARNING: Unrecognized Load High...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After you upgrade to MS-DOS 6.0, you may receive the following message
if you are using Stacker:
WARNING: Unrecognized load high method. Unable to verify driver fit
The driver does load successfully, but you must press a key to
continue.
More Information:
This message occurs if you use a DEVICEHIGH= command for the Stacker
device drivers in your CONFIG.SYS file. It does not occur if you use a
DEVICE= command.
Workaround
----------
To work around this problem, ensure the command for SETVER.EXE is
located above the Stacker device drivers in the CONFIG.SYS file. To do
this, SETVER.EXE must be located on the uncompressed Stacker
partition.
1. Copy SETVER.EXE to the uncompressed drive. For example, if your
compressed drive is C and the swap drive is D, copy SETVER.EXE to
drive D as follows:
copy c:\dos\setver.exe d:\
2. Put the following SETVER.EXE statement at the top of your
CONFIG.SYS file:
device=c:\setver.exe
3. Restart your computer.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96332
TITLE :F5 and F8 Keys Do Not Seem to Affect Startup Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
On some fast computers, the "Starting MS-DOS..." message may flash on
the screen too quickly to allow you to press the F5 or F8 function
key.
If you have problems getting your computer to respond to the F5 and F8
function keys, make sure the following line is not in your CONFIG.SYS
file:
switches=/f
More Information:
You can use a small multiple-configuration menu to determine if the F5
and F8 function keys are working properly. Adding the following five
lines to the top of your CONFIG.SYS file creates a startup menu that
gives you one menu item. You can then either press ENTER to start your
computer, press the F5 function key to bypass your configuration
files, or press the F8 function key to step through the CONFIG.SYS
file.
[COMMON]
[MENU]
MENUITEM=ONE,Your standard startup...
MENUDEFAULT=ONE,15
[ONE]
These statements give you 15 seconds before your CONFIG.SYS and
AUTOEXEC.BAT files are processed. They do not affect the contents of
your CONFIG.SYS file.
Type "help multi-config" (without the quotation marks) at the MS-DOS
command prompt to learn more about using multiple-configuration menus.
Type "help switches" (without the quotation marks) to learn more about
using the Switches command.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96333
TITLE :MS Backup Err Msg: File Is Not a Setup File...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You may receive the following error message when you start Microsoft
Backup for Windows on an NEC portable:
File is not a setup file C:\DOS\DEFAULT.SET
This error occurs because the NEC BIOS creates a DEFAULT.SET file in
the DOS directory when the battery starts running low.
Workaround
----------
To work around this problem, delete or rename the DEFAULT.SET file,
and then restart Microsoft Backup for Windows.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96334
TITLE :Windows for Workgroups or WC Hang on NETBIND Command
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows for Workgroups version 3.1
- Microsoft Workgroup Connections version 1.0
--------------------------------------------------------------------
Summary:
If the Windows for Workgroups or Workgroup Connections network drivers
are loaded at the top of unallocated conventional memory, your system
may stop responding (hang).
This problem can occur if you run a large program before the NETBIND
command.
Workaround
----------
To work around this problem, move the NET START command to the top of
your AUTOEXEC.BAT file.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96383
TITLE :Addstor SSUTIL Utility Reports MS-DOS 6.0 as Version 5.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Addstor compression information utility, SSUTIL, incorrectly
reports the following information about MS-DOS version 6.0:
VERSION is MS-DOS 5.0
REPORTED version is 6.0
More Information:
SSUTIL looks at the boot record signature to determine the version of
MS-DOS. It then calls the GetMSDOSVersion() function to determine the
reported version number.
Because the boot record signature is the same for MS-DOS 5.0 and
MS-DOS 6.0, SSUTIL incorrectly reports the version number.
Note: The incorrect version number detection does not cause any
problems or incompatibilities between MS-DOS 6.0 and Addstor.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96384
TITLE :DoubleSpace Err Msg: Unrecognized Error #109
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you receive the following error message when you attempt to mount a
compressed volume file (CVF), your CVF is probably too fragmented:
Unrecognized Error #109
To work around this problem, either increase the MaxFileFragments
setting in the DBLSPACE.INI file or defragment the CVF. These
procedures are outlined below.
More Information:
To work around this problem, do the following:
1. Edit the DBLSPACE.INI file and increase the MaxFileFragments
setting by using the following steps:
Warning: If you use the incorrect drive letters when you edit the
DBLSPACE.INI file, the system may stop responding (hang) when you
restart it.
a. Remove the Read-Only, System, and Hidden file attributes on the
DBLSPACE.INI file. For example, if drive H is your host drive,
type the following at the MS-DOS command prompt and press ENTER:
attrib h:\dblspace.ini -r -s -h
b. Using MS-DOS Editor, edit the DBLSPACE.INI file and increase the
value for MaxFileFragments.
c. Save the DBLSPACE.INI file and quit MS-DOS Editor.
d. Use the ATTRIB command to reset the file attributes on
DBLSPACE.INI. For example, if your host drive is drive H, type the
following command and press ENTER:
attrib h:\dblspace.ini +r +s +h
2. Restart your computer and try to mount the drive again. If you
still cannot mount the CVF, proceed to step 3.
3. Clear the file attributes from the DoubleSpace CVF and defragment the
drive using the procedure below.
Warning: If the DoubleSpace CVF is mounted when you perform this
procedure, you will corrupt your DoubleSpace drive.
a. Unmount your DoubleSpace drive or start your computer from an
MS-DOS 6 system disk in drive A that does not have a DBLSPACE.BIN
file.
b. Remove the Read-Only, System, and Hidden file attributes on the
DBLSPACE.XXX file. For example, if file is H:\DBLSPACE.000, type
the following at the MS-DOS command prompt and press ENTER:
attrib h:\dblspace.000 -r -s -h
c. Run MS-DOS Defragmenter by typing DEFRAG at the MS-DOS command
prompt and pressing ENTER.
d. Use the ATTRIB command to reset the file attribute on
DBLSPACE.XXX. For example, if file is H:\DBLSPACE.000, type
the following at the MS-DOS command prompt and press ENTER:
attrib h:\dblspace.000 +r +s +h
e. You should now be able to mount the CVF if you unmounted it. If
you restarted your computer from drive A in step a, restart your
computer from the C drive.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96385
TITLE :CTRL+BREAK Hangs System If Running CHKDSK with BREAK=ON Line
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DoubleSpace installed and you press the CTRL+BREAK key combination
when CHKDSK is calling DBLSPACE /CHKDSK, your system may stop
responding (hang). This problem occurs only if you have the BREAK=ON
command in your CONFIG.SYS file.
To work around this problem, either let CHKDSK run DBLSPACE /CHKDSK or
remove the BREAK=ON command from your CONFIG.SYS file.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94331
TITLE :Disk Error Messages with ASPI2DOS.SYS Device Driver
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
ASPI2DOS.SYS is an Adaptec driver used for external SCSI devices such
as the Adaptec 1522 SCSI controller. If SMARTDrive is used to cache a
drive when ASPI2DOS.SYS is installed, you receive the following error
message from the Adaptec controller:
A serious disk error has occurred while writing to drive C.
When you run Microsoft Anti-Virus (MSAV.EXE), you receive the
following error message:
Not ready reading (or writing) drive C:
Note: The double-buffer driver does not prevent these errors.
Workaround
-----------
To work around the problem:
- Remove ASPI2DOS.SYS from the CONFIG.SYS file.
-or-
- Remove SMARTDRV.EXE from the AUTOEXEC.BAT file.
More Information:
This problem usually occurs during frequent alternating reads and
writes by programs such as Microsoft Anti-Virus and SMARTDrive.
Since the controller does not use direct memory access (DMA), loading
the double-buffer driver does not help.
Additional reference words: 6.00 uma double_buffer
-=-=-=-=-=-
ARTICLE-ID:Q96386
TITLE :Cannot Lower Estimated Compression Ratio with DoubleSpace
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DoubleSpace does not allow you to lower the estimated compression
ratio (ECR), you may have lost allocation units at the end of the disk
drive.
To work around this problem, run CHKDSK /F at the MS-DOS command
prompt to recover the lost allocation units.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96387
TITLE :Virus-Protection Program Reports CONFIG.SYS Is Infected
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After you install DoubleSpace or create a new DoubleSpace drive, your
virus-detection software may indicate that the CONFIG.SYS file now
contains a virus. This occurs because DoubleSpace updates the date and
time on the CONFIG.SYS file even if it does not change the file.
Additional reference words: 6.00 infected
-=-=-=-=-=-
ARTICLE-ID:Q96388
TITLE :Uninstalling MS-DOS 6 on an XtraDrive Compressed Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you install MS-DOS 6 Upgrade on a machine that is using XtraDrive
data-compression software, you cannot uninstall MS-DOS without
modifying the Uninstall disk.
More Information:
To successfully uninstall MS-DOS 6 Upgrade:
1. Copy XTRADRV.SYS to the Uninstall disk.
2. Using MS-DOS Editor, create a CONFIG.SYS file on the Uninstall disk
with the following line:
device=a:\xtradrv.sys
3. Restart the computer with the Uninstall disk in drive A. (Press the
CTRL+ALT+DEL key combination.)
Additional reference words: 6.00 xtra extra drive
-=-=-=-=-=-
ARTICLE-ID:Q96389
TITLE :MS-DOS Files to Delete from 8088, 8086, and 80286 Machines
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following MS-DOS files can only be used on computers with 80386 or
higher processors. If you have an 8088, 8086, or 80286 computer, you
can delete the files below.
Delete the following from the root directory:
Filename Description
---------------------------------
WINA20.386 Used for Windows 3.0 enhanced mode
Delete the following from the DOS directory:
Filename Description
---------------------------------
CHKSTATE.SYS MemMaker file
EMM386.EXE Expanded memory manager
MEMMAKER.EXE MemMaker file
MEMMAKER.HLP MemMaker file
MEMMAKER.INF MemMaker file
MONOUMB.386 Windows virtual device driver
SIZER.EXE MemMaker file
VFINTD.386 Virtual device driver for virtual floppy
support with Microsoft Backup for Windows
Additional reference words: 6.00 286 386 486 80486
-=-=-=-=-=-
ARTICLE-ID:Q96390
TITLE :Using DoubleSpace with Compressed Floppy and Removable Disks
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
DoubleSpace supports disk compression on both floppy disks and
removable media disks; however, when you swap a floppy or removable
media disk you must remount the disk.
To mount a disk from the MS-DOS command prompt, type the following:
dblspace /mount drive
where "drive" is the drive location of the disk.
Automation of this feature is under review and will be considered for
inclusion in a future release.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96391
TITLE :DoubleSpace Estimated & Actual Compression Ratios
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
This article discusses common questions and issues with DoubleSpace
actual compression ratio (ACR) and estimated compression ratio (ECR).
The following three subjects are covered:
- Actual Compression Ratio
- Estimated Compression Ratio
- Viewing and Changing the Compression Ratio
More Information:
Actual Compression Ratio
------------------------
The actual compression ratio (ACR) represents the compression ratio
for data that already exists on a drive. The ACR varies over time
depending on the type of files you store on you hard disk.
The ACR is calculated by dividing the sum of the uncompressed data
size by the physical space consumed after the data is compressed. For
example, if a disk with 100 megabytes (MB) of uncompressed data is
compressed and occupies 50 MB of disk space, the compression ratio is
2:1. The formula is as follows:
100MB/50MB =2.0
Note: 2.0 is written as 2.0:1 (that is, 2 to 1)
Estimated Compression Ratio
---------------------------
The estimated compression ratio is a number that DoubleSpace uses to
calculate the amount of free space on a compressed drive. Changing the
ECR doesn't change the compression algorithm or the ACR. It simply
changes the value that DoubleSpace uses to estimate the free disk
space.
You may need to increase the compression ratio if you are trying to
store several new highly compressible files and you are low on disk
space.
For more information on ECR:
- Run DoubleSpace, choose Change Ratio from the Drive menu, and then
press the F1 function key.
-or-
- Type "help dblspace /ratio" (without the quotation marks) at the
MS-DOS command prompt.
Viewing and Changing the Compression Ratio
------------------------------------------
To view the ACR and ECR for a drive, type "dblspace" (without the
quotation marks) at the MS-DOS command prompt, select the drive you
are interested in, and then press the ENTER key.
To view the ACR for a file or directory, use the DIR /C or DIR /CH
command. For example, to see the ACR for COMMAND.COM, type the
following at the MS-DOS command prompt:
dir c:\command.com /ch
To view the ACR for the DOS directory, type the following at the
MS-DOS command prompt:
dir \dos /ch
Note: DIR /C reports the ACR of the compressed data based on an
8-kilobyte (K) cluster size. DIR /CH reports the ACR based on the
compressed data based on the host drive cluster size. Use this number
when you compare the ACR and ECR.
To set the ECR to the ACR value, type "dblspace /ratio" (without the
quotation marks) at the MS-DOS command prompt.
To set the ECR to a specific value, type the following at the MS-DOS
command prompt:
dblspace /ratio=n.n
where "n.n" is the ECR value.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96392
TITLE :Error in MS-DOS Help Example for the MENUCOLOR Command
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using an MS-DOS 6.0 multiple-configuration menu and you set
the MENUCOLOR command in the CONFIG.SYS file to match the example
shown in MS-DOS Help, the menu color does not display.
More Information:
The example in MS-DOS Help shows a space after the comma, which causes
MS-DOS to stop reading the MENUCOLOR command when the CONFIG.SYS file
is processed. As a result, the menu color is not displayed.
To work around this problem remove the space after the comma.
Additional reference words: 6.00 multi-config doc err docerr
-=-=-=-=-=-
ARTICLE-ID:Q96440
TITLE :DoubleSpace Doesn't Mount After Installing RAMDrive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use DoubleSpace with a removable hard drive (such as Syquest,
Bernoulli, or Quatam Passport XL) and later install RAMDrive,
DoubleSpace may refuse to mount its compressed drive(s). This problem
only occurs if the RAMDrive DEVICE command in the CONFIG.SYS file
precedes the removable hard drive DEVICE command line. Since RAMDrive
may inadvertently use the drive letter of the removable drive,
DoubleSpace may not find the compressed volume on the expected drive.
The same behavior may occur if you remove RAMDrive after compressing
your removable hard drive. (The drive letters shift and DoubleSpace
does not mount.)
If this problem was caused by installing RAMDrive, you can simply move
the RAMDrive DEVICE command past the removable drive's DEVICE command
in the CONFIG.SYS file. The advantage of this workaround is that the
drive letter assignments stay the same.
If this problem occurs after removing RAMDrive, run DBLSPACE. From the
Drive menu, choose Mount. DoubleSpace scans all your drives for
compressed volumes and reassigns drive letters appropriately. This
workaround may cause problems for programs configured to specific
drive letters.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96447
TITLE :Manifest Shows EMS Memory with NOEMS Switch
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Quarterdeck's Manifest program indicates that EMS memory exists, even
if EMM386.EXE is loaded with the NOEMS switch. If you add the NOVCPI
switch to the EMM386.EXE line in the CONFIG.SYS file, Manifest no
longer shows any EMS memory.
More Information:
EMM386.EXE version 4.45, which ships with MS-DOS 6.0 is a Virtual
Control Program Interface (VCPI) provider even when the NOEMS switch
is specified. With VCPI support enabled, EMM386.EXE supplies an upper
memory frame buffer for the VCPI applications to use. When an
application checks for EMS memory, it may see this buffer and believe
it to be an EMS page frame, thus reporting that EMS memory is
available when it is not. When the NOVCPI switch is added, it disables
this upper memory buffer, thus disabling what the application is
seeing as EMS.
Maintaining VCPI server functionality with the NOEMS switch specified
is a new feature in MS-DOS 6.0.
It should be noted that VCPI support can exist without a page frame.
For example, EMM386 in MS-DOS 5.0 (version 4.44) provided VCPI support
by using the "frame=0" switch. In MS-DOS 6.0 we can now achieve the
same result using both the NOEMS switch and the NOVCPI switch
together.
Manifest is manufactured by Quarterdeck Office Systems, a vendor
independent of Microsoft; we make no warranty, implied or otherwise,
regarding this product's performance or reliability.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94332
TITLE :System Restarts When DoubleSpace Commands Are Issued
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DBLSPACE /RATIO or other DoubleSpace commands cause the system to
restart, load DBLSPACE.SYS before your network drivers in the
CONFIG.SYS file.
More Information:
Setup installs DBLSPACE.SYS before any network drivers, so this
problem should not occur unless you have moved the DBLSPACE.SYS driver
in the CONFIG.SYS file.
Additional reference words: 6.0 Autoreboot reboot warmboot coldboot
cold warm boot re-boot re-start
-=-=-=-=-=-
ARTICLE-ID:Q96496
TITLE :Err Msg: SYS Is Unable to Operate on Target Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you try to run SYS.COM on a drive that has been compressed with the
DoubleSpace, you may receive the following error message:
SYS is unable to operate on target drive
To work around this problem, you must manually unmount the compressed
drive before you run the SYS command to make drive C a bootable drive.
More Information:
This error usually occurs when an attempt is made to run SYS.COM on a
hard disk drive that has been compressed with DoubleSpace and has
failed because of corrupted MS-DOS files. DoubleSpace performs "drive
swapping," giving the physical drive a drive letter other than C
(typically the fifth letter after the system's last block device) and
designating the compressed volume file as drive C. Even if you boot
from a floppy disk, it is possible that DoubleSpace will mount the
compressed drive and perform the drive swap. Because we cannot run
SYS.COM on a DBLSPACE drive, SYS.COM generates the error message.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96514
TITLE :Difference Between the DIR /C and DIR /CH Commands
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The DIR command has two switches that you can use to display
compression ratio information, /C and /CH. /C displays the compression
ratio of a file assuming that it resides on a drive using 8-kilobyte
(K) clusters. /CH uses the cluster size of the host partition. In most
cases, there is no difference between the output of these switches
unless your DoubleSpace host partition uses a cluster size other than
8 kilobytes. For example, if you have a file on a drive using 4K
clusters, the compression ratio displayed generated from DIR /C would
be 1.5; DIR /CH would generate a compression ratio of 2.0.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96516
TITLE :Changes to MSCDEX.EXE for MS-DOS 6.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft CD-ROM Extensions (MSCDEX.EXE) version 2.22 for MS-DOS is
included in MS-DOS 6 Upgrade and MS-DOS 6.0 plus Enhanced Tools.
MSCDEX.EXE version 2.22 includes code to recognize MS-DOS 6.0 and make
it easier to load MSCDEX.EXE into upper memory blocks (UMBs).
(MSCDEX.EXE 2.22 has a smaller initialization size than earlier
versions, making it easier to fit in smaller UMBs.)
MSCDEX.EXE is included with MS-DOS 6.0 so that you do not need to
obtain additional software to continue using your CD-ROM drive after
you upgrade to MS-DOS 6.0.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96517
TITLE :Using DoubleSpace to Compress a Bootable HardCard
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You should not use DoubleSpace to compress your boot drive if that
drive requires a device driver in the CONFIG.SYS file. Because the
DoubleSpace driver (DBLSPACE.BIN) is loaded with IO.SYS before the
CONFIG.SYS file is processed, Microsoft does not support this
configuration. If you want to use DoubleSpace on such a drive, you
must mount the drive after loading the device drivers in the
CONFIG.SYS file.
For example, if drive C is a Plus Hardcard and you compress that
drive, DoubleSpace cannot automatically mount the drive. You can
either mount the drive from the MS-DOS command prompt or from the
AUTEOXEC.BAT file.
Note: DoubleSpace does not support compression of removable hard disk
drives that require a device driver to write to the drive. This is
because DoubleSpace must mount the drive before the CONFIG.SYS file is
processed, and the mounting process rewrites the BitFAT structure in
the compressed volume file (CVF).
More Information:
You can manually mount the DoubleSpace drive from the command line by
using the DBLSPACE /MO command. If you want to mount the compressed
drive from the AUTOEXEC.BAT file, you must copy the CONFIG.SYS and
AUTOEXEC.BAT files to the host drive, copy the device drivers called
from those files, and then add a line to the AUTOEXEC.BAT file to
mount the compressed drive. To do this, follow the procedure outlined
below.
Note: This procedure does not work if your drive does not meet the
following conditions:
- It is bootable (that is, accessed by the BIOS during the startup
process).
- It is a system disk. (If it is not, use the SYS command to transfer
the MS-DOS system files.)
To automatically mount the compressed drive:
1. Compress the boot drive with DoubleSpace. For example, to compress
drive C, type the following at the MS-DOS command prompt:
DBLSPACE /COMPRESS C:
2. Ensure the following files are in the root directory of the host
drive (the drive containing the compressed volume file [CVF]):
IO.SYS
MSDOS.SYS
COMMAND.COM
DBLSPACE.BIN
DBLSPACE.000
To determine which drive is the host drive, type "DBLSPACE /LIST"
(without the quotation marks) at the MS-DOS command prompt.
Since the files listed above have read-only, hidden, and system
file attributes set, use the /A parameter to see the files. To do
this, type DIR /A at the MS-DOS command prompt.
3. Copy the following three files to the root of the host drive:
DBLSPACE.EXE, CONFIG.SYS, and AUTOEXEC.BAT.
For example, if H is your host drive, you would use the following
three commands to copy these files:
copy c:\dos\dblspace.exe h:\
copy c:\config.sys h:\
copy c:\autoexec.bat h:\
4. Copy any files called from the CONFIG.SYS file to the host drive.
For example, if the command DEVICE=C:\DOS\HIMEM.SYS is in your
CONFIG.SYS file, copy HIMEM.SYS to the host drive with the
following command:
copy c:\dos\himem.sys h:\
5. Edit the CONFIG.SYS file on the host drive to reflect the new
location of the device drivers. Given the above HIMEM.SYS example,
change the CONFIG.SYS file on the host drive (H) to read as follows:
device=c:\himem.sys
6. Add the following line to the AUTOEXEC.BAT file on the host drive:
DBLSPACE /MO
7. Any other programs or executable files called from the AUTOEXEC.BAT
file should be located on the host drive. If they are not, you need
to edit the AUTEXEC.BAT file to reference the correct drive letter.
The host and boot drive letters swap when the DBLSPACE /MO line is
run from the AUTEOXEC.BAT file.
Additional reference words: 6.00 double space
-=-=-=-=-=-
ARTICLE-ID:Q96518
TITLE :Differences Between DOSSHELL.INI in MS-DOS Versions 5 and 6
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
This article discusses the differences between the DOSSHELL.INI file
in MS-DOS versions 5.0 and 6.0.
More Information:
The DOSSHELL.INI file in MS-DOS 6.0 does not contain references to the
MS-DOS 5.0 BACKUP and RESTORE commands.
Since Setup doesn't update a existing DOSSHELL.INI file, the existing
references to Backup Fixed Disk and Restore Fixed Disk are not
updated. BACKUP.EXE is copied to the OLD_DOS directory so that the
Backup Fixed Disk option no longer works. You can either copy the
MS-DOS 5.0 BACKUP command (BACKUP.COM) to the DOS directory or modify
the Backup Fixed Disk properties to reference the new backup program,
Microsoft Backup (MSBACKUP.EXE).
If you don't have an existing DOSSHELL.INI file, Setup creates a new
one with the following default items:
Main Menu
---------
Command Prompt
Editor
MS-DOS QBasic
Disk Utilities Menu
-------------------
MS Anti-Virus
MS Backup
Quick Format
Format
Undelete
Setup leaves the RESTORE command (RESTORE.EXE) from MS-DOS 5.0 in the
DOS directory even though it does not appear as an item in MS-DOS 6
Shell. The BACKUP command (BACKUP.EXE) from MS-DOS 5.0 is available on
the supplemental disk or in the OLD_DOS directory as described above.
To replace your existing DOSSHELL.INI file, you can expand the
appropriate .IN_ file from the original MS-DOS 6 Upgrade disks. For
example, if you have an EGA or VGA video display card, expand EGA.IN_
from the MS-DOS 6 Upgrade disks (Disk 2 of the 1.2-megabyte (MB) set
or Disk 1 of the 1.44-MB set). For example, if you insert the Setup
disk in drive A, you would type the following command:
expand a:ega.in_ c:\dos\ega.ini
If the new utilities made available by the MS-DOS 6.0 DOSSHELL.INI
file are not installed, you must install them using the SETUP command
with the /E parameter.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96519
TITLE :Situations in Which Defragmenter Cannot Run
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft Defragmenter operates on the MS-DOS logical drive level
only. Third-party partitioning utilities that modify or translate disk
geometry (such as Disk Manager and SpeedStor) operate beneath the
MS-DOS file system and are therefore transparent to Defragmenter.
Defragmenter cannot share access to a drive with other tasks;
therefore, you cannot run Defragmenter if Windows or DESQview is
running.
More Information:
Defragmenter does not work in the following situations:
Situation Reason
---------- ------
Network Drive Network software usually does not allow full
single-tasking access to the entire drive,
including the file tables. Often network drives
(such as Novell NetWare) use another file system.
CHKDSK Errors Errors in the drive organization can cause
unpredictable results from Defragmenter.
Defragmenter identifies most CHKDSK errors while
reading the drive organization and then refuses
to run until you correct them.
Windows Defragmenter cannot operate properly in a
multitasking or task-switching situation;
therefore, it detects Windows in real, standard,
and 386 enhanced modes and does not run.
Task Swapper Defragmenter cannot operate properly in a
task-switching situation; therefore, it detects
the MS-DOS Shell task swapper and does not run.
Interlnk Drives Interlnk is not designed to support defragmentation
and other low-level utilities. Specifically, it does
not implement interrupts 25 and 26.
Fastopen The Fastopen program tracks which files are located
in which clusters on your disk. Defragmenter
rearranges data on a cluster level, which confuses
Fastopen.
JOIN JOIN does not allow normal access to a drive.
SUBST SUBST drives do not have their own file tables or
directories to optimize.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.00 3rd party defrag
-=-=-=-=-=-
ARTICLE-ID:Q96520
TITLE :Windows Hangs at Logo Screen with FTP Network and DoubleSpace
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are running FTP Software's PC/TCP network software and
Microsoft Windows in 386 enhanced mode, your SYSTEM.INI file may
contain the line DEVICE=C:\PCTCP\VPCTCP.386 in the [386Enh] section.
If it does, Windows may stop responding (hang) at the logo screen
after you have compressed a drive with DoubleSpace.
More Information:
The system hangs if the line DEVICE=C:\DOS\DBLSPACE.SYS /MOVE is not
present in your CONFIG.SYS file before any of the drivers that load
the network. To correct this problem, add or move the line
C:\DOS\DBLSPACE.SYS /MOVE before the first line that loads the network
software. In most cases, the first line that starts the network is
something similar to C:\PCTCP\PROTMAN.SYS /i:C:\PCTCP.
Additional reference words: 2.04 2.1 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96522
TITLE :Regions Scanned by the EMM386.EXE HIGHSCAN Switch
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The HIGHSCAN switch included in EMM386.EXE version 4.45 allows
EMM386.EXE to map expanded memory pages or upper memory blocks (UMBs)
over portions of the upper memory area (UMA) used by system read-only
memory (ROM).
Choosing "Yes" in response to the MemMaker prompt "Scan the upper
memory area aggressively?" causes MemMaker to add HIGHSCAN to the
EMM386.EXE device= line.
More Information:
If you use the HIGHSCAN switch on the DEVICE=C:\DOS\EMM386.EXE line in
the CONFIG.SYS file, EMM386.EXE examines the system ROM area starting
at memory location F000:0000. If EMM386.EXE determines that ROM is
duplicated between F000h-F7FFh and F800h-FFFFh, EMM386.EXE uses the
F000h-F7FFh region for expanded memory page mapping or UMB memory.
(This adds up to 32 kilobytes to the UMA.
On Micro Channel (MCA) systems with ROM BASIC (for example, IBM PS/2
systems), the HIGHSCAN switch allows EMM386.EXE to map expanded memory
or UMB memory over the ROM BASIC code in the system ROM. Typically
this is the region from F600 to FDFF.
Note: On some systems, EMM386.EXE uses the ROM area and the system
does not operate correctly. The symptoms of this condition vary. For
example, the system may stop responding (hang) or appear to operate
normally until you use a floppy disk drive. Because of these potential
problems, HIGHSCAN is not used by default.
Additional reference words: 6.00 parameter
-=-=-=-=-=-
ARTICLE-ID:Q96541
TITLE :Setup Leaves Windows .INI Files in Root of the Novell Server
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you run MS-DOS 6 Setup when you are logged onto a Novell server,
Setup may leave MS-DOS initialization (.INI) files in the root
directory. This problem occurs when all the following conditions are
exist:
- You are logged on as a supervisor or a user with full access
privileges to the root of the file server.
- You are using a shared installation of Windows (installed with the
SETUP /N command).
- Your Windows initialization files are in a user directory that is
being accessed with a search drive.
- You have installed the Windows-based optional utilities.
If these conditions exist, MS-DOS 6 Setup leaves your initialization
files in the root of the Novell file server.
The following initialization files are left in the root of the Novell
server:
PROTMAN.INI
SYSTEM.INI
WINFILE.INI
Setup also leaves the backup (.BAK) files for those files in the root
of the Novell file server.
Workaround
----------
Use one of the following techniques to correct this situation:
- If this is the only installation of MS-DOS 6 you plan to perform
when you are logged in as supervisor, you can simply move these
six files back to the user directory.
- If you plan to do multiple installations of MS-DOS 6 when you are
logged in as supervisor, temporarily override the search drive before
beginning the MS-DOS 6 Setup on each subsequent computer. For example,
if your Windows initialization files are accessed on Search drive
W:\USER\JOEB. Before beginning the MS-DOS 6 Setup type these two
commands at the MS-DOS command prompt:
map del w:
map w:=sys:user\joeb
When MS-DOS 6 Setup prompts you for the location of Windows directory,
use W:\USER\JOEB for the path.
Note: If desired, you may substitute the second command above with the
following:
map root w:=sys:user\joeb
When MS-DOS 6 Setup prompts you for the location of Windows, use W:\
for the path.
More Information:
Do not use a search drive to specify the location of your Windows
initialization files. A search drive represents its drive letter as
":." instead of ":\." MS-DOS 6 looks at
":.", changes to the root of the drive, and then looks for the
current (.) directory. This is why MS-DOS 6 writes the files to the
root of the server.
If you are logged on as a user without write access privileges to the
root of the file server (as is generally the case with a user on a
Novell network), the same approach as described in the second
technique applies. If you don't have privileges in the root directory,
the temporary initialization files (.$$$) are written to your user
directory. No changes are been made to your original initialization
files. You can safely delete these .$$$ files. Use the second
technique and then restart the MS-DOS 6 Setup program.
The following three .$$$ files may be left in your user directory:
__SYS__.$$$
__PGI__.$$$
__WFI__.$$$
If Setup detects that it did not need to modify one or more of the
initialization files, you may not have all three of these in your user
directory.
Note: This information applies to both the SETUP and SETUP /E
commands. (SETUP /E is used to install the optional components.)
Additional reference words: netware net ware 286 386 2.15 2.2 3.10
3.11 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96552
TITLE :What Defragmentor Does & How It Works with 3rd-Party Utilities
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft Defragmenter reorganizes data on MS-DOS drives so that it
can be retrieved faster.
MS-DOS organizes data on the hard disk into a series of clusters
(allocation units) and then tracks which files are using which
clusters through directory structures and the file allocation tables
(FATs). Neither users nor applications need to know exactly where
specific data is located on the hard disk. When an application needs a
file, it simply asks MS-DOS to get it.
Over time, pieces of files may be spread all over the hard disk. When
this occurs, retrieving files requires more time. Defragmenter
reorganizes the clusters for faster access. (For example, information
is stored at the front of the disk, and parts of files are regrouped
together). Defragmenter uses interrupt calls 25H and 26H to move the
information stored in one cluster to another, directly updating the
FATs and directory structures.
Defragmenter operates at nearly the same level as MS-DOS. However, it
is still uses MS-DOS and is protected from direct interactions with
the following:
- Third-party partitioning utilities that modify or translate disk
geometry (such as Disk Manager and SpeedStor).
- DoubleSpace and third-party drive compression utilities.
Additional reference words: 6.00 3rd-party
-=-=-=-=-=-
ARTICLE-ID:Q94333
TITLE :SETVER Table Entries Are Not Maintained When Upgrading
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you do not install the MS-DOS 6 Upgrade in the current MS-DOS 5.0
directory, your old SETVER entries are not maintained.
More Information:
When you install the MS-DOS 6 Upgrade over MS-DOS 5.0, Setup updates
the current version table (maintained in SETVER.EXE). If you install
MS-DOS 6 in a new directory, Setup cannot update the old version table.
Workaround
----------
To work around this problem:
- Update the new SETVER.EXE file, adding the entries that your
software requires.
-or-
- Uninstall MS-DOS 6.0 and reinstall the MS-DOS 6 Upgrade in the
original MS-DOS directory.
Additional reference words: 6.00 5.00
-=-=-=-=-=-
ARTICLE-ID:Q94334
TITLE :Using MS-DOS 6 Upgrade Fdisk Program with EXTDISK.SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If were using COMPAQ MS-DOS version 4.0 or later before you upgraded
to MS-DOS 6.0, and you are using EXTDISK.SYS, you should use the
COMPAQ version of the Fdisk program. If you were using COMPAQ MS-DOS
version 3.31 or earlier before you upgraded to MS-DOS 6.0, and you are
using EXTDISK.SYS, you should contact Compaq for an updated version of
EXTDISK.SYS.
More Information:
Some COMPAQ systems use a driver called EXTDISK.SYS to access
secondary disk drives. This driver is MS-DOS version dependent. If you
use the MS-DOS version of Fdisk when EXTDISK.SYS is loaded, Fdisk
displays incorrect drive letters for the hard disks attached to the
second controller.
Workaround
----------
You can work around this problem by using the COMPAQ version of Fdisk.
To install the old version of Fdisk:
1. Delete FDISK.EXE from the DOS directory.
2. Copy FDISK.* from your COMPAQ MS-DOS disks to your DOS directory.
For example:
copy a:\fdisk.* c:\dos
3. Add Fdisk to the SETVER.EXE version table for your version of
COMPAQ MS-DOS. For example:
setver fdisk.exe 4.0
4. Restart your computer.
Note: You must use SETVER to tell EXTDISK.SYS that you are using a
previous version of MS-DOS. For more information, query on the
following words in the Microsoft Knowledge Base:
MS-DOS and SETVER and EXTDISK.SYS
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94335
TITLE :DoubleSpace Installation Fails to Update SYSTEM.INI File
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
-----------------------------------------------------------------------
Summary:
If you have multiple installations of Windows on your hard drive,
DoubleSpace may not correctly update the SYSTEM.INI file.
More Information:
Windows stores the location of the permanent swapfile in the [386enh]
section of the SYSTEM.INI file. When you install DoubleSpace, it must
find the SYSTEM.INI file and update the PermSwapDosDrive= setting to
point to the correct drive. If you have multiple copies of Windows
installed, or Windows is not in the path, DoubleSpace cannot find the
SYSTEM.INI file.
Workaround
----------
To workaround this problem, edit the SYSTEM.INI file and change the
drive letter for the PermSwapDosDrive= setting to the DoubleSpace host
drive. For example, if Windows is installed on drive C: and you
installed DoubleSpace, creating drive H:, you would need to edit you
SYSTEM.INI file and change the PermSwapDosDrive=c to
PermSwapDosDrive=h.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q94336
TITLE :How DoubleSpace Assigns the Host Drive Letter
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you install Microsoft DoubleSpace, the installation program
normally leaves four unassigned drive letters between the last drive
and the host drive. For example, if you have two drives (C and D), a
RAM drive (E) and a network connection (F), DoubleSpace skips G, H, I,
and J, and uses drive K for the host drive.
If DoubleSpace detects Novell NetWare in memory, the host drive is
assigned one letter less than the LASTDRIVE= command in the CONFIG.SYS
file. If that drive letter is not available, then the host drive is
assigned the next available drive letter.
If you install DoubleSpace when device drivers that use drive letters
are not loaded (CD-ROM drivers or RAMDrives) or your network software
is not loaded, you may need to change the host drive letter. To do
this:
1. Change to the host drive (for example H).
2. Use the ATTRIB command to change the file attribute on the
DBLSPACE.INI file. For example:
attrib h:\dblspace.ini -s -h -r
3. Edit the DBLSPACE.INI file with a text editor such as MS-DOS
Editor.
4. Change the "LastDrive=" setting to the letter you want to be the
host drive.
5. Change the first parameter in the "ActivateDrive=" line to the same
letter you used in step 4.
Warning: Do not change the second parameter (represented by "xx") in
the following example:
Before change: ActiveDrive=H,xx
After change: ActiveDrive=D,xx
Warning: If you use the incorrect drive letters when you edit the
ActivateDrive= line in the DBLSPACE.INI file, the system may stop
responding (hang) when you restart it.
6. Save your changes and exit the text editor.
7. Reset the System, Hidden, and Read-Only attributes on the
DBLSPACE.INI file. For example:
attrib h:\dblspace.ini +s +h +r
8. Restart your computer (press CTRL+ALT+DEL).
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96555
TITLE :INTERLNK.EXE Doesn't Work with Xircom PPX and Pocket Adapter
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Interlnk does not work properly with the Xircom Parallel Port
Multiplexor (PPX) unless it is on the logical port assigned the
hardware interrupt. Since only one of the two logical ports can be
assigned the hardware interrupt and the Xircom Pocket Adapter must be
on the port assigned the hardware interrupt, you cannot use both
INTERLNK.EXE and the Xircom Pocket Adapter at the same time.
More Information:
By setting up a MS-DOS 6 multiple-configuration menu, you can start
your computer with the appropriate configuration for either the Xircom
Pocket Adapter or Interlnk.
Note: This information also applies to Intersvr, which also requires
the hardware interrupt.
Additional reference words: 6.00 multi-config multiconfig
-=-=-=-=-=-
ARTICLE-ID:Q94356
TITLE :CMOS Access Causes Dell 486D/50 to Hang with EMM386.EXE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use the EMM386.EXE HIGHSCAN switch, Dell 486D/50 machines may
stop responding ("hang") when you attempt to access the CMOS (by
pressing CTRL+ALT+ENTER).
Workaround
----------
To access your CMOS settings on a Dell 486D/50, restart (reboot) the
computer and press the F5 key or press and hold down the SHIFT key to
bypass all commands in your CONFIG.SYS and AUTOEXEC.BAT files. You can
then access your CMOS settings by pressing CTRL+ALT+ENTER. When you
have finished modifying your CMOS settings, restart the computer.
More Information:
The HIGHSCAN switch causes EMM386.EXE to scan the F000-F7FF upper
memory range. On Dell 486D/50 machines, EMM386.EXE detects that this
range is available. You should not have problems using this range on
the Dell 486D/50 except when you attempt to access the CMOS.
Additional reference words: 6.0 6 6.00 DX2 processor freeze lock up
-=-=-=-=-=-
ARTICLE-ID:Q96556
TITLE :MS-DOS: How to Return to Main Menu from Multi-Config Submenu
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are in a multiple-configuration submenu, you can return to the
main menu by pressing the BACKSPACE key.
Additional reference words: 6.0- multi-config multiconfig back space
menus startup start up submenu sub-menu
-=-=-=-=-=-
ARTICLE-ID:Q96557
TITLE :MS-DOS: Boot-Sector Viruses on Compressed Drives
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Boot-sector viruses are activated when you start your computer from
the infected drive (usually drive C) and alter MS-DOS startup code
located in the boot sector of your hard disk. DoubleSpace drives do
not actually have MS-DOS startup code to corrupt; however, if a virus
is detected on a compressed drive, it is likely that the host drive is
also infected.
You can detect and clean viruses from all local drives by using the
following command:
msav /c /l
More Information:
Removing Viruses from Boot Sectors of Compressed Drives
-------------------------------------------------------
In addition to startup code, the boot sector of a hard disk contains
information about the drive layout (including sizes of the drive, root
directory, and file tables). Compressed drives hold this information
in the boot sector; therefore, it is possible that a virus could
corrupt this information.
Which Boot Sector Is Executed During Startup?
---------------------------------------------
If drive C is uncompressed, its boot sector is run during system
startup. If drive C is compressed, the boot sector of its host drive
is run.
What the Boot Sector Does
-------------------------
The MS-DOS 5.0 and 6.0 boot sector startup code does the following:
- Confirms that the system files (IO.SYS and MSDOS.SYS) are the
first two files in the root directory of the drive.
- Loads and executes the first three sectors of the IO.SYS file.
The boot sector is executed by the master boot record (MBR). If you
have more than one partition, the MBR determines which one to run
using the partition table.
Additional reference words: 6.00 change
-=-=-=-=-=-
ARTICLE-ID:Q94357
TITLE :Difference Between DEFRAG and DBLSPACE /DEFRAGMENT
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
There are two ways to defragment a DoubleSpace drive. You can run
DBLSPACE /DEFRAGMENT, or you can run Microsoft Defragmenter
(DEFRAG.EXE).
More Information:
Files stored on a DoubleSpace drive become fragmented just as they do
on a physical drive.
Microsoft Defragmenter (DEFRAG.EXE) makes files contiguous as far as
MS-DOS is concerned, so files are contiguous in virtual clusters. For
example, a DoubleSpace drive would go from
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
C: [1123156-1-13-5-1-2-3-1521--123------- ]
to this:
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
C: [111112222333344455556---------------- ]
NOTE: In these examples, each number represents a piece of a file.
For example, each 1 indicates a piece of file 1.
DBLSPACE /DEFRAGMENT moves data within the compressed volume file
(CVF), so that all the free space is at the end. Using the same
example, the file would go from
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
C: [1123156-1-13-5-1-2-3-1521--123------- ]
to this:
H:\DBLSPACE.000: [121354213221134----------- ]
C: [1123156-1-13-5-1-2-3-1521--123------- ]
If you type DEFRAG to defragment a DoubleSpace drive, Defragmenter
runs DBLSPACE /DEFRAGMENT when it has completed. Once both types of
defragmentation have been done, the sample file would look like this:
H:\DBLSPACE.000: [121354213221134----------- ]
C: [111112222333344455556---------------- ]
Note that files are contiguous on the virtual drive (drive C), but not
within the CVF--free space is contiguous in both places.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94358
TITLE :MemMaker Err Msg with QEMM: 'Bad Command or Filename'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using QEMM to load your files into upper memory and the
FILES command has a plus (+) sign for a delimiter (for example,
C:\QEMM\LOADHI /R:1 FILES+30), you will receive the following error
message:
Bad Command or Filename
More Information:
Using a plus sign as a delimiter is not standard for MS-DOS. If your
QEMM command contains "FILES+nn", MemMaker returns the error message
noted above.
To work around the problem, remove the QEMM "FILES+nn" command from
your AUTOEXEC.BAT file and use the "files=" setting in your CONFIG.SYS
file to specify the number of open files. Run MemMaker again to ensure
that you have the optimal memory configuration.
Additional reference words: 6.00 handles
-=-=-=-=-=-
ARTICLE-ID:Q94377
TITLE :MemMaker Cannot Process Files with More Than 511 Lines
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If your CONFIG.SYS, AUTOEXEC.BAT, or SYSTEM.INI file has 512 or more
lines, MemMaker displays the following error message:
MemMaker cannot continue because the AUTOEXEC.BAT,
CONFIG.SYS, or Windows SYSTEM.INI file is too long.
The file must be less than 512 lines long
* To undo MemMaker's changes, press ENTER.
To work around this problem, exit MemMaker, reduce the size of the
file that is causing the error, and restart MemMaker.
More Information:
You can use MS-DOS Editor to determine the length of a text file. For
example:
1. Start MS-DOS Editor and load a text file such as AUTOEXEC.BAT. For
example, type the following and press ENTER:
EDIT \AUTOEXEC.BAT
2. Press CTRL+END.
The number of lines in the text file is displayed in the
lower-right corner of the screen.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96558
TITLE :MS-DOS 6 Setup Files Installs 80386- and 80486-Specific Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 Setup installs files that are specific to 80386 and 80486
processors even if your processor cannot use these files.
You can delete the following files if you have an 8088 or 8086:
File(s) Requires
------- --------
HIMEM.SYS 80286 and more than 640 kilobytes (K) of RAM
SMARTDRV.EXE HIMEM.SYS
LOADFIX.COM Useful only if using DOS=HIGH
MSTOOLS.DLL Windows 3.1 (or greater) in standard mode
SMARTMON.* Windows 3.1 (or greater) in standard mode
DBLWIN.HLP Windows 3.1 (or greater) in standard mode
Files you can delete if you have an 8088, 8086, or 80286:
File(s) Requires
------- --------
EMM386.EXE 80386 or greater and HIMEM.SYS
MEMMAKER.* 80386 or greater
CHKSTATE.SYS 80386 or greater (used by MEMMAKER.EXE)
VFINTD.386 Windows 3.0 (or greater) in 386 enhanced mode
WINA20.386 Windows 3.0 (or greater) in 386 enhanced mode
MONOUMB.386 Windows 3.0 (or greater) in 386 enhanced mode
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96560
TITLE :POWER.EXE and Advanced Power Management (APM) Support
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You can install the Power program (POWER.EXE) even if your BIOS does
not support the Advanced Power Management (APM) specification. After
you install POWER.EXE in the CONFIG.SYS file, the POWER command
(without any switches) provides status information.
On systems without APM support, POWER displays the following:
Power Management Status
-----------------------
Setting = ADV:REG
CPU: idle 90% of the time
On systems with APM support, POWER displays the following additional
information reported by the BIOS:
Power Management Status
-----------------------
Setting = ADV:REG
CPU: idle 90% of the time
AC Status: OFFLINE
Battery status: High
Battery life (%): 90
More Information:
POWER.EXE detects whether your system has an APM-compliant BIOS and
then adapts accordingly.
When POWER.EXE detects that your system is idle, it saves power by
issuing a CPU HALT instruction. HALT stops CPU execution until the
next hardware interrupt occurs (this is usually the timer interrupt,
which occurs 52 times per second). On systems without an APM-compliant
BIOS, testing reveals a 5% power savings.
If your system has an APM-compliant BIOS, POWER.EXE communicates with
the BIOS. Depending on the frequency of the idle signals from POWER,
the APM-compliant BIOS can save power by shutting down the display or
hard disk, switching the processor to a slower speed, or suspending
the system entirely.
Additional reference words: 6.00 five percent
-=-=-=-=-=-
ARTICLE-ID:Q96562
TITLE :Running Windows 3.1 with Advanced Power Management Systems
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system version 3.1
--------------------------------------------------------------------
Summary:
If are running Windows 3.1 on a system with BIOS chips that support
advanced power management (APM), select MS-DOS System With APM as the
computer type in Windows Setup. This allows Windows power management
services take over power management from POWER.EXE. On computers
without APM support, you can safely run POWER.EXE with Windows.
Additional reference words: 6.00 3.10
-=-=-=-=-=-
ARTICLE-ID:Q94383
TITLE :Error Copying Files with Interlnk on Stacker Volume
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Using Interlnk's INTERSVR command on a volume that has been compressed
using Stacker version 2.0 may fail if INTERSVR incorrectly calculates
the amount of free disk space. If this is the case and you attempt to
copy a file to the compressed volume, you will receive the following
error message:
Error writing drive:
More Information:
When you run INTERSVR on a compressed Stacker volume, Interlnk may
incorrectly calculate the amount of free disk space on the server
machine. Although the DIR command (when issued locally) may report
little or no free disk space, the DIR command issued through Interlnk
may report several megabytes of free disk space.
This may potentially cause data corruption, but a reproducible case
hasn't been found.
This problem occurs with Stacker; this problem does not occur with
Microsoft DoubleSpace.
Stacker is manufactured by STAC Electronics, a vendor independent
of Microsoft; we make no warranty, implied or otherwise, regarding
this product's performance or reliability.
Additional reference words: 6.0 3rdparty dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96563
TITLE :How MS-DOS 6 Upgrade Setup Handles NT Flexboot
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft Windows NT has a Flexboot feature that allows you to choose
the operating system you want to start: Windows NT or MS-DOS. This
feature is controlled by the Windows NT custom master boot record
(MBR), which calls NTLDR when you start your computer. NTLDR then
loads a menu for you to choose which operating system to start. If you
choose MS-DOS, a hidden file called BOOTSECT.DOS is read to start
MS-DOS.
More Information:
If Setup detects NTLDR and BOOTSECT.DOS, it does not update the MBR,
thus preserving Flexboot.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96564
TITLE :Installing MS-DOS 6 Upgrade over OS/2 Boot Manager
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The setup program for MS-DOS 6 Upgrade preserves command line driven
dual-boot programs but disables boot sector driven (that is,
menu-displayed) dual-boot schemes. Therefore, Setup disables OS/2 Boot
Manager versions 2.0 and 2.1; however, this feature can easily be
restored.
More Information:
Boot Sector Driven Dual-Boot Programs
-------------------------------------
Microsoft OS/2 version 1.1 and Compaq OS/2 version 1.2 are the only
versions that use the boot sector driven dual-boot feature. With these
schemes, the boot sector loads a menu from which you choose the
operating system you want to start. MS-DOS 6 Setup overwrites this
information, thus disabling OS/2; you must reinstall OS/2 to enable
this feature.
Command Line Driven Dual-Boot Programs
--------------------------------------
Other OS/2 versions, which use a command line driven dual-boot program
(BOOT /OS2 or BOOT /DOS), are unaffected by MS-DOS 6 Setup.
OS/2 Versions 2.0 and 2.1
-------------------------
In OS/2 versions 2.0 and 2.1, OS/2 Boot Manager displays a menu from
which you choose the operating system you want to start. OS/2 Boot
Manager is controlled by a 1-megabyte (MB) partition on the boot disk.
MS-DOS 6 Setup disables this partition by making the file allocation
table (FAT) partition active. To enable OS/2 Boot Manager, use the
Fdisk program to reactivate the 1-MB non-MS-DOS partition.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94384
TITLE :Err Msg: MSBACKUP Program Files Must Be Located On Hard Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you try to run Microsoft Backup from a floppy disk to restore files to a
hard disk drive, the following error message is displayed:
MSBACKUP program files must be located on your hard disk.
You cannot start MSBACKUP from a floppy disk.
To restore files to a hard disk drive that does not have MS-DOS 6.0
installed, use the following steps:
1.Insert Disk 1 of the MS-DOS 6.0 disk set in your floppy disk drive. Type
"setup/m" (without the quotation marks) and press ENTER to install a
minimal installation.
2.Remove Disk 1 from your floppy disk drive and restart the computer.
3.Replace Disk 1, type "setup/e" (without the quotation marks) to install
optional components.
You can now run Microsoft Backup from the DOS subdirectory and restore
files.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96593
TITLE :Why DoubleSpace Leaves 2 Megabytes Free on the Host Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you compress an existing drive, DoubleSpace leaves approximately
2 megabytes free on the host drive. This space is reserved for files
that DoubleSpace needs when rebooting during the compress-in-place
(CIP) process. The following files are stored on the host drive during
the CIP process:
COMMAND.COM
DBLSPACE.BIN
DBLSPACE.EXE
DBLSPACE.HLP
DBLSPACE.INI
DEFRAG.EXE
DoubleSpace also stores copies of the AUTOEXEC.BAT and CONFIG.SYS
files on the uncompressed portion of the host drive as follows:
AUTOEXEC.000
CONFIG.000
Note: If there are already AUTOEXEC.000 or CONFIG.000 files on the
host drive, DoubleSpace uses 001 for the file extension. If that
filename is used, DoubleSpace uses 002, and so forth.
DoubleSpace uses these files if you restart your computer during a CIP
process. These files are also used when you create a new DoubleSpace
drive or change the size of an existing DoubleSpace drive.
The unused portion of the 2 megabytes of reserved space is used during
the CIP process.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93434
TITLE :MemMaker Copies HIMEM.SYS and EMM386.EXE to C:\DOS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker, and you have MS-DOS installed on a drive other
than your startup (boot) drive (which is usually drive C), MemMaker
creates a DOS directory on the startup drive and copies the following
files to that directory:
- MEMMAKER.EXE
- MEMMAKER.HLP
- MEMMAKER.INF
- EMM386.EXE
- HIMEM.SYS
- CHKSTATE.SYS
- SIZER.EXE
During the optimization process, it also creates MEMMAKER.STS.
Note: The original startup drive might not be drive C if you have a
program such as Stacker from Stac Electronics.
More Information:
For example, if your DOS directory is located on your D drive,
MemMaker creates C:\DOS, copies the files listed above to that
directory, and changes the DEVICE= statements in the CONFIG.SYS file
to point to drive C to ensure that the files are found when MemMaker
restarts the system. MemMaker copies these files to the startup drive
because MemMaker moves the device= statements for HIMEM.SYS AND
EMM386.EXE to the top of the CONFIG.SYS file. Because these files are
then loaded before any devices that might perform drive swapping,
MemMaker must be sure it can find the files it needs to optimize your
system's memory.
MemMaker does not remove these files after it has completed its
optimization. To remove these changes, edit the CONFIG.SYS file and
make sure the device= lines for HIMEM.SYS and EMM386.EXE point to the
drive that contains your full MS-DOS directory. You can then safely
delete the C:\DOS directory.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96603
TITLE :Balancing Power Conservation and Performance with POWER.EXE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Power program (POWER.EXE) monitors keyboard polling and the
Application Idle interrupt to determine if a system is idle; it
monitors use of the hard disk, video functions, and MS-DOS functions
to determine if a system is busy.
POWER.EXE may incorrectly determine that your machine is idle if you
are using communication programs, computation-intensive programs, or
other programs that infrequently access the hard disk. When POWER.EXE
detects that the system is idle, it halts or slows down the CPU, which
adversely affects application performance if your machine is not truly
idle.
More Information:
With the ADV[:MIN|REG|MAX] command line switch, you can indicate
whether your higher priority is power savings or application
performance. Specifically, the ADV parameter controls the keyboard
polling detection. If application performance is suffering because of
false idle detections, you can use the ADV:MIN option to trigger fewer
false idle detections. However, this option provides minimal power
savings when your machine is idle. The ADV:MAX option provides maximum
power savings but increases the chances of false idle detections. The
default setting is ADV:REG, which balances power conservation with
performance.
Type "power" (without the quotation marks and without any parameters)
at the MS-DOS command prompt to determine the current settings.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96604
TITLE :MS-DOS 6 Upgrade Setup Err Msg: Hard Disk Is Not Readable
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The error message "Hard disk is not readable" has several causes. The
most common cause is including the device driver ASPI4DOS.SYS in your
CONFIG.SYS file. If you use this device driver, remark it out in your
CONFIG.SYS file, along with any expanded memory managers (such as
EMM386.EXE or Qemm). You can then install MS-DOS 6 Upgrade and later
restore the line(s) in your CONFIG.SYS file. This problem commonly
occurs when you have a second SCSI device (such as a CD-ROM drive).
More Information:
This error can also occur if any of the following conditions exist:
- A sector read error occurs when reading the master boot records or
the partition boot records. Setup reads this information from the hard
disk and then writes the MBOOT?.DAT and PBOOT?.DAT files to the
Uninstall disk.
- A sector read error occurs when reading the BIOS parameter block
(BPB). Setup reads this information from the hard disk and then writes
the BPB?.DAT files to the Uninstall disk.
- A sector read error occurs when reading the root directory from the
destination hard disk. Setup reads this information from the hard disk
and then writes the ROOT.DAT file to the Uninstall disk.
- A sector read error occurs when reading the file allocation table
(FAT) from the destination hard disk. Setup reads this information
from the hard disk and then writes the ROOT.DAT file to the Uninstall
disk.
- A sector read error occurs when performing the partition table updates
on the attached hard drives. Partition table updates involve
converting MS-DOS-compatible partitions to type 1, 4, or 6 and then
converting logical sectors into 512-byte sectors in the partition boot
record.
- A sector read error occurs when reading the master boot record and
partition boot records to check for unformatted partitions.
- A sector read error occurs when reading the root directory as Setup
tries to obtain the first two root directory entries and determine if
they are MS-DOS system files (IO.SYS and MSDOS.SYS). The above error
can also occur if a sector read error occurs when moving non-MS-DOS
system file entries to make room for the MS-DOS system files in the
first two directory entries.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96625
TITLE :EMM386.EXE and VCPI Services
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
EMM386.EXE version 4.45, included with MS-DOS version 6.0, provides
support for the Virtual Control Program Interface (VCPI) without
having to set an expanded memory page frame and without having to
specify a VCPI memory pool.
VCPI services are provided by default -- no special switches or
parameters are required. If you wish to disable VCPI support you must
use the NOVCPI switch on the EMM386.EXE command in the CONFIG.SYS
file.
More Information:
Several popular MS-DOS applications are "DOS extended" and can
share extended memory and use the protected mode of 80386 and higher
processors through the Virtual Control Program Interface (VCPI).
VCPI is an extension to the expanded memory services (EMS)
interface, and is typically implemented by an EMS emulator such
as EMM386.EXE or Quarterdeck's QEMM386.SYS.
Without VCPI support, "DOS extended" applications would not be
able to run when a system is running in virtual 8086 mode. EMS
emulators use virtual 8086 mode to provide EMS memory mapping
and/or create Upper Memory Blocks (UMBs).
To get VCPI support in the version of EMM386.EXE provided with both
MS-DOS 5.0 and Windows 3.1, you must configure EMM386.EXE to emulated
EMS.
To enable VCPI without EMS support when the NOEMS switch is used, you
must specify a VCPI memory pool size. For example this command can be
used with MS-DOS 5.0's EMM386 to provide 1MB of VCPI memory:
DEVICE=EMM386.EXE 1024 NOEMS
The MS-DOS 6.0 version of EMM386 (4.45) enables VCPI support even when
the NOEMS switch is used without specifying a VCPI size parameter.
Any EMM386 device command that does not include the NOVCPI switch
provides VCPI services.
With the MS-DOS 6 version of EMM386, VCPI memory is sized using
the same parameters as the EMS pool size -- with the EMM386
[memory] and MIN= parameters.
For more information on the EMM386.EXE device driver and the
NOVCPI switch, type HELP EMM386.EXE at the MS-DOS command
prompt.
Additional reference words: 6.00 manager system exteners extenors
-=-=-=-=-=-
ARTICLE-ID:Q96626
TITLE :Uninstall does not Remove DEFAULT.*, DOSBACK.* and .INI Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you Uninstall MS-DOS 6 Upgrade, it does not remove the DEFAULT.*,
DOSBACK.* files from the DOS directory.
All files installed by Setup are removed by Uninstall. DEFAULT.*,
DOSBACK.*, and any .INI files created by optional utilities are not
removed.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96627
TITLE :No Warning if Setup Fails to Modify Your SYSTEM.INI File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run Setup with the /E parameter to install the optional
utilities, Setup does not display any warning or error messages if it
is unable to modify your SYSTEM.INI file because it cannot find the
[386enh] section header.
If the SYSTEM.INI file is not updated with the
DEVICE=C:\DOS\VFINTD.386 line, you receive the following error message
when you start Microsoft Backup for Windows:
Microsoft Backup is not properly installed on this system.
Workaround
----------
To work around this problem, edit your SYSTEM.INI file and add the
following line to the [386enh] section:
DEVICE=C:\DOS\VFINTD.386
Microsoft Backup for Windows should function correctly after you
restart Windows.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96628
TITLE :Screen Does Not Pause With MEM /C /P OR DIR /P
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some older CGA display adapters don't properly handle the scrolling of
text. If you are using on of these cards, the DIR and MEM command /P
parameter may not function correctly.
To work around this problem, add a device statement for ANSI.SYS with
the /S parameter to the CONFIG.SYS file. For example:
device=c:\dos\ansi.sys /s
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96629
TITLE :MS-DOS 6 Upgrade Setup Does Not Remove All Previous DOS Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6 Upgrade Setup does not delete previous and incompatible
versions of some MS-DOS files. For example, Setup does not delete the
following MS-DOS 5.0 files because they don't ship with MS-DOS 6
Upgrade:
SMARTDRV.SYS
JOIN
ASSIGN
If you want to use these files, you can use Setver to change the
version number that MS-DOS reports to the programs.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96633
TITLE :OEM Setup Copies All Files By Default
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS 6.0 OEM Setup program copies all supplied files by default;
this includes the optional Windows utilities BACKUP, UNDELETE, and
ANTI-VIRUS. These components will be copied onto the hard drive
whether or not Windows is installed on the system.
More Information:
The files for the Windows utilities will be copied to the hard drive,
however, they will not be setup correctly if Windows is not installed
at the time of the initial setup. If Windows is later added to the
system, running SETUP /E will properly configure the Windows
utilities.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96655
TITLE :MS-DOS 6.0 SETUP /E: Error Renaming Old Utilities
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When running MS-DOS 6 Setup with the /E parameter to install the
optional programs, Setup may display the following error:
Unrecoverable Error
Error renaming old utilities.
Press ENTER to exit Setup.
This can occur if Setup is using invalid drive information for the
drive where MS-DOS is installed. The drive information can be
corrupted by running SETUP /E when the MS-DOS directory is not listed
in the path.
To correct this problem, exit Setup and restart your computer. Make
sure the MS-DOS directory is in the path and run SETUP /E again.
More Information:
This is a known problem with MS-DOS 6.0 Setup. The MS-DOS directory
must be included in the path to run SETUP /E. If SETUP /E is run when
the MS-DOS directory is not in the path, Setup displays a warning
message stating that it is unable to locate the MS-DOS directory. If
you exit Setup, modify the path to include the MS-DOS directory, and
then run SETUP /E again, the drive information for the MS-DOS drive is
invalid. For example the "Space available on drive" information might
be incorrect. This invalid information results in the unrecoverable
error listed above.
Microsoft has confirmed this to be a problem in MS-DOS Setup version
6.0. We are researching this problem and will post new information
here as it becomes available.
Additional reference words: 6.00 BUSETUP BUSETUP.EXE SETUP.EXE install
optional programs utilities
-=-=-=-=-=-
ARTICLE-ID:Q96695
TITLE :Installation programs and Multi-Config
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Many application installation programs modify the CONFIG.SYS and
AUTOEXEC.BAT files. Most installation programs which modify the
CONFIG.SYS file either adding lines at the top or at the bottom of the
file.
If you have a [COMMON] block at the end of your CONFIG.SYS file, you
shouldn't have any trouble with the programs that add lines at the
bottom of the file.
The most common problem occurs when installation programs update
a specific driver in the CONFIG.SYS file and there are multiple
instances of that driver. Many installation programs only update the
first (or last) occurrence of the driver. If you avoid multiple
occurrences of device drivers in CONFIG.SYS by using a [COMMON]
section, you will probably never experience a problem.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96697
TITLE :Using ANSI Characters with CHOICE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The CHOICE command allows only one key to be used per selection. For
example, you cannot use 12 (twelve) as key selection. CHOICE
interprets this as 1 and 2. however, you can use the ANSII character
set by holding down the ALT key and entering the appropriate 3-key
combination on the numeric keypad. Not all combinations work but you
can use up to 222 different entries from the 255 available. The table
below details the 255 characters.
0-27 Do not work
28-31 Work
32 Do not work
33-255 Work with the some xceptions noted below
More Information:
ALT + 37. displays the '%' sign on your screen.
When you use the percent sign in a batch file it acts as a replaceable
parameter. You must use two percent signs (one immediately after the
other) to use the % symbol. To do this, you need to enter ALT + 37
twice.
ALT + 47 displays the '/' forwardslash.
The forwardslash will not work with CHOICE.
ALT + 60 displays the '<' symbol.
This represents a redirector and does not work with the CHOICE
command.
ALT + 62 displays the '>' symbol.
This represents a redirector and does not work with the CHOICE
command.
ALT + 124 displays the '|' (pipe) symbol.
This represents the MS-DOS pipe and does not work with the CHOICE
command.
ALT + 127 represents the delete key.
This does not work with the CHOICE command.
ALT + 255 represents the spacebar key.
This works if you enter ALT + 255. This does not work if you press the
spacebar key.
If you use the extended characters between 128 and 165, you should use
the /S switch to treat choice keys at case sensitive.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96700
TITLE :MemMaker Cannot Continue if Newwave is in Your AUTOEXEC.BAT
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker, if Newwave is in your AUTEOXEC.BAT file,
MemMaker cannot continue when you exit Newwave.
To work around this problem:
1. Use the REM command to remark out Newwave in your AUTOEXEC.BAT
file. For example:
rem newwave
2. Restart your computer.
3. Run MemMaker.
4. When MemMaker has completed, take the REM command out of your
AUTOEXEC.BAT file so Newwave can load.
5. Restart your computer.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96701
TITLE :DoubleSpace Err Msg: Unknown Error Cause by Watchdog PC
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You may receive the following error when you install DoubleSpace:
Unknown Error
The error is caused by a conflict between DoubleSpace and Watchdog PC
Data Security software.
To work around this problem, disable your Watchdog PC Data Security
software before you install DoubleSpace.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q57730
TITLE :Err Msg: ""No Room for System on Destination Disk"" with SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system versions 3.x, 4.x, 5.0, 5.0a,
and 6.0
--------------------------------------------------------------------
Summary:
In the Microsoft MS-DOS user's manuals for versions 3.3, 3.3a, 4.0,
4.0a, 4.01, 4.01a, 5.0, and 5.0a, the SYS command entry states that
you do not need to reformat your disk when you upgrade to a later
version of MS-DOS. SYS updates system disks even though the new system
files are larger and must be broken up to fit in the available disk
space.
However, when upgrading some system disks, SYS returns the following
error message:
No room for system on destination disk
This error message is caused by one of the following:
- There is not enough free space anywhere on the destination disk for
the relocatable part of the system files.
Solution
--------
Delete some files to make room for the system files. This
is documented in Appendix F of the "Microsoft MS-DOS User's
Reference Manual" for versions 4.01 and earlier, under the "No room
for system on destination disk" error message. If you are running
version 5.0, see the Application Note titled "MS-DOS 5.0 Messages
Reference," PD0489. To obtain application notes, call Microsoft
Product Support Services at (206) 454-2030.
- A file occupies the first clusters of the disk on a non-system
disk.
Solution
--------
If a disk utility is available to find which file(s) occupy the
first clusters of the disk, erase or move those files to clear
the space needed for the system.
If you have the MS-DOS 5 Upgrade or the MS-DOS 6 Upgrade, you can
run Setup with the /M parameter.
If the previous two options are not available, you must reformat the
disk.
- The disk has an original equipment manufacturer (OEM) version of
MS-DOS that does not use the Microsoft naming convention for the
hidden system files.
Solution
--------
Contact the OEM supplier for an MS-DOS upgrade. You should continue
running that dialect of MS-DOS. However, if you must change to the
Microsoft MS-DOS packaged product, see the information provided
below.
More Information:
There is a quick solution for the OEM MS-DOS problem mentioned above.
This solution requires that you have a good understanding of MS-DOS,
and that you have a third-party utility to remove the Hidden, System,
and Read-Only attributes from the system files.
The MS-DOS SYS command looks for the files named IO.SYS and MSDOS.SYS
on the destination disk. If these files are not found, because they do
not exist or are named differently, SYS assumes the disk is not a
system disk and attempts to install the new system files starting at
cluster 2 (IO.SYS must be contiguous starting at cluster 2).
Some OEMs, such as IBM, use different names for the system files. To
make SYS work with these disks, you can rename the two files to IO.SYS
and MSDOS.SYS, as in the following example. (The following example
uses IBM PC-DOS naming conventions.)
1. Using a third-party attribute change utility, remove the Hidden,
Read-Only, and System attributes from IBMBIO.COM and IBMDOS.COM.
MS-DOS does not provide a utility to set or reset the Hidden and
System attributes of a file, because you should not tamper with
these files.
2. Rename these two files as follows:
ren ibmbio.com io.sys
ren ibmdos.com msdos.sys
3. Use the attribute utility to replace the Hidden, Read-Only, and
System attributes.
The SYS command should work correctly after you have made the above
changes. Remember that the SYS command does not transfer COMMAND.COM,
so you must do that manually.
Additional reference words: 3.30 3.30a 4.00 4.00a 5.00 5.00a 6 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93582
TITLE :DoubleSpace Err Msg: 'There Are No More Drive Letters'
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
-----------------------------------------------------------------------
Summary:
If there are not enough drive letters available to DoubleSpace, or you
have not installed DoubleSpace on your hard disk and you attempt to
mount a compressed floppy disk, you may receive the following error
message:
There are no more drive letters reserved for dblspace to use.
To add more, use the options selection from the tools menu.
More Information:
To work around this problem, follow the appropriate procedure below.
DoubleSpace Does Not Have Enough Drive Letters Available
--------------------------------------------------------
If there are no drive letters available for DoubleSpace to mount a
drive, use the following procedure to increase the Last Drive Reserved
For DoubleSpace's Use setting.
1. To run DoubleSpace, type "DBLSPACE" (without the quotation marks)
at the command prompt.
2. From the Tools menu choose Options.
3. Increase your Last Drive Reserved For DoubleSpace's Use setting by
at least one letter.
Note: This procedure causes the host drive letter to change. If
your Windows permanent swap file is located on that host drive,
when you start Windows, you will receive an error message
indicating that your permanent swap file is corrupt. To correct
this problem, run Control Panel and reconfigure your permanent swap
file for the new host drive.
You Are Attempting to Mount a Compressed Floppy Disk
----------------------------------------------------
To work around this problem create a very small new DoubleSpace drive
and then delete it. This creates the DBLSPACE.INI file and loads
DBLSPACE.BIN into memory so you can read the compressed floppy drive.
To do this:
1. To run DoubleSpace, type "DBLSPACE" (without the quotation marks)
at the command prompt.
2. Choose Custom Setup
3. Choose Create A New Empty Compressed Drive.
4. Select a drive you want to use.
5. When you are prompted for the the amount of free space to leave on
the drive, type a number larger than your hard drive.
6. After DoubleSpace tells you the maximum amount free space you can
leave on your drive, type in that number. For example, if
DoubleSpace tells you the maximum amount of free space is 95.55
megabytes (MB), leave 95 MB of free space.
7. Choose Continue.
8. Press the C key to create the compressed drive.
You can now mount the compressed floppy disk. If you do not want to
keep the DoubleSpace drive you created, type the following command at
the MS-DOS command prompt and restart your computer:
deltree /y dblspace.001
As an alternative, you also use the following procedure to create a
DBLSPACE.INI file and load DBLSPACE.BIN in memory:
1. Create a C:\DBLSPACE.INI file (where C is your startup disk) with a
text editor such as Edit. The DBLSPACE.INI file 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 DOS directory to the root directory of
your startup (boot) drive. For example:
copy c:\dos\dblspace.bin c:\
3. Restart your 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:
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93584
TITLE :EMM386.EXE: Default DMA Buffer Size
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
EMM386.EXE's default direct memory access (DMA) buffer size has
increased from 16 to 32 kilobytes.
More Information:
All DMA buffers are stored in extended memory regardless of size.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93592
TITLE :Correcting Illegal Directory Names With DELTREE and MOVE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS DEL command cannot be used to delete a directory with a
blank space in the name (for example "C:\MY WORK"). However, you can
use the MS-DOS 6 programs DELTREE and MOVE to delete or rename these
directories.
More Information:
Some utilities and installation programs allow you to create directory
names with illegal characters (such as spaces). Because a directory
name with a space or other illegal character is not expected, DEL was
not designed to work with them.
Using DELTREE to Delete Illegal Directories
-------------------------------------------
The DELTREE program can be used to delete illegal directories. For
example, type the following at the MS-DOS command prompt:
DELTREE "MY WORK"
Note: You must type the quotation marks.
Using MOVE to Rename Illegal Directories
----------------------------------------
The MOVE program can be used to rename illegal directories. For
example, type the following at the MS-DOS command prompt:
MOVE "MY WORK" MY_WORK
Note: You must type the quotation marks.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93599
TITLE :Difference Between 'DBLSPACE /CHKDSK' and 'CHKDSK'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run DoubleSpace with the /CHKDSK switch (for example, type
DBLSPACE /CHKDSK) on a DoubleSpace partition, it analyzes the
DoubleSpace file allocation table (FAT) for consistency. The
DoubleSpace FAT is a separate data structure from the MS-DOS FAT.
To check the DoubleSpace FAT and the MS-DOS FAT, you must run both
"DBLSPACE /CHKDSK" and "CHKDSK" on the DoubleSpace drive. To analyze
and repair any problems, add the /F switch to both commands.
More Information:
MS-DOS maintains a data structure for the FAT that maintains a "map"
of the disk usage (both files and free space) recording the status of
each sector on the disk. When DoubleSpace is installed, it creates
its own FAT and maps the MS-DOS FAT to the DoubleSpace FAT.
Additional reference words: 6.0 double space
-=-=-=-=-=-
ARTICLE-ID:Q93602
TITLE :How to Disable F5 and F8 During Startup in MS-DOS 6.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 allows you to bypass both AUTOEXEC.BAT and CONFIG.SYS by
pressing the F5 key as you are starting your computer. This can
disable the effectiveness of some password-protection schemes. In
order to disable this feature, add the following line to CONFIG.SYS:
SWITCHES=/N
This line disables both the F5 and F8 keys, which allow you to modify
your startup configuration during the boot process. Note: This line
can be put anywhere in CONFIG.SYS.
Additional reference words: 6.00 howto startup start up
-=-=-=-=-=-
ARTICLE-ID:Q93603
TITLE :After Dark Screen Saver Can Corrupt Screen
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After Dark's MS-DOS-based screen saver, AD_DOS.COM, can corrupt the
screen during MS-DOS Setup if it is allowed to clear image on the
screen and replace it with a screen saver image. Once the screen saver
activates, you can return to a normal screen by pressing any key.
However, if this occurs during Setup, the restored screen is filled
with random characters. Setup continues to function correctly, but you
may have difficulty understanding the prompts.
Additional reference words: 6.00 blanking garbled characters fuzzy
distorted 3rdparty
-=-=-=-=-=-
ARTICLE-ID:Q93652
TITLE :System Hangs When Loading WFWG Drivers
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
If DBLSPACE.SYS is loaded into upper memory after PROTMAN.DOS, the
system may stop responding ("hang") when the network drivers are
loading.
To work around this problem, load DoubleSpace high before you load
PROTMAN.DOS by placing the "device" lines in your CONFIG.SYS file in
the following order:
devicehigh=c:\dos\dblspace.sys /move
device=c:\windows\protman.dos /i:c:\windows
Additional reference words: 6.0 3.1 3.10 wfw wfwg dblspace
-=-=-=-=-=-
ARTICLE-ID:Q93653
TITLE :Novell's NETX Reports MS-DOS 6.0 as MS-DOS 5.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When running with MS-DOS version 6.0, Novell's NETX versions 3.31 and
earlier report the operating system version as MS-DOS 5.0.
More Information:
NETX requires MS-DOS 5.0 or earlier--it does not run with MS-DOS 6.0
unless you use SETVER.EXE to trick it. Since SETVER tells NETX that
the MS-DOS version is 5.0, NETX reports the MS-DOS version as 5.0.
This behavior could be a problem for network administrators who
configure their systems to map to specific directories for different
versions of MS-DOS, depending on the version reported by NETX. For
example, suppose that machines running MS-DOS 3.3 are mapped to
Y:\DOS\V3.30 and machines running MS-DOS 5.0 are mapped to
Y:\DOS\V5.00. In this example, when you use SETVER to tell NETX you
are running MS-DOS 5.0, you are logged onto the Y:\DOS\V5.00
directory.
Additional reference words: 6.0 netx.com netx.exe
-=-=-=-=-=-
ARTICLE-ID:Q90554
TITLE :DoubleSpace Drives Not Viewable in NT MS-DOS Prompt
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Beta 2 Release of Microsoft Windows NT operating system
version 3.1
--------------------------------------------------------------------
Summary:
When using MS-DOS 6 Upgrade DoubleSpace with Windows NT configured for
Dual Boot, you cannot see your compressed files or run your
MS-DOS-based programs when running MS-DOS Prompt under Windows NT.
More Information:
To accomplish disk compression, DoubleSpace uses a device driver
(loaded at system startup) to intercept disk reads and writes from the
command line and MS-DOS-based applications. When you run MS-DOS Prompt
under Windows NT, the DoubleSpace device driver is not loaded.
This feature is under review and will be considered for inclusion in a
future release of Windows NT.
Additional reference words: 6.0 dblspace double space
-=-=-=-=-=-
ARTICLE-ID:Q90564
TITLE :MS-DOS Err Msg: DoubleSpace Cannot Defragment Because...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are running a screen-saver program when you attempt to install
DoubleSpace from MS-DOS 6 Upgrade, you may receive the following error
message:
DoubleSpace cannot defragment C because of an unknown error
To work around this problem, remove the screen-saver from your
CONFIG.SYS or AUTOEXEC.BAT file, restart your computer and install
DoubleSpace. After DoubleSpace is successfully installed, you can add
the screen-saver to your CONFIG.SYS or AUTOEXEC.BAT file.
Additional reference words: 6.0 screensaver blank black blanker tsr
dblspace
-=-=-=-=-=-
ARTICLE-ID:Q90565
TITLE :Changes Made by MS-DOS Setup to the SYSTEM.INI File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you install Microsoft MS-DOS 6 Upgrade, Setup adds the following
line to the [386Ehn] section of the SYSTEM.INI files if you install
the Windows programs.
device=vfintd.386
The virtual device driver (VxD) vfintd.386 adds support to Windows for
virtualize your floppy drives to prevent conflicts between multiple
virtual machines.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q90571
TITLE :Applications That Require SETVER.EXE for MS-DOS 6.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some applications check the MS-DOS version number before executing and
may not run when they detect version "6.00." To work around this
limitation, use SETVER.EXE, included with MS-DOS 6 Upgrade.
The table lists the files in the default SETVER.EXE version table in
MS-DOS version 6.0:
Filename MS-DOS Version
--------------------------
KERNEL.EXE 5.00
NETX.COM 5.00
NETX.EXE 5.00
NET5.COM 5.00
BNETX.COM 5.00
BNETX.EXE 5.00
EMSNETX.EXE 5.00
EMSNET5.EXE 5.00
XMSNETX.EXE 5.00
XMSNET5.EXE 5.00
DOSOAD.SYS 5.00
REDIR50.EXE 5.00
REDIR5.EXE 5.00
REDIRALL.EXE 5.00
REDIRNP4.EXE 5.00
EDLIN.EXE 5.00
BACKUP.EXE 5.00
ASSIGN.COM 5.00
EXE2BIN.EXE 5.00
JOIN.EXE 5.00
RECOVER.EXE 5.00
GRAFTABL.COM 5.00
LMSETUP.EXE 5.00
STACKER.COM 5.00
NCACHE.EXE 5.00
NCACHE2.EXE 5.00
IBMCACHE.SYS 5.00
XTRADRV.SYS 5.00
WINWORD.EXE 4.10
EXCEL.EXE 4.10
LL3.EXE 4.01
REDIR4.EXE 4.00
REDIR40.EXE 4.00
MSREDIR.EXE 4.00
WIN200.BIN 3.40
METRO.EXE 3.31
WIN100.BIN 3.40
HITACHI.SYS 4.00
MSCDEX.EXE 4.00
NET.EXE 4.00
NETWKSTA.EXE 4.00
DXMA0MOD.SYS 3.30
BAN.EXE 4.00
BAN.COM 4.00
DD.EXE 4.01
DD.BIN 4.01
REDIR.EXE 4.00
SYQ55.SYS 4.00
SSTDRIVE.SYS 4.00
ZDRV.SYS 4.01
ZFMT.SYS 4.01
TOPSRDR.EXE 4.00
NETBEUI.DOS 5.00
NET.COM 3.30
The following file looks for versions of MS-DOS earlier than 6.0 and
ARE NOT in the default version table:
Filename MS-DOS Version Description
------------------------------------------------------------------
SLP.EXE 5.0 Seiko Smart Label Printer TSR
UMBFILES.COM 5.0 PC Magazine Utility
For more information, query in the Microsoft Knowledge Base on
"SETVER.EXE" and the specific application name.
More Information:
SETVER allows you to modify the version table that is kept in the
MSDOS.SYS file. When an application associated with an entry in the
version table is executed, the version table tells the program that it
is running under the MS-DOS version listed in the table.
To modify the version table, do the following:
1. At the MS-DOS prompt, type the following:
setver
For example:
setver example.exe 4.01
A warning message will be displayed that states the application
being added to the version table may not be verified by MS-DOS and
could cause corruption.
2. Verify that the command was added to the version table by typing
"setver" (without the quotation marks).
3. Restart the system so that the new Setver table is loaded into
memory.
Before you can use the SETVER command, the version table must be
loaded into memory by a DEVICE command in your CONFIG.SYS file. By
default, the MS-DOS 6.0 Setup program modifies your CONFIG.SYS file to
ensure that the version table is loaded into memory each time you
start your system.
Additional reference words: 4.00 5.00 6.00 4.0 5.0 6.0
-=-=-=-=-=-
ARTICLE-ID:Q90678
TITLE :MS-DOS Setup is Bootable but Setup Doesn't Run
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS Upgrade Setup Disk 1 is ALWAYS bootable. In other words,
The Setup Disk can be used to start up a computer if the hard drive is
inaccessible, cannot be booted, or does not contain an operating
system.
However, the MS-DOS Upgrade 6.0 Setup program does not run if there is
no operating system on the computer. The MS-DOS Upgrade package is
licensed, sold, and designed for users who have an existing copy of
MS-DOS, or some other operating system, who would like to upgrade to
MS-DOS 6.0.
If your computer does not have an operating system installed, and you
don't have your original operating system disks, you need to contact
your computer manufacturer to obtain a copy of its OEM version of
Microsoft MS-DOS 6.0.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q90682
TITLE :COMMAND.COM Corrupted or Missing on a DoubleSpace Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using DoubleSpace and COMMAND.COM cannot be found, the
system is not bootable.
Workaround
----------
1. Start the system from MS-DOS 6.0 Setup disk number 1.
2. Exit from Setup (press F3 twice). The DoubleSpace drive should now
be available.
3. Copy DBLSPACE.BIN to the root directory of drive C, as follows:
copy dblspace.bin c:\
4. Remove the Setup disk from drive A and restart the computer.
More Information:
MS-DOS Setup disk number 1 contains DBLSPACE.BIN. When MS-DOS is
started from drive A and that disk contains DBLSPACE.BIN, the
DoubleSpace drives become accessible just as if you start the system
from drive C.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q91202
TITLE :Multiple Configuration Menu Does Not Display
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If the MENUDEFAULT command in your CONFIG.SYS file is incorrectly
set,the time-out value defaults to zero. As a result, the startup menu
is not displayed when you start your machine.
Common problems with menudefault settings include using the full menu
descriptor (menu_text) instead of the menu block name and using
non-numeric characters.
To determine if your menudefault is incorrectly set, restart your
computer and press the F8 function key when the text "Starting
MS-DOS..." is displayed. If the time-out is defaulting to zero, the
menu is displayed. If the menu is not displayed, another problem
exists.
More Information:
Do not use more than one word for your block name. If you want to use
text to describe your menu options, use a one-word block name followed
by the description. For example, consider the following menu items:
menuitem=dev, Development Configuration
menuitem=wfwg, Windows for Workgroups
menuitem=games, Games
menuitem=files, Files and Buffers Only [dev]
[wfwg]
[games]
[files]
For these menu items, the four default menu possibilities are
"development," "wfwg," "games," and "files."
When you use the menudefault setting, do not include the descriptor
text. For example,
menudefault=wfwg, 30
If you include the descriptor text, it is interpreted as the time-out
setting. Since it is non-numeric text, the menu is not displayed. For
example, the following menudefault line is incorrect:
menudefault=wfwg, Windows for Workgroups, 30
For help on using a multiple configuration menu, type "help
multiconfig" (without the quotation marks) at the MS-DOS command
prompt or see chapter 4 of "Microsoft MS-DOS 6.0 User's Guide."
For help on using the MENUDEFAULT command in your CONFIG.SYS file,
type "help menudefault" (without the quotation marks) at the MS-DOS
command prompt.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q91634
TITLE :Using RAMDrive to Speed Up MS-DOS Task Swapper
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
RAMDrive is a memory-resident program that enables you to use part of
your computer's memory (RAM, or random-access memory), as if it were a
hard disk drive. By using RAMDrive, you can make MS-DOS Task Swapper
run faster.
When you install MS-DOS, the Setup program copies the RAMDRIVE.SYS
file to your DOS directory. To create a RAM drive, you add a DEVICE=
or DEVICEHIGH= command for RAMDRIVE.SYS to your CONFIG.SYS file.
More Information:
To speed up Task Swapper:
1. Make a backup copy of your CONFIG.SYS file.
2. Open your CONFIG.SYS file by using any text editor.
3. Add a DEVICE= or DEVICEHIGH= command line for the RAMDRIVE.SYS
device driver. It should appear similar to the following:
device=c:\dos\ramdrive.sys 512 /e
This example creates a RAM drive that takes up 512K of extended
memory. You can specify how much and what type of memory your RAM
drive uses by customizing the command line. For more information
about RAMDrive command-line options, type "help ramdrive.sys"
(without the quotation marks) at the MS-DOS command prompt.
4. Save the changes to your CONFIG.SYS file.
5. Open your AUTOEXEC.BAT file.
6. Set the TEMP environment variable to your RAM drive by adding a
SET command line. The drive letter of your RAM drive should be the
letter after that of the last disk drive in use. For example, if
your last disk drive in use is C, your RAM drive would be D. In
this case, you would add the following command to your AUTOEXEC.BAT
file:
set temp=d:\
7. Save the changes to your AUTOEXEC.BAT file.
8. Restart your computer.
Note: If RAMDrive is to use extended memory, your CONFIG.SYS file must
contain a DEVICE= command for the HIMEM.SYS memory manager. If
RAMDrive is to use expanded memory, your CONFIG.SYS file must contain
a DEVICE command for the expanded-memory manager that came with your
memory board. The device command for RAMDrive must come after the one
for the memory manager.
You can improve the performance of RAMDrive by doing the following:
- If you run programs from your RAM drive, list your RAM drive first
in your PATH= command. For example, if your RAM drive is drive E,
add E:\ to the beginning of the PATH= command.
- If you use the EMM386 program as an expanded-memory emulator, do
not put the RAM drive in expanded memory. Although RAMDrive can
also use this emulated expanded memory, it won't be as efficient as
it would if it were using real physical memory.
Additional reference words: 6.0 ram drive
-=-=-=-=-=-
ARTICLE-ID:Q91664
TITLE :MS-DOS Backup Err Msg: Unable to Open Component File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use a non-floppy drive, Backup creates a .001 file in a .FUL
directory. For example, if you back up to F:\TEMP on your fixed drive
or a network drive), Backup creates
f:\TEMP\DEFAULT\xxxxxxxx.FUL\xxxxxxxx.001
where xxxxxxxx are numbers and letters generated from the date. Moving
the .001 file causes the restore option in Backup to fail and
generates the following error message:
Unable to open component file
Therefore, if you back up to a network drive, and someone moves your
files, you cannot restore them until they are moved back.
More Information:
To work around this problem, re-create your original directory
structure and move the .001 file back to its original location. If
you cannot remember the original directory structure, attempt to
restore your files again. The error message displayed by Backup tells
you the directory and filename for which it is looking.
Steps to Reproduce Problem
--------------------------
1. Run Backup.
2. Back up files from one drive to a non-floppy drive and minimize
Backup.
3. Run File Manager and move the .001 file to another directory.
4. Switch back to Backup and attempt to restore some files.
How the Backup Filename in Generated
------------------------------------
The backup file for DEFAULT\CCYMMDDA.FUL is calculated as follows:
default = name of backup set
y = last number of year
mm = month of backup
dd = day of backup
a = A - Z, depending on the number backups that day
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q91728
TITLE :MS-DOS 6 DoubleSpace Files and Functions
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
This article contains a list of DoubleSpace files and their functions.
Filename Function
----------------------------------------------------------------------
DBLSPACE.BIN Main DoubleSpace Component
DBLSPACE.EXE For creation or modification of a DoubleSpace drive
DBLSPACE.HLP DoubleSpace on-line help file
DBLSPACE.INF DoubleSpace Setup information file
DBLSPACE.INI DoubleSpace information file
DBLSPACE.WIN Used to keep track of Windows during
DoubleSpace installation
DBLSPACE.SYS Allows MS-DOS to load DoubleSpace device driver high
DBLSPACE.00x Actual DoubleSpace drive stored as a file
More Information:
For definitions of terms used in this article, please see the
DoubleSpace Help.
DBLSPACE.BIN
------------
MS-DOS uses the DBLSPACE.BIN component to mount the compressed volume
file so you can access the files on your compressed drive. This file
loads automatically if it is in the root directory of the startup disk
(no device= line is needed). If you want to load DBLSPACE.BIN into
upper memory, see the DBLSPACE.SYS section of this article.
DBLSPACE.EXE
------------
This file allows you to mount, create or modify DoubleSpace drives.
DoubleSpace accepts the following parameters:
DBLSPACE /CHKDSK [/F] [drive:]
DBLSPACE /COMPRESS drive: [/F] [/NEWDRIVE=drive2:] [/RESERVE=size]
DBLSPACE /CREATE drive: [/NEWDRIVE=drive2:] [/SIZE=size | /RESERVE=size]
DBLSPACE /DEFRAGMENT [/F] [drive:]
DBLSPACE /DELETE drive:
DBLSPACE /FORMAT drive:
DBLSPACE [/INFO] drive:
DBLSPACE /LISTDBLSPACE /MOUNT[=sss] [drive:] [/NEWDRIVE=drive2:]
DBLSPACE /RATIO[=r.r] [drive: | /ALL]
DBLSPACE /SIZE[=size | /RESERVE=size] [drive:]
DBLSPACE /UNMOUNT [drive:]
For more information about DoubleSpace command-line options, type HELP
DBLSPACE or HELP DBLSPACE /switchname (where /switchname is the name
of the switch about which you want more information) at the command
prompt.
DBLSPACE.HLP
------------
This file contains help on DoubleSpace. To access this file, run
DoubleSpace and choose Contents or Index from the Help menu.
DBLSPACE.INF
------------
The DoubleSpace Setup information file is helpful when creating a new
DoubleSpace drive, but it is not required.
Commands under the [SpecialFiles] section indicate actions to be taken
for specific files; the possible actions are COPY=, IGNORE= and MOVE=.
Without a path, any file of that name will match; wild cards (?, *)
are acceptable.
Programs under the [CopyFiles] section are optional utilities that
will be left on the original boot drive if there is enough room..
Programs under the [dangerous] section will be remarked out using the
REM command from CONFIG.SYS file during DoubleSpace Setup but will not
be remarked after Setup has completed.
Programs under the [prior] section will have DEVICEHIGH=DBLSPACE.SYS
placed ABOVE them in the CONFIG.SYS file.
DBLSPACE.INI
------------
This file is used by DoubleSpace to mount the compressed volume and
swap drive letters. The file contains the following settings:
MaxRemovableDrives=
FirstDrive=
LastDrive=
MaxFileFragments=
ActivateDrive=
DBLSPACE.WIN
------------
This is a temporary file that DBLSPACE.BIN generates to keep track of
windows information when a drive is compressed. It should
automatically be deleted after DBLSPACE.BIN completes the compression
of the existing drive.
DBLSPACE.SYS
------------
The DBLSPACE.SYS device driver does not provide access to the
compressed drives; it simply makes it possible for DBLSPACE.BIN to be
loaded high. If you do not plan to move DBLSPACE.BIN into upper
memory, you can safely remove the DEVICE=C:\DOS\DBLSPACE.SYS line from
your CONFIG.SYS file.
DBLSPACE.00x
------------
A compressed drive is not a real disk drive, although it appears that
way to most programs. Instead, a compressed drive exists on your disk
as a hidden file called a compressed volume file (CVF). DBLSPACE.00x
is the compressed volume file.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q92393
TITLE :Dual-Boot Schemes Preserved by MS-DOS 6 Upgrade
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
The MS-DOS 6 Upgrade preserves the master boot record (MBR) if you
have Windows NT Flex Boot or OS/2 Dual Boot installed. In all other
cases, you must manually restore the (MBR).
The MS-DOS 6 Upgrade does not preserve the OS/2 Boot Manager or UNIX
dual-boot partition schemes; however, they can be restored by using
the procedures below.
More Information:
OS/2 Boot Manager
-----------------
Setup does not disable your dual-boot configuration if you are using
OS/2 version 1.2. If your system was set up for multiple-boot
functionality with Boot Manager, use the following procedure to
restore this functionality:
1. Run FDISK.EXE.
2. Choose 2 and press ENTER to set the active partition.
3. Choose the Boot Manager partition (it is listed as a 1-megabyte
non-DOS partition).
4. Exit FDISK.
5. Restart your computer.
UNIX or XENIX
-------------
If your system is set up for dual-boot functionality and you have not
installed the MS-DOS 6 Upgrade, you should install MS-DOS 6 manually.
If your system was set up for dual-boot functionality with UNIX and
you installed MS-DOS using the /u switch, use the following procedure
to restore the dual-boot functionality:
1. Run FDISK.EXE.
2. Choose 2 and press ENTER to set the active partition.
3. Choose the UNIX partition.
4. Exit FDISK.
5. Restart your computer.
6. Consult your UNIX documentation to restore the dual boot
functionality.
For more information on installing the MS-DOS 6 Upgrade on a system
with UNIX or XENIX partitions, refer to the following section in
Chapter 9 of the "Microsoft MS-DOS 6 User's Guide":
Setup displays the "Incompatible hard disk or device driver" screen
Additional reference words: 6.00 dual boot startup system menu
-=-=-=-=-=-
ARTICLE-ID:Q92426
TITLE :LANtastic Allows Hidden and System Files to be Deleted
-----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system versions 3.x, 4.x, 5.x, and 6.0
-----------------------------------------------------------------------
Summary:
LANtastic version 4.1 allows you to delete hidden and system files on
LANtastic servers. This functionality is specific to LANtastic, and
cannot be changed by MS-DOS.
For more information on deleting hidden and system file on a LANtastic
server, please consult your LANtastic documentation.
Additional reference words: 3.00 3.10 3.20 3.30 3.30a 3.31 3.00 4.01
5.00 5.00a 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93366
TITLE :EMM386.EXE: ALTBOOT Parameter
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
A new parameter was added to EMM386.EXE in order to avoid problems
encountered when you attempt to reboot a computer with the key
combination CTRL+ALT+DEL. If your machine stops responding (hangs)
when you press CTRL+ALT+DEL, try adding the ALTBOOT parameter as in
the following example:
DEVICE=C:\DOS\EMM386.EXE ALTBOOT X=C000-C7FF NOEMS
More Information:
The CTRL+ALT+DEL handling routine changed when EMM386.EXE was upgraded
in Microsoft Windows operating system version 3.1. The ALTBOOT
parameter tells EMM386 to handle CTRL+ALT+DEL the same way it does in
Microsoft MS-DOS version 5.0. The ALTBOOT parameter may be needed on
UNISYS PW^2 3256 computers with Phoenix A386 BIOS copyrighted
1985,1991.
Additional reference words: 6.00 UNISYS Phoenix
-=-=-=-=-=-
ARTICLE-ID:Q93374
TITLE :MemMaker Doesn't Find SYSTEM.INI File on Network
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker does not find your Windows SYSTEM.INI file if you are running
a network installation of Windows (installed with SETUP /N) and you
don't log onto the network from your AUTOEXEC.BAT file.
More Information:
MemMaker relies on the CONFIG.SYS and AUTOEXEC.BAT files to find the
files it needs to optimize your system. MemMaker needs to read the
SYSTEM.INI file to determine how much free upper memory block (UMB)
space to set aside for the API translation buffers.
For MemMaker to correctly optimize your systems memory, load the
network software from the AUTOEXEC.BAT file.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93375
TITLE :Changes in EMM386.EXE Version 4.45 (MS-DOS 6.0)
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
Version 4.45 of the Microsoft expanded memory manager (EMM386.EXE),
provided with MS-DOS version 6.0, has the following new features:
- Advanced Upper Memory Scanning
- Expanded and Extended Memory Sharing
- Ability to Provide Upper Memory Regions for Microsoft Windows
- Ability to Load with NOEMS When No Page Frame Is Available
- NOVCPI Switch for Smaller Load Size
- Automatic IBM Token Ring Adapter Detection
- Quiet Loading
- Ability to Provide ROM Shadowing
This article describes these features in detail.
More Information:
Advanced Upper Memory Scanning
------------------------------
EMM386.EXE can now scan the F000h-F7FFh region when the system
read-only memory (ROM) is duplicated between F000h-F7FFh and
F800h-FFFFh. Also, EMM386.EXE will include the ROM BASIC area on IBM
PS/2 systems.
To enable advanced upper memory scanning, add the HIGHSCAN switch to
the device= line for EMM386.EXE in the CONFIG.SYS file.
Expanded and Extended Memory Sharing
------------------------------------
Previous versions of EMM386.EXE allocated as much extended memory
memory as possible during the initialization phase. This tied up
memory that could otherwise have been used by programs that use
expanded memory. EMM386.EXE version 4.45 includes support for dynamic
allocation of memory. This means EMM386.EXE can create and make
available different types of memory as your system requirements
change.
Ability to Provide Upper Memory Regions for Windows
---------------------------------------------------
EMM386.EXE version 4.45 includes a new WIN= switch that defines upper
memory regions available for use by Windows. These regions are similar
to X= regions; memory is not mapped to those areas. But unlike X=
regions, Windows (in 386 enhanced mode) can map its own memory into
these upper memory regions and make more conventional memory available
to MS-DOS-based applications running with Windows.
Ability to Load with No Page Frame
----------------------------------
Previous versions of EMM386.EXE do not load if expanded memory support
is enabled and there is not enough contiguous available address space
for an expanded memeory page frame. To support MEMMAKER.EXE,
EMM386.EXE 4.45 displays a warning message and continues to load when
this situation occurs.
NOVCPI Switch for Smaller Load Size
-----------------------------------
Previous versions of EMM386.EXE disable both expanded memory and
virtual control program interface (VCPI) support when the NOEMS switch
is used. EMM386.EXE 4.45 leaves VCPI support enabled by default when
the NOEMS option is used, relying on the expanded and extended memory
sharing enhancement to supply VCPI memory.
VCPI support can be disabled with the new NOVCPI switch. Using NOEMS
and NOVCPI together results in a reduction in the amount of extended
memory used by EMM386.EXE.
Token Ring Adapter Detection
----------------------------
EMM386.EXE automatically detects the memory location of IBM Token Ring
adapter cards and prevents the mapping of expanded or upper memory
over the adapter. The new Token Ring adapter detection can be disabled
by using the new NOTR command line switch.
Quiet Loading
-------------
By default, EMM386.EXE version 4.45 displays messages only if it
encounters an error condition. Adding the /VERBOSE (or /V) switch to
the EMM386 line in the CONFIG.SYS file forces EMM386.EXE to display
status and error messages while loading.
To display status messages without adding the /V switch, press and
hold down the ALT key while EMM386.EXE starts and loads.
For more information on the EMM386.EXE switches, type "help emm386"
(without the quotation marks) at the MS-DOS command prompt.
Ability to Provide ROM Shadowing
--------------------------------
EMM386.EXE version 4.45 includes a new ROM= switch that defines
regions of read-only memory (ROM) for EMM386.EXE to "shadow."
EMM386.EXE copies the contents of the ROM to extended memory (RAM) and
maps the ROM addresses to this memory. Specifying this switch can
speed up your system if it does not already use shadow RAM.
Additional reference words: 6.00 XMS EMS free up
-=-=-=-=-=-
ARTICLE-ID:Q93377
TITLE :Changes Made to SYSTEM.INI by MS-DOS 6.0 MemMaker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system version 3.0
--------------------------------------------------------------------
Summary:
When you run MS-DOS 6.0 MemMaker, the final screen displays the
following message:
If MemMaker changed your Windows SYSTEM.INI file,
the original file was saved as SYSTEM.UMB.
The Windows SYSTEM.INI file is only changed if you are running Windows
3.0.
More Information:
MemMaker changes the SYSTEM.INI file only when certain options are
selected prior to memory optimization. The following lists all
possible changes to the Windows 3.0 SYSTEM.INI file:
SYSTEMROMBREAKPOINT=FALSE
EMMEXCLUDE=A000-FFFF
EMMINCLUDE=
DUALDISPLAY=TRUE if b000-b7ff is included
NOEMMDRIVER=TRUE if NOEMS is specified
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93654
TITLE :Using the [common] Section with Multiple Configurations
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use multiple configurations in your CONFIG.SYS file, you should
use a [common] section for the device drivers and environment
statements you would normally use for all of your configurations.
If you place the [common] section at the end of your CONFIG.SYS file,
you greatly increase the chances that a setup or installation program
will correctly update your CONFIG.SYS file.
For example, when you install a CD-ROM drive, the installation
software adds the device driver to the CONFIG.SYS file. It will
probably add the device driver at the bottom, in the [common] section.
If you had [Development] as your last section, the CD-ROM driver would
be available only under that configuration, instead of every
configuration.
Additional reference words: 6.0 multi config multi-configuration
-=-=-=-=-=-
ARTICLE-ID:Q93655
TITLE :Changes to MS-DOS 6.0 MSCDEX Version 2.22
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 provides a new version of MSCDEX, which is version 2.22.
The following changes were implemented when MSCDEX.EXE was revised
from version 2.21 to version 2.22:
- MSCDEX now loads into UMA using "lh mscdex ..."
- MSCDEX is no longer version dependent
- The /V switch now reports reasonable memory statistics
- Cosmetic changes
More Information:
MSCDEX Now Loads into UMA Using "lh mscdex ..."
-----------------------------------------------
If there is enough memory available, MSCDEX version 2.21 and earlier
can load into upper memory. MSCDEX version 2.21 and earlier require
the load size of MSCDEX (which varies for different configurations)
plus 48K of memory to load. Development added the 48K requirement to
ensure there is enough memory to load COMMAND.COM.
Therefore you need to have a block of memory (conventional or upper)
equal to the MSCDEX load size plus 48K to load version 2.21 or
earlier.
MSCDEX version 2.22 checks to see if the driver is being loaded above
640K. If it is, MSCDEX does not add 48K to the initialization load
size because it doesn't need to be concerned with the transient
portion of COMMAND.COM.
MSCDEX Is No Longer Version Dependent
-------------------------------------
If you are using MS-DOS 5.0 or 6.0, earlier version of MSCDEX require
you use SETVER.EXE to tell MSCDEX the MS-DOS version is 4.0.
This is no longer required with version 2.22.
The /V Switch Now Reports Reasonable Memory Statistics
------------------------------------------------------
The /V switch now reports accurate memory statistics. Earlier versions
of MSCDEX were not accurate.
Cosmetic Changes
----------------
The version number incremented from 2.21 to 2.22 and the copyright
message has been updated to include 1993.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93678
TITLE :Differences Between SMARTDrive Version 4.0 and 4.1
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following enhancements have been made to SMARTDrive version 4.1:
- Corrections to minor problems for better handling bad sectors
- SMARTDrive now supports DoubleSpace
More Information:
Corrections to Minor Problems for Better Handling Bad Sectors
-------------------------------------------------------------
SMARTDrive version 4.1 includes the following corrections:
- SMARTDrive now correctly deals with bad sectors.
- SMARTDrive now correctly handles the int 21 function 68h (Commit
File) carry flag.
SMARTDrive Now Supports DoubleSpace
-----------------------------------
If a DoubleSpace volume is mounted before SMARTDrive version 4.1 is
loaded, it caches the DoubleSpace host drives. This functionality is
similar to the way SMARTDrive version 4.0 (and 4.1) works with
Stacker. The caching of DoubleSpace through the host drive is
accomplished using a special interface to the DoubleSpace components.
If you specify a DoubleSpace drive on the SMARTDrive command line, you
get the following error message:
You must specify the host drive for a DoubleSpace drive.
To use SMARTDrive with DoubleSpace, you must specify the host drive.
SMARTDrive lists DoubleSpace drives with an asterisks (*), indicating
that caching is really done via the host drive.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q93679
TITLE :Setup Is Unable to Read Uninstall Disk on a COMPAQ
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using SMARTDrive to cache a floppy disk on a COMPAQ
machine, MS-DOS 6 Upgrade may not be able to read the Uninstall disk.
This problem occurs due to a problem in the COMPAQ BIOS. The problem
occurs when SMARTDrive is loaded into upper memory because all floppy
disk data transfers go through the upper memory blocks (UMBs).
To workaround this problem, edit your AUTOEXEC.BAT file so it loads
SMARTDrive in conventional memory with the following command:
smartdrv /l
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93777
TITLE :Corrupt Swap File Warning After Removing Compressed Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0, 3.0a, and 3.1
--------------------------------------------------------------------
Summary:
You may receive a corrupt swap file warning message from Windows after
removing a compressed drive. Because you remove a compressed drive
manually, DoubleSpace cannot update permanent or temporary swap file
settings in SYSTEM.INI or SPART.PAR. Drive letters change resulting in
the corrupt swap file warning because Windows cannot find the swap
file. To restore your swap file settings, run the 386 Enhanced icon
from Control Panel.
Additional reference words: 6.00 3.00 3.00a 3.10 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q93778
TITLE :MS-DOS Setup Doesn't Install Windows-Based Utilities
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Setup does not install Windows-based MS-DOS utilities if it does not
find a Windows installation. After you install Windows you can run
SETUP /E from the MS-DOS 6.0 upgrade disks to install the optional
components for Windows.
Setup does not install Windows-based utilities because it cannot
update SYSTEM.INI, WINFILE.INI or PROGMAN.INI.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93923
TITLE :Error Using LOADHIGH (LH) With Third-Party Shell
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Third-party command interpreters (sometimes called shells) such as
4DOS and NDOS are designed to replace COMMAND.COM. These command
interpreters have to be updated to work correctly with the new MS-DOS
6.0 LOADHIGH (LH) parameters (/L and /S). If you use the /L or /S
parameters with NDOS or 4DOS, you receive the following error message:
Error: Unknown Command "/l:;"
More Information:
MS-DOS 6.0 COMMAND.COM supports two memory specific parameters: /L and
/S, which are determined by MemMaker. For example, "LOADHIGH /L:0;1
MOUSE.COM" is a valid command in MS-DOS 6.0.
Third-party command interpreters such as 4DOS and NDOS have to be
updated to work correctly with these new parameters.
Workaround
----------
To workaround the problem, either use COMMAND.COM for your command
interpreter or remove the /L and /S parameters from your LOADHIGH (LH)
commands.
For more information or to obtain an update to your third-party
command interpreters, please contact your command interpreter vendor.
Additional reference words: 6.0 3rd party 3rdparty replacement shell
shell= four dos 4 dos third
-=-=-=-=-=-
ARTICLE-ID:Q94024
TITLE :Exclude DASDDRVR.SYS When Running MemMaker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker on an IBM PS/2 model 70, you should run it in
the Custom installation mode and exclude the following device driver:
DASDDRVR.SYS
DASDDRVR.SYS is an IBM system patch recommended by IBM for all PS/2s
manufactured prior to June 1991. DASDDRVR.SYS stays resident only if
it detects that your PS/2 needs the patch. If this is the case, it
should install before other drivers that may make calls to the ROM
BIOS (such as HIMEM.SYS and EMM386.EXE).
To work around this problem:
1. Run MemMaker in Custom mode and exclude DASDDRVR.SYS.
For more information on running MemMaker in Custom mode, see
Chapter 6, "Making More Memory Available," in the "MS-DOS 6 User's
Guide."
2. Edit the CONFIG.SYS file with a text editor and make the
DASDDRVR.SYS line the first line in the file.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94131
TITLE :MemMaker Values for Memory Change Don't Match
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When MemMaker reports values in the Change column for conventional
memory and upper memory, the values may not be the same. For example,
MemMaker may report you have 58K more conventional memory and 62K less
memory in the upper memory area (UMA).
Under ideal conditions, these two numbers are the same. If one of the
following conditions exist, the values for the change in conventional
and upper memory don't match:
- A program that loads itself into the UMA changes size (for example,
SMARTDRV.EXE)
- The expanded memory manager (EMM) that MemMaker loads (EMM386.EXE)
utilizes the UMA differently from the current EMM
- A program that MemMaker configured to load into the UMA did not
because of an unanticipated problem.
Additional reference words: 6.0 not memory maker
ARTICLE-ID:Q95997
TITLE :DELTREE: No Error Message If Directory Does Not Exist
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When the DELTREE.EXE command is executed on a directory that does not
exist, no error message is displayed and you are returned to the
MS-DOS prompt. This behavior can be misleading if you mistype a
directory name--since no error message is displayed, you may think
that the directory you were trying to delete was successfully deleted.
More Information:
If the directory you want to delete is specified correctly with the
DELTREE.EXE command, you will receive the following message:
Delete directory
[yn]
where
You are required to answer "y" to delete the entire subdirectory or
"n" to cancel the operation.
For more information on the DELTREE command, type "HELP DELTREE"
(without the quotation marks) at the command prompt.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94568
TITLE :MWAV.EXE Cannot Clean FORMS Virus But MSAV.EXE Can
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If Microsoft Anti-Virus for Windows detects the FORMS virus, the following
generic message is displayed:
The virus infecting this disk has not been analyzed by Central Point
Software. As a result, the virus cannot be removed. See your "MS-DOS 6
User's Guide" for information about updating Microsoft Anti-Virus so you
can detect and remove the latest viruses.
Microsoft Anti-Virus for Windows cannot clean the FORMS virus but the
MS-DOS-based version of Microsoft Anti-Virus (MSAV.EXE) can.
More Information:
If you do not have the MS-DOS-based version of Microsoft Anti-Virus
installed, run SETUP /E to install the optional utilities. For more
information on SETUP /E, see page 4 of the "MS-DOS 6 User's Guide."
Additional reference words: 6.00 form forms
-=-=-=-=-=-
ARTICLE-ID:Q94569
TITLE :Compression Software Doesn't Load After Running MemMaker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you run MemMaker with a third-party disk compression program, such as
Stacker or SuperStor, MemMaker cannot undo the changes in the CONFIG.SYS
and AUTOEXEC.BAT files after a failed boot attempt.
More Information:
If a reboot attempt fails, MemMaker provides a Cancel button to undo
changes. MemMaker attempts to undo all changes to your CONFIG.SYS and
AUTOEXEC.BAT files on the host drive but cannot because the compressed
drive in no longer mounted.
Although MemMaker correctly detects compression on the system and verifies
that the CONFIG.SYS and AUTOEXEC.BAT files match, the problem still occurs
because CHKSTATE.SYS is loaded before the disk-compression software.
MemMaker is able to restore the files on the host drive, but not on the
compressed volume (which is swapped with the host AFTER the disk-
compression software is loaded).
To restore your computer to its previous state, copy and rename the
AUTOEXEC.UMB and CONFIG.UMB files from the host drive to the compressed
volume after you choose the MemMaker Cancel option. For example, if drive D
is the uncompressed host drive and drive C is the compressed volume, use
the following commands:
copy d:\autoexec.umb c:\autoexec.bat
copy d:\config.umb c:\config.sys
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94639
TITLE :Troubleshooting MS Backup and MS Backup for Windows
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0, 3.0a, and 3.1
--------------------------------------------------------------------
Summary:
If you encounter problems running Microsoft Backup for MS-DOS or Microsoft
Backup for Windows, use the steps in the following section to correct the
problems.
Common problems caused by incorrect system configuration include:
- Microsoft Backup appears to stop responding (hang) when run from the
MS-DOS Prompt under Windows.
- Microsoft Backup reports problems accessing the second floppy disk
drive during the compatibility test when run from MS-DOS Prompt under
Windows. Microsoft Backup either displays the following error message or
continues to ask for the first disk after you have inserted the second
one.
Diskette not properly seated.
- Microsoft Backup for Windows causes Windows to close, leaving the
command prompt displayed on the screen.
- Windows reports that the DMA buffer size needs to be increased to 64.
Troubleshooting Microsoft Backup for Windows and Microsoft Backup
-----------------------------------------------------------------
1. Microsoft does not recommend or support running the MS-DOS-based
version of Microsoft Backup (MSBACKUP.EXE) with Windows. If you choose
to do this, you should create a program information file (PIF) for
Microsoft Backup with the following settings:
Display Usage: Full Screen
Execution: Exclusive
2. Your CONFIG.SYS file should include the following settings (the values
shown are minimums):
FILES=30
BUFFERS=30
STACKS=9,256
3. The DMABufferSize= line should be set to at least 32 in the [386Enh]
section of the SYSTEM.INI file.
Additional reference words: 6.00 3.00 3.00a 3.10 win31 win3 win30 ms-dos
backup
-=-=-=-=-=-
ARTICLE-ID:Q94666
TITLE :Difficult to Use F5 & F8 Keys on Data General Computers
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Data General machines may have difficulty accepting input from the F5 and
F8 keys, which are used to bypass or step through the CONFIG.SYS and
AUTOEXEC.BAT files. You must press the F5 or F8 key immediately after
hearing the first beep from your computer BIOS at system startup. You may
have to press the F5 or F8 key many times.
On most computers, you have a few seconds to press the F5 or F8 key after
you see the "Staring MS-DOS..." prompt and hear the beep.
For more information, contact Data General.
Additional reference words: 6.00 function key keys
-=-=-=-=-=-
ARTICLE-ID:Q94722
TITLE :Running MemMaker to Optimize a Startup Floppy Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker to optimize a startup (boot) floppy disk, it
incorrectly prompts you to "Remove all floppy disks from your floppy-disk
drives and then press Enter." Although MemMaker specifically supports the
optimization of a startup floppy disk, it displays a generic prompt that
assumes you are optimizing drive C.
To work around this problem, ignore the message to remove all floppy disks,
and press ENTER to restart your computer.
More Information:
To optimize a startup floppy disk, you must run MemMaker from drive A. If
you do not, MemMaker optimizes the startup files on your hard disk drive.
To start MemMaker from drive A:
1. Change to drive A.
2. Start MemMaker. (To do this, type "memmaker" (without the quotation
marks and then press ENTER).
Note: When you run MemMaker to optimize a startup floppy disk, you must
have the following five files on the floppy disk in drive A.
CHKSTATE.SYS
EMM386.EXE
HIMEM.SYS
MEMMAKER.EXE
SIZER.EXE
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94772
TITLE :MemMaker Err Msg with Perscope: UMB's Overran List Buffer
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker detects the protected memory used by the Periscope board, but it
does not exclude the range correctly resulting in the following error
message:
UMB's overran list buffer
To work around this problem, add the x= switch to the device= line for
EMM386 to exclude the C800-CFFF range. For example:
device=c:\dos\emm386.exe x=c800-cfff
More Information:
MemMaker detects the first 24 kilobytes (K) of memory used by the Periscope
board but does not detect the last 8K. Therefore, when MemMaker adds the x=
parameter, it does not exclude a large enough range.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94775
TITLE :Disks Created by MS-DOS 6 Upgrade Using SETUP /F
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
With MS-DOS 6 Upgrade, you can create a single startup floppy disk for
drive A using the /F parameter. The contents of this disk vary based on
disk capacity.
Note: MS-DOS 6 Upgrade does NOT have the ability to install the complete
operating system (with all programs) to floppy disks.
More Information:
Floppy Disk Contents for SETUP /F:
File
Filename Attributes Disk Size
---------------------------------------------------------
360K 720K 1.2MB 1.44MB
(5.25") (3.5") (5.25") (3.5")
IO.SYS SHR X X X X
MSDOS.SYS SHR X X X X
COMMAND.COM R X X X X
DBLSPACE.BIN SHR X X X X
ATTRIB.EXE A X X X X
DEBUG.EXE A X X X X
EXPAND.EXE A X X X X
FDISK.EXE A X X X X
FORMAT.COM A X X X X
RESTORE.EXE A X X X X
SYS.COM A X X X X
CHKDSK.EXE A X X X X
EDIT.COM A X X X
QBASIC.EXE A X X X
XCOPY.EXE A X X
MSD.EXE A X X
MSAV.EXE A X X X
DBLSPACE.EXE A X X
Additional reference words: 6.00 floppy diskette
-=-=-=-=-=-
ARTICLE-ID:Q94815
TITLE :MSD Err Msg: Error Writing Bad File Number
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you attempt to print a Microsoft Diagnostics (MSD) report to an inactive
port, you receive the following error message:
Error Writing Bad File Number
To correct this problem, print to an active port.
Additional reference words: 6.00 win31 win wfw wfwg
-=-=-=-=-=-
ARTICLE-ID:Q94329
TITLE :MS-DOS 6 OEM Setup Doesn't Boot on Tandy 1000TX 286
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some Tandy 1000TX 286 computers have a 3.5-inch floppy disk drive that
can be configured as a 360K drive. If the drive has been reconfigured,
the MS-DOS 6 OEM 720K Disk 1 will not start (boot) the computer.
Workaround
----------
To work around this problem:
1. Modify or create the CONFIG.SYS file on Disk 1, and add the
following line:
DRIVPARM=/d:0 /f:2
2. Boot the system using this disk.
Setup should now run normally.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94985
TITLE :MemMaker Fails to Undo Changes to CONFIG.SYS File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If your AUTOEXEC.BAT, CONFIG.SYS, or Windows SYSTEM.INI file is marked as
read-only, MemMaker displays the following error message:
MemMaker cannot continue because it cannot gain access to the
AUTOEXEC.BAT, CONFIG.SYS, or Windows SYSTEM.INI file. Make sure the
read-only attribute for those files is not set.
To undo MemMaker's changes, press ENTER.
If your AUTOEXEC.BAT file or SYSTEM.INI file is marked read-only but the
CONFIG.SYS file is not, MemMaker does not undo the changes it made to the
CONFIG.SYS file.
To work around this problem, remove the read-only attribute on the
AUTOEXEC.BAT and/or SYSTEM.INI file and restart MemMaker. To remove the
read-only attribute on the AUTOEXEC.BAT and/or SYSTEM.INI files, use the
ATTRIB command as follows:
attrib c:\autoexec.bat -r
-and/or-
attrib c:\windows\system.ini -r
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95955
TITLE :Configuring MSCDEX for Multiple CD-ROM Drives
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft CD-ROM Extensions (MSCDEX) can control multiple CD-ROM
drives. To configure your system to do this, you must make some
adjustments to the parameters on your CD-ROM driver in the CONFIG.SYS
file and to the MSCDEX command in your AUTOEXEC.BAT file.
More Information:
MSCDEX uses the /D:MSCDxxx parameter to differentiate between the
drives. For example, the following commands assign the Creative Labs
CD-ROM driver (SBPCD.SYS) to drive m and the external CD-ROM
(TSLCDR.SYS) to drive n:
CONFIG.SYS File
---------------
device=c:\sbpro\sbpcd.sys /d:mscd001 /p:220
device=c:\scsi\tslcdr.sys /d:mscd000
AUTOEXEC.BAT File
-----------------
mscdex /d:mscd001 /l:m /d:mscd000 /l:n
Note: Because MS-DOS treats CD-ROM drives like network drives, you can
assign them to any available drive letter.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94867
TITLE :Err Msg after Running MemMaker: Double-Buffering Driver...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you have a device= statement for SMARTDRV.EXE in your CONFIG.SYS file,
but you are not using the /DOUBLE_BUFFER switch, MemMaker may change the
device= statement to devicehigh=. If so, you receive the following error
message:
Double-buffering driver cannot be loaded into a UMB.
Do not use the devicehigh command or other load-high
utilities to load Smartdrv.exe
To correct this problem, in the CONFIG.SYS file, change the devicehigh=
statement for SMARTDRV.EXE to device= and add the /DOUBLE_BUFFER switch,
then run MemMaker again.
More Information:
MemMaker recognizes and ignores the device= statement for SMARTDRV.EXE only
if you are using the /DOUBLE_BUFFER switch.
A device= statement in the CONFIG.SYS file does not load the SMARTDrive
cache; it loads only the double-buffering device driver embedded in the
SMARTDRV.EXE file. This device driver cannot be loaded into upper memory.
For more information on SMARTDrive and double buffering, query on the
following words in the Microsoft Knowledge Base:
smartdrive and double and buffer and bus and mastering
Additional reference words: 6.00 line
-=-=-=-=-=-
ARTICLE-ID:Q94891
TITLE :Why MemMaker Doesn't Work with Multi-Config Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
This article explains why MemMaker doesn't work with MS-DOS Multi-Config
files.
Important: You can use MemMaker with multiple configurations, but doing so
requires creating separate configuration files to run MemMaker. For more
information, see the "Using MemMaker with Multiple Configurations" section
in Chapter 6 of the "MS-DOS User's Guide."
More Information:
MemMaker removes all references to memory managers, the FILES= statement,
the BUFFERS= statement, and the DOS= statement. It then adds the following
statements at the top of the CONFIG.SYS file:
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE
buffers=
files=
dos=umb
lastdrive=
FCBS=
[Everything else remains in the same order]
Note: The
specific installation and configuration.
Because of this design, MemMaker cannot work with configuration files that
contain Multi-Config sections that reference multiple memory managers or
have different memory configurations.
MemMaker also uses a program called SIZER.EXE to determine memory
requirements for device drivers and terminate-and-stay-resident (TSR)
programs. MemMaker analyzes the contents of the entire CONFIG.SYS and
AUTOEXEC.BAT files (regardless of Multi-Config headings) to calculate the
optimum memory configuration for your system. Because the files are viewed
as a single unit, each individual configuration will not be optimized after
you run MemMaker.
Additional reference words: 6.00 MULTICONFIG
-=-=-=-=-=-
ARTICLE-ID:Q94940
TITLE :Interlnk Cannot Access CD-ROM Drives
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Interlnk cannot access CD-ROM drives. Interlnk accesses drives using a
block device driver. This means that Interlnk can recognize standard drives
but not network drives. Because CD- ROM drives use a network interface,
Interlnk cannot be used to access them.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95998
TITLE :SmartMon Incorrectly Reports Cache Status with DBLSPACE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The SMARTDrive Monitor (SMARTMON.EXE) provides an interface to the
performance of SMARTDrive 4.0, the disk cache included with MS-DOS 6.
If you attempt to turn on caching for a DBLSPACE drive by typing the
SMARTDRV.EXE command at the command prompt, you receive an error
message indicating that you must specify the host drive rather than
the compressed drive.
However, if you are using the SMARTDrive Monitor and you select the
compressed drive and then select the Cache Reads And Writes button,
this action is ignored and you do not receive an error message. When
SmartMon is reloaded, it defaults back to no read or write cache on
the DBLSPACE drive.
Microsoft has confirmed this to be a problem in SmartMon version 3.1.
We are researching this problem and will post new information here in
the Microsoft Knowledge Base as it becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95182
TITLE :DXMC0MOD.SYS Err Msg: Invalid Shared RAM Address
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Due to a difference in line parsing between the DEVICE and DEVICEHIGH
commands you may receive one of the following error messages when the
IBM network device driver, DXMC0MOD.SYS, loads:
Invalid shared RAM address
-or-
Invalid early token ring release
After these error messages are displayed, the DXMC0MOD.SYS device
driver does not load and the network fails to start. This occurs most
often after MemMaker has been used, and DEVICE commands have been
changed to DEVICEHIGH.
To enable your network to start and avoid these error messages, make
sure enough commas are used in the DXMC0MOD.SYS statement to act as
delimiters for the three optional parameters required by DXMC0MOD.SYS.
For example, each of the following lines cause error messages to be
displayed:
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001,D800
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS ,D800
To avoid these errors, change each line to the following:
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001,,
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS 400000000001,D800,
DEVICEHIGH=C:\LSP\DXMC0MOD.SYS ,D800,
More Information:
This problem is caused by the manner in which DEVICEHIGH parses
command lines. The DXMC0MOD.SYS device driver does not correctly
interpret the DEVICEHIGH parameter information.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95203
TITLE :Err Msg: SmartMon Unable to Save the New Cache Settings
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows Resource Kit version 3.1
--------------------------------------------------------------------
Summary:
If you used SMARTDrive Monitor (SmartMon) to change SMARTDrive's
cache settings, you may receive the following error message after
exiting SmartMon:
SmartMon is unable to save the new cache settings in the specified
batch file.
This error message is displayed when SmartMon is unable to find the
SMARTDrive command line in the AUTOEXEC.BAT file. This may be due to
the fact that SmartMon does not recognize the LH command and /L switch
when they are used together. For example, SmartMon cannot modify the
following line:
lh c:\dos\smartdrv.exe /l
To work around this problem, change the cache settings by manually
editing the AUTOEXEC.BAT file.
Microsoft has confirmed this to be a problem in SmartMon version 3.1.
We are researching this problem and will post new information here as
it becomes available.
Additional reference words: 6.00 smartdrive smartdrv monitor
-=-=-=-=-=-
ARTICLE-ID:Q95204
TITLE :MS-DOS 6.0: ANSI.SYS Turns Off Menu Colors
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are loading the ANSI.SYS driver, MS-DOS 6.0 multiple
configuration colors set with the menucolor= setting are reset to the
default colors.
More Information:
The menucolor= setting in the CONFIG.SYS file allows you to define
your menu colors. When ANSI.SYS is loaded through one of the menu
blocks, the screen colors are reset. This occurs because ANSI.SYS is a
block device for the console (CON). ANSI.SYS takes over all output to
the console and manipulates the data in an ANSI (American National
Standards Institute) format.
ANSI.SYS turns off the menu colors because it does not detect the
previous state of the CON device.
Additional reference words: 6.00 multiconfig multi-config
-=-=-=-=-=-
ARTICLE-ID:Q95288
TITLE :InterLnk Causes Extra Drive Letters in File Manager
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0, 3.0a, and 3.1
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
If Interlnk is loaded in the CONFIG.SYS file, Microsoft Windows File
Manager indicates the presence of the Interlnk drives with removable
media icons (sometimes called "floppy icons"). If Interlnk is loaded
but you don't have an active connection to another computer, you will
receive the following error message when you try to access one of the
Interlnk drives:
Error Selecting Drive
There is no disk in drive x.
Insert a disk, and then try again.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95348
TITLE :Converting Stacker Compressed Removable Disks
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
To convert a Stacker-compressed floppy disk, you must have
approximately 900K of free disk space on the removable disk. To
convert a Stacker-compressed removable media disk (such as Bernoulli
disks and removable optical disks) you must have approximately 1
megabyte (MB) of free disk space on the removable disk. The free disk
space can be either at the end of the Stacker volume file (SVF) or on
the uncompressed portion of the disk.
If you do not have enough free disk space to compress a removable disk
and you cannot remove any files to create more free disk space (or the
disk capacity is less than 900K [360K or 720K]), use the procedure
below (which was taken from the README.TXT file).
More Information:
DoubleSpace requires 900K free disk space so it can create a 512K
DoubleSpace compressed volume file (CVF). DoubleSpace also requires
400K-500K free disk space so it can internally unfragment a highly
fragmented SVF.
If DoubleSpace cannot convert a Stacker-compressed volume file due to
disk space limitations, do the following:
1. Insert the floppy disk in drive A or B.
2. Move the STACVOL.DSK file to the host drive on your hard disk. If
you don't know which drive is your host drive, start DoubleSpace by
typing DBLSPACE at the command prompt and choosing the Info command
from the Drive menu. Exit DoubleSpace.
When you move the file, change its extension to .001. For example
if the floppy disk is in drive A, and your host drive is drive D,
type the following at the command prompt:
move a:\stacvol.dsk d:\stacvol.001
If you have insufficient disk space, start DoubleSpace by typing
DBLSPSACE at the command prompt, and choose Change Size from the
Drive menu. Make the size of the uncompressed drive large enough to
contain the Stacker-compressed volume file.
3. If are using Stacker version 2.0, delete the STACKER.DRV file on
the floppy disk. If you are using Stacker version 3.0, delete the
STACKER.EXE and README.STC files.
4. Covert the compressed volume file to DoubleSpace format, as in the
following example:
dblspace /convstac=d:\stacvol.001
After DoubleSpace converts the file it will mount it.
5. Make sure your floppy disk is in drive A or B and then compress it
by choosing the Existing Drive command from the Compress menu in
DoubleSpace. Follow the instructions on your screen.
DoubleSpace mounts the floppy drive after it finishes
compressing the floppy disk.
6. Exit DoubleSpace.
7. Use the XCOPY command to copy all the files on the new compressed
drive on your hard disk to the compressed floppy disk. For example,
if the compressed drive is J, and the floppy disk is in drive A,
type the following at the command prompt:
xcopy j:\*.* a: /s
8. Delete the compressed drive on your hard disk. For example, if your
compressed drive is J, type the following at the command prompt:
dblspace /delete j:
To confirm the deletion, type "Y" (without the quotation marks).
Additional reference words: 6.00 svf cvf syquest floppy disk drive
removable media
-=-=-=-=-=-
ARTICLE-ID:Q94330
TITLE :DoubleSpace Setup Runs in Mono on Some Older 8514 Cards
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Microsoft DoubleSpace setup and configuration program
(DBLSPACE.EXE) runs in monochrome on the following 8514 video cards:
- Original IBM 8514 video cards. This behavior does not occur on
newer 8514 cards, or on ATI Ultra cards in 8514 mode.
- Paradise 8514/A cards.
This problem occurs due to a limitation of the cards, not DoubleSpace.
Additional reference words: 6.0 mono monochrome mono-chrome black and
white b&w amber dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95349
TITLE :Cannot Open More Than One File at a Time with EXPAND
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS Help contains a phrase that may be unclear. The help file
states that the filename parameter:
Specifies the location and name of a compressed file or files
The EXPAND command does not support wildcards (such as * and ?) and
cannot expand more than one file at a time.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94386
TITLE :Insufficient Memory Error Message with DBLSPACE /RATIO
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
If you run DBLSPACE /RATIO before the NET command is used in the
AUTOEXEC.BAT file, you may receive an insufficient memory error message.
This problem occurs when the network has not released the memory used
during loading because network binding has not yet occurred.
More Information:
It is not necessary to run DBLSPACE /RATIO from the AUTOEXEC.BAT file since
DoubleSpace reliably reports the amount of free disk space. However, if you
want to run DBLSPACE /RATIO from the AUTOEXEC.BAT file, run the NET START
command before you run DBLSPACE /RATIO as in the following example:
c:\windows\net start
c:\dos\dblspace /ratio
Additional reference words: 6.00 wfw wfwg
-=-=-=-=-=-
ARTICLE-ID:Q96083
TITLE :DoubleSpace Err Msg: Drive is Too Fragmented to Resize
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
When you try to resize a DoubleSpace drive and the MS-DOS 5.0 MIRROR
program is installed, you may receive the following error message
Drive C is too fragmented to resize. Before resizing drive
C, defragment it by typing DEFRAG.EXE /H /Q x: at the MS-DOS
command prompt
where x is the drive letter of the compressed drive.
Running DEFRAG /H /Q C: does not solve the problem; you still cannot
resize the DoubleSpace drive.
This problem occurs because MIRROR is creating a file called
MIRORSAV.FIL at the end of the drive. In most cases, DoubleSpace
cannot resize a drive if there is an unmovable file near the end of
the drive. Since the file has Read-only, Hidden, and System file
attributes set, it cannot be moved when you run Defragmenter
(DEFRAG.EXE).
If you do not use MIRROR, it is possible that another program has
placed a file with its System attribute set near the end of the drive.
More Information:
You can use the ATTRIB command to removed the file attributes on the
MIRROR file. For example, if the file is on drive C, issue the
following command from the MS-DOS command prompt:
attrib -s c:\mirorsav.fil
After running Defragmenter with the parameters suggested in the error
message, you should be able to resize the DoubleSpace drive.
Additional reference words: 6.00 dblspace doublespace
-=-=-=-=-=-
ARTICLE-ID:Q94387
TITLE :Setup Creates OLD_DOS.x Directory with /G & /H Switches
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Although you don't have the option to uninstall if you install Microsoft MS-
DOS 6 Upgrade using the /G and /H switches together, Setup still creates an
OLD_DOS.x directory. Because you cannot uninstall, it is safe to delete the
OLD_DOS.x directory using DELOLDOS.EXE.
More Information:
Setup /G disables the Uninstall feature of MS-DOS. Setup /H installs MS-DOS
with very few prompts for user input and cannot be used without the /G
switch.
Setup uses the OLD_DOS.x directory to create temporary CONFIG.SYS and
AUTOEXEC.BAT files when it modifies them. Setup does not copy any other MS-
DOS files to this directory when you install MS-DOS 6 Upgrade using the /G
and /H switches together.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94388
TITLE :Modifying MS-DOS Help Command Reference
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Microsoft MS-DOS 6 Help Command Reference can be customized to add site-
specific information and annotations with the HELPMAKE.EXE program supplied
with Microsoft C Compiler. Corporate sites, network administrators, and
computer consultants can modify the MS-DOS 6 Help Command Reference by
using HELPMAKE.EXE to decode and recompile the help file (HELP.HLP).
For more information on modifying help files, refer to the Microsoft C
Compiler documentation. To order Microsoft C, call Microsoft Consumer Sales
(800) 426-9400.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94411
TITLE :MemMaker Doesn't Optimize Batch Files in AUTOEXEC.BAT
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If a third-party memory manager has optimized memory by using specific
loading programs or parameters within batch files, the following error
message is displayed after you run MemMaker:
Bad Command or Filename
Note: You may also receive error messages from the third-party expanded
memory manager (EMM) if commands such as LOADHI (from QEMM) are called.
More Information:
Some third-party memory managers optimize one or more levels deep in batch
files called from the AUTOEXEC.BAT file, trying to load programs in upper
memory. MemMaker does not analyze software called from batch files within
the AUTOEXEC.BAT file, but instead treats the whole batch file as one
entity and attempts to load it in upper memory.
If you receive error messages because commands specific to third-party EMMs
are still in your batch files, edit the files and remove the third-party
specific information.
For example, if you have the following QEMM command in a batch file called
from the AUTOEXEC.BAT file, you receive the following error message after
you run MemMaker:
LOADHI /R:2 doskey /insert
To work around this problem, remove the QEMM-specific information. For
example:
doskey /insert
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95436
TITLE :Why Should I Upgrade to MS-DOS 6?
---------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
---------------------------------------------------------------------
Summary:
The MS-DOS 6 Upgrade includes the following new or enhanced features:
- Microsoft DoubleSpace
- Microsoft MemMaker
- Microsoft Backup
- Microsoft Anti-Virus
- Microsoft Undelete
- MultiConfig
- Interactive Start
- Microsoft Defragmenter
- MS-DOS Help
- Enhanced SMARTDrive
- Microsoft Diagnostics (MSD)
- Interlnk
- Enhanced Commands
This article briefly describes these enhancements and their benefits to
the user.
More Information:
Microsoft DoubleSpace
---------------------
Microsoft DoubleSpace increases your available disk space by
integrating compression into the operating system. You can use
DoubleSpace to increase available space on both hard disks and floppy
disks.
Microsoft MemMaker
------------------
Microsoft MemMaker is a memory-optimization program that makes it easy
to free conventional memory by moving device drivers and memory-resident
programs from conventional memory into the upper memory area (UMA). If
your computer has an 80386 or higher processor, you can use MemMaker to
increase available conventional memory so that programs run faster and
more efficiently.
Microsoft Backup
----------------
Microsoft Backup is a utility for backing up your hard disk drive.
MS-DOS 6 includes both Backup for MS-DOS, a program you can start from
the MS-DOS command prompt, and Backup for Windows, a program you can
use with Microsoft Windows.
Microsoft Anti-Virus
--------------------
Microsoft Anti-Virus can identify and remove more than 1000 different
computer viruses. MS-DOS 6 includes both Anti-Virus for MS-DOS, a
program you can start from the MS-DOS command prompt, and Anti-Virus
for Windows, a program you can use with Windows.
Microsoft Undelete
------------------
Microsoft Undelete enables you to choose one of three levels of
protection in case you accidentally delete a file. MS-DOS 6 includes
Undelete for MS-DOS, a program you can run from the MS-DOS command
prompt, and Undelete for Windows, a program you can use with Windows.
For more information about Undelete, see the chapter "Managing Your
System" in the MS-DOS 6 user's guide.
MultiConfig
-----------
MultiConfig allows you to define more than one configuration in your
CONFIG.SYS file. If your CONFIG.SYS file defines multiple
configurations, MS-DOS displays a menu that enables you to choose the
configuration you want to use each time you start your computer.
Interactive Start
-----------------
Interactive Start gives you the ability to bypass startup commands
when you turn on your computer. This feature allows you to choose
which CONFIG.SYS commands MS-DOS should carry out and whether MS-DOS
should run your AUTOEXEC.BAT file. By controlling the commands your
computer uses to start up, you can pinpoint problems more quickly and
easily.
Microsoft Defragmenter
----------------------
Microsoft Defragmenter reorganizes files on your hard disk to minimize
the time it takes your computer to access them.
MS-DOS Help
-----------
MS-DOS Help is a complete online reference to MS-DOS commands. The
reference includes information about how to type commands and their
parameters and switches, notes about commands, and examples of how to
use commands.
Enhanced SMARTDrive
-------------------
The SMARTDrive program included with MS-DOS 6 speeds up your computer
by using a disk cache, which stores information to be written to your
hard disk and writes it to the disk later, when system resources are
in less demand.
Microsoft Diagnostics
---------------------
Microsoft Diagnostics (MSD) gathers and displays technical information
about your computer.
Interlnk
--------
Interlnk enables you to easily transfer files between computers. With
Interlnk and a cable, you can access information on another computer
without having to use floppy disks to copy files to that computer.
Enhanced Commands
-----------------
The following commands have been added or enhanced for MS-DOS 6:
- The MOVE command moves one or more files from one directory or drive
to another. You can also use the Move command to rename directories.
- The CHOICE command allows you to prompt a user for input when
running a batch program. The CHOICE command allows you to display a
specified prompt, pause for user input, and return an error-level
parameter to the batch program.
- The DELTREE command deletes a directory and all of its files and
subdirectories.
Additional reference words: 6.00 feature summary dblspace multi-config
-=-=-=-=-=-
ARTICLE-ID:Q95494
TITLE :DoubleSpace Err Msg: 'Not Enough Conventional Memory...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you start your computer using the interactive startup option in
order to free enough memory to run the DoubleSpace Stacker conversion
option, you may receive the following error message after DoubleSpace
restarts your computer:
Not enough conventional memory
More Information:
When you start your computer and press the F8, F5, or SHIFT key to
free enough conventional memory to run the DoubleSpace Stacker
converter, you must also use the interactive startup option when
DoubleSpace restarts your computer. If you do not use this option, you
will not have enough memory to complete the conversion.
If you use the F5 key to bypass the CONFIG.SYS and AUTOEXEC.BAT files,
the only directory in the PATH environment variable is C:\DOS;
therefore, DoubleSpace cannot start Stacker.
Workaround
----------
To work around this situation, either use the F8 key to bypass some of
your device drives before and during the Stacker conversion process,
or remark out (REM) some of the device drivers and
terminate-and-stay-resident (TSR) programs in your CONFIG.SYS file.
Additional reference words: 6.00 reboot boot dblspace
-=-=-=-=-=-
ARTICLE-ID:Q94412
TITLE :AUTOEXEC File Is Not Processed Running 3rd-Party Shell
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some third-party command shells (such as NDOS) do not require the /P
switch (which specifies the command shell is permanent). As a result, if
you use a third-party shell without the /P switch, and set environment
variables from your CONFIG.SYS file or use MS-DOS 6 startup menus, your
AUTOEXEC.BAT file is not processed when you start your computer.
More Information:
Third-party command shells that do not require the /P switch check to see
if an environment has been created. If it has, they do not call the
AUTOEXEC.BAT file. If you use the MS-DOS 6 startup menu feature or you set
environment variables (such as PATH or PROMPT) in your CONFIG.SYS file, an
environment is created and the AUTOEXEC.BAT file is not processed.
Additional reference words: 6.00 NDOS 4DOS norton symantic
-=-=-=-=-=-
ARTICLE-ID:Q95495
TITLE :DblSpace Err: DoubleSpace Cannot Find STACKER.COM...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you run DoubleSpace and choose to convert a Stacker volume to a
DoubleSpace volume, and the Stacker directory is not in the PATH, you
receive the following error message:
DoubleSpace cannot find STACKER.COM in the path. This file is required
for Stacker conversion. Add the directory with STACKER.COM to the
path.
More Information:
When you convert a Stacker volume to a DoubleSpace volume, DoubleSpace
runs the STACKER.COM file to get information on Stacker drive mapping.
If the Stacker directory is not in the PATH environment variable, you
receive the above error message.
The Stacker directory can be removed from the PATH environment
variable after DoubleSpace has been installed.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94413
TITLE :Setup Checks for 6 Free Entries in the Root Directory
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system versions 5.0, 5.0a, and 6.0
--------------------------------------------------------------------
Summary:
The Microsoft MS-DOS installation program (SETUP.EXE) checks the root
directory of your startup drive (usually C) to determine if there is enough
room for MS-DOS files in the root directory. Is some cases, Setup may
incorrectly determine that enough room exists.
More Information:
You cannot have more than 512 entries (files or directories) in the root
directory of an MS-DOS partition. Setup does not allow you to install MS-
DOS Upgrade if you have 507 or more entries in the root directory
(including hidden files). This ensures that MS-DOS Setup can create at
least six entries.
In some cases, six entries is not enough. When Setup runs out of entries,
the installation cannot be successfully completed. For example, if you have
506 entries in the root directory, you are using PC-DOS, and you install MS-
DOS 6 Upgrade in a new directory, Setup cannot successfully install all the
files.
The information below lists all potential files and directories that may be
placed in the root directory and under what conditions they are installed.
Any combination of the factors listed below results in an incomplete
installation.
- WINA20.386 is copied to the root directory if your computer is capable
of running Microsoft Windows in 386 enhanced mode and you have Windows
version 3.0 installed.
- If you are using IBM PC-DOS, the files IBMBIO.COM and IBMDOS.COM are no
longer used but are not deleted. MSDOS.SYS AND IO.SYS are copied to the
root directory as two additional files.
- If you choose a new directory when you install MS-DOS, an additional
root directory entry is used.
- If AUTOEXEC.BAT and CONFIG.SYS are changed by Setup, the files
AUTOEXEC.OLD and CONFIG.OLD are created in the root directory.
- Setup creates an OLD_DOS.1 directory.
- If use the /E switch to install both the MS-DOS-based and the Windows-
based programs that ship with MS-DOS, Setup creates a WINDOWS directory.
(This does not apply to MS-DOS 5 Upgrade).
Workaround
----------
To work around this problem, remove unnecessary files from the root
directory and rerun Setup.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96029
TITLE :SPEEDCACHE PLUS Version 4.3 Not MS-DOS 6.0-Compatible
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Iomega's SPEEDCACHE PLUS version 4.3 is not compatible with Microsoft
MS-DOS 6.
SPEEDCACHE PLUS is used to decrease the access time on Bernoulli
drives. Iomega is testing SpeedCache with MS-DOS 6 and will make an
updated version available soon.
For more information, contact Iomega at (800) 546-5522.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95497
TITLE :Less Disk Space After Converting a Stacker Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you convert a drive from Stacker to DoubleSpace, DoubleSpace might
show that you have less compressed disk space than you had with
Stacker. This apparent disparity occurs because DoubleSpace is
thoroughly integrated with the MS-DOS operating system and can more
accurately estimate compressed disk space. In fact, you may actually
have more compressed disk space than you had before the conversion,
regardless of what was reported.
In addition, DoubleSpace continually updates its compressed disk space
estimates. As a result, as you work with a compressed drive,
DoubleSpace updates its estimates to reflect the actual current state
of file compression on your drive.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95532
TITLE :Deleting Unneeded Files After Converting a Stacker Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you want to save disk space after converting a Stacker volume file
(SVF) to a DoubleSpace compressed volume file (CVF), you can remove
most of your Stacker files.
More Information:
Since Stacker swaps the drive letters during the processing of the
CONFIG.SYS file, Stacker requires that the startup files (and files
called from the CONFIG.SYS file) be located on the uncompressed host
drive. Because DoubleSpace loads before CONFIG.SYS is processed
(unlike Stacker), you can delete any file (and directory) that Stacker
put on the host drive for CONFIG.SYS processing. These commonly
include files in the DOS and WINDOWS directories on the host drive.
In addition, you can delete AUTOEXEC.* and CONFIG.* on the host drive
since they only need to reside on the startup drive (C:).
The only files that must remain on the DoubleSpace host drive (of your
bootable partition) are DBLSPACE.BIN, DBLSPACE.INI, DBLSPACE.00X,
IO.SYS, MS-DOS.SYS, and your Windows permanent swap file if you have
one (386SPART.PAR). These files should have the following attributes:
System, Hidden, and Read-Only.
You can also safely remove the remarked out (REM) Stacker lines from
the CONFIG.SYS file, remove the Stacker directory from the PATH
environment variable in the AUTOEXEC.BAT file, and delete the Stacker
directory from the hard disk.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q94414
TITLE :OLD_DOS.x Directory Created Even if You Can't Uninstall
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Although you don't have the option to uninstall when you install Microsoft
MS-DOS 6 Upgrade on a system with a disk-compression program (such as
Stacker), Setup still creates an OLD_DOS.x directory. Because you cannot
uninstall, it is safe to delete the OLD_DOS.x directory using DELOLDOS.EXE.
More Information:
Setup uses the OLD_DOS.x directory to create temporary CONFIG.SYS and
AUTOEXEC.BAT files when it modifies them. Setup does not copy any other MS-
DOS files to this directory when you install MS-DOS 6 Upgrade over a disk-
compression program.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95745
TITLE :Err Msg with Iomega: 'MS-DOS 6 Cannot Be Installed...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you attempt install the MS-DOS 6 Upgrade on an Iomega Bernoulli
drive, you may receive the following error message:
MS-DOS 6 can not be installed because of an unrecognized partition.
Exit or install on floppy disks.
Iomega is currently working on new drivers for their drives that will
correct this problem.
For more information, contact Iomega at 1-800-546-5522. Microsoft will
post new information here as it becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94554
TITLE :HIMEM.SYS and EMM386.EXE Are Not Verbose by Default
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
In Microsoft MS-DOS version 6.0, HIMEM.SYS and EMM386.EXE do not display
any initialization information by default. When you start your computer, no
information is displayed by either device driver as CONFIG.SYS is
processed. To show data such as A20 handling switches and upper memory area
(UMA) information, you must add the /VERBOSE (/V) switch to each device
driver statement in the CONFIG.SYS file. For example:
DEVICE=C:\DOS\HIMEM.SYS /V
DEVICE=C:\DOS\EMM386.EXE NOEMS X=D000-D7FF /V
You can also display startup information by pressing the ALT key while your
computer is starting. This is useful for a one-time status check of these
drivers.
Note: If either device driver finds an error during initialization, it
automatically switches to verbose mode, displaying both the error and its
normal startup information.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96030
TITLE :Err Msg: 'DoubleSpace Cannot Continue...' with Bernoulli
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you set up DoubleSpace on a Bernoulli disk that has been
formatted with the Iomega Format utility, you may receive the
following error message:
DoubleSpace can not continue because an unrecognized error has
occurred.
If you choose the Yes button to continue setting up DoubleSpace, the
program reboots your computer and restores the original configuration
files--your data is not lost.
More Information:
The Iomega Format utility is provided with Bernoulli drives. For more
information on this utility, contact Iomega at (800) 546-5522.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95855
TITLE :Backup Err Msg: Not Ready Error Accessing Drive x
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You may receive the following error message when you back up
to a network drive using Microsoft Backup for Windows
Not ready error accessing drive x
where x is the letter of your network drive.
This error occurs when the network generates a timeout error, due to
the way MS-DOS creates a file for the backup. Therefore, this error
occurs more often with a slow server or when you're doing a very large
backup.
Workaround
----------
To work around this problem, either back up smaller portions of your
hard disk or increase your timeout setting for your network. If you
are using Microsoft LAN Manager version 2.1 or later, or a 100-percent
LAN Manager-compatible network, add the following statement to the
[workstation] section of the LANMAN.INI file.
SESSTIMEOUT=180
Additional reference words: 6.0 decnet ibm lan server lan manager
compatible
-=-=-=-=-=-
ARTICLE-ID:Q94555
TITLE :MemMaker: Order of Entries in the CONFIG.SYS File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker always modifies the CONFIG.SYS file so that the entries are in the
following order:
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE
buffers=
files=
dos=umb
lastdrive=
FCBS=
[Everything else in the same order it was already in]
The
specific installation and configuration.
More Information:
MemMaker does not have a feature that allows drivers load before any of
those listed above. If there is a problem with a specific driver that needs
to be loaded before the above lines, that driver may not function until you
manually edit the CONFIG.SYS file and move the driver to where it belongs.
To work around this problem:
1. Edit the CONFIG.SYS file and comment out (REM) the device driver you
are having problems with.
2. Run MemMaker.
3. Edit the CONFIG.SYS file and remove "REM" from the device driver.
4. Return the device driver to its previous location.
Note: If the memory configuration that MemMaker created changes when you
follow this procedure, you must manually optimize your configuration.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96061
TITLE :MS-DOS Err Msg: Could Not Copy COMMAND.COM to Target...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use the SYS command (SYS.COM) to transfer the MS-DOS startup
file to another disk and COMMAND.COM is not in the root directory of
your startup drive, you receive the following error message:
Could not copy COMMAND.COM onto target disk
More Information:
Even if the COMSPEC environment variable and the SHELL= statement in
the CONFIG.SYS file point to COMMAND.COM in a different directory,
SYS.COM still looks for COMMAND.COM in the root directory of the
startup drive.
Workaround
----------
To work around this problem, copy COMMAND.COM to the root directory of
your startup drive (see your MS-DOS manual for information about
copying files). Then, set the read-only attribute with the ATTRIB
command. For example, type the following at the MS-DOS command prompt
and press ENTER:
attrib +r command.com
Additional reference words: 6.00 SYS COMMAND COMSPEC SHELL boot err
msg
-=-=-=-=-=-
ARTICLE-ID:Q95533
TITLE :Largest Possible DoubleSpace Drive Is 512 MB
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS limit for a drive using an 8K cluster size is 512 MB
(65,536 clusters at 8192 bytes per cluster). Because DoubleSpace
supports only 8K clusters, a drive compressed with DoubleSpace is
limited to 512 MB. If your compression ration is 2:1, the physical
size of the compressed value file (CVF) will be 256 MB.
Accessing data by 8K clusters (as compared with 4K or 2K clusters)
increases the speed of the disk read times (in most cases). With an 8K
cluster size, the MS-DOS kernel reads in more sectors than it would
with a smaller cluster size.
For more information on cluster sizes, query on the following words in
the Microsoft Knowledge Base:
cluster and logical and ms-dos
Additional reference words: 6.0 input/output i/o reads dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95536
TITLE :Results of DBLSPACE /CHKDSK
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The DBLSPACE /CHKDSK command evaluates errors and then sorts them into
three categories: lost clusters, cross-linked files, and other.
The "other" category indicates one or more of the following problems:
- There is a damaged extended BIOS parameter block (BPB). (This is
the BPB specific to the compressed volume file [CVF].)
- There is a damaged beginning or ending signature in the CVF.
- An entry in the MD-FAT (Microsoft DoubleSpace - file allocation
table) is corrupt (unreadable).
- The MD-FAT makes a reference to the MS-DOS FAT that is not valid.
- The sector heap offset is out of range; for example, the sector
heap is larger than the CVF or beyond the size of the logical
compressed drive.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q95557
TITLE :System Stops Responding with GAI.SYS Loaded High
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The device driver for the APPIAN Rendition IIe Video card (GAI.SYS)
cannot be loaded high.
If you are using this video card, you need to manually exclude GAI.SYS
when running MemMaker in custom mode, or modify the MEMMAKER.INF file.
To exclude the GAI.SYS device driver, edit the MEMMAKER.INF file with
a text editor such as MS-DOS Editor, and add the following line:
*GAI
More Information:
If GAI.SYS is loaded high (into upper memory) the system may stop
responding (hang) at random. This can also occur when you run the
MS-DOS Prompt icon in Windows.
Additional reference words: 6.0 uma umb devicehigh
-=-=-=-=-=-
ARTICLE-ID:Q95558
TITLE :MemMaker Doesn't Remove All References to QEMM
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker removes all references to QEMM. However, if one of your QEMM
statements in the CONFIG.SYS file does not have an equal sign (=),
MemMaker ignores it; the driver is not loaded by MemMaker, nor is it
removed from the CONFIG.SYS file. If this occurs, you may receive an
error message from MemMaker stating that another expanded memory
manager (EMM) is already running.
To work around this problem, edit your CONFIG.SYS file with a text
editor such as MS-DOS Editor and put equal signs in your DEVICE
commands.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q95559
TITLE :MemMaker Does Not Preserve Redirection Settings
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker does not preserve redirection syntax in the AUTOEXEC.BAT
file. For example, if you have C:\DOS\DOSKEY >NUL in the AUTOEXEC.BAT
file, MemMaker will change it to LH /L:x,nnnn C:\DOS\DOSKEY.
To work around this problem, edit your AUTOEXEC.BAT file and put the
>NUL statement back in after you run MemMaker.
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96087
TITLE :Bernoulli Drive Doesn't Mount with DoubleSpace Loaded
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DBSPACE.SYS is loaded in the CONFIG.SYS file before Iomega's device
driver (RCD.SYS) then the Bernoulli mount code is discarded before the
Bernoulli drives become readable.
RCD.SYS should be loaded as high as possible in the CONFIG.SYS file
and MUST be loaded before DBLSPACE.SYS.
Note: DBLSPACE.SYS does not load a device driver for DoubleSpace. It
simply moves DBLSPACE.BIN in memory.
The Iomega and Bernoulli products included here are manufactured by
vendors independent of Microsoft; we make no warranty, implied or
otherwise, regarding these products' performance or reliability.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96093
TITLE :Manifest Shows EMS Memory with NOEMS Switch
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Quarterdeck's Manifest program shows that there is expanded memory
specification (EMS) memory, even if EMM386.EXE is loaded with the NOEMS
switch. If the NOVCPI switch is added to the EMM386.EXE line in the
CONFIG.SYS file, Manifest will no longer show any EMS memory.
More Information:
EMM386.EXE is a VCPI provider even when the NOEMS switch is specified.
With VCPI support enabled, EMM386.EXE supplies an upper-memory frame
buffer for the VCPI applications to use. When an application checks for
EMS memory it may see this buffer and believe it to be an EMS page
frame, thus reporting that EMS memory is available when in actuality it
is not. When the NOVCPI switch is added, it disables this upper-memory
buffer, thus disabling what the application is seeing as EMS.
This is a functional change in MS-DOS 6.0. To make EMM386.EXE perform
like it does in earlier versions of MS-DOS, both the NOEMS switch and
the NOVCPI switch are required.
Manifest is manufactured by a vendor independent of Microsoft; we make
no warranty, implied or otherwise, regarding this product's performance
or reliability.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95560
TITLE :MemMaker Converts Some Variables to Drive Letters
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you set an environment variable in the AUTOEXEC.BAT file and then
use it to run a program, MemMaker converts the environment variable to
its true name.
For example, if your AUTOEXEC.BAT file contains these lines before you
run MemMaker
set xdrive=d
%xdrive%:\dos\doskey
they are converted to:
set xdrive=d
lh /l:xxxx d:\dos\doskey
To work around this problem, either do not set environment variables
to drive letters or directories, or modify your CONFIG.SYS and
AUTOEXEC.BAT files after you run MemMaker.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96250
TITLE :How to Remove DoubleSpace and Preserve Your Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following procedure describes how to remove DoubleSpace from your
hard disk while preserving your files. It is a lengthy procedure and
should be followed only if DoubleSpace removal is necessary. If you
need to change the size of your DoubleSpace volume, type "help
dblspace" (without the quotation marks) at the MS-DOS command prompt
and refer to the online help topic DBLSPACE /SIZE.
Note: This example assumes that you have compressed your boot drive
(C) and that your DoubleSpace host partition is H. For more
information on how DoubleSpace assigns host partitions, query on the
following words in the Microsoft Knowledge Base:
doublespace and assigns and host
If you are not removing DoubleSpace from your boot drive, skip
steps 2-7.
1. Back up all the files you want to preserve from your compressed
drive (C) by using Microsoft Backup or a third-party backup utility.
(For information on using Microsoft Backup, see Chapter 3, "Managing
Your System," in the "Microsoft MS-DOS User's Guide.")
2. When you remove DoubleSpace, what is now drive H will become drive
C, which means you will boot from drive H. To be able to boot from
drive H and restore your backup files, the DoubleSpace host partition
must contain the necessary MS-DOS system files and utilities.
Furthermore, if you stored your backup files on a network drive,
network redirectors must be available.
Determine how much free space you will need to copy the MS-DOS
files (and network redirectors) on the DoubleSpace host partition
(drive H). To do so, use the DIR command. For example, to see how
much space is needed for your MS-DOS files, type the following
command:
dir c:\dos
The output appears as follows:
...
UNFORMAT.COM
VALIDATE.COM
VSAFE.COM
XCOPY.EXE
194 file(s) 7003143 bytes
12959744 bytes free
The next-to-last line shows the number of bytes used by the files in
the DOS directory. This number is the amount of free disk space needed
to store the necessary files and utilities after DoubleSpace is
removed.
3. To free unused disk space from the DoubleSpace compressed volume,
use the /SIZE switch as follows:
dblspace /size
4. Determine how much free space there is on the DoubleSpace host
partition. To do this, change to drive H and use the DIR command. The
last line of the output from the DIR command shows the number of bytes
free on drive H. If this number is greater than the number you found
in step 2, there is enough space to copy the necessary files and
utilities, and you can proceed with step 6. If there is not enough
space on the DoubleSpace host partition, proceed to step 5.
5. Delete enough files on drive C to create the needed space you
determined during step 2. (Note: Do not delete any MS-DOS or network
files; those files must be present during this procedure.)
You can use the DELTREE command to do this. (DELTREE quickly deletes
entire directories.) For example, to remove the WORD directory and all
the files and subdirectories it contains, type the following:
deltree /y c:\word
After you delete some files, shrink the DoubleSpace volume file
again by typing the following:
dblspace /size
To find out if you've created enough free disk space, change to drive
H and use the DIR command. Again, the bytes in use and bytes free are
displayed. If the last line, "bytes free," shows enough free disk
space, continue with step 6. Otherwise, repeat step 5.
6. Copy all the MS-DOS and network files that you need (the files you
determined were necessary during step 2) to the DoubleSpace host
partition (drive H). To preserve the file and directory structure, you
can use the XCOPY command with the /S switch. For example, to copy all
the MS-DOS files into a DOS directory on H, type the following:
md h:\dos
xcopy c:\dos\*.* h:\dos /s
7. Make sure there is a copy of COMMAND.COM in the root of the
DoubleSpace host partition by typing the following:
dir h:\command.com
If COMMAND.COM is not present, copy it from the boot drive (C) with
the following command:
copy c:\command.com h:\
Repeat this step for AUTOEXEC.BAT and CONFIG.SYS files. These files
need to be in the root of the DoubleSpace host partition as well.
You now have all the files you need to boot from the uncompressed
drive and restore your backup files; you can begin removing the
DoubleSpace volume.
8. Switch to the root of the DoubleSpace host partition by typing the
following:
h:
cd\
9. Delete the DoubleSpace files by using the following command:
deltree /y dblspace.*
10. If you are removing DoubleSpace from your boot drive, open the
CONFIG.SYS file from the DoubleSpace host partition (H) in a text
editor, such as MS-DOS Editor. If you are not removing DoubleSpace
from your boot drive, open the CONFIG.SYS file from drive C. Remove
any reference to DBLSPACE.SYS. For example, change your DBLSPACE.SYS
DEVICE command to appear as follows:
rem device=c:\dos\dblspace.sys
11. Restart your computer by pressing CTRL+ALT+DEL.
12. Restore your backup files.
DoubleSpace has now been removed from your system.
Additional reference words: 6.00 howto
-=-=-=-=-=-
ARTICLE-ID:Q95599
TITLE :DblSpace Err Msg: DoubleSpace Cannot Convert Your...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you convert a Stacker volume to a DoubleSpace volume, your
Stacker compressed volume file (CVF) must have 8K clusters. If it does
not, you receive the following error:
DoubleSpace cannot convert your Stacker drives because they have a
cluster size other than 8K. To convert your Stacker drives to
DoubleSpace format, follow the instructions in the DoubleSpace
section of the README.TXT file.
More Information:
When you install Stacker version 2.0 or 3.0, you have the option of
using cluster sizes other than the 8K default.
- Stacker 2.0 supports 4K and 8K clusters
- Stacker 3.0 supports 4K, 8K, 16K, and 32K clusters
Since the conversion of a Stacker volume is done cluster by cluster,
and DoubleSpace uses 8K clusters, DoubleSpace cannot convert Stacker
volumes if they don't have 8K clusters.
Additional reference words: 6.0 err msg errmsg
-=-=-=-=-=-
ARTICLE-ID:Q95601
TITLE :Windows Error Message: Corrupt Swap File Warning
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0 and 3.1
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
Microsoft Windows versions 3.0 and 3.1 allow you to create a permanent
swap file on an MS-DOS 6.0 DoubleSpace drive. If you do this, you
receive one of the following messages when you restart Windows:
Windows 3.1:
Corrupt Swap File Warning - The permanent swap file is corrupt
Windows 3.0:
Corrupt Swap File Warning - Your swap file is corrupt
To work around this situation, delete the permanent swap file and
create a permanent swap file on your host drive.
Note: The host drive is the drive that actually contains the
DoubleSpace compressed volume file (CVF). For more information, run
DoubleSpace and choose Contents from the Help menu.
More Information:
Windows Doesn't Detect DoubleSpace
----------------------------------
Windows cannot create a permanent swap file on CVFs created by disk
compression programs such as DoubleSpace, Stacker, and SuperStor.
Since Windows does direct disk read/write operations to a permanent
swap file, the swap file must be located on a physical hard disk, not
a CVF.
Because DoubleSpace had not been developed when Windows 3.1 was
released, it was not possible to add detection code to Windows to
prevent it from installing on a DoubleSpace drive.
Additional Problems with Windows 3.0
------------------------------------
When you run Windows 3.0 in real mode (in order to run SWAPFILE.EXE),
you receive the following message:
Unsupported DOS version; upgrade to DOS version 3.1 or higher
This message is obviously incorrect. To work around this situation,
run SPATCH.BAT, which is located on your original MS-DOS 6.0 disks.
For more information on DoubleSpace, type the following at the MS-DOS
command prompt:
help dblspace
Additional reference words: 6.0 swapfile dblspace double space
dblspace.exe err msg errmsg
-=-=-=-=-=-
ARTICLE-ID:Q95856
TITLE :Uninstalling MS-DOS 6 Upgrade After Compressing a Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You cannot use the MS-DOS 6 Upgrade Uninstall disk to restore your
previous version of MS-DOS if you have compressed any of your hard
disk drives with DoubleSpace or a third-party disk-compression program
unless you remove all traces of the disk-compression software.
If you attempt to restore your previous version of MS-DOS and you have
compressed your hard disk drive with DoubleSpace, you receive the
following error:
Because you installed DoubleSpace after installing MS-DOS 6,
you cannot restore your previous version of DOS.
More Information:
If you have compressed you hard disk drive with DoubleSpace and would
like to restore your previous version of MS-DOS, query on the
following words in the Microsoft Knowledge Base and follow the
procedure in the article about removing DoubleSpace and preserving
your files:
preserve and doublespace and remove and ms-dos
After you have followed the procedure in the article, restart your
computer with the Uninstall disk in drive A.
For more information about restoring your previous version of MS-DOS,
query on the following words in the Microsoft Knowledge Base:
uninstall and no and disk and old_dos
If you have compressed your hard disk drive with a third-party disk
compression program, consult your documentation or contact the
manufacture for assistance in removing the software before running
Uninstall.
Additional reference words: 6.00 double space dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96128
TITLE :How Setup, MemMaker, and DoubleSpace Find Windows
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Setup, MemMaker, and DoubleSpace need to locate the Windows directory
on your hard disk (if you have one). To find the Windows directory,
Setup looks for the following four files:
WIN.COM
PROGMAN.INI
SYSTEM.INI
When you run SETUP /E to install the optional utilities, Setup checks
to make sure your DOS directory is in the path and looks for
DISKCOPY.COM in that directory.
MemMaker and DoubleSpace look for the following three files:
WINVER.EXE
SYSTEM.INI
WINFILE.INI
Additional reference words: 6.00 setup.exe busetup.exe memmaker.exe
dblspace dblspace.exe
-=-=-=-=-=-
ARTICLE-ID:Q95632
TITLE :DBLSPACE.INI File Settings
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
The following are valid settings for the DBLSPACE.INI file:
MaxRemovableDrives=
FirstDrive=
LastDrive=
MaxFileFragments=
ActivateDrive=
More Information:
MaxRemovableDrives=
-------------------------------------
This setting specifies the number of hard drive partitions available
to MS-DOS.
FirstDrive=
-------------------------
This setting specifies the lowest logical drive letter available for a
DoubleSpace host drive.
LastDrive=
------------------------
This setting specifies the highest logical drive letter available for
a DoubleSpace host drive.
Note: DoubleSpace loads host drives starting at LastDrive= and works
back to FirstDrive=.
MaxFileFragments=
-----------------------
MaxFileFragments is set to 2600 during installation of DoubleSpace.
After DoubleSpace is installed, each time the compressed volume file
(CVF) is changed (deleted, mounted, unmounted, resized), the
MaxFileFragments setting is changed to reflect the new number of file
fragments in all compressed volume files. The new number is a sum of
the file fragments in all CVF's plus 110.
For example, if the CVF on drive C has 6 fragments and the CVF on
drive D has 3 fragments, then maxfilefragments=119 (110+6+3). The new
value is used to allocate adequate memory the next time the CVF is
mounted. The changes in the DBLSPACE.INI file (with respect to
allocating memory) take effect after you restart your computer.
Note: The initial setting (2600) and the number added when a CVF is
changed (110) are both read from the DBLSPACE.INF file.
ActivateDrive=
--------------------------------------------------------------
This setting specifies three things:
- The first drive letter specifies which drive letter to use for the
host drive.
- The second drive letter specifies which drive to use for the
compress volume file (CVF).
- The third digit is the last number of the compress volume file
(DBLSPACE.00x). This digit indicates which DoubleSpace volume
should be mounted.
For example, "ActivateDrive=H,C0" indicates DoubleSpace was used to
compress drive C (using CIP), drive H is used for the host drive, and
the DoubleSpace file name is DBLSPACE.000.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95633
TITLE :Automating RAMDrive Compression with DoubleSpace
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
It is possible to compress a RAMDrive with DoubleSpace. However, since
the information on the RAMDrive is lost each time you restart your
computer, you have to recompress the RAMDrive each time you start your
system.
You can avoid this problem by storing the RAMDrive compressed volume
file (CVF) on your hard drive and placing two commands in your
AUTOEXEC.BAT file to copy and mount the CVF on the RAMDrive when you
start your computer.
More Information:
The compression of the RAMDrive can be automated using the following
procedure:
1. Create RAMDrive. For example, to create a 1 MB RAMDrive in extended
memory, place the following statement in your CONFIG.SYS file:
device=c:\dos\ramdrive.sys 1024 /e
2. Restart your computer to load the RAMDrive.
MS-DOS assigns the next available drive letter for the RAMDrive.
For example, if you only have one hard drive (C), the RAMDrive
is assigned the drive letter D. This procedure continues to use D:
in the examples.
3. Compress the RAMDrive using the following command:
dblspace /compress d: /reserve=.13
The /RESERVE=.13 switch isn't necessary but it gives you the most
compressed space. On a 1 MB compressed RAMDrive, you have 1.59 MB free
on the RAMDrive and .13 MB free on the host drive.
4. Change the CVF attributes so the file can be copied. For example:
attrib h:\dblspace.000 -s -h -r
This example assumes the host drive is H:. To determine your host
drive, type DBLSPACE /LIST at the MS-DOS command prompt. Write the
drive mapping information down, because you need it in step 5.
5. Copy the compressed volume file (CVF) to your hard drive.
To avoid having to recompress the RAMDrive each time you start your
computer, you must store the CVF on your hard drive. This requires
approximately 1 MB of space on your hard drive.
To copy the compressed volume file to your hard drive, type the
following at the MS-DOS command prompt:
copy h:\dblspace.000 c:\dos\ramcvf.000
Since this file cannot be compressed (it already is) you should
copy it to an uncompressed drive.
6. Add the following lines to your AUTOEXEC.BAT file so the CVF is
copied to your RAMDrive and mounted each time you start your computer.
REM Copies and Mounts CVF to RAMDrive
copy c:\dos\ramcvf.000 d:\dblspace.000
dblspace /mount=000 d: /newdrive=h:
Substitute the appropriate drive letters for C:, D:, and H:. Drive
C: should be the uncompressed drive where you store the RAMDrive
CVF, drive D: is the RAMDrive, and drive H: is the host.
7. Restart your computer. To determine if the procedure worked, type
DBLSPACE /LIST at the MS-DOS command prompt.
WARNING: Any information stored on a RAMDrive is lost when you restart
or turn off your computer. To prevent data loss, copy any file you
want to save from your RAMDrive to your hard drive before turning off
your computer.
Additional reference words: 6.0 6 compressed
-=-=-=-=-=-
ARTICLE-ID:Q96130
TITLE :How DBLSPACE.BIN Determines If It Should Stay in Memory
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you have DBLSPACE.BIN in the root directory of your startup drive
(usually C) but you do not have a compressed volume file (CVF),
DBLSPACE.BIN still loads in memory.
After DBLSPACE.BIN loads in memory, it searches for the DBLSPACE.INI
file. If it finds this file, DBLSPACE.BIN remains in memory and
continues the boot process by loading IO.SYS in memory. (It doesn't
matter whether the DBLSPACE.INI file is valid.)
If the DBLSPACE.INI file is not found, DBLSPACE.BIN does not remain
loaded in memory.
Note: The DBLSPACE.SYS command in the CONFIG.SYS file does not effect
this process.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95634
TITLE :Manual Installation Err Msg: Incompatible Partition
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
If you attempt to perform a manual installation of MS-DOS 6 Upgrade,
using the "You need to install MS-DOS manually" procedure in
Diagnosing and Solving Problems, step 3 says to use the SETUP /Q
command. However, if Setup detects you have a special master boot
record (MBR) or an incompatible partition, Setup displays the
"Incompatible partition" screen.
Workaround
----------
If you have one of the following drives and you receive this error
message, run setup with the /U and /Q switches (for example, A:SETUP
/U /Q).
- Priam
- Everex
- SpeedStor Bootall
- Micro House DrivePro
Installing the Optional Programs
--------------------------------
If you attempt to install the optional programs at a later date, you
should also use the /U switch. For example:
setup /u /e
Setup Syntax
------------
/E Installs Windows and MS-DOS optional programs.
/Q Copies MS-DOS files to a hard disk.
/U Installs MS-DOS even if Setup detects disk partitions
that might be incompatible with MS-DOS 6.
For more information of Setup switches, insert MS-DOS 6 Upgrade Setup
Disk 1 in one of your floppy disk drives, change to that drive at the
MS-DOS command prompt and type SETUP /?.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96133
TITLE :DoubleSpace Err Msg: 'Your Computer Might Be Running...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you try to install DoubleSpace while running a version of
SMARTDrive from a version of MS-DOS earlier than 6.0, the following
dialog box appears:
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.
To install DoubleSpace and avoid this error message, make sure you are
loading MS-DOS 6.0 SMARTDrive. The SMARTDrive command line in
AUTOEXEC.BAT should look similar to the following:
c:\dos\smartdrv.exe
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95635
TITLE :Using Unique Labels with Multi-Config
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
When using a Multi-Config startup menu with MS-DOS 6.0, the label
names you use in your AUTOEXEC.BAT file must be unique within the
first eight characters. This is true for all MS-DOS labels.
More Information:
For example, if your startup menu has two labels, (Emp_John_Smith and
Emp_John_Smyth) and your AUTOEXEC.BAT file has a GOTO %CONFIG%
command, MS-DOS will always jump to the :Emp_John_Smith label if it
appears before the :Emp_John_Smyth label in the AUTOEXEC.BAT file.
To workaround or avoid this problem, make sure all menu items in your
CONFIG.SYS and their corresponding labels in your AUTOEXEC.BAT file
are unique within the first eight characters.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96152
TITLE :Setup Adds MS-DOS Directory to Every PATH Statement
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 Setup adds the MS-DOS directory to every PATH statement in
your AUTOEXEC.BAT file. For example, if Setup finds the following
lines in your AUTOEXEC.BAT file
path c:\dos;c:\windows
path %path%;c:\c700\bin
it adds "c:\dos" to the second line even though the MS-DOS directory
is already present in the first line. The lines appear as follows:
path c:\dos;c:\windows
path c:\dos;%path%;c:\c700;c:\bin
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95956
TITLE :MSCDEX Doesn't Load with Trantor CD-ROM Driver
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Trantor CD-ROM driver TSLCDR.SYS (commonly used with Adaptec 1542b
SCSI cards) cannot be found in memory by MSCDEX when you have a very
large CONFIG.SYS file and you use a MS-DOS 6.0 multiple configuration
menu. As a result, MSCEDEX won't load for this device driver.
Workaround
----------
To work around this problem, decrease the size of the CONFIG.SYS file
or don't use a multiple configuration menu.
We are researching this problem and will post new information here as
it becomes available.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.0 dblspace multi-config 3rdparty
-=-=-=-=-=-
ARTICLE-ID:Q95957
TITLE :Qemm Err Msg: File Server Encountered a Critical...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use QuarterDeck's Qemm extended memory manager with Windows
in 386 enhanced mode, Windows may generate the following error message
when you run Intel's Faxability Plus for Windows:
File server encountered a critical error and terminated.
To work around this problem, disable the Stealth Mapping feature in
Qemm. For information about how to do this, See your Qemm manual
More Information:
Faxability Plus for Windows comes with the Satisfaxion Fax/Modem.
CASMGR, a terminate-and-stay-resident (TSR) program that captures the
fax and communicates with the fax/modem card, also causes this error
message.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.0 VSERVER
-=-=-=-=-=-
ARTICLE-ID:Q95808
TITLE :How to Install MS-DOS 6 Upgrade over DR-DOS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft PSS supports the installation of Microsoft MS-DOS 6 Upgrade
over Novell DR-DOS.
Much of the information in the "More Information" section of this
article section was taken from the MS-DOS 6 Upgrade README.TXT file.
More Information:
It is possible to upgrade from DR-DOS to the MS-DOS 6 Upgrade;
however, before you run the Setup program, you should first review the
following precautions and carry out those that apply to your system:
- If you have any security features, including password protection,
disable them. For more information, refer to page 187 in the
"Microsoft MS-DOS 6 User's Guide."
Warning: The MS-DOS 6 Upgrade Setup program cannot create an
Uninstall disk if your CONFIG.SYS or AUTOEXEC.BAT file is password
protected. If any of your DR-DOS system files or your DR-DOS
directory are password protected, use the DR-DOS password command
to disable the password protection before you install MS-DOS 6.
- If you have the DELWATCH delete-protection program installed on
your computer, you must disable DELWATCH and purge your deleted
files before you install MS-DOS 6. To do this, refer to pages
187-188 in the "Microsoft MS-DOS 6 User's Guide."
- If your CONFIG.SYS or AUTOEXEC.BAT file uses any conditional DR-DOS
commands (such as ? or goto), remove those commands and adjust the
order of the remaining commands accordingly.
- If your CONFIG.SYS file contains the DR-DOS chain command, remove
it and adjust the other CONFIG.SYS commands accordingly.
- If your computer uses disk compression, but drive C is not
compressed, run Setup as described in the "Getting Started" Chapter
of the "Microsoft MS-DOS 6 User's Guide." When Setup displays the
message "Your CONFIG.SYS file contains commands that are not valid
MS-DOS commands," select the Modify Original Files option.
- If your hard disk is compressed, carry out the procedure in the
section of the README.TXT file titled "Setup detects that your
computer uses DR-DOS."
- If Setup displays the message "Your computer uses a disk-
compression program and does not have enough free disk space to set
up MS-DOS," you must convert your DR-DOS 6 SuperStor (SSTOR)
compressed drive to an MS-DOS 6 DoubleSpace drive using the
procedure below. This is necessary because the DR-DOS 6 SSTOR
utility does not provide the functionality to increase the size of
your uncompressed host drive.
To run the MS-DOS 6 Setup program, do the following:
1. Use the DR-DOS Backup command to back up your program and data
files. For more information on using the DR-DOS Backup command,
refer to your DR-DOS documentation.
2. Insert the MS-DOS 6 Setup Disk 1 in drive A or B and use the setup
command with the /f switch. For example, if you insert Setup Disk 1
in drive A, type the following at the MS-DOS command prompt and
then press enter:
a:setup /f
Important: After you type the above command and Setup prompts you
to insert a disk to create the startup floppy disk, you MUST create
that disk in drive A. Also, be sure that you choose to install on
drive A.
3. Ensure the startup disk you created in step 2 is in drive A and
then restart your computer by pressing CTRL+ALT+DEL.
4. Use the MS-DOS Format command to reformat all of your drives. When
you format drive C, be sure to use the /s parameter to make the
disk bootable. To do this, type the following command at the MS-DOS
command prompt and then press enter:
format c: /s
5. To restore your program and data files, use the MS-DOS 6 restore
command (this command is located on the startup disk you created in
step 2). For example, to restore your files to from drive A to
drive C, type the following at the MS-DOS command prompt and then
press enter:
restore a: c:\*.* /s
Important: Do NOT restart your computer before proceeding to
step 6.
Note: If some of your files cannot be restored to your hard disk
because you don't have enough disk space, you need to install the
MS-DOS 6 Upgrade, run DoubleSpace to compress your hard disk, and
then restore your files. After you finish restoring your files,
continue with step 6.
6. To remove your DR-DOS files, install the MS-DOS 6 Upgrade again. To
do this, insert the MS-DOS 6 Setup Disk 1 in drive A, type setup,
and follow the instructions on your screen.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96167
TITLE :DoubleSpace Identifies Windows 3.1 in Standard Mode as Shell
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you attempt to run DoubleSpace or any of the DoubleSpace command
line functions from the MS-DOS Prompt with Windows 3.1 in standard
mode, you receive the following error message:
You are running the MS-DOS Shell. To run DoubleSpace,
you must first quit the MS-DOS Shell.
This error occurs because the code used to detect MS-DOS Shell is the
same as the code to detect Windows in standard mode, and the detection
for Shell precedes the detection for Windows.
Additional reference words: 6.00 DoubleSpace dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95814
TITLE :EMM386.EXE May Cause PS/2 to Hang with HIGHSCAN
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use the IBM Reference Diskettes version 1.31 for the PS/2 model
90 or 95, you may not be able to use the HIGHSCAN switch with
EMM386.EXE. Using HIGHSCAN may cause your system to stop responding
(hang).
This problem does not occur with Reference Diskette version 1.10.
More Information:
The newer Reference Diskette uses memory addresses in the F000-F7FF
range (although it may use additional memory elsewhere in the
upper memory area).
To workaround this problem, run MemMaker Custom Setup and choose No
when prompted to "Scan the Upper Memory Area Aggressively?"
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95816
TITLE :DBLSPACE.SYS /MOVE Is in the CONFIG.SYS File Twice
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
During installation, DoubleSpace may add more than one
"DEVICEHIGH=C:\DOS\DBLSPACE.SYS /MOVE" statement to the CONFIG.SYS
file. DoubleSpace adds this line to more than one location in the
CONFIG.SYS file if DoubleSpace determines that DBLSPACE.BIN may cause
problems for network device drivers.
More Information:
DBLSPACE.SYS /MOVE does not load a device driver for DoubleSpace.
Instead, it moves the DoubleSpace component (DBLSPACE.BIN) in memory.
Multiple instances of DBLSPACE.SYS do not use additional memory
because this device drive simple moves DBLSPACE.BIN and then unloads
itself.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95818
TITLE :Brooklyn Bridge Installation Changes CONFIG.SYS File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use an MS-DOS 6 multiple configuration menu, your CONFIG.SYS
file becomes scrambled when you install Brooklyn Bridge version 3.5.
More Information:
Installing Brooklyn Bride on a system using a multiple configuration
menu results in the following:
- All blank lines are removed.
- A screen dump (both character and attributes) is inserted into the
middle of the CONFIG.SYS file.
- DEVICE=BRIDGE1.DEV is added to an unexpected location, such as the end
of and existing CONFIG.SYS command.
The Brooklyn Bridge installation program does not give the user a
choice to update the CONFIG.SYS file - it is done automatically.
However, Brooklyn Bridge does create a backup CONFIG.SYS file called
CONFIG.OLD.
Note: This problem may apply to other versions of Brooklyn Bridge -
Microsoft has tested MS-DOS 6 with Brooklyn Bridge version 3.5 only.
Additional reference words: 6.00 multi-config
-=-=-=-=-=-
ARTICLE-ID:Q95819
TITLE :Defragmenter Err Msg: 'Insufficient Memory...'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If there are too many files and directories on your hard drive, MS-DOS
Defragmenter (DEFRAG) can run out of memory. If Defragmenter runs out
of memory before beginning optimization, you will receive the
following error message:
Insufficient memory - Error Reading the FAT
Defragmenter is limited by the number of files/directories and NOT the
disk size. It is unlikely you will see this problem unless you have
more than 10,000 files/directories on your drive.
You may be able to alleviate the problem by increasing the amount of
free conventional memory and available upper memory blocks (UMBs).
More Information:
If you have freed as much conventional memory as possible and you are
using a 386 or 486 machine, try the following temporary workaround:
1. Make sure EMM386.EXE is being loaded in the CONFIG.SYS file.
2. Using an ASCII text editor such as MS-DOS Edit, add the I=A000-BF77
and NOEM parameters to the device=C:\DOS\EMM386.EXE line in the
CONFIG.SYS.
Note: The A000-B7FF range is commonly used by video cards. Unless
you have a monochrome video card, do not run any graphics
applications when you are using the I=A000-B7FF parameter.
3. Save the CONFIG.SYS file and quit the text editor.
4. Restart your computer.
5. Run Defragmenter with the /G0 switch to prevent it from running in
graphics mode. For example, you would type:
defrag /g0
Note: The switch is G and the number zero not G and the letter O.
6. Edit your CONFIG.SYS file and remove the parameters you added in
step 2.
7. Save the text file, exit the editor and restart your computer.
If, after following the above procedure, you continue to run out of
memory when you attempt to defragment your drive, the problem is most
likely occurring because you have more files than Defragmenter handle.
To optimize your disk, you will need to remove some files from your
disk. If this problem occurs frequently, you may want to consider
creating smaller partitions or multiple DoubleSpace drives on the same
partition.
Additional reference words: 6.00 dos msdos defrag raise the ceiling
dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96169
TITLE :AUTOEXEC.BAT and CONFIG.SYS Backups on Uninstall Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 Setup saves backup copies of the AUTOEXEC.BAT and
CONFIG.SYS files on the Uninstall disk that you create during
installation. No copies are saved in the boot drive of your hard disk.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95824
TITLE :Constant or Random Beeping in Windows with Anti-Virus
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If your computer makes a beeping sound randomly when you are running
Windows, or if Windows stops responding (hangs), and you are loading
Microsoft Anti-Virus, you need to load VSafe Manager (MWAVTSR.EXE).
VSafe Manager is a Windows-based terminate-and-stay-resident (TSR)
program designed to allow bidirectional communication with VSafe. For
more information on VSafe Manager, query on the following words in the
Microsoft Knowledge Base:
vsafe and manager and mwavtsr.exe
Additional reference words: 6.00 VM Beep-o-matic beep MSAV safe
-=-=-=-=-=-
ARTICLE-ID:Q96180
TITLE :VSAFE Err Msg: Program Is Trying to Write to Hard Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following pop-up dialog box may be displayed when you perform a
disk operation that writes to the disk:
VSAFE Warning
Program is trying to write to hard disk
Do you wish to continue?
You can then choose one of three options: Stop, Continue or Boot. If
you choose Stop, the following error message is displayed:
ATTENTION: A serious disk error has occurred while writing
to drive C.
(Note: If you are running MS-DOS Prompt from Windows, this error
message is displayed in a blue screen with the heading "Serious Disk
Error.")
You can now choose to retry the operation. This causes the first VSAFE
error to display again. Until you choose Continue or Boot, you are not
able to escape these recurring warning messages. If you choose
Continue, the write operation is performed. If you choose Boot, the
write operation aborts, your system restarts, and any information you
were trying to save is lost.
This problem is caused by VSAFE installed with the write-protect
option and SMARTDrive installed with write caching enabled. If you
want to use VSAFE with the write-protect option, do not enable
SMARTDrive write caching.
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here as it
becomes available.
Additional reference words: 6.00 write protect protected
-=-=-=-=-=-
ARTICLE-ID:Q96185
TITLE :Norton Speed Disk May Cause Lost Clusters with DBLSPACE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After you use any version of Symantec Norton Speed Disk prior to
version 7.0 on a compressed DoubleSpace drive, the DBLSPACE /CHKDSK
command may report a very large number of lost allocation units.
This occurs when you have set the option to Clear Unused Disk Space
and then perform a full optimization.
Solution
--------
To correct this problem, type "dblspace /chkdsk /f" (without the
quotation marks) at the MS-DOS command prompt and press ENTER.
Note: The Compress program from PCTools versions 5.5 and 6.0 may also
cause the above problem if the Clear Unused Disk Space option is set
when you perform a full optimization.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.00 PCTools Compress Speedisk Norton
dblspace DoubleSpace double space 3rdparty
-=-=-=-=-=-
ARTICLE-ID:Q95835
TITLE :What VSafe Manager (MWAVTSR.EXE) Does and How It Works
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
VSafe Manager (MWAVTSR.EXE) is a Windows-based application that allows
bidirectional communication with VSafe.
VSafe in not a Windows-based application; therefore, if you are
running Windows, the only way VSafe can inform you that there is a
problem is to cause the system to beep. When VSafe Manager is running,
VSafe can send you messages through VSafe Manager. In addition, VSafe
Manager lets you change VSafe settings while Windows is running.
More Information:
The most common problem with VSafe Manager occurs when Windows beeps
as you start it. This beeping occurs after you have upgraded Windows
because VSafe checks the files that are loading against the CHKLIST.MS
file in the loading file's directory. If they don't match, VSafe tries
to prevent the file from loading.
To work around this problem, do one of the following:
- Rescan you disk with Microsoft Anti-Virus after upgrading to create
new checksum files.
-or-
- Delete the current checksum files.
To create new checksum files:
1. From the Options menu, choose Set Options.
2. Select the Create New Checksums check box and choose the OK button.
3. Select the drive you want to scan and choose the Detect button.
To delete the checksum files:
1. Select the drive from which you want to delete the checksum files.
2. From the Scan menu, choose Delete CHKLIST Files.
3. Choose the Delete button.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96327
TITLE :Disconnected Network Drive Icon Becomes Floppy Disk Drive Icon
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system version 3.1
- Microsoft LAN Manager versions 2.1, 2.1a, and 2.2
--------------------------------------------------------------------
Summary:
Under certain circumstances, Windows File Manager may not disconnect
from a network drive correctly. After attempting to disconnect, the
network drive icon changes to a floppy disk drive icon. If you choose
the floppy icon, File Manager displays an error message stating that
no floppy disk in the drive. Until you reboot your computer, File
Manager maintains the dysfunctional floppy disk drive icon.
To work around this problem, do the following:
1. Change to your DoubleSpace host partition and use the ATTRIB
command to remove the hidden, system, and read-only attributes of
the DBLSPACE.INI file:
attrib dblspace.ini -h -s -r
2. Open DBLSPACE.INI in a text editor, such as MS-DOS Editor. You
should see two lines similar to the following (not necessarily in this
order):
LastDrive=M
ActivateDrive=H,C0
3. Change the ActivateDrive= statement's first parameter to the next
drive letter following your last physical drive letter. For example,
if you have two partitions (C and D) on one physical hard drive, set
ActivateDrive= to E.
Warning: If you use the incorrect drive letters when you edit the
ActivateDrive= line in the DBLSPACE.INI file, the system may stop
responding (hang) when you restart it.
4. Set LastDrive= to the same letter you used in step 3. As with the
previous example, if you have one physical drive and two
partitions, C and D, your DBLSPACE.INI file would include the
following lines:
LastDrive=E
ActivateDrive=E,C0
5. Save the changes you made to the DBLSPACE.INI file and use the
ATTRIB command to reset its attributes as follows:
attrib dblspace.ini +h +s +r
6. Restart your computer.
After you restart your computer, DoubleSpace uses the new drive letter
as its host partition. This results in no available drive letters
between your physical hard disk drive and the DoubleSpace host
partition to use for network redirections. You must use drive letters
following the host partition drive letter; this effectively avoids the
floppy disk drive icon problem.
Note: This procedure restricts the creation of additional DoubleSpace
compressed drives. If you later decide to create additional compressed
drives, you must change the LastDrive= statement in the DBLSPACE.INI
file to a higher letter than the one specified in ActivateDrive=. For
example, if your host drive is assigned to D, your DBLSPACE.INI file
should include the following lines:
LastDrive=E
ActivateDrive=D,C0
This gives DoubleSpace the necessary drive letter to use when it
creates another DoubleSpace compressed drive.
Steps to Reproduce Problem
--------------------------
1. Run DBLSPACE to determine the DoubleSpace host partition drive
letter.
2. Before you start Windows, use the LAN Manager command, NET USE, to
connect to a network drive, specifying a drive letter prior to the one
used by the DoubleSpace host partition.
3. Start Windows and run File Manager.
4. From the Disk menu, choose Disconnect Drive or Network Connections
(depending on your version of LAN Manager). Disconnect the network
drive you connected to in step 2.
After you close the network dialog box, the network drive icon changes
to a floppy disk drive icon. If you choose this icon, File Manager
notifies you that there is no disk in the floppy disk drive.
Microsoft has confirmed this to be a problem in MS-DOS version 6.0. We
are researching this problem and will post new information here as it
becomes available.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96197
TITLE :Cannot See Dell Partitions After Upgrading to MS-DOS 6
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 5.0, 5.0a, and 6.0
--------------------------------------------------------------------
Summary:
If you install the MS-DOS 6 Upgrade on a machine running Dell DOS
version 3.3, you may be unable to access all your partitions after you
upgrade your computer.
If you have already installed the MS-DOS 6 Upgrade and you cannot see
all your partitions, restart your computer with the Uninstall disk in
drive A to uninstall MS-DOS 6.0.
Note: This information also applies to MS-DOS versions 5.0 and 5.0a.
More Information:
Workaround
----------
To work around this problem, back up your data, repartition your hard
disk drive, upgrade to MS-DOS 6, and then restore your data.
For specific instructions on repartitioning your hard disk drive
without losing data, download PD0466.EXE (for MS-DOS 5.O) or PD0771
(for MS-DOS 6.0) from the MSDL or CompuServe. These application notes
are titled as follows:
- PD0466: How Do I Repartition My Hard Disk into One Partition?
- PD0771: Repartitioning Your Hard Disk to Upgrade to MS-DOS 6.0
For more information, query on the following words in the
Microsoft Knowledge Base:
PD0466 or PD0771
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
product's performance or reliability.
Additional reference words: 3.30 5.00 5.00a 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96200
TITLE :DoubleSpace Cannot Mount Compressed Write-Protected Disk
Summary:
When you attempt to mount a DoubleSpace compressed floppy disk, you
receive the following error if the disk is write protected
DoubleSpace cannot mount drive x because the file x:\DBLSPACE.000
is not a valid compressed volume file.
where x is the floppy drive letter.
Workaround
----------
To work around this problem, remove the write protection for the
floppy disk.
More Information:
You can mount a floppy disk by running DoubleSpace or you can mount
the floppy disk with the MS-DOS DBLSPACE /MOUNT command. For example,
type the following command at the MS-DOS command prompt and press
ENTER if your floppy disk drive is drive A:
dblspace /mount a:
For more information on DoubleSpace, type "help dblspace" (without the
quotation marks) at the MS-DOS command prompt and press ENTER.
Additional reference words: 6.00 DoubleSpace dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96202
TITLE :Drive Letter Memory Use Is Listed Incorrectly in Help
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Under "Last drive reserved for Dblspace's use," MS-DOS DoubleSpace
Help incorrectly states the following:
Each drive letter uses 24K of memory: to conserve memory, decrease
this amount.
Actually, each drive letter uses 24 bytes of memory.
Additional reference words: 6.00 doc err docerr documentation error
-=-=-=-=-=-
ARTICLE-ID:Q96204
TITLE :You have a SCSI Hard Disk Drive and MemMaker Hangs
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you have an SCSI hard disk and MemMaker stops responding (hangs), a
device driver may be loading into upper memory before the SMARTDrive
double_buffer driver in the CONFIG.SYS file.
Workaround
----------
To work around this problem,
1. Restart your computer (if you haven't already done so).
2. When MemMaker prompts you for input, choose Cancel And Undo Changes.
3. Use MS-DOS Editor to add the following line to the beginning of
your CONFIG.SYS file:
device=c:\dos\smartdrv.exe /double_buffer
Note: If this line already appears in your CONFIG.SYS file, make
sure it is the first line.
4. Save your CONFIG.SYS file.
5. Try running MemMaker again.
If this does not correct the problem refer to Chapter 6 of the
"Microsoft MS-DOS 6 User's Guide" for information about
troubleshooting MemMaker.
For more information about SMARTDrive and the double_buffer driver, query
on the following words in the Microsoft Knowledge Base:
smartdrive and double_buffer
The SCSI hard drive is manufactured by a vendor independent of
Microsoft; we make no warranty, implied or otherwise, regarding this
product's performance or reliability.
Additional reference words: 6.0 load loading high umb uma devicehigh
-=-=-=-=-=-
ARTICLE-ID:Q96329
TITLE :How MemMaker Finds Current Files and Buffers Settings
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
To determine the current settings for the following four environment
variables set in the CONFIG.SYS file, MemMaker scans memory:
Buffers=
FCBS=
Files=
Lastdrive=
MemMaker searches memory instead of reading the CONFIG.SYS file
because a third-party memory manager may be loading these commands
into upper memory. This is necessary because MemMaker may not
recognize your third-party memory management loading scheme.
Additional reference words: 6.00 uma umb
-=-=-=-=-=-
ARTICLE-ID:Q95836
TITLE :BUSETUP Runs from Drive A Only
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Page 5 of the "Microsoft MS-DOS User's Guide" indicates that you can
use the BUSETUP /E command to install the optional utilities from
either drive A or drive B.
This information is incorrect, you can run BUSETUP only from drive A.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q95857
TITLE :DoubleSpace Err Msg: DoubleSpace Cannot Convert Stacker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use DoubleSpace to convert a Stacker volume file (SVF) to a
DoubleSpace compressed volume, you receive the following error message
if the Stacker volume file has never been mounted:
Error: DoubleSpace cannot convert your Stacker drives because
they have a cluster size other than 8K. To convert your Stacker
drives to DoubleSpace format, follow the instructions in the
DoubleSpace section of the README.TXT file.
This error occurs regardless of the Stacker volume file cluster size
if the Stacker volume file has never been mounted. If the Stacker
volume file has been mounted and you receive this error message, you
need to convert your Stacker volume file to 8K clusters.
Workaround
----------
If your Stacker volume file has never been mounted, either mount the
Stacker volume file and then run DoubleSpace, or mount the Stacker
volume file, dismount the Stacker volume file, and then run
DoubleSpace.
Additional reference words: 6.0 unmount dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95858
TITLE :What Does BUSETUP.EXE Do?
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS 6 Upgrade
--------------------------------------------------------------------
Summary:
BUSETUP.EXE is the executable file for Bootable Upgrade Setup and is
located on Setup Disk 1 of MS-DOS 6 Upgrade.
Because Setup Disk 1 can be used to start your system and MS-DOS 6
Upgrade is licensed as an upgrade package only, BUSETUP.EXE is
designed to run only when your machine already has an operating system
installed.
When you start your computer from MS-DOS 6 Upgrade Setup Disk 1, the
AUTOEXEC.BAT file runs BUSETUP.EXE.
Additional reference words: 6.0 boot
-=-=-=-=-=-
ARTICLE-ID:Q95859
TITLE :Extra Tools Menu Added to Norton Desktop for Windows
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If Windows is installed on your computer when you run the MS-DOS 6
Upgrade Setup program, Setup installs a Tools menu in the File Manager
toolbar. If you use Norton Desktop for Windows, you have two Tools
menus after you install the MS-DOS 6 Upgrade.
This problem occurs because Norton Desktop for Windows has one Tools
menu and inherits a second one from File Manager by reading the
WINFILE.INI file.
More Information:
The two tools menus have different functions. The Tools menu in File
Manager and the Tools menu in Norton Desktop for Windows give you the
following options:
Command Description
---------------------------------
Backup Runs Microsoft Backup
Antivirus Runs Microsoft Anti-Virus
DoubleSpace Info Provides DoubleSpace statistics if you have
DoubleSpace installed
You can keep both Tools menus in Norton Desktop for Windows or you can
remove the second Tools menu by telling Norton Desktop for Windows to
ignore the add-ins section in the File Manager information file
(WINFILE.INI).
To configure Norton Desktop for Windows to ignore File Manager
add-ins, set MaxWinFileExtensions equal to zero in your NDW.INI file.
This disables all of the add-ins inherited from File Manager. For
example:
MaxWinFileExtensions=0
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95861
TITLE :RAMDRIVE.SYS Should Precede DBLSPACE.SYS in CONFIG.SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The RAMDRIVE.SYS line in the CONFIG.SYS file should precede the
DBLSPACE.SYS line or the RAMDrive will receive a different drive
designation from what it was before. This can become a problem if you
have many batch files referencing the RAMDrive. For example, if your
batch files reference drive D and it becomes drive I after DoubleSpace
is installed, your batch files will not work.
More Information:
The drives used for DoubleSpace are selected from the last available
drive rather than the first available drive. If RAMDRIVE.SYS precedes
the DBLSPACE.SYS line, then the RAMDrive's drive letter comes right
after the last physical drive. For example, if you have a drive C and a
floppy disk drive A, then the RAMDrive is assigned the letter D.
If the RAMDRIVE.SYS line comes after the DBLSPACE.SYS line,
DoubleSpace has already allocated all the drive letters between drive
C and its host drive (probably drive H) so the RAMDrive is assigned
letter I.
For information on how DoubleSpace assigns host drive letters, query
on the following words in the Microsoft Knowledge Base:
doublespace and assigns and host
For more information on RAMDrive, type "help ramdrive.sys" (without
the quotation marks) at the MS-DOS command prompt and press ENTER.
Additional reference words: 6.00 double space dblspace
-=-=-=-=-=-
ARTICLE-ID:Q95959
TITLE :Intersvr Resets Screen Mode
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Intersvr resets the screen to 25-line mode and may not display
information on the lower part of the screen when you are loading
XANSI.SYS and using an Orchid ProDesigner IIs in 80-characters-per
line/60-lines-per-screen mode. There is no work around at this time.
This problem does not occur with ANSI.SYS and MODE.COM when they are
used with the video modes they support.
More Information:
For more information on MODE and video support, type the following at
the MS-DOS command prompt and press ENTER:
help mode (set display mode)
Intersvr is a component of the MS-DOS file transfer utility Interlnk.
For more information on Interlnk, type the following command at the
MS-DOS command prompt or see Chapter 7, "Features for Your Laptop
Computer," in the "MS-DOS 6 User's Guide":
help interlnk
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96330
TITLE :MS-DOS 6 Upgrade Does Not Update SHELL= in CONFIG.SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Unlike previous versions of Microsoft MS-DOS, when you install MS-DOS
6 Upgrade, the Shell command in the CONFIG.SYS file is not updated if
you are not using COMMAND.COM.
More Information:
If you are using a third-party shell with MS-DOS 6.0, you may have
problems with multiple-configuration menus, MemMaker, and the startup
function keys (F5 and F8).
To correct these problems, either use COMMAND.COM or contact your
third-party shell manufacturer for an updated version.
The default Shell command for MS-DOS 6 Upgrade is as follows:
shell=c:\dos\command.com c:\dos /p
If the current Shell is COMMAND.COM, Setup updates the path, keeps the
/E parameter (if there is one), and adds the /P parameter if it does
not already exist.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96331
TITLE :Stacker Err Msg: WARNING: Unrecognized Load High...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After you upgrade to MS-DOS 6.0, you may receive the following message
if you are using Stacker:
WARNING: Unrecognized load high method. Unable to verify driver fit
The driver does load successfully, but you must press a key to
continue.
More Information:
This message occurs if you use a DEVICEHIGH= command for the Stacker
device drivers in your CONFIG.SYS file. It does not occur if you use a
DEVICE= command.
Workaround
----------
To work around this problem, ensure the command for SETVER.EXE is
located above the Stacker device drivers in the CONFIG.SYS file. To do
this, SETVER.EXE must be located on the uncompressed Stacker
partition.
1. Copy SETVER.EXE to the uncompressed drive. For example, if your
compressed drive is C and the swap drive is D, copy SETVER.EXE to
drive D as follows:
copy c:\dos\setver.exe d:\
2. Put the following SETVER.EXE statement at the top of your
CONFIG.SYS file:
device=c:\setver.exe
3. Restart your computer.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96332
TITLE :F5 and F8 Keys Do Not Seem to Affect Startup Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
On some fast computers, the "Starting MS-DOS..." message may flash on
the screen too quickly to allow you to press the F5 or F8 function
key.
If you have problems getting your computer to respond to the F5 and F8
function keys, make sure the following line is not in your CONFIG.SYS
file:
switches=/f
More Information:
You can use a small multiple-configuration menu to determine if the F5
and F8 function keys are working properly. Adding the following five
lines to the top of your CONFIG.SYS file creates a startup menu that
gives you one menu item. You can then either press ENTER to start your
computer, press the F5 function key to bypass your configuration
files, or press the F8 function key to step through the CONFIG.SYS
file.
[COMMON]
[MENU]
MENUITEM=ONE,Your standard startup...
MENUDEFAULT=ONE,15
[ONE]
These statements give you 15 seconds before your CONFIG.SYS and
AUTOEXEC.BAT files are processed. They do not affect the contents of
your CONFIG.SYS file.
Type "help multi-config" (without the quotation marks) at the MS-DOS
command prompt to learn more about using multiple-configuration menus.
Type "help switches" (without the quotation marks) to learn more about
using the Switches command.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96333
TITLE :MS Backup Err Msg: File Is Not a Setup File...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You may receive the following error message when you start Microsoft
Backup for Windows on an NEC portable:
File is not a setup file C:\DOS\DEFAULT.SET
This error occurs because the NEC BIOS creates a DEFAULT.SET file in
the DOS directory when the battery starts running low.
Workaround
----------
To work around this problem, delete or rename the DEFAULT.SET file,
and then restart Microsoft Backup for Windows.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96334
TITLE :Windows for Workgroups or WC Hang on NETBIND Command
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows for Workgroups version 3.1
- Microsoft Workgroup Connections version 1.0
--------------------------------------------------------------------
Summary:
If the Windows for Workgroups or Workgroup Connections network drivers
are loaded at the top of unallocated conventional memory, your system
may stop responding (hang).
This problem can occur if you run a large program before the NETBIND
command.
Workaround
----------
To work around this problem, move the NET START command to the top of
your AUTOEXEC.BAT file.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96383
TITLE :Addstor SSUTIL Utility Reports MS-DOS 6.0 as Version 5.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Addstor compression information utility, SSUTIL, incorrectly
reports the following information about MS-DOS version 6.0:
VERSION is MS-DOS 5.0
REPORTED version is 6.0
More Information:
SSUTIL looks at the boot record signature to determine the version of
MS-DOS. It then calls the GetMSDOSVersion() function to determine the
reported version number.
Because the boot record signature is the same for MS-DOS 5.0 and
MS-DOS 6.0, SSUTIL incorrectly reports the version number.
Note: The incorrect version number detection does not cause any
problems or incompatibilities between MS-DOS 6.0 and Addstor.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96384
TITLE :DoubleSpace Err Msg: Unrecognized Error #109
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you receive the following error message when you attempt to mount a
compressed volume file (CVF), your CVF is probably too fragmented:
Unrecognized Error #109
To work around this problem, either increase the MaxFileFragments
setting in the DBLSPACE.INI file or defragment the CVF. These
procedures are outlined below.
More Information:
To work around this problem, do the following:
1. Edit the DBLSPACE.INI file and increase the MaxFileFragments
setting by using the following steps:
Warning: If you use the incorrect drive letters when you edit the
DBLSPACE.INI file, the system may stop responding (hang) when you
restart it.
a. Remove the Read-Only, System, and Hidden file attributes on the
DBLSPACE.INI file. For example, if drive H is your host drive,
type the following at the MS-DOS command prompt and press ENTER:
attrib h:\dblspace.ini -r -s -h
b. Using MS-DOS Editor, edit the DBLSPACE.INI file and increase the
value for MaxFileFragments.
c. Save the DBLSPACE.INI file and quit MS-DOS Editor.
d. Use the ATTRIB command to reset the file attributes on
DBLSPACE.INI. For example, if your host drive is drive H, type the
following command and press ENTER:
attrib h:\dblspace.ini +r +s +h
2. Restart your computer and try to mount the drive again. If you
still cannot mount the CVF, proceed to step 3.
3. Clear the file attributes from the DoubleSpace CVF and defragment the
drive using the procedure below.
Warning: If the DoubleSpace CVF is mounted when you perform this
procedure, you will corrupt your DoubleSpace drive.
a. Unmount your DoubleSpace drive or start your computer from an
MS-DOS 6 system disk in drive A that does not have a DBLSPACE.BIN
file.
b. Remove the Read-Only, System, and Hidden file attributes on the
DBLSPACE.XXX file. For example, if file is H:\DBLSPACE.000, type
the following at the MS-DOS command prompt and press ENTER:
attrib h:\dblspace.000 -r -s -h
c. Run MS-DOS Defragmenter by typing DEFRAG at the MS-DOS command
prompt and pressing ENTER.
d. Use the ATTRIB command to reset the file attribute on
DBLSPACE.XXX. For example, if file is H:\DBLSPACE.000, type
the following at the MS-DOS command prompt and press ENTER:
attrib h:\dblspace.000 +r +s +h
e. You should now be able to mount the CVF if you unmounted it. If
you restarted your computer from drive A in step a, restart your
computer from the C drive.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96385
TITLE :CTRL+BREAK Hangs System If Running CHKDSK with BREAK=ON Line
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DoubleSpace installed and you press the CTRL+BREAK key combination
when CHKDSK is calling DBLSPACE /CHKDSK, your system may stop
responding (hang). This problem occurs only if you have the BREAK=ON
command in your CONFIG.SYS file.
To work around this problem, either let CHKDSK run DBLSPACE /CHKDSK or
remove the BREAK=ON command from your CONFIG.SYS file.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94331
TITLE :Disk Error Messages with ASPI2DOS.SYS Device Driver
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
ASPI2DOS.SYS is an Adaptec driver used for external SCSI devices such
as the Adaptec 1522 SCSI controller. If SMARTDrive is used to cache a
drive when ASPI2DOS.SYS is installed, you receive the following error
message from the Adaptec controller:
A serious disk error has occurred while writing to drive C.
When you run Microsoft Anti-Virus (MSAV.EXE), you receive the
following error message:
Not ready reading (or writing) drive C:
Note: The double-buffer driver does not prevent these errors.
Workaround
-----------
To work around the problem:
- Remove ASPI2DOS.SYS from the CONFIG.SYS file.
-or-
- Remove SMARTDRV.EXE from the AUTOEXEC.BAT file.
More Information:
This problem usually occurs during frequent alternating reads and
writes by programs such as Microsoft Anti-Virus and SMARTDrive.
Since the controller does not use direct memory access (DMA), loading
the double-buffer driver does not help.
Additional reference words: 6.00 uma double_buffer
-=-=-=-=-=-
ARTICLE-ID:Q96386
TITLE :Cannot Lower Estimated Compression Ratio with DoubleSpace
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DoubleSpace does not allow you to lower the estimated compression
ratio (ECR), you may have lost allocation units at the end of the disk
drive.
To work around this problem, run CHKDSK /F at the MS-DOS command
prompt to recover the lost allocation units.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96387
TITLE :Virus-Protection Program Reports CONFIG.SYS Is Infected
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After you install DoubleSpace or create a new DoubleSpace drive, your
virus-detection software may indicate that the CONFIG.SYS file now
contains a virus. This occurs because DoubleSpace updates the date and
time on the CONFIG.SYS file even if it does not change the file.
Additional reference words: 6.00 infected
-=-=-=-=-=-
ARTICLE-ID:Q96388
TITLE :Uninstalling MS-DOS 6 on an XtraDrive Compressed Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you install MS-DOS 6 Upgrade on a machine that is using XtraDrive
data-compression software, you cannot uninstall MS-DOS without
modifying the Uninstall disk.
More Information:
To successfully uninstall MS-DOS 6 Upgrade:
1. Copy XTRADRV.SYS to the Uninstall disk.
2. Using MS-DOS Editor, create a CONFIG.SYS file on the Uninstall disk
with the following line:
device=a:\xtradrv.sys
3. Restart the computer with the Uninstall disk in drive A. (Press the
CTRL+ALT+DEL key combination.)
Additional reference words: 6.00 xtra extra drive
-=-=-=-=-=-
ARTICLE-ID:Q96389
TITLE :MS-DOS Files to Delete from 8088, 8086, and 80286 Machines
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following MS-DOS files can only be used on computers with 80386 or
higher processors. If you have an 8088, 8086, or 80286 computer, you
can delete the files below.
Delete the following from the root directory:
Filename Description
---------------------------------
WINA20.386 Used for Windows 3.0 enhanced mode
Delete the following from the DOS directory:
Filename Description
---------------------------------
CHKSTATE.SYS MemMaker file
EMM386.EXE Expanded memory manager
MEMMAKER.EXE MemMaker file
MEMMAKER.HLP MemMaker file
MEMMAKER.INF MemMaker file
MONOUMB.386 Windows virtual device driver
SIZER.EXE MemMaker file
VFINTD.386 Virtual device driver for virtual floppy
support with Microsoft Backup for Windows
Additional reference words: 6.00 286 386 486 80486
-=-=-=-=-=-
ARTICLE-ID:Q96390
TITLE :Using DoubleSpace with Compressed Floppy and Removable Disks
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
DoubleSpace supports disk compression on both floppy disks and
removable media disks; however, when you swap a floppy or removable
media disk you must remount the disk.
To mount a disk from the MS-DOS command prompt, type the following:
dblspace /mount drive
where "drive" is the drive location of the disk.
Automation of this feature is under review and will be considered for
inclusion in a future release.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96391
TITLE :DoubleSpace Estimated & Actual Compression Ratios
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
This article discusses common questions and issues with DoubleSpace
actual compression ratio (ACR) and estimated compression ratio (ECR).
The following three subjects are covered:
- Actual Compression Ratio
- Estimated Compression Ratio
- Viewing and Changing the Compression Ratio
More Information:
Actual Compression Ratio
------------------------
The actual compression ratio (ACR) represents the compression ratio
for data that already exists on a drive. The ACR varies over time
depending on the type of files you store on you hard disk.
The ACR is calculated by dividing the sum of the uncompressed data
size by the physical space consumed after the data is compressed. For
example, if a disk with 100 megabytes (MB) of uncompressed data is
compressed and occupies 50 MB of disk space, the compression ratio is
2:1. The formula is as follows:
100MB/50MB =2.0
Note: 2.0 is written as 2.0:1 (that is, 2 to 1)
Estimated Compression Ratio
---------------------------
The estimated compression ratio is a number that DoubleSpace uses to
calculate the amount of free space on a compressed drive. Changing the
ECR doesn't change the compression algorithm or the ACR. It simply
changes the value that DoubleSpace uses to estimate the free disk
space.
You may need to increase the compression ratio if you are trying to
store several new highly compressible files and you are low on disk
space.
For more information on ECR:
- Run DoubleSpace, choose Change Ratio from the Drive menu, and then
press the F1 function key.
-or-
- Type "help dblspace /ratio" (without the quotation marks) at the
MS-DOS command prompt.
Viewing and Changing the Compression Ratio
------------------------------------------
To view the ACR and ECR for a drive, type "dblspace" (without the
quotation marks) at the MS-DOS command prompt, select the drive you
are interested in, and then press the ENTER key.
To view the ACR for a file or directory, use the DIR /C or DIR /CH
command. For example, to see the ACR for COMMAND.COM, type the
following at the MS-DOS command prompt:
dir c:\command.com /ch
To view the ACR for the DOS directory, type the following at the
MS-DOS command prompt:
dir \dos /ch
Note: DIR /C reports the ACR of the compressed data based on an
8-kilobyte (K) cluster size. DIR /CH reports the ACR based on the
compressed data based on the host drive cluster size. Use this number
when you compare the ACR and ECR.
To set the ECR to the ACR value, type "dblspace /ratio" (without the
quotation marks) at the MS-DOS command prompt.
To set the ECR to a specific value, type the following at the MS-DOS
command prompt:
dblspace /ratio=n.n
where "n.n" is the ECR value.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96392
TITLE :Error in MS-DOS Help Example for the MENUCOLOR Command
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using an MS-DOS 6.0 multiple-configuration menu and you set
the MENUCOLOR command in the CONFIG.SYS file to match the example
shown in MS-DOS Help, the menu color does not display.
More Information:
The example in MS-DOS Help shows a space after the comma, which causes
MS-DOS to stop reading the MENUCOLOR command when the CONFIG.SYS file
is processed. As a result, the menu color is not displayed.
To work around this problem remove the space after the comma.
Additional reference words: 6.00 multi-config doc err docerr
-=-=-=-=-=-
ARTICLE-ID:Q96440
TITLE :DoubleSpace Doesn't Mount After Installing RAMDrive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use DoubleSpace with a removable hard drive (such as Syquest,
Bernoulli, or Quatam Passport XL) and later install RAMDrive,
DoubleSpace may refuse to mount its compressed drive(s). This problem
only occurs if the RAMDrive DEVICE command in the CONFIG.SYS file
precedes the removable hard drive DEVICE command line. Since RAMDrive
may inadvertently use the drive letter of the removable drive,
DoubleSpace may not find the compressed volume on the expected drive.
The same behavior may occur if you remove RAMDrive after compressing
your removable hard drive. (The drive letters shift and DoubleSpace
does not mount.)
If this problem was caused by installing RAMDrive, you can simply move
the RAMDrive DEVICE command past the removable drive's DEVICE command
in the CONFIG.SYS file. The advantage of this workaround is that the
drive letter assignments stay the same.
If this problem occurs after removing RAMDrive, run DBLSPACE. From the
Drive menu, choose Mount. DoubleSpace scans all your drives for
compressed volumes and reassigns drive letters appropriately. This
workaround may cause problems for programs configured to specific
drive letters.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96447
TITLE :Manifest Shows EMS Memory with NOEMS Switch
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Quarterdeck's Manifest program indicates that EMS memory exists, even
if EMM386.EXE is loaded with the NOEMS switch. If you add the NOVCPI
switch to the EMM386.EXE line in the CONFIG.SYS file, Manifest no
longer shows any EMS memory.
More Information:
EMM386.EXE version 4.45, which ships with MS-DOS 6.0 is a Virtual
Control Program Interface (VCPI) provider even when the NOEMS switch
is specified. With VCPI support enabled, EMM386.EXE supplies an upper
memory frame buffer for the VCPI applications to use. When an
application checks for EMS memory, it may see this buffer and believe
it to be an EMS page frame, thus reporting that EMS memory is
available when it is not. When the NOVCPI switch is added, it disables
this upper memory buffer, thus disabling what the application is
seeing as EMS.
Maintaining VCPI server functionality with the NOEMS switch specified
is a new feature in MS-DOS 6.0.
It should be noted that VCPI support can exist without a page frame.
For example, EMM386 in MS-DOS 5.0 (version 4.44) provided VCPI support
by using the "frame=0" switch. In MS-DOS 6.0 we can now achieve the
same result using both the NOEMS switch and the NOVCPI switch
together.
Manifest is manufactured by Quarterdeck Office Systems, a vendor
independent of Microsoft; we make no warranty, implied or otherwise,
regarding this product's performance or reliability.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94332
TITLE :System Restarts When DoubleSpace Commands Are Issued
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If DBLSPACE /RATIO or other DoubleSpace commands cause the system to
restart, load DBLSPACE.SYS before your network drivers in the
CONFIG.SYS file.
More Information:
Setup installs DBLSPACE.SYS before any network drivers, so this
problem should not occur unless you have moved the DBLSPACE.SYS driver
in the CONFIG.SYS file.
Additional reference words: 6.0 Autoreboot reboot warmboot coldboot
cold warm boot re-boot re-start
-=-=-=-=-=-
ARTICLE-ID:Q96496
TITLE :Err Msg: SYS Is Unable to Operate on Target Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you try to run SYS.COM on a drive that has been compressed with the
DoubleSpace, you may receive the following error message:
SYS is unable to operate on target drive
To work around this problem, you must manually unmount the compressed
drive before you run the SYS command to make drive C a bootable drive.
More Information:
This error usually occurs when an attempt is made to run SYS.COM on a
hard disk drive that has been compressed with DoubleSpace and has
failed because of corrupted MS-DOS files. DoubleSpace performs "drive
swapping," giving the physical drive a drive letter other than C
(typically the fifth letter after the system's last block device) and
designating the compressed volume file as drive C. Even if you boot
from a floppy disk, it is possible that DoubleSpace will mount the
compressed drive and perform the drive swap. Because we cannot run
SYS.COM on a DBLSPACE drive, SYS.COM generates the error message.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96514
TITLE :Difference Between the DIR /C and DIR /CH Commands
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The DIR command has two switches that you can use to display
compression ratio information, /C and /CH. /C displays the compression
ratio of a file assuming that it resides on a drive using 8-kilobyte
(K) clusters. /CH uses the cluster size of the host partition. In most
cases, there is no difference between the output of these switches
unless your DoubleSpace host partition uses a cluster size other than
8 kilobytes. For example, if you have a file on a drive using 4K
clusters, the compression ratio displayed generated from DIR /C would
be 1.5; DIR /CH would generate a compression ratio of 2.0.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96516
TITLE :Changes to MSCDEX.EXE for MS-DOS 6.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft CD-ROM Extensions (MSCDEX.EXE) version 2.22 for MS-DOS is
included in MS-DOS 6 Upgrade and MS-DOS 6.0 plus Enhanced Tools.
MSCDEX.EXE version 2.22 includes code to recognize MS-DOS 6.0 and make
it easier to load MSCDEX.EXE into upper memory blocks (UMBs).
(MSCDEX.EXE 2.22 has a smaller initialization size than earlier
versions, making it easier to fit in smaller UMBs.)
MSCDEX.EXE is included with MS-DOS 6.0 so that you do not need to
obtain additional software to continue using your CD-ROM drive after
you upgrade to MS-DOS 6.0.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96517
TITLE :Using DoubleSpace to Compress a Bootable HardCard
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You should not use DoubleSpace to compress your boot drive if that
drive requires a device driver in the CONFIG.SYS file. Because the
DoubleSpace driver (DBLSPACE.BIN) is loaded with IO.SYS before the
CONFIG.SYS file is processed, Microsoft does not support this
configuration. If you want to use DoubleSpace on such a drive, you
must mount the drive after loading the device drivers in the
CONFIG.SYS file.
For example, if drive C is a Plus Hardcard and you compress that
drive, DoubleSpace cannot automatically mount the drive. You can
either mount the drive from the MS-DOS command prompt or from the
AUTEOXEC.BAT file.
Note: DoubleSpace does not support compression of removable hard disk
drives that require a device driver to write to the drive. This is
because DoubleSpace must mount the drive before the CONFIG.SYS file is
processed, and the mounting process rewrites the BitFAT structure in
the compressed volume file (CVF).
More Information:
You can manually mount the DoubleSpace drive from the command line by
using the DBLSPACE /MO command. If you want to mount the compressed
drive from the AUTOEXEC.BAT file, you must copy the CONFIG.SYS and
AUTOEXEC.BAT files to the host drive, copy the device drivers called
from those files, and then add a line to the AUTOEXEC.BAT file to
mount the compressed drive. To do this, follow the procedure outlined
below.
Note: This procedure does not work if your drive does not meet the
following conditions:
- It is bootable (that is, accessed by the BIOS during the startup
process).
- It is a system disk. (If it is not, use the SYS command to transfer
the MS-DOS system files.)
To automatically mount the compressed drive:
1. Compress the boot drive with DoubleSpace. For example, to compress
drive C, type the following at the MS-DOS command prompt:
DBLSPACE /COMPRESS C:
2. Ensure the following files are in the root directory of the host
drive (the drive containing the compressed volume file [CVF]):
IO.SYS
MSDOS.SYS
COMMAND.COM
DBLSPACE.BIN
DBLSPACE.000
To determine which drive is the host drive, type "DBLSPACE /LIST"
(without the quotation marks) at the MS-DOS command prompt.
Since the files listed above have read-only, hidden, and system
file attributes set, use the /A parameter to see the files. To do
this, type DIR /A at the MS-DOS command prompt.
3. Copy the following three files to the root of the host drive:
DBLSPACE.EXE, CONFIG.SYS, and AUTOEXEC.BAT.
For example, if H is your host drive, you would use the following
three commands to copy these files:
copy c:\dos\dblspace.exe h:\
copy c:\config.sys h:\
copy c:\autoexec.bat h:\
4. Copy any files called from the CONFIG.SYS file to the host drive.
For example, if the command DEVICE=C:\DOS\HIMEM.SYS is in your
CONFIG.SYS file, copy HIMEM.SYS to the host drive with the
following command:
copy c:\dos\himem.sys h:\
5. Edit the CONFIG.SYS file on the host drive to reflect the new
location of the device drivers. Given the above HIMEM.SYS example,
change the CONFIG.SYS file on the host drive (H) to read as follows:
device=c:\himem.sys
6. Add the following line to the AUTOEXEC.BAT file on the host drive:
DBLSPACE /MO
7. Any other programs or executable files called from the AUTOEXEC.BAT
file should be located on the host drive. If they are not, you need
to edit the AUTEXEC.BAT file to reference the correct drive letter.
The host and boot drive letters swap when the DBLSPACE /MO line is
run from the AUTEOXEC.BAT file.
Additional reference words: 6.00 double space
-=-=-=-=-=-
ARTICLE-ID:Q96518
TITLE :Differences Between DOSSHELL.INI in MS-DOS Versions 5 and 6
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
This article discusses the differences between the DOSSHELL.INI file
in MS-DOS versions 5.0 and 6.0.
More Information:
The DOSSHELL.INI file in MS-DOS 6.0 does not contain references to the
MS-DOS 5.0 BACKUP and RESTORE commands.
Since Setup doesn't update a existing DOSSHELL.INI file, the existing
references to Backup Fixed Disk and Restore Fixed Disk are not
updated. BACKUP.EXE is copied to the OLD_DOS directory so that the
Backup Fixed Disk option no longer works. You can either copy the
MS-DOS 5.0 BACKUP command (BACKUP.COM) to the DOS directory or modify
the Backup Fixed Disk properties to reference the new backup program,
Microsoft Backup (MSBACKUP.EXE).
If you don't have an existing DOSSHELL.INI file, Setup creates a new
one with the following default items:
Main Menu
---------
Command Prompt
Editor
MS-DOS QBasic
Disk Utilities Menu
-------------------
MS Anti-Virus
MS Backup
Quick Format
Format
Undelete
Setup leaves the RESTORE command (RESTORE.EXE) from MS-DOS 5.0 in the
DOS directory even though it does not appear as an item in MS-DOS 6
Shell. The BACKUP command (BACKUP.EXE) from MS-DOS 5.0 is available on
the supplemental disk or in the OLD_DOS directory as described above.
To replace your existing DOSSHELL.INI file, you can expand the
appropriate .IN_ file from the original MS-DOS 6 Upgrade disks. For
example, if you have an EGA or VGA video display card, expand EGA.IN_
from the MS-DOS 6 Upgrade disks (Disk 2 of the 1.2-megabyte (MB) set
or Disk 1 of the 1.44-MB set). For example, if you insert the Setup
disk in drive A, you would type the following command:
expand a:ega.in_ c:\dos\ega.ini
If the new utilities made available by the MS-DOS 6.0 DOSSHELL.INI
file are not installed, you must install them using the SETUP command
with the /E parameter.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96519
TITLE :Situations in Which Defragmenter Cannot Run
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft Defragmenter operates on the MS-DOS logical drive level
only. Third-party partitioning utilities that modify or translate disk
geometry (such as Disk Manager and SpeedStor) operate beneath the
MS-DOS file system and are therefore transparent to Defragmenter.
Defragmenter cannot share access to a drive with other tasks;
therefore, you cannot run Defragmenter if Windows or DESQview is
running.
More Information:
Defragmenter does not work in the following situations:
Situation Reason
---------- ------
Network Drive Network software usually does not allow full
single-tasking access to the entire drive,
including the file tables. Often network drives
(such as Novell NetWare) use another file system.
CHKDSK Errors Errors in the drive organization can cause
unpredictable results from Defragmenter.
Defragmenter identifies most CHKDSK errors while
reading the drive organization and then refuses
to run until you correct them.
Windows Defragmenter cannot operate properly in a
multitasking or task-switching situation;
therefore, it detects Windows in real, standard,
and 386 enhanced modes and does not run.
Task Swapper Defragmenter cannot operate properly in a
task-switching situation; therefore, it detects
the MS-DOS Shell task swapper and does not run.
Interlnk Drives Interlnk is not designed to support defragmentation
and other low-level utilities. Specifically, it does
not implement interrupts 25 and 26.
Fastopen The Fastopen program tracks which files are located
in which clusters on your disk. Defragmenter
rearranges data on a cluster level, which confuses
Fastopen.
JOIN JOIN does not allow normal access to a drive.
SUBST SUBST drives do not have their own file tables or
directories to optimize.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
Additional reference words: 6.00 3rd party defrag
-=-=-=-=-=-
ARTICLE-ID:Q96520
TITLE :Windows Hangs at Logo Screen with FTP Network and DoubleSpace
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are running FTP Software's PC/TCP network software and
Microsoft Windows in 386 enhanced mode, your SYSTEM.INI file may
contain the line DEVICE=C:\PCTCP\VPCTCP.386 in the [386Enh] section.
If it does, Windows may stop responding (hang) at the logo screen
after you have compressed a drive with DoubleSpace.
More Information:
The system hangs if the line DEVICE=C:\DOS\DBLSPACE.SYS /MOVE is not
present in your CONFIG.SYS file before any of the drivers that load
the network. To correct this problem, add or move the line
C:\DOS\DBLSPACE.SYS /MOVE before the first line that loads the network
software. In most cases, the first line that starts the network is
something similar to C:\PCTCP\PROTMAN.SYS /i:C:\PCTCP.
Additional reference words: 2.04 2.1 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96522
TITLE :Regions Scanned by the EMM386.EXE HIGHSCAN Switch
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The HIGHSCAN switch included in EMM386.EXE version 4.45 allows
EMM386.EXE to map expanded memory pages or upper memory blocks (UMBs)
over portions of the upper memory area (UMA) used by system read-only
memory (ROM).
Choosing "Yes" in response to the MemMaker prompt "Scan the upper
memory area aggressively?" causes MemMaker to add HIGHSCAN to the
EMM386.EXE device= line.
More Information:
If you use the HIGHSCAN switch on the DEVICE=C:\DOS\EMM386.EXE line in
the CONFIG.SYS file, EMM386.EXE examines the system ROM area starting
at memory location F000:0000. If EMM386.EXE determines that ROM is
duplicated between F000h-F7FFh and F800h-FFFFh, EMM386.EXE uses the
F000h-F7FFh region for expanded memory page mapping or UMB memory.
(This adds up to 32 kilobytes to the UMA.
On Micro Channel (MCA) systems with ROM BASIC (for example, IBM PS/2
systems), the HIGHSCAN switch allows EMM386.EXE to map expanded memory
or UMB memory over the ROM BASIC code in the system ROM. Typically
this is the region from F600 to FDFF.
Note: On some systems, EMM386.EXE uses the ROM area and the system
does not operate correctly. The symptoms of this condition vary. For
example, the system may stop responding (hang) or appear to operate
normally until you use a floppy disk drive. Because of these potential
problems, HIGHSCAN is not used by default.
Additional reference words: 6.00 parameter
-=-=-=-=-=-
ARTICLE-ID:Q96541
TITLE :Setup Leaves Windows .INI Files in Root of the Novell Server
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you run MS-DOS 6 Setup when you are logged onto a Novell server,
Setup may leave MS-DOS initialization (.INI) files in the root
directory. This problem occurs when all the following conditions are
exist:
- You are logged on as a supervisor or a user with full access
privileges to the root of the file server.
- You are using a shared installation of Windows (installed with the
SETUP /N command).
- Your Windows initialization files are in a user directory that is
being accessed with a search drive.
- You have installed the Windows-based optional utilities.
If these conditions exist, MS-DOS 6 Setup leaves your initialization
files in the root of the Novell file server.
The following initialization files are left in the root of the Novell
server:
PROTMAN.INI
SYSTEM.INI
WINFILE.INI
Setup also leaves the backup (.BAK) files for those files in the root
of the Novell file server.
Workaround
----------
Use one of the following techniques to correct this situation:
- If this is the only installation of MS-DOS 6 you plan to perform
when you are logged in as supervisor, you can simply move these
six files back to the user directory.
- If you plan to do multiple installations of MS-DOS 6 when you are
logged in as supervisor, temporarily override the search drive before
beginning the MS-DOS 6 Setup on each subsequent computer. For example,
if your Windows initialization files are accessed on Search drive
W:\USER\JOEB. Before beginning the MS-DOS 6 Setup type these two
commands at the MS-DOS command prompt:
map del w:
map w:=sys:user\joeb
When MS-DOS 6 Setup prompts you for the location of Windows directory,
use W:\USER\JOEB for the path.
Note: If desired, you may substitute the second command above with the
following:
map root w:=sys:user\joeb
When MS-DOS 6 Setup prompts you for the location of Windows, use W:\
for the path.
More Information:
Do not use a search drive to specify the location of your Windows
initialization files. A search drive represents its drive letter as
"
"
current (.) directory. This is why MS-DOS 6 writes the files to the
root of the server.
If you are logged on as a user without write access privileges to the
root of the file server (as is generally the case with a user on a
Novell network), the same approach as described in the second
technique applies. If you don't have privileges in the root directory,
the temporary initialization files (.$$$) are written to your user
directory. No changes are been made to your original initialization
files. You can safely delete these .$$$ files. Use the second
technique and then restart the MS-DOS 6 Setup program.
The following three .$$$ files may be left in your user directory:
__SYS__.$$$
__PGI__.$$$
__WFI__.$$$
If Setup detects that it did not need to modify one or more of the
initialization files, you may not have all three of these in your user
directory.
Note: This information applies to both the SETUP and SETUP /E
commands. (SETUP /E is used to install the optional components.)
Additional reference words: netware net ware 286 386 2.15 2.2 3.10
3.11 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96552
TITLE :What Defragmentor Does & How It Works with 3rd-Party Utilities
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft Defragmenter reorganizes data on MS-DOS drives so that it
can be retrieved faster.
MS-DOS organizes data on the hard disk into a series of clusters
(allocation units) and then tracks which files are using which
clusters through directory structures and the file allocation tables
(FATs). Neither users nor applications need to know exactly where
specific data is located on the hard disk. When an application needs a
file, it simply asks MS-DOS to get it.
Over time, pieces of files may be spread all over the hard disk. When
this occurs, retrieving files requires more time. Defragmenter
reorganizes the clusters for faster access. (For example, information
is stored at the front of the disk, and parts of files are regrouped
together). Defragmenter uses interrupt calls 25H and 26H to move the
information stored in one cluster to another, directly updating the
FATs and directory structures.
Defragmenter operates at nearly the same level as MS-DOS. However, it
is still uses MS-DOS and is protected from direct interactions with
the following:
- Third-party partitioning utilities that modify or translate disk
geometry (such as Disk Manager and SpeedStor).
- DoubleSpace and third-party drive compression utilities.
Additional reference words: 6.00 3rd-party
-=-=-=-=-=-
ARTICLE-ID:Q94333
TITLE :SETVER Table Entries Are Not Maintained When Upgrading
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you do not install the MS-DOS 6 Upgrade in the current MS-DOS 5.0
directory, your old SETVER entries are not maintained.
More Information:
When you install the MS-DOS 6 Upgrade over MS-DOS 5.0, Setup updates
the current version table (maintained in SETVER.EXE). If you install
MS-DOS 6 in a new directory, Setup cannot update the old version table.
Workaround
----------
To work around this problem:
- Update the new SETVER.EXE file, adding the entries that your
software requires.
-or-
- Uninstall MS-DOS 6.0 and reinstall the MS-DOS 6 Upgrade in the
original MS-DOS directory.
Additional reference words: 6.00 5.00
-=-=-=-=-=-
ARTICLE-ID:Q94334
TITLE :Using MS-DOS 6 Upgrade Fdisk Program with EXTDISK.SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If were using COMPAQ MS-DOS version 4.0 or later before you upgraded
to MS-DOS 6.0, and you are using EXTDISK.SYS, you should use the
COMPAQ version of the Fdisk program. If you were using COMPAQ MS-DOS
version 3.31 or earlier before you upgraded to MS-DOS 6.0, and you are
using EXTDISK.SYS, you should contact Compaq for an updated version of
EXTDISK.SYS.
More Information:
Some COMPAQ systems use a driver called EXTDISK.SYS to access
secondary disk drives. This driver is MS-DOS version dependent. If you
use the MS-DOS version of Fdisk when EXTDISK.SYS is loaded, Fdisk
displays incorrect drive letters for the hard disks attached to the
second controller.
Workaround
----------
You can work around this problem by using the COMPAQ version of Fdisk.
To install the old version of Fdisk:
1. Delete FDISK.EXE from the DOS directory.
2. Copy FDISK.* from your COMPAQ MS-DOS disks to your DOS directory.
For example:
copy a:\fdisk.* c:\dos
3. Add Fdisk to the SETVER.EXE version table for your version of
COMPAQ MS-DOS. For example:
setver fdisk.exe 4.0
4. Restart your computer.
Note: You must use SETVER to tell EXTDISK.SYS that you are using a
previous version of MS-DOS. For more information, query on the
following words in the Microsoft Knowledge Base:
MS-DOS and SETVER and EXTDISK.SYS
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94335
TITLE :DoubleSpace Installation Fails to Update SYSTEM.INI File
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
-----------------------------------------------------------------------
Summary:
If you have multiple installations of Windows on your hard drive,
DoubleSpace may not correctly update the SYSTEM.INI file.
More Information:
Windows stores the location of the permanent swapfile in the [386enh]
section of the SYSTEM.INI file. When you install DoubleSpace, it must
find the SYSTEM.INI file and update the PermSwapDosDrive= setting to
point to the correct drive. If you have multiple copies of Windows
installed, or Windows is not in the path, DoubleSpace cannot find the
SYSTEM.INI file.
Workaround
----------
To workaround this problem, edit the SYSTEM.INI file and change the
drive letter for the PermSwapDosDrive= setting to the DoubleSpace host
drive. For example, if Windows is installed on drive C: and you
installed DoubleSpace, creating drive H:, you would need to edit you
SYSTEM.INI file and change the PermSwapDosDrive=c to
PermSwapDosDrive=h.
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q94336
TITLE :How DoubleSpace Assigns the Host Drive Letter
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you install Microsoft DoubleSpace, the installation program
normally leaves four unassigned drive letters between the last drive
and the host drive. For example, if you have two drives (C and D), a
RAM drive (E) and a network connection (F), DoubleSpace skips G, H, I,
and J, and uses drive K for the host drive.
If DoubleSpace detects Novell NetWare in memory, the host drive is
assigned one letter less than the LASTDRIVE= command in the CONFIG.SYS
file. If that drive letter is not available, then the host drive is
assigned the next available drive letter.
If you install DoubleSpace when device drivers that use drive letters
are not loaded (CD-ROM drivers or RAMDrives) or your network software
is not loaded, you may need to change the host drive letter. To do
this:
1. Change to the host drive (for example H).
2. Use the ATTRIB command to change the file attribute on the
DBLSPACE.INI file. For example:
attrib h:\dblspace.ini -s -h -r
3. Edit the DBLSPACE.INI file with a text editor such as MS-DOS
Editor.
4. Change the "LastDrive=" setting to the letter you want to be the
host drive.
5. Change the first parameter in the "ActivateDrive=" line to the same
letter you used in step 4.
Warning: Do not change the second parameter (represented by "xx") in
the following example:
Before change: ActiveDrive=H,xx
After change: ActiveDrive=D,xx
Warning: If you use the incorrect drive letters when you edit the
ActivateDrive= line in the DBLSPACE.INI file, the system may stop
responding (hang) when you restart it.
6. Save your changes and exit the text editor.
7. Reset the System, Hidden, and Read-Only attributes on the
DBLSPACE.INI file. For example:
attrib h:\dblspace.ini +s +h +r
8. Restart your computer (press CTRL+ALT+DEL).
Additional reference words: 6.00 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96555
TITLE :INTERLNK.EXE Doesn't Work with Xircom PPX and Pocket Adapter
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Interlnk does not work properly with the Xircom Parallel Port
Multiplexor (PPX) unless it is on the logical port assigned the
hardware interrupt. Since only one of the two logical ports can be
assigned the hardware interrupt and the Xircom Pocket Adapter must be
on the port assigned the hardware interrupt, you cannot use both
INTERLNK.EXE and the Xircom Pocket Adapter at the same time.
More Information:
By setting up a MS-DOS 6 multiple-configuration menu, you can start
your computer with the appropriate configuration for either the Xircom
Pocket Adapter or Interlnk.
Note: This information also applies to Intersvr, which also requires
the hardware interrupt.
Additional reference words: 6.00 multi-config multiconfig
-=-=-=-=-=-
ARTICLE-ID:Q94356
TITLE :CMOS Access Causes Dell 486D/50 to Hang with EMM386.EXE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use the EMM386.EXE HIGHSCAN switch, Dell 486D/50 machines may
stop responding ("hang") when you attempt to access the CMOS (by
pressing CTRL+ALT+ENTER).
Workaround
----------
To access your CMOS settings on a Dell 486D/50, restart (reboot) the
computer and press the F5 key or press and hold down the SHIFT key to
bypass all commands in your CONFIG.SYS and AUTOEXEC.BAT files. You can
then access your CMOS settings by pressing CTRL+ALT+ENTER. When you
have finished modifying your CMOS settings, restart the computer.
More Information:
The HIGHSCAN switch causes EMM386.EXE to scan the F000-F7FF upper
memory range. On Dell 486D/50 machines, EMM386.EXE detects that this
range is available. You should not have problems using this range on
the Dell 486D/50 except when you attempt to access the CMOS.
Additional reference words: 6.0 6 6.00 DX2 processor freeze lock up
-=-=-=-=-=-
ARTICLE-ID:Q96556
TITLE :MS-DOS: How to Return to Main Menu from Multi-Config Submenu
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are in a multiple-configuration submenu, you can return to the
main menu by pressing the BACKSPACE key.
Additional reference words: 6.0- multi-config multiconfig back space
menus startup start up submenu sub-menu
-=-=-=-=-=-
ARTICLE-ID:Q96557
TITLE :MS-DOS: Boot-Sector Viruses on Compressed Drives
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Boot-sector viruses are activated when you start your computer from
the infected drive (usually drive C) and alter MS-DOS startup code
located in the boot sector of your hard disk. DoubleSpace drives do
not actually have MS-DOS startup code to corrupt; however, if a virus
is detected on a compressed drive, it is likely that the host drive is
also infected.
You can detect and clean viruses from all local drives by using the
following command:
msav /c /l
More Information:
Removing Viruses from Boot Sectors of Compressed Drives
-------------------------------------------------------
In addition to startup code, the boot sector of a hard disk contains
information about the drive layout (including sizes of the drive, root
directory, and file tables). Compressed drives hold this information
in the boot sector; therefore, it is possible that a virus could
corrupt this information.
Which Boot Sector Is Executed During Startup?
---------------------------------------------
If drive C is uncompressed, its boot sector is run during system
startup. If drive C is compressed, the boot sector of its host drive
is run.
What the Boot Sector Does
-------------------------
The MS-DOS 5.0 and 6.0 boot sector startup code does the following:
- Confirms that the system files (IO.SYS and MSDOS.SYS) are the
first two files in the root directory of the drive.
- Loads and executes the first three sectors of the IO.SYS file.
The boot sector is executed by the master boot record (MBR). If you
have more than one partition, the MBR determines which one to run
using the partition table.
Additional reference words: 6.00 change
-=-=-=-=-=-
ARTICLE-ID:Q94357
TITLE :Difference Between DEFRAG and DBLSPACE /DEFRAGMENT
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
There are two ways to defragment a DoubleSpace drive. You can run
DBLSPACE /DEFRAGMENT, or you can run Microsoft Defragmenter
(DEFRAG.EXE).
More Information:
Files stored on a DoubleSpace drive become fragmented just as they do
on a physical drive.
Microsoft Defragmenter (DEFRAG.EXE) makes files contiguous as far as
MS-DOS is concerned, so files are contiguous in virtual clusters. For
example, a DoubleSpace drive would go from
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
C: [1123156-1-13-5-1-2-3-1521--123------- ]
to this:
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
C: [111112222333344455556---------------- ]
NOTE: In these examples, each number represents a piece of a file.
For example, each 1 indicates a piece of file 1.
DBLSPACE /DEFRAGMENT moves data within the compressed volume file
(CVF), so that all the free space is at the end. Using the same
example, the file would go from
H:\DBLSPACE.000: [1213--542---132-2--113---4 ]
C: [1123156-1-13-5-1-2-3-1521--123------- ]
to this:
H:\DBLSPACE.000: [121354213221134----------- ]
C: [1123156-1-13-5-1-2-3-1521--123------- ]
If you type DEFRAG to defragment a DoubleSpace drive, Defragmenter
runs DBLSPACE /DEFRAGMENT when it has completed. Once both types of
defragmentation have been done, the sample file would look like this:
H:\DBLSPACE.000: [121354213221134----------- ]
C: [111112222333344455556---------------- ]
Note that files are contiguous on the virtual drive (drive C), but not
within the CVF--free space is contiguous in both places.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94358
TITLE :MemMaker Err Msg with QEMM: 'Bad Command or Filename'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using QEMM to load your files into upper memory and the
FILES command has a plus (+) sign for a delimiter (for example,
C:\QEMM\LOADHI /R:1 FILES+30), you will receive the following error
message:
Bad Command or Filename
More Information:
Using a plus sign as a delimiter is not standard for MS-DOS. If your
QEMM command contains "FILES+nn", MemMaker returns the error message
noted above.
To work around the problem, remove the QEMM "FILES+nn" command from
your AUTOEXEC.BAT file and use the "files=" setting in your CONFIG.SYS
file to specify the number of open files. Run MemMaker again to ensure
that you have the optimal memory configuration.
Additional reference words: 6.00 handles
-=-=-=-=-=-
ARTICLE-ID:Q94377
TITLE :MemMaker Cannot Process Files with More Than 511 Lines
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If your CONFIG.SYS, AUTOEXEC.BAT, or SYSTEM.INI file has 512 or more
lines, MemMaker displays the following error message:
MemMaker cannot continue because the AUTOEXEC.BAT,
CONFIG.SYS, or Windows SYSTEM.INI file is too long.
The file must be less than 512 lines long
* To undo MemMaker's changes, press ENTER.
To work around this problem, exit MemMaker, reduce the size of the
file that is causing the error, and restart MemMaker.
More Information:
You can use MS-DOS Editor to determine the length of a text file. For
example:
1. Start MS-DOS Editor and load a text file such as AUTOEXEC.BAT. For
example, type the following and press ENTER:
EDIT \AUTOEXEC.BAT
2. Press CTRL+END.
The number of lines in the text file is displayed in the
lower-right corner of the screen.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96558
TITLE :MS-DOS 6 Setup Files Installs 80386- and 80486-Specific Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 Setup installs files that are specific to 80386 and 80486
processors even if your processor cannot use these files.
You can delete the following files if you have an 8088 or 8086:
File(s) Requires
------- --------
HIMEM.SYS 80286 and more than 640 kilobytes (K) of RAM
SMARTDRV.EXE HIMEM.SYS
LOADFIX.COM Useful only if using DOS=HIGH
MSTOOLS.DLL Windows 3.1 (or greater) in standard mode
SMARTMON.* Windows 3.1 (or greater) in standard mode
DBLWIN.HLP Windows 3.1 (or greater) in standard mode
Files you can delete if you have an 8088, 8086, or 80286:
File(s) Requires
------- --------
EMM386.EXE 80386 or greater and HIMEM.SYS
MEMMAKER.* 80386 or greater
CHKSTATE.SYS 80386 or greater (used by MEMMAKER.EXE)
VFINTD.386 Windows 3.0 (or greater) in 386 enhanced mode
WINA20.386 Windows 3.0 (or greater) in 386 enhanced mode
MONOUMB.386 Windows 3.0 (or greater) in 386 enhanced mode
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96560
TITLE :POWER.EXE and Advanced Power Management (APM) Support
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You can install the Power program (POWER.EXE) even if your BIOS does
not support the Advanced Power Management (APM) specification. After
you install POWER.EXE in the CONFIG.SYS file, the POWER command
(without any switches) provides status information.
On systems without APM support, POWER displays the following:
Power Management Status
-----------------------
Setting = ADV:REG
CPU: idle 90% of the time
On systems with APM support, POWER displays the following additional
information reported by the BIOS:
Power Management Status
-----------------------
Setting = ADV:REG
CPU: idle 90% of the time
AC Status: OFFLINE
Battery status: High
Battery life (%): 90
More Information:
POWER.EXE detects whether your system has an APM-compliant BIOS and
then adapts accordingly.
When POWER.EXE detects that your system is idle, it saves power by
issuing a CPU HALT instruction. HALT stops CPU execution until the
next hardware interrupt occurs (this is usually the timer interrupt,
which occurs 52 times per second). On systems without an APM-compliant
BIOS, testing reveals a 5% power savings.
If your system has an APM-compliant BIOS, POWER.EXE communicates with
the BIOS. Depending on the frequency of the idle signals from POWER,
the APM-compliant BIOS can save power by shutting down the display or
hard disk, switching the processor to a slower speed, or suspending
the system entirely.
Additional reference words: 6.00 five percent
-=-=-=-=-=-
ARTICLE-ID:Q96562
TITLE :Running Windows 3.1 with Advanced Power Management Systems
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system version 3.1
--------------------------------------------------------------------
Summary:
If are running Windows 3.1 on a system with BIOS chips that support
advanced power management (APM), select MS-DOS System With APM as the
computer type in Windows Setup. This allows Windows power management
services take over power management from POWER.EXE. On computers
without APM support, you can safely run POWER.EXE with Windows.
Additional reference words: 6.00 3.10
-=-=-=-=-=-
ARTICLE-ID:Q94383
TITLE :Error Copying Files with Interlnk on Stacker Volume
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Using Interlnk's INTERSVR command on a volume that has been compressed
using Stacker version 2.0 may fail if INTERSVR incorrectly calculates
the amount of free disk space. If this is the case and you attempt to
copy a file to the compressed volume, you will receive the following
error message:
Error writing drive
More Information:
When you run INTERSVR on a compressed Stacker volume, Interlnk may
incorrectly calculate the amount of free disk space on the server
machine. Although the DIR command (when issued locally) may report
little or no free disk space, the DIR command issued through Interlnk
may report several megabytes of free disk space.
This may potentially cause data corruption, but a reproducible case
hasn't been found.
This problem occurs with Stacker; this problem does not occur with
Microsoft DoubleSpace.
Stacker is manufactured by STAC Electronics, a vendor independent
of Microsoft; we make no warranty, implied or otherwise, regarding
this product's performance or reliability.
Additional reference words: 6.0 3rdparty dblspace
-=-=-=-=-=-
ARTICLE-ID:Q96563
TITLE :How MS-DOS 6 Upgrade Setup Handles NT Flexboot
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Microsoft Windows NT has a Flexboot feature that allows you to choose
the operating system you want to start: Windows NT or MS-DOS. This
feature is controlled by the Windows NT custom master boot record
(MBR), which calls NTLDR when you start your computer. NTLDR then
loads a menu for you to choose which operating system to start. If you
choose MS-DOS, a hidden file called BOOTSECT.DOS is read to start
MS-DOS.
More Information:
If Setup detects NTLDR and BOOTSECT.DOS, it does not update the MBR,
thus preserving Flexboot.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96564
TITLE :Installing MS-DOS 6 Upgrade over OS/2 Boot Manager
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The setup program for MS-DOS 6 Upgrade preserves command line driven
dual-boot programs but disables boot sector driven (that is,
menu-displayed) dual-boot schemes. Therefore, Setup disables OS/2 Boot
Manager versions 2.0 and 2.1; however, this feature can easily be
restored.
More Information:
Boot Sector Driven Dual-Boot Programs
-------------------------------------
Microsoft OS/2 version 1.1 and Compaq OS/2 version 1.2 are the only
versions that use the boot sector driven dual-boot feature. With these
schemes, the boot sector loads a menu from which you choose the
operating system you want to start. MS-DOS 6 Setup overwrites this
information, thus disabling OS/2; you must reinstall OS/2 to enable
this feature.
Command Line Driven Dual-Boot Programs
--------------------------------------
Other OS/2 versions, which use a command line driven dual-boot program
(BOOT /OS2 or BOOT /DOS), are unaffected by MS-DOS 6 Setup.
OS/2 Versions 2.0 and 2.1
-------------------------
In OS/2 versions 2.0 and 2.1, OS/2 Boot Manager displays a menu from
which you choose the operating system you want to start. OS/2 Boot
Manager is controlled by a 1-megabyte (MB) partition on the boot disk.
MS-DOS 6 Setup disables this partition by making the file allocation
table (FAT) partition active. To enable OS/2 Boot Manager, use the
Fdisk program to reactivate the 1-MB non-MS-DOS partition.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q94384
TITLE :Err Msg: MSBACKUP Program Files Must Be Located On Hard Disk
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you try to run Microsoft Backup from a floppy disk to restore files to a
hard disk drive, the following error message is displayed:
MSBACKUP program files must be located on your hard disk.
You cannot start MSBACKUP from a floppy disk.
To restore files to a hard disk drive that does not have MS-DOS 6.0
installed, use the following steps:
1.Insert Disk 1 of the MS-DOS 6.0 disk set in your floppy disk drive. Type
"setup/m" (without the quotation marks) and press ENTER to install a
minimal installation.
2.Remove Disk 1 from your floppy disk drive and restart the computer.
3.Replace Disk 1, type "setup/e" (without the quotation marks) to install
optional components.
You can now run Microsoft Backup from the DOS subdirectory and restore
files.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96593
TITLE :Why DoubleSpace Leaves 2 Megabytes Free on the Host Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you compress an existing drive, DoubleSpace leaves approximately
2 megabytes free on the host drive. This space is reserved for files
that DoubleSpace needs when rebooting during the compress-in-place
(CIP) process. The following files are stored on the host drive during
the CIP process:
COMMAND.COM
DBLSPACE.BIN
DBLSPACE.EXE
DBLSPACE.HLP
DBLSPACE.INI
DEFRAG.EXE
DoubleSpace also stores copies of the AUTOEXEC.BAT and CONFIG.SYS
files on the uncompressed portion of the host drive as follows:
AUTOEXEC.000
CONFIG.000
Note: If there are already AUTOEXEC.000 or CONFIG.000 files on the
host drive, DoubleSpace uses 001 for the file extension. If that
filename is used, DoubleSpace uses 002, and so forth.
DoubleSpace uses these files if you restart your computer during a CIP
process. These files are also used when you create a new DoubleSpace
drive or change the size of an existing DoubleSpace drive.
The unused portion of the 2 megabytes of reserved space is used during
the CIP process.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93434
TITLE :MemMaker Copies HIMEM.SYS and EMM386.EXE to C:\DOS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker, and you have MS-DOS installed on a drive other
than your startup (boot) drive (which is usually drive C), MemMaker
creates a DOS directory on the startup drive and copies the following
files to that directory:
- MEMMAKER.EXE
- MEMMAKER.HLP
- MEMMAKER.INF
- EMM386.EXE
- HIMEM.SYS
- CHKSTATE.SYS
- SIZER.EXE
During the optimization process, it also creates MEMMAKER.STS.
Note: The original startup drive might not be drive C if you have a
program such as Stacker from Stac Electronics.
More Information:
For example, if your DOS directory is located on your D drive,
MemMaker creates C:\DOS, copies the files listed above to that
directory, and changes the DEVICE= statements in the CONFIG.SYS file
to point to drive C to ensure that the files are found when MemMaker
restarts the system. MemMaker copies these files to the startup drive
because MemMaker moves the device= statements for HIMEM.SYS AND
EMM386.EXE to the top of the CONFIG.SYS file. Because these files are
then loaded before any devices that might perform drive swapping,
MemMaker must be sure it can find the files it needs to optimize your
system's memory.
MemMaker does not remove these files after it has completed its
optimization. To remove these changes, edit the CONFIG.SYS file and
make sure the device= lines for HIMEM.SYS and EMM386.EXE point to the
drive that contains your full MS-DOS directory. You can then safely
delete the C:\DOS directory.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96603
TITLE :Balancing Power Conservation and Performance with POWER.EXE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The Power program (POWER.EXE) monitors keyboard polling and the
Application Idle interrupt to determine if a system is idle; it
monitors use of the hard disk, video functions, and MS-DOS functions
to determine if a system is busy.
POWER.EXE may incorrectly determine that your machine is idle if you
are using communication programs, computation-intensive programs, or
other programs that infrequently access the hard disk. When POWER.EXE
detects that the system is idle, it halts or slows down the CPU, which
adversely affects application performance if your machine is not truly
idle.
More Information:
With the ADV[:MIN|REG|MAX] command line switch, you can indicate
whether your higher priority is power savings or application
performance. Specifically, the ADV parameter controls the keyboard
polling detection. If application performance is suffering because of
false idle detections, you can use the ADV:MIN option to trigger fewer
false idle detections. However, this option provides minimal power
savings when your machine is idle. The ADV:MAX option provides maximum
power savings but increases the chances of false idle detections. The
default setting is ADV:REG, which balances power conservation with
performance.
Type "power" (without the quotation marks and without any parameters)
at the MS-DOS command prompt to determine the current settings.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96604
TITLE :MS-DOS 6 Upgrade Setup Err Msg: Hard Disk Is Not Readable
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The error message "Hard disk is not readable" has several causes. The
most common cause is including the device driver ASPI4DOS.SYS in your
CONFIG.SYS file. If you use this device driver, remark it out in your
CONFIG.SYS file, along with any expanded memory managers (such as
EMM386.EXE or Qemm). You can then install MS-DOS 6 Upgrade and later
restore the line(s) in your CONFIG.SYS file. This problem commonly
occurs when you have a second SCSI device (such as a CD-ROM drive).
More Information:
This error can also occur if any of the following conditions exist:
- A sector read error occurs when reading the master boot records or
the partition boot records. Setup reads this information from the hard
disk and then writes the MBOOT?.DAT and PBOOT?.DAT files to the
Uninstall disk.
- A sector read error occurs when reading the BIOS parameter block
(BPB). Setup reads this information from the hard disk and then writes
the BPB?.DAT files to the Uninstall disk.
- A sector read error occurs when reading the root directory from the
destination hard disk. Setup reads this information from the hard disk
and then writes the ROOT.DAT file to the Uninstall disk.
- A sector read error occurs when reading the file allocation table
(FAT) from the destination hard disk. Setup reads this information
from the hard disk and then writes the ROOT.DAT file to the Uninstall
disk.
- A sector read error occurs when performing the partition table updates
on the attached hard drives. Partition table updates involve
converting MS-DOS-compatible partitions to type 1, 4, or 6 and then
converting logical sectors into 512-byte sectors in the partition boot
record.
- A sector read error occurs when reading the master boot record and
partition boot records to check for unformatted partitions.
- A sector read error occurs when reading the root directory as Setup
tries to obtain the first two root directory entries and determine if
they are MS-DOS system files (IO.SYS and MSDOS.SYS). The above error
can also occur if a sector read error occurs when moving non-MS-DOS
system file entries to make room for the MS-DOS system files in the
first two directory entries.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96625
TITLE :EMM386.EXE and VCPI Services
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
EMM386.EXE version 4.45, included with MS-DOS version 6.0, provides
support for the Virtual Control Program Interface (VCPI) without
having to set an expanded memory page frame and without having to
specify a VCPI memory pool.
VCPI services are provided by default -- no special switches or
parameters are required. If you wish to disable VCPI support you must
use the NOVCPI switch on the EMM386.EXE command in the CONFIG.SYS
file.
More Information:
Several popular MS-DOS applications are "DOS extended" and can
share extended memory and use the protected mode of 80386 and higher
processors through the Virtual Control Program Interface (VCPI).
VCPI is an extension to the expanded memory services (EMS)
interface, and is typically implemented by an EMS emulator such
as EMM386.EXE or Quarterdeck's QEMM386.SYS.
Without VCPI support, "DOS extended" applications would not be
able to run when a system is running in virtual 8086 mode. EMS
emulators use virtual 8086 mode to provide EMS memory mapping
and/or create Upper Memory Blocks (UMBs).
To get VCPI support in the version of EMM386.EXE provided with both
MS-DOS 5.0 and Windows 3.1, you must configure EMM386.EXE to emulated
EMS.
To enable VCPI without EMS support when the NOEMS switch is used, you
must specify a VCPI memory pool size. For example this command can be
used with MS-DOS 5.0's EMM386 to provide 1MB of VCPI memory:
DEVICE=EMM386.EXE 1024 NOEMS
The MS-DOS 6.0 version of EMM386 (4.45) enables VCPI support even when
the NOEMS switch is used without specifying a VCPI size parameter.
Any EMM386 device command that does not include the NOVCPI switch
provides VCPI services.
With the MS-DOS 6 version of EMM386, VCPI memory is sized using
the same parameters as the EMS pool size -- with the EMM386
[memory] and MIN= parameters.
For more information on the EMM386.EXE device driver and the
NOVCPI switch, type HELP EMM386.EXE at the MS-DOS command
prompt.
Additional reference words: 6.00 manager system exteners extenors
-=-=-=-=-=-
ARTICLE-ID:Q96626
TITLE :Uninstall does not Remove DEFAULT.*, DOSBACK.* and .INI Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you Uninstall MS-DOS 6 Upgrade, it does not remove the DEFAULT.*,
DOSBACK.* files from the DOS directory.
All files installed by Setup are removed by Uninstall. DEFAULT.*,
DOSBACK.*, and any .INI files created by optional utilities are not
removed.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96627
TITLE :No Warning if Setup Fails to Modify Your SYSTEM.INI File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run Setup with the /E parameter to install the optional
utilities, Setup does not display any warning or error messages if it
is unable to modify your SYSTEM.INI file because it cannot find the
[386enh] section header.
If the SYSTEM.INI file is not updated with the
DEVICE=C:\DOS\VFINTD.386 line, you receive the following error message
when you start Microsoft Backup for Windows:
Microsoft Backup is not properly installed on this system.
Workaround
----------
To work around this problem, edit your SYSTEM.INI file and add the
following line to the [386enh] section:
DEVICE=C:\DOS\VFINTD.386
Microsoft Backup for Windows should function correctly after you
restart Windows.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96628
TITLE :Screen Does Not Pause With MEM /C /P OR DIR /P
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some older CGA display adapters don't properly handle the scrolling of
text. If you are using on of these cards, the DIR and MEM command /P
parameter may not function correctly.
To work around this problem, add a device statement for ANSI.SYS with
the /S parameter to the CONFIG.SYS file. For example:
device=c:\dos\ansi.sys /s
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96629
TITLE :MS-DOS 6 Upgrade Setup Does Not Remove All Previous DOS Files
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6 Upgrade Setup does not delete previous and incompatible
versions of some MS-DOS files. For example, Setup does not delete the
following MS-DOS 5.0 files because they don't ship with MS-DOS 6
Upgrade:
SMARTDRV.SYS
JOIN
ASSIGN
If you want to use these files, you can use Setver to change the
version number that MS-DOS reports to the programs.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96633
TITLE :OEM Setup Copies All Files By Default
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS 6.0 OEM Setup program copies all supplied files by default;
this includes the optional Windows utilities BACKUP, UNDELETE, and
ANTI-VIRUS. These components will be copied onto the hard drive
whether or not Windows is installed on the system.
More Information:
The files for the Windows utilities will be copied to the hard drive,
however, they will not be setup correctly if Windows is not installed
at the time of the initial setup. If Windows is later added to the
system, running SETUP /E will properly configure the Windows
utilities.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q96655
TITLE :MS-DOS 6.0 SETUP /E: Error Renaming Old Utilities
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When running MS-DOS 6 Setup with the /E parameter to install the
optional programs, Setup may display the following error:
Unrecoverable Error
Error renaming old utilities.
Press ENTER to exit Setup.
This can occur if Setup is using invalid drive information for the
drive where MS-DOS is installed. The drive information can be
corrupted by running SETUP /E when the MS-DOS directory is not listed
in the path.
To correct this problem, exit Setup and restart your computer. Make
sure the MS-DOS directory is in the path and run SETUP /E again.
More Information:
This is a known problem with MS-DOS 6.0 Setup. The MS-DOS directory
must be included in the path to run SETUP /E. If SETUP /E is run when
the MS-DOS directory is not in the path, Setup displays a warning
message stating that it is unable to locate the MS-DOS directory. If
you exit Setup, modify the path to include the MS-DOS directory, and
then run SETUP /E again, the drive information for the MS-DOS drive is
invalid. For example the "Space available on drive" information might
be incorrect. This invalid information results in the unrecoverable
error listed above.
Microsoft has confirmed this to be a problem in MS-DOS Setup version
6.0. We are researching this problem and will post new information
here as it becomes available.
Additional reference words: 6.00 BUSETUP BUSETUP.EXE SETUP.EXE install
optional programs utilities
-=-=-=-=-=-
ARTICLE-ID:Q96695
TITLE :Installation programs and Multi-Config
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Many application installation programs modify the CONFIG.SYS and
AUTOEXEC.BAT files. Most installation programs which modify the
CONFIG.SYS file either adding lines at the top or at the bottom of the
file.
If you have a [COMMON] block at the end of your CONFIG.SYS file, you
shouldn't have any trouble with the programs that add lines at the
bottom of the file.
The most common problem occurs when installation programs update
a specific driver in the CONFIG.SYS file and there are multiple
instances of that driver. Many installation programs only update the
first (or last) occurrence of the driver. If you avoid multiple
occurrences of device drivers in CONFIG.SYS by using a [COMMON]
section, you will probably never experience a problem.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96697
TITLE :Using ANSI Characters with CHOICE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The CHOICE command allows only one key to be used per selection. For
example, you cannot use 12 (twelve) as key selection. CHOICE
interprets this as 1 and 2. however, you can use the ANSII character
set by holding down the ALT key and entering the appropriate 3-key
combination on the numeric keypad. Not all combinations work but you
can use up to 222 different entries from the 255 available. The table
below details the 255 characters.
0-27 Do not work
28-31 Work
32 Do not work
33-255 Work with the some xceptions noted below
More Information:
ALT + 37. displays the '%' sign on your screen.
When you use the percent sign in a batch file it acts as a replaceable
parameter. You must use two percent signs (one immediately after the
other) to use the % symbol. To do this, you need to enter ALT + 37
twice.
ALT + 47 displays the '/' forwardslash.
The forwardslash will not work with CHOICE.
ALT + 60 displays the '<' symbol.
This represents a redirector and does not work with the CHOICE
command.
ALT + 62 displays the '>' symbol.
This represents a redirector and does not work with the CHOICE
command.
ALT + 124 displays the '|' (pipe) symbol.
This represents the MS-DOS pipe and does not work with the CHOICE
command.
ALT + 127 represents the delete key.
This does not work with the CHOICE command.
ALT + 255 represents the spacebar key.
This works if you enter ALT + 255. This does not work if you press the
spacebar key.
If you use the extended characters between 128 and 165, you should use
the /S switch to treat choice keys at case sensitive.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96700
TITLE :MemMaker Cannot Continue if Newwave is in Your AUTOEXEC.BAT
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker, if Newwave is in your AUTEOXEC.BAT file,
MemMaker cannot continue when you exit Newwave.
To work around this problem:
1. Use the REM command to remark out Newwave in your AUTOEXEC.BAT
file. For example:
rem newwave
2. Restart your computer.
3. Run MemMaker.
4. When MemMaker has completed, take the REM command out of your
AUTOEXEC.BAT file so Newwave can load.
5. Restart your computer.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q96701
TITLE :DoubleSpace Err Msg: Unknown Error Cause by Watchdog PC
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
You may receive the following error when you install DoubleSpace:
Unknown Error
The error is caused by a conflict between DoubleSpace and Watchdog PC
Data Security software.
To work around this problem, disable your Watchdog PC Data Security
software before you install DoubleSpace.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q57730
TITLE :Err Msg: ""No Room for System on Destination Disk"" with SYS
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system versions 3.x, 4.x, 5.0, 5.0a,
and 6.0
--------------------------------------------------------------------
Summary:
In the Microsoft MS-DOS user's manuals for versions 3.3, 3.3a, 4.0,
4.0a, 4.01, 4.01a, 5.0, and 5.0a, the SYS command entry states that
you do not need to reformat your disk when you upgrade to a later
version of MS-DOS. SYS updates system disks even though the new system
files are larger and must be broken up to fit in the available disk
space.
However, when upgrading some system disks, SYS returns the following
error message:
No room for system on destination disk
This error message is caused by one of the following:
- There is not enough free space anywhere on the destination disk for
the relocatable part of the system files.
Solution
--------
Delete some files to make room for the system files. This
is documented in Appendix F of the "Microsoft MS-DOS User's
Reference Manual" for versions 4.01 and earlier, under the "No room
for system on destination disk" error message. If you are running
version 5.0, see the Application Note titled "MS-DOS 5.0 Messages
Reference," PD0489. To obtain application notes, call Microsoft
Product Support Services at (206) 454-2030.
- A file occupies the first clusters of the disk on a non-system
disk.
Solution
--------
If a disk utility is available to find which file(s) occupy the
first clusters of the disk, erase or move those files to clear
the space needed for the system.
If you have the MS-DOS 5 Upgrade or the MS-DOS 6 Upgrade, you can
run Setup with the /M parameter.
If the previous two options are not available, you must reformat the
disk.
- The disk has an original equipment manufacturer (OEM) version of
MS-DOS that does not use the Microsoft naming convention for the
hidden system files.
Solution
--------
Contact the OEM supplier for an MS-DOS upgrade. You should continue
running that dialect of MS-DOS. However, if you must change to the
Microsoft MS-DOS packaged product, see the information provided
below.
More Information:
There is a quick solution for the OEM MS-DOS problem mentioned above.
This solution requires that you have a good understanding of MS-DOS,
and that you have a third-party utility to remove the Hidden, System,
and Read-Only attributes from the system files.
The MS-DOS SYS command looks for the files named IO.SYS and MSDOS.SYS
on the destination disk. If these files are not found, because they do
not exist or are named differently, SYS assumes the disk is not a
system disk and attempts to install the new system files starting at
cluster 2 (IO.SYS must be contiguous starting at cluster 2).
Some OEMs, such as IBM, use different names for the system files. To
make SYS work with these disks, you can rename the two files to IO.SYS
and MSDOS.SYS, as in the following example. (The following example
uses IBM PC-DOS naming conventions.)
1. Using a third-party attribute change utility, remove the Hidden,
Read-Only, and System attributes from IBMBIO.COM and IBMDOS.COM.
MS-DOS does not provide a utility to set or reset the Hidden and
System attributes of a file, because you should not tamper with
these files.
2. Rename these two files as follows:
ren ibmbio.com io.sys
ren ibmdos.com msdos.sys
3. Use the attribute utility to replace the Hidden, Read-Only, and
System attributes.
The SYS command should work correctly after you have made the above
changes. Remember that the SYS command does not transfer COMMAND.COM,
so you must do that manually.
Additional reference words: 3.30 3.30a 4.00 4.00a 5.00 5.00a 6 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93582
TITLE :DoubleSpace Err Msg: 'There Are No More Drive Letters'
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
-----------------------------------------------------------------------
Summary:
If there are not enough drive letters available to DoubleSpace, or you
have not installed DoubleSpace on your hard disk and you attempt to
mount a compressed floppy disk, you may receive the following error
message:
There are no more drive letters reserved for dblspace to use.
To add more, use the options selection from the tools menu.
More Information:
To work around this problem, follow the appropriate procedure below.
DoubleSpace Does Not Have Enough Drive Letters Available
--------------------------------------------------------
If there are no drive letters available for DoubleSpace to mount a
drive, use the following procedure to increase the Last Drive Reserved
For DoubleSpace's Use setting.
1. To run DoubleSpace, type "DBLSPACE" (without the quotation marks)
at the command prompt.
2. From the Tools menu choose Options.
3. Increase your Last Drive Reserved For DoubleSpace's Use setting by
at least one letter.
Note: This procedure causes the host drive letter to change. If
your Windows permanent swap file is located on that host drive,
when you start Windows, you will receive an error message
indicating that your permanent swap file is corrupt. To correct
this problem, run Control Panel and reconfigure your permanent swap
file for the new host drive.
You Are Attempting to Mount a Compressed Floppy Disk
----------------------------------------------------
To work around this problem create a very small new DoubleSpace drive
and then delete it. This creates the DBLSPACE.INI file and loads
DBLSPACE.BIN into memory so you can read the compressed floppy drive.
To do this:
1. To run DoubleSpace, type "DBLSPACE" (without the quotation marks)
at the command prompt.
2. Choose Custom Setup
3. Choose Create A New Empty Compressed Drive.
4. Select a drive you want to use.
5. When you are prompted for the the amount of free space to leave on
the drive, type a number larger than your hard drive.
6. After DoubleSpace tells you the maximum amount free space you can
leave on your drive, type in that number. For example, if
DoubleSpace tells you the maximum amount of free space is 95.55
megabytes (MB), leave 95 MB of free space.
7. Choose Continue.
8. Press the C key to create the compressed drive.
You can now mount the compressed floppy disk. If you do not want to
keep the DoubleSpace drive you created, type the following command at
the MS-DOS command prompt and restart your computer:
deltree /y dblspace.001
As an alternative, you also use the following procedure to create a
DBLSPACE.INI file and load DBLSPACE.BIN in memory:
1. Create a C:\DBLSPACE.INI file (where C is your startup disk) with a
text editor such as Edit. The DBLSPACE.INI file 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 DOS directory to the root directory of
your startup (boot) drive. For example:
copy c:\dos\dblspace.bin c:\
3. Restart your 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:
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93584
TITLE :EMM386.EXE: Default DMA Buffer Size
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
EMM386.EXE's default direct memory access (DMA) buffer size has
increased from 16 to 32 kilobytes.
More Information:
All DMA buffers are stored in extended memory regardless of size.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93592
TITLE :Correcting Illegal Directory Names With DELTREE and MOVE
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS DEL command cannot be used to delete a directory with a
blank space in the name (for example "C:\MY WORK"). However, you can
use the MS-DOS 6 programs DELTREE and MOVE to delete or rename these
directories.
More Information:
Some utilities and installation programs allow you to create directory
names with illegal characters (such as spaces). Because a directory
name with a space or other illegal character is not expected, DEL was
not designed to work with them.
Using DELTREE to Delete Illegal Directories
-------------------------------------------
The DELTREE program can be used to delete illegal directories. For
example, type the following at the MS-DOS command prompt:
DELTREE "MY WORK"
Note: You must type the quotation marks.
Using MOVE to Rename Illegal Directories
----------------------------------------
The MOVE program can be used to rename illegal directories. For
example, type the following at the MS-DOS command prompt:
MOVE "MY WORK" MY_WORK
Note: You must type the quotation marks.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93599
TITLE :Difference Between 'DBLSPACE /CHKDSK' and 'CHKDSK'
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run DoubleSpace with the /CHKDSK switch (for example, type
DBLSPACE /CHKDSK) on a DoubleSpace partition, it analyzes the
DoubleSpace file allocation table (FAT) for consistency. The
DoubleSpace FAT is a separate data structure from the MS-DOS FAT.
To check the DoubleSpace FAT and the MS-DOS FAT, you must run both
"DBLSPACE /CHKDSK" and "CHKDSK" on the DoubleSpace drive. To analyze
and repair any problems, add the /F switch to both commands.
More Information:
MS-DOS maintains a data structure for the FAT that maintains a "map"
of the disk usage (both files and free space) recording the status of
each sector on the disk. When DoubleSpace is installed, it creates
its own FAT and maps the MS-DOS FAT to the DoubleSpace FAT.
Additional reference words: 6.0 double space
-=-=-=-=-=-
ARTICLE-ID:Q93602
TITLE :How to Disable F5 and F8 During Startup in MS-DOS 6.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 allows you to bypass both AUTOEXEC.BAT and CONFIG.SYS by
pressing the F5 key as you are starting your computer. This can
disable the effectiveness of some password-protection schemes. In
order to disable this feature, add the following line to CONFIG.SYS:
SWITCHES=/N
This line disables both the F5 and F8 keys, which allow you to modify
your startup configuration during the boot process. Note: This line
can be put anywhere in CONFIG.SYS.
Additional reference words: 6.00 howto startup start up
-=-=-=-=-=-
ARTICLE-ID:Q93603
TITLE :After Dark Screen Saver Can Corrupt Screen
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
After Dark's MS-DOS-based screen saver, AD_DOS.COM, can corrupt the
screen during MS-DOS Setup if it is allowed to clear image on the
screen and replace it with a screen saver image. Once the screen saver
activates, you can return to a normal screen by pressing any key.
However, if this occurs during Setup, the restored screen is filled
with random characters. Setup continues to function correctly, but you
may have difficulty understanding the prompts.
Additional reference words: 6.00 blanking garbled characters fuzzy
distorted 3rdparty
-=-=-=-=-=-
ARTICLE-ID:Q93652
TITLE :System Hangs When Loading WFWG Drivers
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows for Workgroups version 3.1
--------------------------------------------------------------------
Summary:
If DBLSPACE.SYS is loaded into upper memory after PROTMAN.DOS, the
system may stop responding ("hang") when the network drivers are
loading.
To work around this problem, load DoubleSpace high before you load
PROTMAN.DOS by placing the "device" lines in your CONFIG.SYS file in
the following order:
devicehigh=c:\dos\dblspace.sys /move
device=c:\windows\protman.dos /i:c:\windows
Additional reference words: 6.0 3.1 3.10 wfw wfwg dblspace
-=-=-=-=-=-
ARTICLE-ID:Q93653
TITLE :Novell's NETX Reports MS-DOS 6.0 as MS-DOS 5.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When running with MS-DOS version 6.0, Novell's NETX versions 3.31 and
earlier report the operating system version as MS-DOS 5.0.
More Information:
NETX requires MS-DOS 5.0 or earlier--it does not run with MS-DOS 6.0
unless you use SETVER.EXE to trick it. Since SETVER tells NETX that
the MS-DOS version is 5.0, NETX reports the MS-DOS version as 5.0.
This behavior could be a problem for network administrators who
configure their systems to map to specific directories for different
versions of MS-DOS, depending on the version reported by NETX. For
example, suppose that machines running MS-DOS 3.3 are mapped to
Y:\DOS\V3.30 and machines running MS-DOS 5.0 are mapped to
Y:\DOS\V5.00. In this example, when you use SETVER to tell NETX you
are running MS-DOS 5.0, you are logged onto the Y:\DOS\V5.00
directory.
Additional reference words: 6.0 netx.com netx.exe
-=-=-=-=-=-
ARTICLE-ID:Q90554
TITLE :DoubleSpace Drives Not Viewable in NT MS-DOS Prompt
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Beta 2 Release of Microsoft Windows NT operating system
version 3.1
--------------------------------------------------------------------
Summary:
When using MS-DOS 6 Upgrade DoubleSpace with Windows NT configured for
Dual Boot, you cannot see your compressed files or run your
MS-DOS-based programs when running MS-DOS Prompt under Windows NT.
More Information:
To accomplish disk compression, DoubleSpace uses a device driver
(loaded at system startup) to intercept disk reads and writes from the
command line and MS-DOS-based applications. When you run MS-DOS Prompt
under Windows NT, the DoubleSpace device driver is not loaded.
This feature is under review and will be considered for inclusion in a
future release of Windows NT.
Additional reference words: 6.0 dblspace double space
-=-=-=-=-=-
ARTICLE-ID:Q90564
TITLE :MS-DOS Err Msg: DoubleSpace Cannot Defragment Because...
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are running a screen-saver program when you attempt to install
DoubleSpace from MS-DOS 6 Upgrade, you may receive the following error
message:
DoubleSpace cannot defragment C because of an unknown error
To work around this problem, remove the screen-saver from your
CONFIG.SYS or AUTOEXEC.BAT file, restart your computer and install
DoubleSpace. After DoubleSpace is successfully installed, you can add
the screen-saver to your CONFIG.SYS or AUTOEXEC.BAT file.
Additional reference words: 6.0 screensaver blank black blanker tsr
dblspace
-=-=-=-=-=-
ARTICLE-ID:Q90565
TITLE :Changes Made by MS-DOS Setup to the SYSTEM.INI File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you install Microsoft MS-DOS 6 Upgrade, Setup adds the following
line to the [386Ehn] section of the SYSTEM.INI files if you install
the Windows programs.
device=vfintd.386
The virtual device driver (VxD) vfintd.386 adds support to Windows for
virtualize your floppy drives to prevent conflicts between multiple
virtual machines.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q90571
TITLE :Applications That Require SETVER.EXE for MS-DOS 6.0
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Some applications check the MS-DOS version number before executing and
may not run when they detect version "6.00." To work around this
limitation, use SETVER.EXE, included with MS-DOS 6 Upgrade.
The table lists the files in the default SETVER.EXE version table in
MS-DOS version 6.0:
Filename MS-DOS Version
--------------------------
KERNEL.EXE 5.00
NETX.COM 5.00
NETX.EXE 5.00
NET5.COM 5.00
BNETX.COM 5.00
BNETX.EXE 5.00
EMSNETX.EXE 5.00
EMSNET5.EXE 5.00
XMSNETX.EXE 5.00
XMSNET5.EXE 5.00
DOSOAD.SYS 5.00
REDIR50.EXE 5.00
REDIR5.EXE 5.00
REDIRALL.EXE 5.00
REDIRNP4.EXE 5.00
EDLIN.EXE 5.00
BACKUP.EXE 5.00
ASSIGN.COM 5.00
EXE2BIN.EXE 5.00
JOIN.EXE 5.00
RECOVER.EXE 5.00
GRAFTABL.COM 5.00
LMSETUP.EXE 5.00
STACKER.COM 5.00
NCACHE.EXE 5.00
NCACHE2.EXE 5.00
IBMCACHE.SYS 5.00
XTRADRV.SYS 5.00
WINWORD.EXE 4.10
EXCEL.EXE 4.10
LL3.EXE 4.01
REDIR4.EXE 4.00
REDIR40.EXE 4.00
MSREDIR.EXE 4.00
WIN200.BIN 3.40
METRO.EXE 3.31
WIN100.BIN 3.40
HITACHI.SYS 4.00
MSCDEX.EXE 4.00
NET.EXE 4.00
NETWKSTA.EXE 4.00
DXMA0MOD.SYS 3.30
BAN.EXE 4.00
BAN.COM 4.00
DD.EXE 4.01
DD.BIN 4.01
REDIR.EXE 4.00
SYQ55.SYS 4.00
SSTDRIVE.SYS 4.00
ZDRV.SYS 4.01
ZFMT.SYS 4.01
TOPSRDR.EXE 4.00
NETBEUI.DOS 5.00
NET.COM 3.30
The following file looks for versions of MS-DOS earlier than 6.0 and
ARE NOT in the default version table:
Filename MS-DOS Version Description
------------------------------------------------------------------
SLP.EXE 5.0 Seiko Smart Label Printer TSR
UMBFILES.COM 5.0 PC Magazine Utility
For more information, query in the Microsoft Knowledge Base on
"SETVER.EXE" and the specific application name.
More Information:
SETVER allows you to modify the version table that is kept in the
MSDOS.SYS file. When an application associated with an entry in the
version table is executed, the version table tells the program that it
is running under the MS-DOS version listed in the table.
To modify the version table, do the following:
1. At the MS-DOS prompt, type the following:
setver
For example:
setver example.exe 4.01
A warning message will be displayed that states the application
being added to the version table may not be verified by MS-DOS and
could cause corruption.
2. Verify that the command was added to the version table by typing
"setver" (without the quotation marks).
3. Restart the system so that the new Setver table is loaded into
memory.
Before you can use the SETVER command, the version table must be
loaded into memory by a DEVICE command in your CONFIG.SYS file. By
default, the MS-DOS 6.0 Setup program modifies your CONFIG.SYS file to
ensure that the version table is loaded into memory each time you
start your system.
Additional reference words: 4.00 5.00 6.00 4.0 5.0 6.0
-=-=-=-=-=-
ARTICLE-ID:Q90678
TITLE :MS-DOS Setup is Bootable but Setup Doesn't Run
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The MS-DOS Upgrade Setup Disk 1 is ALWAYS bootable. In other words,
The Setup Disk can be used to start up a computer if the hard drive is
inaccessible, cannot be booted, or does not contain an operating
system.
However, the MS-DOS Upgrade 6.0 Setup program does not run if there is
no operating system on the computer. The MS-DOS Upgrade package is
licensed, sold, and designed for users who have an existing copy of
MS-DOS, or some other operating system, who would like to upgrade to
MS-DOS 6.0.
If your computer does not have an operating system installed, and you
don't have your original operating system disks, you need to contact
your computer manufacturer to obtain a copy of its OEM version of
Microsoft MS-DOS 6.0.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q90682
TITLE :COMMAND.COM Corrupted or Missing on a DoubleSpace Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using DoubleSpace and COMMAND.COM cannot be found, the
system is not bootable.
Workaround
----------
1. Start the system from MS-DOS 6.0 Setup disk number 1.
2. Exit from Setup (press F3 twice). The DoubleSpace drive should now
be available.
3. Copy DBLSPACE.BIN to the root directory of drive C, as follows:
copy dblspace.bin c:\
4. Remove the Setup disk from drive A and restart the computer.
More Information:
MS-DOS Setup disk number 1 contains DBLSPACE.BIN. When MS-DOS is
started from drive A and that disk contains DBLSPACE.BIN, the
DoubleSpace drives become accessible just as if you start the system
from drive C.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q91202
TITLE :Multiple Configuration Menu Does Not Display
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If the MENUDEFAULT command in your CONFIG.SYS file is incorrectly
set,the time-out value defaults to zero. As a result, the startup menu
is not displayed when you start your machine.
Common problems with menudefault settings include using the full menu
descriptor (menu_text) instead of the menu block name and using
non-numeric characters.
To determine if your menudefault is incorrectly set, restart your
computer and press the F8 function key when the text "Starting
MS-DOS..." is displayed. If the time-out is defaulting to zero, the
menu is displayed. If the menu is not displayed, another problem
exists.
More Information:
Do not use more than one word for your block name. If you want to use
text to describe your menu options, use a one-word block name followed
by the description. For example, consider the following menu items:
menuitem=dev, Development Configuration
menuitem=wfwg, Windows for Workgroups
menuitem=games, Games
menuitem=files, Files and Buffers Only [dev]
[wfwg]
[games]
[files]
For these menu items, the four default menu possibilities are
"development," "wfwg," "games," and "files."
When you use the menudefault setting, do not include the descriptor
text. For example,
menudefault=wfwg, 30
If you include the descriptor text, it is interpreted as the time-out
setting. Since it is non-numeric text, the menu is not displayed. For
example, the following menudefault line is incorrect:
menudefault=wfwg, Windows for Workgroups, 30
For help on using a multiple configuration menu, type "help
multiconfig" (without the quotation marks) at the MS-DOS command
prompt or see chapter 4 of "Microsoft MS-DOS 6.0 User's Guide."
For help on using the MENUDEFAULT command in your CONFIG.SYS file,
type "help menudefault" (without the quotation marks) at the MS-DOS
command prompt.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q91634
TITLE :Using RAMDrive to Speed Up MS-DOS Task Swapper
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
RAMDrive is a memory-resident program that enables you to use part of
your computer's memory (RAM, or random-access memory), as if it were a
hard disk drive. By using RAMDrive, you can make MS-DOS Task Swapper
run faster.
When you install MS-DOS, the Setup program copies the RAMDRIVE.SYS
file to your DOS directory. To create a RAM drive, you add a DEVICE=
or DEVICEHIGH= command for RAMDRIVE.SYS to your CONFIG.SYS file.
More Information:
To speed up Task Swapper:
1. Make a backup copy of your CONFIG.SYS file.
2. Open your CONFIG.SYS file by using any text editor.
3. Add a DEVICE= or DEVICEHIGH= command line for the RAMDRIVE.SYS
device driver. It should appear similar to the following:
device=c:\dos\ramdrive.sys 512 /e
This example creates a RAM drive that takes up 512K of extended
memory. You can specify how much and what type of memory your RAM
drive uses by customizing the command line. For more information
about RAMDrive command-line options, type "help ramdrive.sys"
(without the quotation marks) at the MS-DOS command prompt.
4. Save the changes to your CONFIG.SYS file.
5. Open your AUTOEXEC.BAT file.
6. Set the TEMP environment variable to your RAM drive by adding a
SET command line. The drive letter of your RAM drive should be the
letter after that of the last disk drive in use. For example, if
your last disk drive in use is C, your RAM drive would be D. In
this case, you would add the following command to your AUTOEXEC.BAT
file:
set temp=d:\
7. Save the changes to your AUTOEXEC.BAT file.
8. Restart your computer.
Note: If RAMDrive is to use extended memory, your CONFIG.SYS file must
contain a DEVICE= command for the HIMEM.SYS memory manager. If
RAMDrive is to use expanded memory, your CONFIG.SYS file must contain
a DEVICE command for the expanded-memory manager that came with your
memory board. The device command for RAMDrive must come after the one
for the memory manager.
You can improve the performance of RAMDrive by doing the following:
- If you run programs from your RAM drive, list your RAM drive first
in your PATH= command. For example, if your RAM drive is drive E,
add E:\ to the beginning of the PATH= command.
- If you use the EMM386 program as an expanded-memory emulator, do
not put the RAM drive in expanded memory. Although RAMDrive can
also use this emulated expanded memory, it won't be as efficient as
it would if it were using real physical memory.
Additional reference words: 6.0 ram drive
-=-=-=-=-=-
ARTICLE-ID:Q91664
TITLE :MS-DOS Backup Err Msg: Unable to Open Component File
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you use a non-floppy drive, Backup creates a .001 file in a .FUL
directory. For example, if you back up to F:\TEMP on your fixed drive
or a network drive), Backup creates
f:\TEMP\DEFAULT\xxxxxxxx.FUL\xxxxxxxx.001
where xxxxxxxx are numbers and letters generated from the date. Moving
the .001 file causes the restore option in Backup to fail and
generates the following error message:
Unable to open component file
Therefore, if you back up to a network drive, and someone moves your
files, you cannot restore them until they are moved back.
More Information:
To work around this problem, re-create your original directory
structure and move the .001 file back to its original location. If
you cannot remember the original directory structure, attempt to
restore your files again. The error message displayed by Backup tells
you the directory and filename for which it is looking.
Steps to Reproduce Problem
--------------------------
1. Run Backup.
2. Back up files from one drive to a non-floppy drive and minimize
Backup.
3. Run File Manager and move the .001 file to another directory.
4. Switch back to Backup and attempt to restore some files.
How the Backup Filename in Generated
------------------------------------
The backup file for DEFAULT\CCYMMDDA.FUL is calculated as follows:
default = name of backup set
y = last number of year
mm = month of backup
dd = day of backup
a = A - Z, depending on the number backups that day
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q91728
TITLE :MS-DOS 6 DoubleSpace Files and Functions
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
This article contains a list of DoubleSpace files and their functions.
Filename Function
----------------------------------------------------------------------
DBLSPACE.BIN Main DoubleSpace Component
DBLSPACE.EXE For creation or modification of a DoubleSpace drive
DBLSPACE.HLP DoubleSpace on-line help file
DBLSPACE.INF DoubleSpace Setup information file
DBLSPACE.INI DoubleSpace information file
DBLSPACE.WIN Used to keep track of Windows during
DoubleSpace installation
DBLSPACE.SYS Allows MS-DOS to load DoubleSpace device driver high
DBLSPACE.00x Actual DoubleSpace drive stored as a file
More Information:
For definitions of terms used in this article, please see the
DoubleSpace Help.
DBLSPACE.BIN
------------
MS-DOS uses the DBLSPACE.BIN component to mount the compressed volume
file so you can access the files on your compressed drive. This file
loads automatically if it is in the root directory of the startup disk
(no device= line is needed). If you want to load DBLSPACE.BIN into
upper memory, see the DBLSPACE.SYS section of this article.
DBLSPACE.EXE
------------
This file allows you to mount, create or modify DoubleSpace drives.
DoubleSpace accepts the following parameters:
DBLSPACE /CHKDSK [/F] [drive:]
DBLSPACE /COMPRESS drive: [/F] [/NEWDRIVE=drive2:] [/RESERVE=size]
DBLSPACE /CREATE drive: [/NEWDRIVE=drive2:] [/SIZE=size | /RESERVE=size]
DBLSPACE /DEFRAGMENT [/F] [drive:]
DBLSPACE /DELETE drive:
DBLSPACE /FORMAT drive:
DBLSPACE [/INFO] drive:
DBLSPACE /LISTDBLSPACE /MOUNT[=sss] [drive:] [/NEWDRIVE=drive2:]
DBLSPACE /RATIO[=r.r] [drive: | /ALL]
DBLSPACE /SIZE[=size | /RESERVE=size] [drive:]
DBLSPACE /UNMOUNT [drive:]
For more information about DoubleSpace command-line options, type HELP
DBLSPACE or HELP DBLSPACE /switchname (where /switchname is the name
of the switch about which you want more information) at the command
prompt.
DBLSPACE.HLP
------------
This file contains help on DoubleSpace. To access this file, run
DoubleSpace and choose Contents or Index from the Help menu.
DBLSPACE.INF
------------
The DoubleSpace Setup information file is helpful when creating a new
DoubleSpace drive, but it is not required.
Commands under the [SpecialFiles] section indicate actions to be taken
for specific files; the possible actions are COPY=, IGNORE= and MOVE=.
Without a path, any file of that name will match; wild cards (?, *)
are acceptable.
Programs under the [CopyFiles] section are optional utilities that
will be left on the original boot drive if there is enough room..
Programs under the [dangerous] section will be remarked out using the
REM command from CONFIG.SYS file during DoubleSpace Setup but will not
be remarked after Setup has completed.
Programs under the [prior] section will have DEVICEHIGH=DBLSPACE.SYS
placed ABOVE them in the CONFIG.SYS file.
DBLSPACE.INI
------------
This file is used by DoubleSpace to mount the compressed volume and
swap drive letters. The file contains the following settings:
MaxRemovableDrives=
FirstDrive=
LastDrive=
MaxFileFragments=
ActivateDrive=
DBLSPACE.WIN
------------
This is a temporary file that DBLSPACE.BIN generates to keep track of
windows information when a drive is compressed. It should
automatically be deleted after DBLSPACE.BIN completes the compression
of the existing drive.
DBLSPACE.SYS
------------
The DBLSPACE.SYS device driver does not provide access to the
compressed drives; it simply makes it possible for DBLSPACE.BIN to be
loaded high. If you do not plan to move DBLSPACE.BIN into upper
memory, you can safely remove the DEVICE=C:\DOS\DBLSPACE.SYS line from
your CONFIG.SYS file.
DBLSPACE.00x
------------
A compressed drive is not a real disk drive, although it appears that
way to most programs. Instead, a compressed drive exists on your disk
as a hidden file called a compressed volume file (CVF). DBLSPACE.00x
is the compressed volume file.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q92393
TITLE :Dual-Boot Schemes Preserved by MS-DOS 6 Upgrade
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
The MS-DOS 6 Upgrade preserves the master boot record (MBR) if you
have Windows NT Flex Boot or OS/2 Dual Boot installed. In all other
cases, you must manually restore the (MBR).
The MS-DOS 6 Upgrade does not preserve the OS/2 Boot Manager or UNIX
dual-boot partition schemes; however, they can be restored by using
the procedures below.
More Information:
OS/2 Boot Manager
-----------------
Setup does not disable your dual-boot configuration if you are using
OS/2 version 1.2. If your system was set up for multiple-boot
functionality with Boot Manager, use the following procedure to
restore this functionality:
1. Run FDISK.EXE.
2. Choose 2 and press ENTER to set the active partition.
3. Choose the Boot Manager partition (it is listed as a 1-megabyte
non-DOS partition).
4. Exit FDISK.
5. Restart your computer.
UNIX or XENIX
-------------
If your system is set up for dual-boot functionality and you have not
installed the MS-DOS 6 Upgrade, you should install MS-DOS 6 manually.
If your system was set up for dual-boot functionality with UNIX and
you installed MS-DOS using the /u switch, use the following procedure
to restore the dual-boot functionality:
1. Run FDISK.EXE.
2. Choose 2 and press ENTER to set the active partition.
3. Choose the UNIX partition.
4. Exit FDISK.
5. Restart your computer.
6. Consult your UNIX documentation to restore the dual boot
functionality.
For more information on installing the MS-DOS 6 Upgrade on a system
with UNIX or XENIX partitions, refer to the following section in
Chapter 9 of the "Microsoft MS-DOS 6 User's Guide":
Setup displays the "Incompatible hard disk or device driver" screen
Additional reference words: 6.00 dual boot startup system menu
-=-=-=-=-=-
ARTICLE-ID:Q92426
TITLE :LANtastic Allows Hidden and System Files to be Deleted
-----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system versions 3.x, 4.x, 5.x, and 6.0
-----------------------------------------------------------------------
Summary:
LANtastic version 4.1 allows you to delete hidden and system files on
LANtastic servers. This functionality is specific to LANtastic, and
cannot be changed by MS-DOS.
For more information on deleting hidden and system file on a LANtastic
server, please consult your LANtastic documentation.
Additional reference words: 3.00 3.10 3.20 3.30 3.30a 3.31 3.00 4.01
5.00 5.00a 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93366
TITLE :EMM386.EXE: ALTBOOT Parameter
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
A new parameter was added to EMM386.EXE in order to avoid problems
encountered when you attempt to reboot a computer with the key
combination CTRL+ALT+DEL. If your machine stops responding (hangs)
when you press CTRL+ALT+DEL, try adding the ALTBOOT parameter as in
the following example:
DEVICE=C:\DOS\EMM386.EXE ALTBOOT X=C000-C7FF NOEMS
More Information:
The CTRL+ALT+DEL handling routine changed when EMM386.EXE was upgraded
in Microsoft Windows operating system version 3.1. The ALTBOOT
parameter tells EMM386 to handle CTRL+ALT+DEL the same way it does in
Microsoft MS-DOS version 5.0. The ALTBOOT parameter may be needed on
UNISYS PW^2 3256 computers with Phoenix A386 BIOS copyrighted
1985,1991.
Additional reference words: 6.00 UNISYS Phoenix
-=-=-=-=-=-
ARTICLE-ID:Q93374
TITLE :MemMaker Doesn't Find SYSTEM.INI File on Network
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MemMaker does not find your Windows SYSTEM.INI file if you are running
a network installation of Windows (installed with SETUP /N) and you
don't log onto the network from your AUTOEXEC.BAT file.
More Information:
MemMaker relies on the CONFIG.SYS and AUTOEXEC.BAT files to find the
files it needs to optimize your system. MemMaker needs to read the
SYSTEM.INI file to determine how much free upper memory block (UMB)
space to set aside for the API translation buffers.
For MemMaker to correctly optimize your systems memory, load the
network software from the AUTOEXEC.BAT file.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93375
TITLE :Changes in EMM386.EXE Version 4.45 (MS-DOS 6.0)
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
----------------------------------------------------------------------
Summary:
Version 4.45 of the Microsoft expanded memory manager (EMM386.EXE),
provided with MS-DOS version 6.0, has the following new features:
- Advanced Upper Memory Scanning
- Expanded and Extended Memory Sharing
- Ability to Provide Upper Memory Regions for Microsoft Windows
- Ability to Load with NOEMS When No Page Frame Is Available
- NOVCPI Switch for Smaller Load Size
- Automatic IBM Token Ring Adapter Detection
- Quiet Loading
- Ability to Provide ROM Shadowing
This article describes these features in detail.
More Information:
Advanced Upper Memory Scanning
------------------------------
EMM386.EXE can now scan the F000h-F7FFh region when the system
read-only memory (ROM) is duplicated between F000h-F7FFh and
F800h-FFFFh. Also, EMM386.EXE will include the ROM BASIC area on IBM
PS/2 systems.
To enable advanced upper memory scanning, add the HIGHSCAN switch to
the device= line for EMM386.EXE in the CONFIG.SYS file.
Expanded and Extended Memory Sharing
------------------------------------
Previous versions of EMM386.EXE allocated as much extended memory
memory as possible during the initialization phase. This tied up
memory that could otherwise have been used by programs that use
expanded memory. EMM386.EXE version 4.45 includes support for dynamic
allocation of memory. This means EMM386.EXE can create and make
available different types of memory as your system requirements
change.
Ability to Provide Upper Memory Regions for Windows
---------------------------------------------------
EMM386.EXE version 4.45 includes a new WIN= switch that defines upper
memory regions available for use by Windows. These regions are similar
to X= regions; memory is not mapped to those areas. But unlike X=
regions, Windows (in 386 enhanced mode) can map its own memory into
these upper memory regions and make more conventional memory available
to MS-DOS-based applications running with Windows.
Ability to Load with No Page Frame
----------------------------------
Previous versions of EMM386.EXE do not load if expanded memory support
is enabled and there is not enough contiguous available address space
for an expanded memeory page frame. To support MEMMAKER.EXE,
EMM386.EXE 4.45 displays a warning message and continues to load when
this situation occurs.
NOVCPI Switch for Smaller Load Size
-----------------------------------
Previous versions of EMM386.EXE disable both expanded memory and
virtual control program interface (VCPI) support when the NOEMS switch
is used. EMM386.EXE 4.45 leaves VCPI support enabled by default when
the NOEMS option is used, relying on the expanded and extended memory
sharing enhancement to supply VCPI memory.
VCPI support can be disabled with the new NOVCPI switch. Using NOEMS
and NOVCPI together results in a reduction in the amount of extended
memory used by EMM386.EXE.
Token Ring Adapter Detection
----------------------------
EMM386.EXE automatically detects the memory location of IBM Token Ring
adapter cards and prevents the mapping of expanded or upper memory
over the adapter. The new Token Ring adapter detection can be disabled
by using the new NOTR command line switch.
Quiet Loading
-------------
By default, EMM386.EXE version 4.45 displays messages only if it
encounters an error condition. Adding the /VERBOSE (or /V) switch to
the EMM386 line in the CONFIG.SYS file forces EMM386.EXE to display
status and error messages while loading.
To display status messages without adding the /V switch, press and
hold down the ALT key while EMM386.EXE starts and loads.
For more information on the EMM386.EXE switches, type "help emm386"
(without the quotation marks) at the MS-DOS command prompt.
Ability to Provide ROM Shadowing
--------------------------------
EMM386.EXE version 4.45 includes a new ROM= switch that defines
regions of read-only memory (ROM) for EMM386.EXE to "shadow."
EMM386.EXE copies the contents of the ROM to extended memory (RAM) and
maps the ROM addresses to this memory. Specifying this switch can
speed up your system if it does not already use shadow RAM.
Additional reference words: 6.00 XMS EMS free up
-=-=-=-=-=-
ARTICLE-ID:Q93377
TITLE :Changes Made to SYSTEM.INI by MS-DOS 6.0 MemMaker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system version 3.0
--------------------------------------------------------------------
Summary:
When you run MS-DOS 6.0 MemMaker, the final screen displays the
following message:
If MemMaker changed your Windows SYSTEM.INI file,
the original file was saved as SYSTEM.UMB.
The Windows SYSTEM.INI file is only changed if you are running Windows
3.0.
More Information:
MemMaker changes the SYSTEM.INI file only when certain options are
selected prior to memory optimization. The following lists all
possible changes to the Windows 3.0 SYSTEM.INI file:
SYSTEMROMBREAKPOINT=FALSE
EMMEXCLUDE=A000-FFFF
EMMINCLUDE=
DUALDISPLAY=TRUE if b000-b7ff is included
NOEMMDRIVER=TRUE if NOEMS is specified
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93654
TITLE :Using the [common] Section with Multiple Configurations
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you use multiple configurations in your CONFIG.SYS file, you should
use a [common] section for the device drivers and environment
statements you would normally use for all of your configurations.
If you place the [common] section at the end of your CONFIG.SYS file,
you greatly increase the chances that a setup or installation program
will correctly update your CONFIG.SYS file.
For example, when you install a CD-ROM drive, the installation
software adds the device driver to the CONFIG.SYS file. It will
probably add the device driver at the bottom, in the [common] section.
If you had [Development] as your last section, the CD-ROM driver would
be available only under that configuration, instead of every
configuration.
Additional reference words: 6.0 multi config multi-configuration
-=-=-=-=-=-
ARTICLE-ID:Q93655
TITLE :Changes to MS-DOS 6.0 MSCDEX Version 2.22
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
MS-DOS 6.0 provides a new version of MSCDEX, which is version 2.22.
The following changes were implemented when MSCDEX.EXE was revised
from version 2.21 to version 2.22:
- MSCDEX now loads into UMA using "lh mscdex ..."
- MSCDEX is no longer version dependent
- The /V switch now reports reasonable memory statistics
- Cosmetic changes
More Information:
MSCDEX Now Loads into UMA Using "lh mscdex ..."
-----------------------------------------------
If there is enough memory available, MSCDEX version 2.21 and earlier
can load into upper memory. MSCDEX version 2.21 and earlier require
the load size of MSCDEX (which varies for different configurations)
plus 48K of memory to load. Development added the 48K requirement to
ensure there is enough memory to load COMMAND.COM.
Therefore you need to have a block of memory (conventional or upper)
equal to the MSCDEX load size plus 48K to load version 2.21 or
earlier.
MSCDEX version 2.22 checks to see if the driver is being loaded above
640K. If it is, MSCDEX does not add 48K to the initialization load
size because it doesn't need to be concerned with the transient
portion of COMMAND.COM.
MSCDEX Is No Longer Version Dependent
-------------------------------------
If you are using MS-DOS 5.0 or 6.0, earlier version of MSCDEX require
you use SETVER.EXE to tell MSCDEX the MS-DOS version is 4.0.
This is no longer required with version 2.22.
The /V Switch Now Reports Reasonable Memory Statistics
------------------------------------------------------
The /V switch now reports accurate memory statistics. Earlier versions
of MSCDEX were not accurate.
Cosmetic Changes
----------------
The version number incremented from 2.21 to 2.22 and the copyright
message has been updated to include 1993.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93678
TITLE :Differences Between SMARTDrive Version 4.0 and 4.1
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
The following enhancements have been made to SMARTDrive version 4.1:
- Corrections to minor problems for better handling bad sectors
- SMARTDrive now supports DoubleSpace
More Information:
Corrections to Minor Problems for Better Handling Bad Sectors
-------------------------------------------------------------
SMARTDrive version 4.1 includes the following corrections:
- SMARTDrive now correctly deals with bad sectors.
- SMARTDrive now correctly handles the int 21 function 68h (Commit
File) carry flag.
SMARTDrive Now Supports DoubleSpace
-----------------------------------
If a DoubleSpace volume is mounted before SMARTDrive version 4.1 is
loaded, it caches the DoubleSpace host drives. This functionality is
similar to the way SMARTDrive version 4.0 (and 4.1) works with
Stacker. The caching of DoubleSpace through the host drive is
accomplished using a special interface to the DoubleSpace components.
If you specify a DoubleSpace drive on the SMARTDrive command line, you
get the following error message:
You must specify the host drive for a DoubleSpace drive.
To use SMARTDrive with DoubleSpace, you must specify the host drive.
SMARTDrive lists DoubleSpace drives with an asterisks (*), indicating
that caching is really done via the host drive.
Additional reference words: 6.0 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q93679
TITLE :Setup Is Unable to Read Uninstall Disk on a COMPAQ
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
If you are using SMARTDrive to cache a floppy disk on a COMPAQ
machine, MS-DOS 6 Upgrade may not be able to read the Uninstall disk.
This problem occurs due to a problem in the COMPAQ BIOS. The problem
occurs when SMARTDrive is loaded into upper memory because all floppy
disk data transfers go through the upper memory blocks (UMBs).
To workaround this problem, edit your AUTOEXEC.BAT file so it loads
SMARTDrive in conventional memory with the following command:
smartdrv /l
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q93777
TITLE :Corrupt Swap File Warning After Removing Compressed Drive
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
- Microsoft Windows operating system versions 3.0, 3.0a, and 3.1
--------------------------------------------------------------------
Summary:
You may receive a corrupt swap file warning message from Windows after
removing a compressed drive. Because you remove a compressed drive
manually, DoubleSpace cannot update permanent or temporary swap file
settings in SYSTEM.INI or SPART.PAR. Drive letters change resulting in
the corrupt swap file warning because Windows cannot find the swap
file. To restore your swap file settings, run the 386 Enhanced icon
from Control Panel.
Additional reference words: 6.00 3.00 3.00a 3.10 dblspace
-=-=-=-=-=-
ARTICLE-ID:Q93778
TITLE :MS-DOS Setup Doesn't Install Windows-Based Utilities
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Setup does not install Windows-based MS-DOS utilities if it does not
find a Windows installation. After you install Windows you can run
SETUP /E from the MS-DOS 6.0 upgrade disks to install the optional
components for Windows.
Setup does not install Windows-based utilities because it cannot
update SYSTEM.INI, WINFILE.INI or PROGMAN.INI.
Additional reference words: 6.00
-=-=-=-=-=-
ARTICLE-ID:Q93923
TITLE :Error Using LOADHIGH (LH) With Third-Party Shell
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
Third-party command interpreters (sometimes called shells) such as
4DOS and NDOS are designed to replace COMMAND.COM. These command
interpreters have to be updated to work correctly with the new MS-DOS
6.0 LOADHIGH (LH) parameters (/L and /S). If you use the /L or /S
parameters with NDOS or 4DOS, you receive the following error message:
Error: Unknown Command "/l:
More Information:
MS-DOS 6.0 COMMAND.COM supports two memory specific parameters: /L and
/S, which are determined by MemMaker. For example, "LOADHIGH /L:0;1
MOUSE.COM" is a valid command in MS-DOS 6.0.
Third-party command interpreters such as 4DOS and NDOS have to be
updated to work correctly with these new parameters.
Workaround
----------
To workaround the problem, either use COMMAND.COM for your command
interpreter or remove the /L and /S parameters from your LOADHIGH (LH)
commands.
For more information or to obtain an update to your third-party
command interpreters, please contact your command interpreter vendor.
Additional reference words: 6.0 3rd party 3rdparty replacement shell
shell= four dos 4 dos third
-=-=-=-=-=-
ARTICLE-ID:Q94024
TITLE :Exclude DASDDRVR.SYS When Running MemMaker
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When you run MemMaker on an IBM PS/2 model 70, you should run it in
the Custom installation mode and exclude the following device driver:
DASDDRVR.SYS
DASDDRVR.SYS is an IBM system patch recommended by IBM for all PS/2s
manufactured prior to June 1991. DASDDRVR.SYS stays resident only if
it detects that your PS/2 needs the patch. If this is the case, it
should install before other drivers that may make calls to the ROM
BIOS (such as HIMEM.SYS and EMM386.EXE).
To work around this problem:
1. Run MemMaker in Custom mode and exclude DASDDRVR.SYS.
For more information on running MemMaker in Custom mode, see
Chapter 6, "Making More Memory Available," in the "MS-DOS 6 User's
Guide."
2. Edit the CONFIG.SYS file with a text editor and make the
DASDDRVR.SYS line the first line in the file.
Additional reference words: 6.0
-=-=-=-=-=-
ARTICLE-ID:Q94131
TITLE :MemMaker Values for Memory Change Don't Match
--------------------------------------------------------------------
The information in this article applies to:
- Microsoft MS-DOS operating system version 6.0
--------------------------------------------------------------------
Summary:
When MemMaker reports values in the Change column for conventional
memory and upper memory, the values may not be the same. For example,
MemMaker may report you have 58K more conventional memory and 62K less
memory in the upper memory area (UMA).
Under ideal conditions, these two numbers are the same. If one of the
following conditions exist, the values for the change in conventional
and upper memory don't match:
- A program that loads itself into the UMA changes size (for example,
SMARTDRV.EXE)
- The expanded memory manager (EMM) that MemMaker loads (EMM386.EXE)
utilizes the UMA differently from the current EMM
- A program that MemMaker configured to load into the UMA did not
because of an unanticipated problem.
Additional reference words: 6.0 not memory maker
December 14, 2017
Add comments