╔════════════════════════════════════════════════════════════════════════╗ ║ C O M P A Q (R) P E R S O N A L C O M P U T E R S ║ ║ U S E R P R O G R A M S ║ ╟────────────────────────────────────────────────────────────────────────╢ ║ The utilities provided on this diskette supersede earlier versions ║ ║ of the utilities located on COMPAQ MS-DOS(R) or other USER PROGRAMS ║ ║ diskettes. Refer to the individual selections listed below for ║ ║ specific version or date information. ║ ║ ║ ║ These utilities enable you to take advantage of specific ║ ║ capabilities of your computer. ║ ║ ║ ║ At the A> prompt, type the NUMBER of the utility for which you ║ ║ want information and press the ENTER key. ║ ║ ║ ║ 1. ADAPT.COM 5. CHARSET.COM 9. INSTALL.EXE ║ ║ 2. CACHE.EXE 6. CLOCK.SYS 10. KEYBDP.COM ║ ║ 3. CEMM.COM 7. GRAPHICS.COM 11. MODE.COM ║ ║ 4. CEMM.EXE 8. INST386.EXE 12. VDISK.SYS ║ ║ ║ ║ ║ ║ SETUP is located on the COMPAQ USER DIAGNOSTICS diskette. ║ ╚════════════════════════════════════════════════════════════════════════╝
Important information and a packing list for MS-DOS
version 5.0 are on the distribution disks as follows:
README.TXT disk #2
APPNOTES.TXT disk #1
PACKING.LST disk #1
These files will be copied to your disk when you install
MS-DOS.
Be sure to read section 2 of README.TXT before installing
MS-DOS version 5.0. It contains hardware specific tips
to help ensure that your installation is successful.
README.TXT
NOTES ON IBM DOS VERSION 5.0
===========================
This readme provides important information not included in the
IBM DOS User's Guide and Reference or in on-line Help.
Look through the following table of contents to determine
whether your software or hardware is included.
ATTENTION CODEVIEW AND INTEL ABOVEBOARD USERS
+++++++++++++++++++++++++++++++++++++++++++++
APPNOTES.TXT contains critical information about
using CodeView and Intel Aboveboard with DOS
5.0.
+++++++++++++++++++++++++++++++++++++++++++++
For information about using applications with DOS 5.0,
see the APPNOTES.TXT file.
The following topics are discussed in this file:
1. Readme Conventions
2. Machine-Specific HIMEM.SYS Switches
* Bull Micral 60
* COMPUADD 386
* Datamedia 386/486
* Hitachi HL500C
* Intel 301z or 302
* JDR 386/33
* Toshiba 5100
* UNISYS PowerPort
3. Installing DOS 5.0 on an OS/2 Dual-Boot System
4. Notes on Memory Management
4.1 Problems Loading into the Upper Memory Area
4.2 Intel Expanded-Memory Driver (EMM.SYS)
4.3 Phoenix BIOS and HIMEM.SYS
5. Notes on Windows
5.1 DOS Applications in Expanded Memory
5.2 "Unable to start Enhanced Mode Windows" Message
5.3 WINA20.386 File
5.4 "High Memory Area in Use" Message (Windows/386 2.1)
5.5 "Cannot run Windows in standard mode" Message
6. Making Your Hardware Compatible with DOS 5.0
6.1 Using a Mouse with DOS Shell
* Logitech
* Microsoft
6.2 XGA and EMM386.EXE
7. Making Your Network Compatible with DOS 5.0
7.1 DOS Shell and Networks
7.2 AT&T StarGROUP
7.3 PC-NFS 3.0
7.4 TOPS Network
8. Documentation Corrections and Additions
8.1 New CV.COM for CodeView
8.2 Documentation Corrections
8.3 Hercules Display Adapter (MSHERC.COM)
8.4 QBasic "On Error" Command
8.5 SMARTDRV and Third-Party Partitions
1. README CONVENTIONS
=====================
If you have questions about procedures or commands mentioned
in this file, you will probably find answers in the IBM
DOS User's Guide and Reference. The following paragraphs
describe frequently mentioned topics that the guide covers in
more detail.
Many sections of the readme discuss changing your CONFIG.SYS
file. For detailed information about modifying a CONFIG.SYS
file, see Chapter 11 of the DOS User's Guide and Reference.
The readme often refers to DEVICE commands in your CONFIG.SYS
file. For example, one section recommends "adding a machine:1
switch to the DEVICE=HIMEM.SYS command in your CONFIG.SYS
file." These DEVICE= statements indicate the type of command
in the CONFIG.SYS file. You need to modify these statements to
reflect the configuration of your system. For more information,
see the DEVICE command in Chapter 14 of the DOS User's
Guide and Reference.
The readme sometimes asks you to use the EXPAND command to copy
files from the distribution disks to your hard disk. See Chapter
14 of the DOS User's Guide and Reference for more
information about using the EXPAND command.
2. MACHINE-SPECIFIC HIMEM.SYS SWITCHES
--------------------------------------
To install DOS 5.0 on a system listed in this section,
you must do the following:
1. Insert Disk 1 in drive A and restart your system to
run Setup.
2. When Setup ends, press F3.
3. Edit your CONFIG.SYS file as follows:
a. Add the appropriate /machine switch to the
DEVICE=HIMEM.SYS command. For example, if you have an
Intel 301z, your DEVICE=HIMEM.SYS command would look
like this:
device=c:\dos\himem.sys /machine:8
b. Restart your system.
System Switch
------ ------
Bull Micral 60 /machine:16
COMPUADD 386 systems /machine:1 or /machine:8
Datamedia 386/486 /machine:2
Hitachi HL500C /machine:8
Intel 301z or 302 /machine:8
JDR 386/33 /machine:1
Toshiba 5100 /machine:7
UNISYS PowerPort /machine:2
3. INSTALLING DOS 5.0 ON AN OS/2 DUAL-BOOT SYSTEM
----------------------------------------------------
If you install your operating system by using the BOOT /OS2 or
BOOT /DOS command, install DOS 5.0 as follows:
1. Start DOS by using the BOOT /DOS command.
2. Run Setup.
If you use the form of an OS/2 dual-boot system that prompts
you at startup to select an operating system, do the following:
1. Install DOS 5.0 on your hard disk.
2. Create a system disk by inserting a disk in drive A and
typing the FORMAT A: /S command.
3. Delete the COMMAND.COM file from the floppy disk.
4. On the floppy disk, create a CONFIG.SYS file that
includes the following:
shell=c:\dos\command.com /p /e:256
5. On the floppy disk, create an AUTOEXEC.BAT file that
includes the following commands:
path=c:\dos
append /e
append c:\dos
prompt $p$g
set comspec=
6. Reinstall the OS/2 operating system on your hard disk.
7. Insert in drive A the system disk you created and restart
your computer.
8. Run the dual-boot program (C:\DUALBOOT\DUALBOOT.EXE).
4. NOTES ON MEMORY MANAGEMENT
=============================
4.1 Problems Loading into the Upper Memory Area
-----------------------------------------------
Some computers with hard disk controllers, specifically bus
master DMA controllers, may not be able to load device drivers
or programs into the upper memory area. Try adding a
DEVICE=SMARTDRV.SYS command before any DEVICEHIGH commands in
your CONFIG.SYS file.
4.2 Intel Expanded-Memory Driver (EMM.SYS)
------------------------------------------
Use the Intel expanded-memory driver NE or E switch when
installing the driver for Aboveboard. See your Aboveboard
documentation for more information.
4.3 Phoenix BIOS and HIMEM.SYS
------------------------------
If your system includes a Phoenix BIOS and DOS 5.0 doesn't
work correctly, try adding a /machine:1 or /machine:8 switch
to the DEVICE=HIMEM.SYS command in your CONFIG.SYS file.
5. NOTES ON WINDOWS
===================
5.1 DOS Applications in Expanded Memory
---------------------------------------
If you load device drivers and memory-resident programs into
the upper memory area, and you run DOS applications that use
expanded memory under Windows 3.0, specify the RAM switch with
the DEVICE=EMM386.EXE command in your CONFIG.SYS file.
5.2 "Unable to start Enhanced Mode Windows" Message
---------------------------------------------------
If you start Windows enhanced mode 3.0, and get a message
stating "EMM386: Unable to start Enhanced Mode Windows due
to invalid path specification for EMM386", add the /y=path
switch to the DEVICE=EMM386.EXE command in your CONFIG.SYS
file. "Path" specifies the location of the EMM386.EXE file
when you start Windows.
For example, if the EMM386.EXE file is in the \DOS directory on
drive C, your command would look like this:
DEVICE=EMM386.EXE /y=c:\dos\emm386.exe
5.3 WINA20.386 File
-------------------
Setup installs a read-only file named WINA20.386 in your root
directory.
If you move the WINA20.386 file to a different directory, do the
following:
1. Add a SWITCHES=/W command to your CONFIG.SYS file.
2. Add a DEVICE=[drive:][path]]WINA20.386 command to the
[386Enh] section of your Windows SYSTEM.INI file.
5.4 "High Memory Area in Use" Message (Windows/386 2.1)
-------------------------------------------------------
You cannot run Windows/386 2.1 when DOS 5.0 is loaded into
the high memory area. Also, the DOS 5.0 versions of
SMARTDRV.SYS and RAMDRIVE.SYS are not compatible with Windows/386
2.1. To run Windows/386 2.1 with DOS 5.0, use the versions of
SMARTDRV.SYS and RAMDRIVE.SYS that came with Windows and remove
the DOS=HIGH command, if any, from your CONFIG.SYS file.
5.5 "Cannot run Windows in standard mode" Message
-------------------------------------------------
If you have a DEVICE=EMM386.EXE command in your CONFIG.SYS file,
you cannot run Windows 3.0 in standard mode. Either remove
the DEVICE=EMM386.EXE command or run Windows in real or enhanced
mode.
NOTE: Using EMM386 may reduce the amount of extended memory
available to Windows and cause Windows to try to start in
standard mode. To prevent this, reduce the amount of extended
memory that other device drivers use. For example, if you are
using SMARTDRV, try setting the MinCacheSize parameter to 0.
6. MAKING YOUR HARDWARE COMPATIBLE WITH DOS 5.0
==================================================
6.1 Using a Mouse with DOS Shell
-----------------------------------
If you have a Logitech or Microsoft mouse, use the following
driver versions with DOS Shell:
Logitech mouse version 5.01 or later
Microsoft mouse version 6.21 or later
6.2 XGA and EMM386.EXE
----------------------
If you use an XGA display with EMM386.EXE, you may need to
exclude certain memory ranges with the EMM386 EXCLUDE option
(x=). To determine which memory ranges to exclude, use your
reference disk to view the memory map.
7. MAKING YOUR NETWORK COMPATIBLE WITH DOS 5.0
=================================================
7.1 DOS Shell and Networks
-----------------------------
Most network software won't work correctly if you start it from
a DOS Shell command prompt. Start your network before starting
DOS Shell.
7.2 AT&T StarGROUP
-------------------
If your AT&T StarGROUP version does not support DOS 5.0,
contact your AT&T representative or the AT&T National Systems
Support Hotline for information about required modifications or
upgrades.
7.3 PC-NFS 3.0
--------------
If you use PC-NFS 3.0 with DOS Shell, DOS Shell may
display more drives than you have currently enabled. To
prevent this, use the PC-NFS /d switch to specify the number
of drives you are using. For more information, see your PC-NFS
documentation.
If you can't use the COPY or XCOPY command on PC-NFS 3.01,
contact your vendor to get an updated version of the PCNFS.SYS
device driver.
7.4 TOPS Network
----------------
If your system is a TOPS workstation, the DOS Shell MOVE
command may not work.
Don't use the LOADHIGH command with a TOPS network.
8. DOCUMENTATION CORRECTIONS AND ADDITIONS
==========================================
8.1 New CV.COM for CodeView
---------------------------
Users of CodeView versions 3.0 to 3.13 should use the program
CV.COM to start CodeView. For more details, see the section
on CodeView in the file APPNOTES.TXT.
8.2 Documentation Corrections
-----------------------------
The following are corrections to the DOS User's
Guide and Reference:
COMP /? Help:
Online help for the COMP command /d switch should state that
the default format is hexadecimal.
FORMAT Command:
If you can't use the FORMAT command to format an
unformatted disk, try using the /u switch.
MIRROR Command:
You cannot use the MIRROR command with a network drive or
any drive you created by using the ASSIGN, SUBST, or JOIN
command.
UNDELETE Command:
Do not use the UNDELETE command in the following
circumstances:
* When other programs are active.
* With the LOAD= command or the Shift+Enter key
combination in Windows.
* With Task Swapper in DOS Shell.
UNFORMAT Command:
The UNFORMAT /p switch is not compatible with the /j switch.
8.3 Hercules Display Adapter (MSHERC.COM)
-----------------------------------------
If you use DOS Editor or QBasic with a Hercules display
adapter, run MSHERC.COM before you run either program.
8.4 QBasic "On Error" Command
-----------------------------
Online help for QBasic incorrectly states that
ON ERROR RESUME NEXT is a valid statement. The correct syntax
is as follows:
ON ERROR GOTO <LINE/LABEL>
8.5 SMARTDRV and Third-Party Partitions
-----------------------------------------
If your system includes a third-party disk partition and you
try to use SMARTDRV, you may receive a message stating that
you cannot load SMARTDRV.
You can force SMARTDRV to load by specifying the /p switch.
However, doing so may corrupt your hard disk if either of the
following conditions is true:
* Your hard disk contains more than 1024 cylinders.
* Your hard disk is not supported by the system's ROM BIOS.
If you have partitions created by using third-party
disk-partitioning software, use SMARTDRV ONLY if you are sure
your hard disk contains 1024 or fewer cylinders AND it is
supported directly by the system's ROM BIOS.
README.TXT
MS-DOS VERSION 5.0 の諸注意
このテキストは, マニュアルおよびオンラインヘルプには含まれていない重要な
情報を提供します.
お手持ちのソフトウェアまたはハードウェアがこの記載内容に該当するかどうかは,
以下の内容一覧表を参照してください.
CodeView と INTEL社 ABOVEBOARD をご使用の方に対する注意
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
APPNOTES.TXT に MS-DOS5.0 で CodeView と INTEL社 ABOVEBOARD を使用する場合
の重要な注意事項を記載しています.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
MS-DOS5.0 で種々のアプリケーションを使用する場合の情報は, APPNOTES.TXT を
参照してください.
本ファイル(README.TXT)の記載内容一覧
====================================
1. 本ファイル(README.TXT)の記載内容について
2. マシンに依存する HIMEM.SYS のスイッチ情報
*Bull Micral 60
*COMPUADD 386
*Datamedia 386/486
*Hitachi HL500C
*Intel 301z または 302
*JDR 386/33
*Toshiba 5100
*UNISYS PowerPort
3. MS OS/2 デュアルブートシステムへの MS-DOS5.0 のインストール
4. メモリ管理についての諸注意
4.1 アッパーメモリ領域へロードする場合の問題点
4.2 Intel社 EMSドライバ(EMM.SYS)
4.3 Phoenix社 BIOS と HIMEM.SYS
5. MS Windows についての注意
5.1 EMSメモリを使用する DOSアプリケーション
5.2 "Unable to start Enhanced Mode Windows"メッセージ
5.3 WINA20.386 ファイル
5.4 "High Memory Area in Use"メッセージ(Windows/386 2.1)
5.5 "Cannot run Windows in standard mode"メッセージ
6. ご使用のマシンで MS-DOS5.0 を使用するためのノウハウ
6.1 MS-DOS シェルでのマウスの使用
*Logitech マウス
*マイクロソフトマウス
6.2 XGA と EMM386.EXE
7. MS-DOS5.0 でネットワークを使用するためのノウハウ
7.1 MS-DOS シェルとネットワーク
7.2 AT&T社 Start-GROUP
7.3 PC-NFS 3.0
7.4 TOPS Network
8. ドキュメントの訂正と追加
8.1 CodeView 用の CV.COM
8.2 ドキュメントの訂正
8.4 SMARTDrive と サードパーティのハードディスクパーティション
8.5 JP.BAT と US.BAT
8.6 SETUPE.BAT と SETUPJ.BAT
9. MS-DOS/V 固有の注意点
9.1 $IAS 使用上の注意点
9.2 その他の注意点
１．本ファイル(README.TXT)の記載内容について
============================================
本ファイルで説明している手順やコマンドについて質問がある場合, マニュアル
を参照してください.
たぶん答えが見つかるでしょう.
本ファイルで頻繁に取り上げる話題で, マニュアルに詳細説明があるものは
次のとおりです.
本ファイルでは, 頻繁に CONFIG.SYS の変更方法について説明しています.
CONFIG.SYS の修正方法についての詳細な情報はマニュアルを参照して
ください.
本ファイルでは, しばしば CONFIG.SYS の DEVICE コマンドについて触れます.
例えば,"CONFIG.SYS の DEVICE=HIMEM.SYS に machine:1 スイッチを追加する"と
勧めている箇所があります. この DEVICE= という記述は CONFIG.SYS のコマンド
の一種です. システム構成の変更を反映するためには, これらの記述を変更することが
必要です. 詳しくはマニュアルを参照してください.
本ファイルでは, インストールディスクからハードディスクへファイルをコピー
するために EXPAND コマンドを使用するようにと説明している部分があります.
EXPAND コマンドの使用方法についてはマニュアルを参照してください.
２．マシンに依存する HIMEM.SYS のスイッチ情報
=============================================
一覧表のマシンに MS-DOS5.0 をインストールするには, 次の手順に従ってください.
(1) ドライブ A: にインストールディスク１を挿入し, システムを再起動します.
SETUP が起動されます.
(2) SETUP が終了したら, F3 キーを押します.
(3) CONFIG.SYS を次の様に編集します.
DEVICE=HIMEM.SYS コマンド行に適切な /machine スイッチを追加します.
例えば Intel社 301z の場合
device=c:\dos\himem.sys /machine:8
(4) システムを再起動します.
ｼｽﾃﾑ ｽｨｯﾁ
----------------------------------------------------
Bull Micral 60 /machine:16
COMPUADD 386 systems /machine:1 または /machine:8
Datamedia 386/486 /machine:2
Hitachi HL500C /machine:8
Intel 301zもしくは302 /machine:8
JDR 386/486 /machine:1
Toshiba 5100 /machine:7
UNISYS PowerPort /machine:2
３．MS OS/2 デュアルブートシステムへの MS-DOS5.0 のインストール
===============================================================
MS OS/2 V1.2 の場合(BOOT /OS2 ,BOOT /DOS により起動 OS を選択している場合)
(1) BOOT /DOS により MS-DOS を起動します.
(2) SETUP を実行します.
MS OS/2 V1.1 の場合(システム起動時のメニューにより OS を選択している場合)
(1) ハードディスクに MS-DOS 5.0 をインストールします.
(2) ドライブ A にディスクを入れ, システムディスクを作成します.
FORMAT A: /S
(3) 作成したシステムディスクから COMMAND.COM を削除します.
(4) 次に, システムディスクに 次の行を含む CONFIG.SYS を作成します.
shell=c:\dos\command.com /p /e:256
(5) さらに, システムディスクに次の行を含む AUTOEXEC.BAT を作成します.
path=c:\dos
append /e
append c:\dos
prompt $p$g
set comspec=
(6) ハードディスクに再度 MS OS/2 をインストールします.
(7) 先に作成したシステムディスクをドライブ A に挿入し,システムを再起動します.
(8) C:\DUALBOOT\DUALBOOT.EXE を実行します.
４．メモリ管理についての諸注意
==============================
４．１ アッパーメモリ領域へロードする場合の問題点
-------------------------------------------------
ハードディスクコントローラ, 特にバスマスタ DMA コントローラを有するものを
セットしたシステムでは, アッパーメモリ領域にデバイスドライバやプログラムを
ロードすることができない場合があります. この場合, CONFIG.SYS の全ての
DEVICEHIGH コマンドの前に DEVICE=SMARTDRV.SYS を追加してみてください.
４．２ Intel社 EMSドライバ(EMM.SYS)
-----------------------------------
Aboveboard用EMSドライバをインストールする場合, NE または E スイッチを
使用します. 詳細は Aboveboard のマニュアルを参照してください.
４．３ Phoenix社 BIOS と HIMEM.SYS
----------------------------------
ご使用のシステムが Phoenix社 BIOS を採用していて MS-DOS5.0が正しく動かない
場合, CONFIG.SYS の DEVICE=HIMEM.SYS コマンドに /machime:1 か /machine:8 の
スイッチを追加してみてください.
５．MS Windows についての注意
=============================
５．１ EMSメモリを使用する DOSアプリケーション
----------------------------------------------
MS Windows3.0 でデバイスドライバやメモリ常駐型プログラムをアッパーメモリ
領域にロードし, 同時に EMS メモリを使用する DOS アプリケーションを使用する場合,
CONFIG.SYS の DEVICE=EMM386.EXE コマンドに RAM スイッチを指定してください.
５．２ "Unable to start Enhanced Mode Windows"メッセージ
--------------------------------------------------------
Windows3.0 をエンハンスモードで起動しようとして "EMM386:Unable to start
Enhanced Mode Windows due to invalid path specification" メッセージが表示された
場合, CONFIG.SYS の DEVICE=EMM386.EXE コマンドに /y=path スイッチを追加して
ください."Path"は Windows を起動する際の EMM386.EXE の位置を指定します.
例えば, EMM386.EXE がドライブ C の \DOS ディレクトリにある場合, 次のように
なります.
DEVICE=EMM386.EXE /y=c:\dos\emm386.exe
５．３ WINA20.386 ファイル
--------------------------
SETUP はルートディレクトリに読み込み専用ファイル WINA20.386 をインストール
します.
WINA20.386 ファイルを他のディレクトリに移す場合, 次の操作が必要です.
(1) CONFIG.SYS に SWITCHES=/W コマンドを追加します.
(2) Windows の SYSTEM.INI ファイルの [386Enh] セクションに
DEVICE=[drive:][path]]WINA20.386 コマンドを追加します.
５．４ "High Memory Area in Use"メッセージ(Windows/386 2.1)
-----------------------------------------------------------
MS-DOS5.0 がハイメモリ領域にロードされている場合, Windows/386 2.1 は起動
できません. また, MS-DOS5.0 の SMARTDRV.SYS と RAMDRIVE.SYS は Windoes/386 2.1
とは使用できません. MS-DOS5.0 で Windows/386 2.1 を使用するには, Windows に付属
の SMARTDRV.SYS と RAMDRIVE.SYS を使用し, CONFIG.SYS から DOS=HIGH コマンドを
削除してください.
５．５ "Cannot run Windows in standard mode"メッセージ
------------------------------------------------------
CONFIG.SYS に DEVICE=EMM386.EXE コマンドがある場合, Windows3.0 をスタンダード
モードで起動することはできません.DEVICE=EMM386.EXE コマンドを削除するか, リアル
またはエンハンスモードで起動するかしてください.
注意: EMM386 を使用すると使用可能エクステンドメモリが減少し, Windows がスタン
ダードモードで起動しようとする場合があります.これを防ぐには, 他のデバイスドラ
イバが使用するエクステンドメモリ量を減らします. 例えば, SMARTDriveを使用して
いる場合, MinCacheSize パラメータを０に設定してみてください.
６．ご使用のマシンで MS-DOS5.0 を使用するためのノウハウ
=======================================================
６．１ MS-DOS シェルでのマウスの使用
------------------------------------
Logitech マウス, またはマイクロソフトマウスをご使用の場合, MS-DOS シェルでは
次のバージョンのドライバを使用ください.
*Logitech マウス バージョン 5.01 以降
*マイクロソフトマウス バージョン 6.21 以降
６．２ XGA と EMM386.EXE
------------------------
XGA ディスプレイと EMM386.EXE を使用する場合, EMM386 の EXCLUDE オプション
(x=)で特定のメモリ範囲を除外しなけらばならない可能性があります. 除外すべき
メモリ範囲を知るには, リファレンスディスクを使用して, メモリマップを調べます.
７．MS-DOS5.0 でネットワークを使用するためのノウハウ
====================================================
７．１ MS-DOS シェルとネットワーク
----------------------------------
ほとんどのネットワークソフトウェアは, MS-DOS シェルから正しく起動できません.
MS-DOS シェルを起動する前にネットワークを起動してください.
７．２ AT&T社 Start-GROUP
-------------------------
お手持ちのバージョンのAT&T社 StartGROUP が MS-DOS5.0 をサポートしていない場合
AT&T社に照会し, 必要な修正やアップグレードについての情報を入手してください.
７．３ PC-NFS 3.0
-----------------
MS-DOS シェルで PC-NFS 3.0 を使用する場合, MS-DOS シェルが現在使用可能な
ドライブより多数のドライブを表示する場合があります. これを防ぐには,使用中の
ドライブ数を指定する PC-NFS /d スイッチを指定してください. 詳細は PC-NFS の
ドキュメントを参照してください.
PC-NFS 3.01 において COPY や XCOPY コマンドを使用できない場合, ベンダに
照会して最新の PCNFS.SYS ドライバを入手してください.
７．４ TOPS Network
-------------------
ご使用のシステムが TOPS のワークステーションの場合, MS-DOS シェルの MOVE
コマンドが動作しない場合があります.
TOPS ネットワークでは LOADHIGH コマンドを使用しないでください.
８．ドキュメントの訂正と追加
============================
８．１ CodeView 用の CV.COM
---------------------------
CodeView バージョン 3.0 から 3.13 のユーザは,CV.COM プログラムを使用して
CodeView を起動してください. 詳細は APPNOTES.TXT のCodeView のセクションを
参照してください.
８．２ ドキュメントの訂正
-------------------------
マニュアルの訂正情報を以下に示します.
FORMATｺﾏﾝﾄﾞ:
未フォーマットのディスクを FORMAT コマンドでフォーマットできない場合,
/u スイッチを試してみてください.
MIRRORｺﾏﾝﾄﾞ:
MIRROR コマンドは ネットワークドライブや, ASSIGN, SUBST, JOIN コマンドに
より生成されたドライブに対しては使用できません.
UNDELETEｺﾏﾝﾄﾞ:
次の状況では UNDELETE コマンドは使用できません.
*他のプログラムがアクティブのとき
*Windows で LOAD= コマンドや, Shift + Enter キーでの使用
*MS-DOS シェルのタスクスワッパ使用中
UNFORMATｺﾏﾝﾄﾞ:
UNFORMAT /p スイッチは /j スイッチと同時には指定できません.
８．３ SMARTDrive と サードパーティのハードディスクパーティション
-----------------------------------------------------------------
ご使用のシステムのハードディスクにサードパーティのパーティションが存在し,
SMARTDriveを使用しようとする場合, SMARTDrive がロードできないというメッセージが
表示されることがあります.
/p スイッチの指定により SMARTDrive を強制的にロードすることができますが,
この場合, 次の条件でハードディスクを破壊する恐れがあります.
*そのハードディスクが1024を超えるシリンダを有する
*そのハードディスクがシステムのROM BIOSによってサポートされていない
サードパーティのパーティション作成ソフトウェアによって生成されたパーティ
ションがある場合, そのハードディスクのシリンダ数が1024以下であり, かつシステム
ROM BIOSによって直接サポートされていることが確実な場合のみ SMARTDrive を
使用してください.
８．４ JP.BAT と US.BAT
-----------------------
日本語モードと英語モードの切り替えはそれぞれ JP.BAT 及び US.BAT を
使用してください.
８．５ SETUPE.BAT と SETUPJ.BAT
-------------------------------
英語及び日本語のセットアップを行ないたいときにはセットアップをいったん終了
してからそれぞれ SETUPE.BAT 及び SETUPJ.BAT を実行してください. また, この
コマンドを実行するさいにはセットアップ・ディスクは書き込み可能でなければ
なりません.
９．MS-DOS/V 固有の注意点
=========================
９．１ $IAS 使用上の注意点
--------------------------
$IAS を組み込んで MSIME を DOSSHELL/WINDOWS のタスクスイッチ上で使用する場合
EMS の容量を 384キロバイト以上に設定して MSIMEI.SYS に /Pn オプションを追加し
てください.
$IAS を組み込んでいる時は ADDDRV/DELDRV コマンドは使用しないでください.
$IAS を組み込んで DOSSHELL 上でかな漢字変換を使用した場合, 最下行の表示が壊れ
ます.
$IAS を組み込んで MSIME をグラフィックス・モードで使用する場合 $IAS に /G=
オプションを追加してください.
EMS が確保できない場合に $IAS を組み込むと DOS のメモリー容量が圧迫されて
アプリケーションが動作しない場合があります.
$IAS を組み込んで MS$KANJI API を使用しているアプリケーションを実行すると
正しく動作しない場合があります.
$IAS を組み込んでいる時は SELKKC コマンドは使用できません.
$IAS を組み込んでいて 101 英語キーボードを使用している場合一部の仮想キーコー
ドが変わります.
９．２ その他のの注意点
-----------------------
IBM 版の DOS/V がすでにインストールされているマシンにインストールした場合
IBMBIO.COM および IBMDOS.COM は残ったままとなります.
$IAESKK を使用する場合 $SYS1DIC.FNT をインストールした MS-DOS のディレクト
リーからルートディレクトリーにコピーしてください.
プリンターのモードを日本語／英語に切り替える必要がある場合はモードの切り替え
は CHEV コマンドを使用してください.
$FONT の読み込むフォントは MS-DOS をインストールしたディレクトリーにコピー
されています. フォントファイルがルートディレクトリーにあることを前提ににして
いるアプリケーションを動作させる場合, フォントファイルをルートディレクトリー
にコピーして CONFIG.SYS 内の $FONT の /P= パラメーターを削除してください.
IBM PC/AT 互換機の CPU が i80486DX2/66MHz のマシンでは, システム起動時の
コマンドプロンプトで '^@' が表示されることがありますが, AUTOEXEC.BAT ファイル
内で KEYB.COM より後に DOSKEY.COM を組み込むことで回避できます.
KKCFUNC および $IAS が組み込まれてない場合, 'かな漢字変換は組み込まれまれま
せんでした.' と MSIMEI.SYS が表示しますが MSIMEK.SYS はすでに組み込まれている
ので'MEM /D' において 'MSIMEK' が表示されます.
Novell DOS 7 Release Notes
==========================
These release notes contain information about the following topics. This
information is NOT included in the Novell DOS 7 User Guide or in DOSBook.
- Using DOUBLESPACE and SUPERSTOR drives
- Compressing Bernoulli drives with Stacker
- Using the NWCACHE delayed write mode
- Enabling CD-ROM drives
- Full-screen programs on non-standard VGAs
- Undeleting files across the network
- Configuring the EMM386 memory manager to increase EMS handles
- DOS Protected Mode Services (DPMS) loading order
- Task Manager - loading LOCK as a permanent task
- network drive mappings
- LAN Workplace for DOS support
- running 4DOS
- using the task switcher and server
- DOSBook corrections (DOSKEY and NET SAVE)
- Setting up "one-time login"
- Connecting to NetWare 2 and 3 servers
- Using a network copy of MS Windows on the local server
- Increasing the number of file handles when required
- Using OEM-supplied network board drivers
- Running Personal NetWare with other networking products
- The Personal NetWare tutorial
- Modifications made to MS Windows .INI files by Personal NetWare
- Using remote computers on the network
- Information on Remote Program Load
- Getting updates to Search and Destroy anti-virus
DOUBLESPACE and SUPERSTOR Drives
================================
Drives which have been compressed using Doublespace or SuperStor are
supported by Novell DOS 7. However, to gain the full benefit of reduced
memory consumption and more robust disk compression, it is recommended
that you convert your Doublespace or SuperStor drives to Stacker. You can
use the conversion option in the Novell DOS 7 SETUP program. Run SETUP
after you install Novell DOS 7. Note that the conversion does not support
Superstor Pro drives.
For performance reasons, this conversion operates initially on the
container file format only. Conversion of actual data to Stacker format
is performed subsequently whenever any existing SuperStor or Doublespace
compressed data is written back to the disk.
If you run the DISKOPT program on a drive that is partially converted,
the disk optimizer automatically performs a complete Stacker conversion
by compressing all remaining data. If you run Setup to change the size
of the stacker drive, or try to unstack the drive, it must have been
previously converted entirely to Stacker or you may encounter error
messages. Refer to the Novell DOS 7 User Guide or DOSBook for information
about DISKOPT and its options.
Note: Early versions of Norton Utilities 7.0 will incorrectly diagnose a
converted Superstor or Doublespace drive as faulty. THIS IS NOT A FAULT
ON THE DRIVE. Please contact your supplier for an updated version of the
Norton Utilities.
Stacker
=======
Do not attempt to compress Bernoulli bootable drives. You can compress
Bernoulli drives that are not bootable, however.
NWCACHE
=======
Delayed write mode is disabled as part of the default configuration
for NWCACHE. This is a safety feature to prevent loss of data if the
computer is switched off before disk writes have been completed. Enabling
delayed write mode will improve performance but you must make sure you do
NOT switch off your computer before all data is written to the disk. Do
this in one of the following ways:
1. Perform a "soft boot" (press Ctrl+Alt+Del) before switching the
computer off. A soft boot automatically flushes all pending data to
disk.
2. Wait beyond the delayed write time you specified, after the disk access
light goes out.
3. Wait for the system prompt to return (see below).
When delayed write mode is enabled, the cache is 'flushed' (all data is
written to the disk) BEFORE the system prompt returns, by default. This is
a safety feature. You can disable (or re-enable) this feature by specifying
the following option in the NWCACHE start-up or control command at the
system prompt:
/FLUSH=ON|OFF
If delayed write is enabled (on a computer that is running the Personal
NetWare server software), you can also save memory by setting the number
of I/O buffers to zero via the NET ADMIN program.
Using CD-ROM Drives
===================
To use a CD-ROM drive with Novell DOS 7, the device driver for your
CD-ROM drive must be loaded. CONFIG.SYS must include a DEVICE (or
DEVICEHIGH) statement that loads the appropriate driver (the one that
came with your CD-ROM drive). The DEVICE statement must include a
/D:drivername parameter, where drivername is the 'signature' assigned
to the driver.
Novell DOS 7 includes the NWCDEX program to provide access to CD-ROM
drives. You can load NWCDEX at the system prompt or in the AUTOEXEC.BAT
file. Note that the device driver that came with your CD-ROM drive must
be loaded BEFORE you load NWCDEX (see previous paragraph).
Note: You can use MSCDEX to access CD-ROM drives, but using NWCDEX allows
you to use DPMS and saves memory.
The syntax of NWCDEX is as follows:
NWCDEX [/?|/H] /D:drivername [/E] [/L:letter] [/M:number] [/N] [/V]
/?|/H Displays help text.
/D:drivername Specifies the name of the CD-ROM driver. This name matches
the drivername specified in the DEVICE statement that loads
the driver.
/E Specifies the use of expanded memory (if available) when
DPMS is not available.
/L:letter Specifies the drive letter to assign to the CD-ROM drive.
The default is to use the first available (unused) drive.
/M:number Specifies the number of sector buffers to allocate. The
default is 14.
/N Disables the use of DPMS. By default, NWCDEX will use
extended memory if DPMS is not available.
/V Prints debug information during initialization.
Example
-------
The following examples show the appropriate statements in CONFIG.SYS and
AUTOEXEC.BAT to load and access a CD-ROM drive. In this example, the CD-ROM
driver supplied with the drive is CDROMDRV.SYS and it is to be accessed as
drive G:
in CONFIG.SYS:
DEVICE=C:\NWDOS\CDROMDRV.SYS /D:NWCD000
in AUTOEXEC.BAT:
NWCDEX /D:NWCD000 /L:G
Full-Screen Programs and Non-Standard VGAs
==========================================
Some portable, laptop, and notebook computers with LCD or TFT displays
support a non-standard VGA text mode known as 'Expanded' or 'Stretched'
text. This mode 'stretches' the standard 80x25 (400 pixels high) text
mode so that it fills the entire physical screen which is 480 pixels
high. This mode, if used, may interfere with the enhanced text mode of
the full screen programs, such as NET ADMIN.
If you encounter problems, it is recommended that you disable the
'Stretched' text on your computer. Refer to the documentation for your
computer for information about CMOS setup configuration.
If you cannot disable this mode or prefer to keep 'Stretched'
mode enabled, you can disable the enhanced text mode of the full
screen programs in one of three ways:
1. By entering the name of the program followed by the /N switch
at the system prompt
2. By selecting to disable the enhanced text mode globally from within
the SETUP program
3. By editing the NWDOS.INI file to change NewUI = ON to NewUI = OFF
Undeleting Files Across the Network
===================================
You can use UNDELETE to recover deleted files across the network on both
Personal NetWare and NetWare 2, 3, and 4 servers. To undelete a file from
a Personal NetWare server, the file must have been saved as a pending
delete file by DELWATCH and DELWATCH must have been run on the Personal
NetWare server prior to the file being deleted. Note that it is NOT
necessary to run DELWATCH on the client computer from which UNDELETE is
being run.
EMM386 Memory Manager
=====================
For applications that require more EMS/XMS handles, add the following
option to the EMM386 DEVICE statement in CONFIG.SYS to increase the
number of handles available:
HANDLES=n (where n is a number from 0 to 255)
DOS Protected Mode Services (DPMS)
==================================
Be aware that the DPMS driver must always be loaded before the software
that uses it (NWCACHE, SERVER.EXE, etc.).
Loading LOCK Permanently Under the Task Manager
===============================================
You can load LOCK as a permanent task under the Task Manager by
using the LOCK /P option with the TASKMGR /C command as follows:
TASKMGR /C LOCK password /P
where password is the password you use to unlock the system.
Network Drive Mappings under the Task Manager
=============================================
The Task Manager defaults to global NetWare drive mappings. Changes
made to drive mappings in one DOS session are duplicated to ALL DOS
sessions.
LAN Workplace for DOS Support under the Task Manager
====================================================
The Task Manager supports LAN Workplace for DOS. To enable it, you
must edit the TASKMGR.INI file. Uncomment the following two lines:
vxd=c:\lwfd\vtcpip.386
and
GlobalPages=2
Refer to the instructions contained in the TASKMGR.INI file for more
information.
Load the network drivers (including TCPIP.EXE) before loading the Task
Manager.
Running 4DOS under the Task Manager
===================================
To run 4DOS under the Task Manager (multitasker), you must edit the
TASKMGR.INI file to make the following change in the [Shell] section:
Exec=FALSE
to
Exec=TRUE
Using the Task Switcher and Personal NetWare Server
===================================================
If you are using the task switcher with the Personal NetWare server,
it is recommended that you add the following line to your NET.CFG file:
ALTERNATE CALLDOS = ON
Note: This line is required for Task Switching ONLY and will not be used
in Multi-Tasking mode.
DOSBook Corrections
===================
DOSKEY
The parameters for the DOSKEY command have changed and are incorrectly
documented in the "Command Reference" chapter of DOSBook. Use DOSKEY as
follows:
DOSKEY [/?] [/M] [/R] [/B=nnnn] [/H] [/I] [/O] [macro=[text]]
where
/? Displays help text about DOSKEY.
/M Lists all the DOSKEY macros currently stored in the
buffer.
/R Clears all macros from the command line buffer and
installs a new version of DOSKEY.
/B=nnnn Changes the size of the macro and command line history
buffer, where nnnn is the size in number of bytes. The
default size is 512 bytes.
/H Lists the contents of the command line history buffer.
/I Sets the default editing mode to insert.
/O Sets the default editing mode to overstrike.
macro=text Creates a new macro, when you specify the commands you
want the macro to execute (text).
macro= Deletes the macro.
NET SAVE
The description of NET SAVE in the "NET Commands" chapter of DOSBook
incorrectly states that network connections are saved to a batch file
called NWLOGIN.BAT. The name of this file should be PNWLOGIN.BAT.
One-time Login
==============
"One-time login" is a facility that allows a user to log in to both the
local computer and multiple network servers (and a workgroup) by entering
a username and password ONCE only.
One-time login works by remaking the network connections previously saved
in a local login script. When the login script is rerun, the one-time
login username and password are substituted each time they are requested
by a LOGIN command in the login script. One-time login requires that the
same username and password are used on all servers and the workgroup. By
default, the LOCK program also uses the one-time login password.
To use the one-time login facility, your computer must be configured so
that Novell DOS 7 security is enabled and the Personal NetWare server
is loaded. A local user must be defined, as documented in the "Creating
and Modifying User Accounts" section of the "Setting Up the Network"
chapter in the Novell DOS 7 User Guide and DOSBook.
To set up one-time login, do the following:
1. Reboot the computer.
2. You will be prompted for a username and password; enter the correct
username and password for the defined local user.
3. When you are logged in to the computer, you will be prompted to load
the network software; answer Y to this prompt.
You will be logged in to your workgroup automatically.
4. Make any required connections to other NetWare servers and map drives.
This is documented in the "Logging In" section of the "Using the
Network" chapter of the Novell DOS 7 User Guide and DOSBook.
5. Save your current network settings to your local login script. This is
documented in the "Saving Connections" section of the "Using the
Network" chapter in the Novell DOS 7 User Guide and DOSBook.
The next time you reboot your computer and log in, you will be logged
back in to the workgroup and servers automatically and drives will be
remapped automatically.
Connecting to NetWare 2 and 3 Servers
=====================================
If you experience difficulty connecting to NetWare 2 or 3 servers, ask
your system administrator to check that you have the correct Frame settings
for your network in NET.CFG.
Notes for Existing NetWare 2 and 3 Users
========================================
1. Do not use NETX.COM or related shells with Personal NetWare. The
Personal NetWare client gives you simultaneous access to NetWare 2, 3,
and 4 servers as well as Personal NetWare servers.
2. Path names must be less than 64 characters long. VLMs cannot support
a path name of more than 64 characters. To use longer paths, map a root
drive and continue from there.
Using a Network Copy of MS Windows on the Local Server
======================================================
If you run a network installation of MS Windows on your the local server
and you want to use that version of MS Windows at the server, you must map
a drive to the server and make sure that your path statement references
both the network copy of MS Windows and your own MS Windows directory.
Increasing the Number of File Handles
=====================================
If, as you run more applications and add more users, you encounter
problems running applications across the network, be aware that the
number of file handles allocated in the CONFIG.SYS file at the server
may not be sufficient. This may also be true when you are running the
server under MS Windows. An indication that this situation has occurred
would be getting unexpected "File not found" or "Directory not found"
error messages when doing a DIR command to a drive on that server.
The documentation for your applications should indicate the number of
file handles required per user; make sure that you allow the correct number
in the server's CONFIG.SYS, given the number of users running the
application and the number of times the application is run. If necessary,
change the FILES value. If a value greater than 255 is required, use
NET ADMIN to reconfigure the server so that it does not use the CONFIG.SYS
FILES value and set the required value.
OEM-supplied Network Board Drivers
==================================
To use a third-party network board driver that does not include a .INS
file, do the following:
1. Copy the driver file to the directory into which you installed
Personal NetWare. For example:
COPY A:\MYDRIVER.COM C:\NWCLIENT
2. Change to the Personal NetWare directory and rename the INS.OEM file
to xxxxxxxx.INS, where xxxxxxxx is the name of the driver file. For
example:
REN INS.OEM MYDRIVER.INS
3. Edit the new .INS file with an ASCII text editor and replace the two
references to 3RDPARTY.COM with the file name of your driver. The .INS
file looks like this:
InS_StArT
3RDPARTY.COM
1.0
^ Third Party Driver without .INS file,3RDPARTY.COM,IE0
!RIE0(INT)
2
@3
4
5
10
11
12
15
!RIE0(PORT)
@300
320
340
360
240
280
2C0
InS_EnD
4. Run SETUP. On the screen that allows you to choose the primary
network interface board, display the list of drivers and choose
'Third party driver without .INS file'.
5. Choose to accept the changes and continue, to confirm your choice.
Running Personal NetWare with Other Networking Products
=======================================================
The name (NET.EXE) of the Personal NetWare NET program is likely to
exist in other networking products. After you install Novell DOS 7 with
Personal NetWare, the PATH command will cause the operating system to
search the NWCLIENT directory first. NWCLIENT contains NET.EXE. If you
want to use a different NET.EXE program, edit the PATH command so that
the appropriate directory is searched BEFORE the NWCLIENT directory.
Alternatively, you may find that if you install a different networking
product (or MS Windows), the PATH command is changed so that the NWCLIENT
directory is no longer searched first and a different NET.EXE program
is run instead of Personal NetWare NET.EXE. If you want the Personal
NetWare NET program to run, edit the PATH command so that NWCLIENT is
searched first.
The Personal NetWare Tutorial
=============================
There are two tutorials supplied with Personal NetWare.
One describes how to use DOS versions of the Personal NetWare programs,
the other the MS Windows versions.
To install the tutorial for MS Windows, load MS Windows and run
WINTUTOR.EXE from "Tutorial disk 1". Follow the instructions given on
the screen. Once installation is complete, run the tutorial by selecting
the Tutorial icon from the Personal Netware Tutorial program group.
To install the tutorial for DOS, insert "Tutorial disk 1" in your
diskette drive and run DOSTUTOR.EXE from that drive. Follow the
instructions given on the screen. Once installation is complete,
run the DOS tutorial by entering PNWTRAIN at the system prompt.
Note: If you choose to install the DOS Personal NetWare tutorial to a
directory other than the default one, you must change to this directory
to run the tutorial.
Modifications to MS Windows INI Files
=====================================
When you install the MS Windows element of Personal NetWare,
the following files are modified automatically: SYSTEM.INI,
WIN.INI, and PROGMAN.INI.
The following modifications are made to SYSTEM.INI:
in the [boot] section: network.drv= is replaced by
network.drv=netware.drv
(This loads the NetWare user tools)
in the [boot.description]: network.drv= is replaced by
network.drv=Personal NetWare
(This defines which Personal NetWare
device version you are using)
in the [386Enh] section: network=dosnet is replaced by
network=*vnetbios;vipx.386;vnetware.386
(This specifies the type of network
used with MS Windows 386 Enhanced mode)
TimerCriticalSection= is replaced by
TimerCriticalSection=10000
(Personal NetWare uses this setting to
ensure that network traffic on your
computer runs smoothly)
ReflectDOSInt2A=TRUE is added.
OverlappedIO=OFF is added.
PSPIncrement=5 is added.
UniqueDOSPSP=TRUE is added.
The following modifications are made to WIN.INI:
in the [windows] section: load= is replaced by
load=nwpopup.exe
(This allows network messages to display
in MS Windows)
Netwarn=1 is added.
(If this is set but the network is not
loaded, MS Windows will display a pop-up
indicating that the network is not loaded)
The following modifications are made to PROGMAN.INI:
in the [groups] section: Groupx=C:\windows\pnw.grp is added to
the list of group files.
(This causes MS Windows to load the
Personal NetWare program group in
Program Manager).
Using Remote Computers on the Network
=====================================
For information about how to set up the network so that remote diskless
computers can boot from the Remote Boot disk image files stored on a
Personal NetWare server's hard disk, read the file called RPLDOC.TXT.
Updating the Search & Destroy virus program
===========================================
Updates to the Search and Destroy virus library can be downloaded from the
Sympantec/Fifth Generation BBS at:
504-295-3344 2400 baud N/8/1
504-295-3261 9600 baud N/8/1
or from CompuServe at:
GOFIFTH
in the anti-virus forum.
README.TXT
NOTES ON MS-DOS 6
===========================
This file provides important information not included in the
Microsoft MS-DOS User's Guide or in MS-DOS Help.
The following are the major sections of the README.TXT file:
1. Setup
2. MemMaker and Memory Management
3. Windows
4. Hardware Compatibility with MS-DOS 6
5. Microsoft Programs
6. Third-Party Programs
7. DoubleSpace
8. Resource Kit
If the subject you need information on doesn't appear in the
README.TXT file, you may find it in one of the following text
files included with MS-DOS:
* NETWORKS.TXT, which describes how to update your network software
to work with MS-DOS 6.
* CONNECT.TXT, which contains additional notes about Workgroup
Connection.
* MAIL.TXT, which desribes how to use Microsoft Mail.
If you have questions about procedures or commands mentioned
in any of the text files, you will probably find answers in the
Microsoft MS-DOS User's Guide or, if you have installed MS-DOS 6,
in MS-DOS Help.
Look through the following table of contents to find the specific
topic you are looking for. If you are using the MS-DOS Editor to
view this file, you can use the Find command on the Search
menu to go to the topic you want to read.
The following topics are discussed in this file:
1. Notes on Setup
1.1 You deleted files from the directory that Setup needs
to install the optional programs
1.2 You need to install MS-DOS manually
2. MemMaker and Memory Management
2.1 Intel Expanded-Memory Driver (EMM.SYS)
2.2 When you run Windows, MS-DOS indicates that your
display driver uses the monochrome address range
2.3 MemMaker does not restart after the "MemMaker will now
restart your computer to test the new memory configuration"
screen
2.4 Running MemMaker with a system that has a batch program called
from the AUTOEXEC.BAT file
2.5 Undoing MemMaker changes on a system with disk-compression
2.6 Running MemMaker on a computer with PC-NFS
2.7 Your computer has an Adaptec controller card, and MemMaker
won't work correctly
2.8 386MAX (5.11 or Earlier)
2.9 Optimizing the Order of Programs in CONFIG.SYS and AUTOEXEC.BAT
3. Windows
3.1 "Cannot run Windows in standard mode" Message
3.2 Your computer uses a Windows 3.0 permanent swap file
4. Hardware Compatibility with MS-DOS 6
4.1 Compaq EXTDISK.SYS Driver
4.2 Hardcard
4.3 Inboard 386/PC
4.4 Olivetti and AT&T System with a CGA Video Board
4.5 Toshiba
5. Microsoft Programs
5.1 Running Backup for MS-DOS under Windows
5.2 Defrag
5.3 Microsoft CD-ROM Extensions
6. Third-party Programs
6.1 Above Board 286 and Above Board Plus Installation
Programs
6.2 After Dark for DOS (AD-DOS)
6.3 AutoCAD release 10
6.4 CodeView
6.5 Defragment programs
6.6 Fastback
6.7 GeoWorks
6.8 6.6 Lotus 1-2-3 version 3.x with MS-DOS Shell Task Swapper
6.9 Norton Desktop for Windows 2.0
6.10 PC Tools
6.11 PC-Kwik Disk Accelerator
6.12 Soft-ICE
6.13 Task Swapper and Asynchronous I/O
6.14 Ventura Publisher
7. DoubleSpace
7.1 Installing DoubleSpace If You Use Stacker
7.2 Installing DoubleSpace If You Use Another Disk-Compression Program
7.3 Installing DoubleSpace Manually
7.4 DoubleSpace Setup indicates that your computer is running an
incompatible disk-caching program
7.5 Your computer runs out of disk space while compressing
a drive
7.6 Your compressed drive runs out of disk space
7.7 Your uncompressed drive runs out of disk space
7.8 DoubleSpace did not compress all of your files because
the drive ran out of disk space
7.9 DoubleSpace could not convert a Stacker drive because
there was not enough free space
7.10 DoubleSpace Cannot Convert a Stacker Drive Because
There is Not Enough Free Memory
7.11 Removing DoubleSpace From Your Computer
7.12 Your Workgroup Connection persistent drives conflict with your
DoubleSpace drives
7.13 DoubleSpace and Windows Permanent Swap Files
7.14 Using Stacker Floppy Disks with DoubleSpace
7.15 If EXTDISK.SYS displays a warning about drive letters
7.16 Novell Networks and DoubleSpace
7.17 Using the DBLSPACE.INI File
7.18 You Receive the Message "A CVF is Damaged" When You Start
Your Computer
7.19 You Need a Special Device Driver to Use Your Compressed
Startup Drive
7.20 Defragmenting Uncompressed Drives After Changing File Attributes
7.21 Files DoubleSpace Cannot Compress
7.22 DoubleSpace and Microsoft Mail 3.0 .MMF Files
7.23 Defragmenter Runs Out Of Memory While You Are Compressing a Drive
7.24 Free Space Requirements for Converting a Stacker Drive
8. MS-DOS Supplemental Disk
1. NOTES ON SETUP
================
1.1 You deleted files from the directory that Setup needs
to install the optional programs
---------------------------------------------------------
If you typed "setup /e" at the command prompt, Setup displayed
the "Setup did not find the files it needs in the directory
specified" message, and you think you deleted the files from
your hard disk, carry out the following procedure.
1. Reinstall MS-DOS 6 again.
2. After Setup is finished, type the following at the command
prompt:
setup /e
1.2 You need to install MS-DOS manually
---------------------------------------
If you need to install MS-DOS manually, carry out the following procedure:
1. Insert Setup Disk 1 in drive, and restart your computer by pressing
CTRL+ALT+DEL.
2. After the first screen appears, exit Setup by pressing F3 twice.
3. To transfer your system files, type the following at the command
prompt:
sys a: c:
4. Create a directory on your hard drive for containing your MS-DOS 6
files.
5. Copy all the decompressed files on Setup Disk 1 to your MS-DOS
directory.
6. Use the EXPAND command to decompress the rest of files on your Setup
disks and copy them to your MS-DOS directgory. You must expand the
compressed files one at a time. For example, to decompress the EGA.SY_
file and copy it to the DOS directory, type the following at the command
prompt:
a:expand ega.sy_ c:\dos\ega.sys
For more information about the EXPAND command and the location and
extensions of specific files, see the PACKING.LST file on the Setup
disks.
7. Create startup files in the root of drive C. For more information about
creating your startup files, see the chapter "Configuring Your System"
of the Microsoft MS-DOS 6 User's Guide.
8. Restart your computer by pressing CTRL+ALT+DEL.
2. MEMMAKER AND MEMORY MANAGEMENT
=================================
2.1 Intel Expanded-Memory Driver (EMM.SYS)
------------------------------------------
If you use Intel's EMM.SYS driver with Aboveboard, use
EMM.SYS version 4.0 revision D or later . If you have an
earlier version, contact Intel for a free upgrade.
2.2 When you run Windows, MS-DOS indicates that your display
driver uses the monochrome address range
------------------------------------------------------------
If your computer uses a Windows 3.0 display driver, you need
to modify your SYSTEM.INI file to make the driver compatible
with the MS-DOS 6 EMM386 memory manager. Carry out the
following procedure:
1. Open your SYSTEM.INI file by using any text editor.
2. Find the [386enh] section.
3. Add a DEVICE= line for the MONOUMB.386 file. For example, if
DOS is your MS-DOS directory, add the following line:
DEVICE=C:\DOS\MONOUMB.386
4. Save the file.
5. Restart your computer by pressing CTRL+ALT+DEL.
6. Run Windows again.
2.3 MemMaker does not restart after the "MemMaker will now restart
your computer to test the new memory configuration" screen
------------------------------------------------------------------
If your AUTOEXEC.BAT file contains a command (other than the CALL
command) that starts a batch program, MemMaker might not restart
after it displays this screen. If this happens carry out the
following procedure.
* Type the following at the command prompt:
find /i "memmaker" autoexec.bat >t.bat
Then type the following at the command prompt:
t.bat
MemMaker should restart normally.
2.4 Running MemMaker with a system that has a batch program called
from the AUTOEXEC.BAT file
------------------------------------------------------------------
MemMaker does not optimize programs loaded in a batch
program called from your AUTOEXEC.BAT file. If any of those
programs are loaded high, change their command lines to load them
in conventional memory before you run MemMaker.
2.5 Undoing MemMaker changes on a system with disk-compression
--------------------------------------------------------------
When you undo MemMaker changes on a system with third-party
disk-compression software, you might receive a message instructing
you to run MemMaker with the /SESSION switch. Ignore this message.
Instead, copy the AUTOEXEC.BAT and CONFIG.SYS files from your host
(uncompressed drive) to your compressed drive. Then restart your
computer by pressing CTRL+ALT+DEL.
2.6 Running MemMaker on a computer with PC-NFS
----------------------------------------------
If you use PC-NFS network software, carry out the following procedure
before you run MemMaker:
1. Open your MEMMAKER.INF file using any text editor. This file is
in the directory that contains your MS-DOS files.
2. Add the following line to the file:
*NET
3. Save the file, and then run MemMaker.
2.7 Your computer has an Adaptec controller card, and MemMaker
won't work correctly
-------------------------------------------------------------------
If MemMaker stop running when you try to optimize your computer's
memory configuration, and you use the ADAPTEC.SYS driver with your
Adaptec controller card, your computer is probably incompatible
with MemMaker. Carry out the following procedure to restore your
system:
1. Restart your computer by pressing CTRL+ALT+DEL.
2. The following text is displayed on your screen:
Starting MS-DOS...
While the text is on your screen, press and release the F8 key.
3. Carry out all the commands in your CONFIG.SYS file by pressing
Y each time your are prompted except when you are prompted for
the EMM386.EXE command. When you are prompted for this command,
press N to bypass it.
4. When you prompted for your AUTOEXEC.BAT file, press Y to process
it.
5. Open your CONFIG.SYS by using any text editor. Move the command
for the ADAPTEC.SYS driver so that it appears before the commands
for your HIMEM.SYS and EMM386.EXE files.
6. Save the file, and then restart your computer by pressing
CTRL+ALT+DEL.
2.8 386MAX (5.11 or Earlier)
----------------------------
If you have used the SETVER command to report a different
version number to a program you are loading into the upper
memory area with 386LOAD.COM or MAXHI.COM, also use the
SETVER command to report that number to 386LOAD.COM or
MAXHI.COM. For information about the SETVER command, type
HELP SETVER at the command prompt after you have installed
MS-DOS 6.
The new version number is reported to all programs loaded by
386LOAD.COM and MAXHI.COM.
MAXHI.COM programs supplied with versions of 386MAX earlier
than 5.0 are incompatible with MS-DOS 6.
2.9 Optimizing the Order of Programs in CONFIG.SYS and AUTOEXEC.BAT
-------------------------------------------------------------------
In the "Making More Memory Available" chapter of the MS-DOS 6 User's
Guide, the section "Fine-Tuning Your Memory Configuration" explains
how to free additional memory after running MemMaker. The procedure
"To optimize the order of device drivers and memory-resident programs"
explains that you can optimize memory by sorting device drivers
and memory-residents by their MaxSize values.
To optimize your system further, follow the steps in that procedure,
but instead sort the programs by the difference between each program's
MaxSize and FinalSize values. In general, a program with a large difference
between its MaxSize and FinalSize values should be loaded before a
program with little or no difference between those values.
3. WINDOWS
==========
3.1 "Cannot run Windows in standard mode" Message
-------------------------------------------------
If you have a DEVICE=EMM386.EXE command that includes the
RAM or NOEMS switch in your CONFIG.SYS file, you cannot run
Windows 3.0 in standard mode. Either remove the RAM or NOEMS
switch or run Windows in real or enhanced mode. (If you
remove RAM or NOEMS, you won't be able to load programs and
device drivers into the upper memory area. If you include
RAM or NOEMS, you won't be able to run Windows in standard
mode.)
NOTE: Using EMM386 may reduce the amount of extended memory
available to Windows and cause Windows to try to start in
standard mode. To prevent this, reduce the amount of
extended memory that other device drivers use. For example,
if you are using SMARTDrive, try setting the MinCacheSize
parameter to 0.
3.2 Your computer uses a Windows 3.0 permanent swap file
--------------------------------------------------------
If your computer uses a Windows 3.0 permanent swap file, you
need to run the SPATCH.BAT program to make the swap file
compatible with MS-DOS 6. To do so, carry out the following
procedure:
1. Make sure the SPATCH.BAT program is on your hard disk. If it
isn't, copy it from the Setup disks. For the location of the
file on the Setup disk, view the PACKING.LST file on Setup Disk
1.
2. Type the following at the command prompt:
spatch [drive]:[path]swapfile.exe
For the drive and path parameters, specify the location of
your SWAPFILE.EXE file.
3. Follow the instructions on your screen.
The program modifies the SWAPFILE.EXE for use with MS-DOS 6
and saves a backup copy as SWAPFILE.SAV. After you have confirmed
the file works correctly, you can delete the SWAPFILE.SAV file.
4. HARDWARE COMPATIBILITY WITH MS-DOS
=====================================
4.1 Compaq EXTDISK.SYS Driver
-----------------------------
Compaq EXTDISK.SYS driver version 3.00 or later is
compatible with MS-DOS 6. If you have version less
than 3.00, contact your vendor for an upgrade.
4.2 Hardcard
------------
a) Hardcard II
If you can't use Plus Development Hardcard II or Hardcard
II XL when running EMM386.EXE, specify the exclude (x=)
switch to prevent EMM386 from conflicting with the card's
BIOS address.
See your Hardcard II manual to determine which address
space to exclude. Type HELP EMM386.EXE at the command
prompt for more information about the exclude switch.
b) Hardcard 40 or Passport
If you are using Hardcard 40 or a Passport removable
disk, and you have a DEVICE command for PLUSDRV.SYS in
your CONFIG.SYS file, carry out the following procedure
before upgrading to MS-DOS 6:
1. Disable or remove the DEVICE command for PLUSDRV.SYS
command line in your CONFIG.SYS file.
2. Run MS-DOS 6 Setup.
3. Reenable or return the DEVICE command for PLUSDRV.SYS
in your CONFIG.SYS file. Make it the last line in the
file.
4.3 Inboard 386/PC
-------------------
The Inboard 386/PC is incompatible with the EMM386 memory
manager that comes with MS-DOS 6. Do not load EMM386 in your
CONFIG.SYS file and do not run MemMaker.
4.4 Olivetti and AT&T Systems with a CGA Video Board
----------------------------------------------------
An Olivetti or AT&T system with a CGA video board may not scroll
correctly. Add the /S switch to the DEVICE=ANSI.SYS command
in your CONFIG.SYS file.
4.5 Toshiba
-------------------
Toshiba T3100SX computer's suspend/resume feature is
incompatible with EMM386.EXE. Either disable the feature or
do not use EMM386.EXE.
If you used the MS-DOS 5.0 version of EMM386 before you ran
Setup, and you use the Power Management function, you should not use
the new version of EMM386. Instead, you should use the old version,
which was saved as EMM38650.EXE in your DOS directory.
5. MICROSOFT PROGRAMS
5.1 Running Backup for MS-DOS under Windows
-------------------------------------------
It is recommended that you don't run Backup for MS-DOS under Windows.
However, if you do, and if your system is not configured correctly, Backup
may display the following symptoms:
o Backup appears to stop running--for example, the clock moves, but
there is no disk activity.
o Backup reports problems while testing the second floppy disk during
the compatibility test. For example, it might displays a "Diskette
not properly seated" message or it might ask for Disk 1 repeatedly.
o Windows displays a message that DMA buffer size needs to be increased.
o Backup quits unexpectedly.
You can correctly configure your system by carrying out the following procedure.
1. Open your CONFIG.SYS and make it sure contains the following command
lines:
FILES=30
BUFFERS=30
STACKS-9,256
2. Open your SYSTEM.INI file by choosing the Run command from Program
Manager, typing SYSEDIT, and selecting the SYSTEM.INI file.
3. Locate the [386enh] section.
4. Add the following line to the section:
DMABufferSize=32
5. When you run Backup, make sure that you specify with the Settings
command from the Control menu that Backup run with the Exclusive
and Full Screen options. (If you're running Backup full screen,
press ALT+SPACEBAR to choose the Control menu.)
5.2 Defrag
----------
If you run Defrag and MS-DOS still displays out-of-memory messages after
you have followed the procedures in "An MS-DOS program displays
an out-of-memory message" in the chapter "Diagnosing and Solving
Problems" of the Microsoft MS-DOS User's Guide, your computer
might have too many files for Defrag to reorganize the files on
your hard disk. For Defrag to work correctly, you might need to
delete some files or move them to a floppy disk or a network drive.
5.3 Microsoft CD-ROM Extensions
-------------------------------
Use the MSCDEX.EXE file that comes wtih MS-DOS 6.
If you load MSCDEX.EXE with a batch file or program,
make sure it loads the MSCDEX.EXE file that comes with
MS-DOS 6. The MS-DOS Setup program copies the file
to the directory that contains your MS-DOS files.
6. THIRD-PARTY PROGRAMS
=======================
6.1 Above Board 286 and Above Board Plus Installation
Programs
-----------------------------------------------------
CAUTION: The Intel Above Board installation program that
shipped before May 1989 tests extended memory in a
way that can corrupt extended memory.
Before using an Above Board installation program prior to
May 1989, make sure you haven't loaded software such as
SMARTDrive or RAMDrive that uses extended memory. After the
Above Board has been installed, other software using
extended memory is unaffected.
6.2 After Dark for DOS (AD-DOS)
-------------------------------
If you run After Dark for DOS (AD-DOS) at the same time you
are running programs that use DPMI, you may have problems with
MS-DOS--for example, your system may halt suddenly or you may
receive "packed-file corrupt" messages. Examples of programs
that use DPMI are Microsoft MASM61, C7, and FoxPro25.
6.3 AutoCAD release 10
---------------------
To run AutoCAD release 10 for MS-DOS, contact Autodesk for a
patch file. No patch is needed for AutoCAD386.
6.4 CodeView
-----------
CAUTION: Using versions 3.0 to 3.13 of the CodeView CV.EXE
file may cause data loss if your system has a 80386 memory
manager (such as EMM386.EXE) and device drivers or programs
that use extended memory. To determine which version you
have, type CV.EXE at the command prompt.
This problem has been fixed in CodeView version 3.14. Call
Microsoft C Support to get this version.
6.5 Defragment programs
-----------------------
Third-party defragmentation programs, such as PC Tools COMPRESS or
Norton SpeedDisk, are currently incompatible with DoubleSpace
drives. Do not use them. When running MS-DOS 6, use the
DEFRAG command from the command prompt or the Defragment command
from DoubleSpace. These commands are fully integrated with MS-DOS 6.
6.6 Fastback
-------------
To ensure that you don't lose data, if you have a version
of Fifth Generation Systems Fastback earlier than 3.0, you
must use the LOADFIX command before running Fastback or the
Fastback installation program. Type the following:
LOADFIX FB.EXE
or
LOADFIX FBINSTAL.EXE
For information about the LOADFIX command, type HELP LOADFIX
at the command prompt.
6.7 GeoWorks
-------------
To install GeoWorks version 1.2 on MS-DOS 6, you must use the
SETVER command to change the MS-DOS version for the GeoWorks
setup program. Carry out the following procedure:
1. Before you run GeoWorks Setup, type the following at the
command prompt:
setver setup.exe 5.00
2. Restart your computer by pressing CTRL+ALT+DEL.
3. Run the GeoWorks setup program.
4. After you have installed GeoWorks, type the following at
the command prompt:
setver setup.exe /delete
5. Restart your computer by pressing CTRL+ALT+DEL.
If you have a version of GeoWorks (PC/GEOS) earlier than
1.2, use the SETVER command to report version number 4.01 to
the GEOS.EXE file. Type the following:
SETVER GEOS.EXE 4.01
Do not run the installation program for GeoWorks Ensemble
when MS-DOS Shell Task Swapper is active.
Use the Exclusive Tasking option when running GeoWorks
Ensemble with Windows.
6.8 Lotus 1-2-3 version 3.x with MS-DOS Shell Task Swapper
-----------------------------------------------------------
If you use Lotus 1-2-3 version 3.x with the Task Swapper
in MS-DOS Shell, do not specify the NOVCPI switch with the
EMM386.EXE command in your CONFIG.SYS file.
6.9 Norton Desktop for Windows 2.0
----------------------------------
Setup modifies Norton Desktop for Windows by adding a
second Tools menu which contains Backup and Antivirus commands
(if you installed these Windows programs), as well as a
DoubleSpace Info command.
If you installed the Anti-Virus, Backup, and Undelete
for Windows, you can add to Norton Desktop a Microsoft
Tools group containing the programs' icons. Carry out Procedure 1
if you have a group open and want to add to it the
Microsoft Tools group. Carry out Procedure 2 if you don't have a
group open.
Procedure 1 To add the Microsoft Tools Group if the group window
is open:
* Drag the file C:\DOS\WNTOOLS.GRP and drop it on the group window.
Procedure 2 To add the Microsoft Tools Group if the the group window\
is not open:
1. Select the group into which you want the Microsoft Tools group to
go--for example, the Main or Quick Access group.
2. From Norton Desktop for Windows, choose New from the File menu.
3. In the New dialog box, select Group as the Type.
4. In the Group File Name box, type the path to the WNTOOLS.GRP file.
This file is in the directory that contains your MS-DOS files. For
example, if this directory is C:\DOS, type the following:
C:\DOS\WNTOOLS.GRP
5. Choose OK.
6.10 PC Tools
------------
The FORMAT command of PC Tools version 7.1 conflicts with
MS-DOS 6. You should use the FORMAT.EXE command that comes
with MS-DOS 6.
The COMPRESS command of PC Tools version 6.0 is incompatible
with DoubleSpace. Do not use it. When running MS-DOS 6, use the
DEFRAG command from the command prompt or the Defragment command
from DoubleSpace. These commands are fully integrated with MS-DOS 6.
6.11 PC-Kwik Disk Accelerator
-----------------------------
Do not load versions of Multisoft PC-Kwik Disk Accelerator
earlier than 2.0 into the upper memory area.
6.12 Soft-ICE
-------------
When using Nu-Mega Soft-ICE, load it before loading other
drivers. Otherwise, you may lose data stored in extended
memory by drivers such as SMARTDrive.
In addition, when running Soft-ICE and SMARTDrive, do not
press CTRL+ALT+DEL until you are sure that your computer's
software has finished writing to disk. Otherwise, you might
lose data.
6.13 Task Swapper and Asynchronous I/O
--------------------------------------
Some programs that perform asynchronous communications are
incompatible with MS-DOS Shell Task Swapper. Terminal-
emulation software (such as SmartCom and Procomm Plus) and
server/client software (such as Laplink and Blast) are
asynchronous communications programs. If you can't use an
asynchronous program with Task Swapper, contact your vendor
for more information, or disable Task Swapper.
6.14 Ventura Publisher
----------------------
If you can't start a version of Ventura Publisher, make sure your
Ventura Publisher directory is within the first 70 characters of
the PATH command in your AUTOEXEC.BAT file.
7. DOUBLESPACE
==============
7.1 Installing DoubleSpace If You Use Stacker
---------------------------------------------
If you use Stacker disk-compression software, you can install
DoubleSpace and automatically convert your compressed drives
to DoubleSpace format.
Note: If your version of Stacker is 1.1 or you compressed your drive
with a 4K cluster size, you cannot automatically convert your Stacker
drive; you must convert it manually, as described in the procedure
"Installing DoubleSpace Manually."
To install DoubleSpace, carry out the folllowing procedure.
1. Type the following at the command prompt:
dblspace
2. Follow the instructions on your screen. DoubleSpace Setup will
prompt you to convert your Stacker drives.
3. After DoubleSpace Setup converts your Stacker drives, DoubleSpace
informs you that there are some Stacker files you might want to
delete from your uncompressed drive. The following are files and
directories you can delete:
CONFIG.*
AUTOEXEC.STC
STACKER.LOG
COMMAND.COM
Your Stacker directory and all its files
Your Windows, MS-DOS, and OLD_DOS.x directories, if any, and all
their files
NOTE:
You can use the DELTREE command to delete directories and all
their commands.
7.2 Installing DoubleSpace If You Use Another Disk-Compression Program
----------------------------------------------------------------------
If your computer uses Stacker disk-compression software, see
section 7.1.
If your computer uses XtraDrive disk compression, use its
uninstallation program to remove the compression, and then
install DoubleSpace.
If your computer uses another disk-compression program,
you can install DoubleSpace manually by following the procedure
in the following section.
7.3 Installing DoubleSpace Manually
-----------------------------------
To convert your disk-compression software to DoubleSpace manually:
1. Install MS-DOS 6 if you haven't already done so.
2. Use Microsoft Backup to back up the files on your hard disk.
3. Insert Setup Disk 1 in drive A, and restart your computer
by pressing CTRL+ALT+DEL. When the first screen appears, press
F3 twice to exit Setup.
Or, create a startup disk by inserting Setup Disk in drive B,
and typing B:SETUP /F. When prompted, choose to install
MS-DOS to the floppy disk in drive A. After Setup is finished,
restart your computer by inserting the startup disk in drive A
and pressing CTRL+ALT+DEL.
4. Use the format command to format the drive that contains the
file that stores all of your compressed files. If you don't know
where this file is located, see your disk-compression
documentation.
If you are reformatting drive C, include the /S switch to transfer
your system files, as in the following example:
format c: /s
NOTE
If you don't format drive C, remove from your CONFIG.SYS and
AUTOEXEC.BAT files any commands that were used by your disk-
compression software.
5. If you formatted drive C, make sure Setup Disk 1 is in drive A
or B, and type A:SETUP or B:SETUP at the command prompt.
Follow the instructions on your screen.
6. Install DoubleSpace by typing DBLSPACE at the command prompt.
Follow the instructions on your screen.
For more information about DoubleSpace, see the chapter
"Freeing Disk Space" of the Microsoft MS-DOS User's Guide.
7. Restore the files you backed up.
7.4 DoubleSpace Setup indicates that your computer is running an
incompatible disk-caching program
----------------------------------------------------------------
If DoubleSpace Setup displays a message indicating your computer
is running an incompatible disk-caching program, carry out the
following procedure to install DoubleSpace:
1. Open your CONFIG.SYS file by typing EDIT C:\CONFIG.SYS
at the command prompt.
2. Delete the line that contains the device command that loads
your disk-caching program.
3. Make sure you have a line for the MS-DOS 6 SMARTDRV program.
For example, if C:\DOS is your MS-DOS directory, add the
following line:
C:\DOS\SMARTDRV.EXE /DOUBLE_BUFFER
4. Save the file.
5. Open your AUTOEXEC.BAT file.
6. Make sure you have a line for the MS-DOS 6 SMARTDRV program.
For example, if DOS is your MS-DOS directory, add the
following line:
C:\DOS\SMARTDRV.EXE /L
7. Save the file, and restart your computer by pressing
CTRL+ALT+DEL.
8. Run DoubleSpace again.
7.5 You attempt to mount a compressed floppy disk, and MS-DOS
displays an error message
-------------------------------------------------------------
If you have not installed DoubleSpace on your hard disk, and you
attempt to mount a compressed floppy disk, MS-DOS displays
the following message:
There are no more drive letters reserved
for DoubleSpace to use. To add more drive letters,
choose the Options command from the Tools menu.
You must load DBLSPACE.BIN and create a DBLSPACE.INI file to mount
compressed floppy disks if you have not installed DoubleSpace on your
hard disk.
To correct this problem:
1. Create a C:\DBLSPACE.INI file by using any text editor.
DBLSPACE.INI should contain the following two lines:
MaxRemovableDrives=2
LastDrive=F
Note: LastDrive= must be set to one letter higher than your last
logical drive letter. For example, if your last drive is E:,
use LastDrive=F in your DBLSPACE.INI file.
2. Copy DBLSPACE.BIN from your MS-DOS directory to the root directory of
your startup drive. For example, type the following at the command
prompt:
copy c:\dos\dblspace.bin c:\
3. Restart the computer.
4. You can now mount the compressed disk in your floppy drive. For
example, if the disk is in drive A:, type the following at the
command prompt:
dblspace /mount a:
7.6 Your compressed drive runs out of disk space
------------------------------------------------
If your compressed drive runs out of free disk space, you can
use the following techniques to free some space on that drive:
* Specify a higher estimated compression ratio for that drive.
* Enlarge that drive.
* Carry out the DEFRAG command on that drive.
The rest of this section explains each technique.
Specifying A Higher Estimated Compression Ratio
If a compressed drive's estimated compression ratio is too small,
MS-DOS might report that there is no more free space on that drive,
when some space is in fact available. (Raising the estimated compression
ratio is most effective if the files you are trying to store are highly
compressible. It will have no effect if the drive really is out of space.)
To specify a larger estimated compression ratio:
1. Start the DoubleSpace program by typing DBLSPACE at the command
prompt.
2. Select the compressed drive you want to change, and then choose
the Change Ratio command from the Drive menu.
DoubleSpace displays the Change Compression Ratio dialog box.
3. Specify a larger compression ratio, and then choose OK. For more
information, choose the Help button.
You can also change the estimated compression ratio from the command prompt.
For more information, type HELP DBLSPACE /RATIO at the command prompt.
Enlarging a Compressed Drive
You can enlarge a compressed drive to make more space available on it.
Enlarging a compressed drive uses free space on the uncompressed drive
(the host drive).
To enlarge the compressed drive:
1. Start the DoubleSpace program by typing DBLSPACE at the command prompt.
2. Select the compressed drive you want to enlarge, and then choose
the Change Size command from the Drive menu.
DoubleSpace displays the Change Size dialog box. The New Free Space
line shows how much free space the compressed and uncompressed drives
will have if you choose OK.
3. Specify a smaller number for the New Free Space on the uncompressed
drive. Notice that as you change this number, DoubleSpace adjusts
the New Free Space amount for the compressed drive. When the New Free
Space amount for both drives appears the way you want, choose OK.
DoubleSpace enlarges the drive.
Carrying Out the DEFRAG Command on the Compressed Drive
Sometimes, you can free additional space on a compressed drive by
carrying out the DEFRAG command on it. Although defragmenting files
does not free space on an uncompressed drive, it can sometimes free
space on a compressed drive.
To carry out the DEFRAG command on the compressed drive:
1. Start the Defrag program by typing DEFRAG at the command prompt.
2. When the Defrag program starts, select the compressed drive, and
then choose OK.
3. Choose the Optimization Method command from the Optimize menu.
Defrag displays the Select Optimization Method dialog.
4. Select Full Optimization, and then choose OK.
5. Choose the Begin Optimization command from the Optimize menu.
Defrag optimizes the compressed drive. (This process optimizes the
way the compressed drives' compressed volume file is stored on
your hard disk.)
When Defrag finishes optimizing, it starts DoubleSpace to defragment
the way files are stored on the compressed drive. During this
extra optimization step, DoubleSpace frees as much space on
the drive as possible.
6. To quit the Defrag program, Choose Exit from the Optimize menu.
7.7 Your uncompressed drive runs out of disk space
--------------------------------------------------
If your uncompressed drive (host drive) runs out of free disk space, you
can enlarge it by reducing the size of any compressed drives that are
stored on that uncompressed drive. Of course, this will reduce the
amount of free space on the compressed drive(s).
To enlarge the uncompressed drive (host drive):
1. Start the DoubleSpace program by typing DBLSPACE at the command prompt.
2. Select the compressed drive whose size you want to reduce, and then
choose the Change Size command from the Drive menu. (You need to select
a compressed drive that is stored on the uncompressed drive that's
out of space. To find out which compressed drives are stored
on that uncompressed drive, type DBLSPACE /LIST at the command prompt.)
DoubleSpace displays the Change Size dialog box. The New Free Space
line shows how much free space the compressed and uncompressed drives
will have if you choose OK.
3. Specify a larger number for the New Free Space on the uncompressed
drive. Notice that as you change this number, DoubleSpace adjusts
the New Free Space amount for the compressed drive. When the New Free
Space amount for both drives appears the way you want, choose OK.
DoubleSpace reduces the size of the compressed drive, which makes
more free space available on the corresponding uncompressed drive.
7.8 DoubleSpace did not compress all of your files because
the drive ran out of disk space
----------------------------------------------------------
If DoubleSpace indicates that it could not compress some
of your files because there was not enough disk space, carry
out the following procedure.
1. Type DBLSPACE at the command prompt.
2. To determine which drive is your uncompressed drive, choose
Info from the Drive menu. Then choose Exit from the Drive
menu.
3. Back up to floppy disks the files that were left uncompressed
on the uncompressed drive.
4. Delete the files that were left uncompressed on the uncompressed
drive.
5. Type DBLSPACE at the command prompt.
6. Choose Change Size from the Drive menu.
7. To increase the size of your compressed drive, decrease the size
of your uncompressed drive. Choose OK.
7. Choose Exit from the Drive menu, and copy the backed-up files
to your compressed drive. If you run out of space again, repeat
steps 5 through 7 until the compressed drive is large enough.
7.9 DoubleSpace could not convert a Stacker drive because
there was not enough free space
---------------------------------------------------------
DoubleSpace indicates how much free space needs to be free
on your startup or uncompressed drive. Make a note of this
amount. Then carry out the following procedure:
1. Type the following at the command prompt:
chkdsk drive:
For the drive parameter, type the drive letter of your
uncompressed drive. A line similar to the following should
appear on your screen:
20386 bytes available on disk
2. Delete unnecessary files or move files to another drive until
you have enough free disk space. You might want to back up
the files before you delete them.
IMPORTANT
Do not delete your COMMAND.COM, AUTOEXEC.BAT, or CONFIG.SYS
files, your hidden Stacker or system files, or STACKER.COM
and SSWAP.COM files in your Stacker directory. If you cannot
delete enough unnecessary files, use the SDEFRAG /G command to
make more uncompressed space available. Or contact your disk-
compression software vendor.
3. Run DoubleSpace again.
7.10 DoubleSpace Cannot Convert a Stacker Drive Because
There is Not Enough Free Memory
-------------------------------------------------------
If DoubleSpace displays a message that it cannot convert
Stacker because there is not enough free memory, carry out
the procedures in "An MS-DOS-based program displays an
out-of-memory message" in the chapter "Diagnosing and Solving
Problems" of the Microsoft MS-DOS 6 User's Guide.
IMPORTANT
In procedure 2, make sure not to bypass any commands that
enable access to your Stacker drives. For example, don't
bypass the DEVICE commands that load the STACKER.COM and
SSWAP.COM commands.
7.11 Removing DoubleSpace From Your Computer
--------------------------------------------
There is no method for automatically removing DoubleSpace.
You can only remove it manually. To do so, carry out the
following procedure:
1. Back up the files on the compressed drive. If you're using
a backup program on the compressed drive, make sure the
program files are on another drive or are on a floppy disk.
2. Type DBLSPACE at the command prompt.
3. Choose the Info command from the Drive menu. Note on which
uncompressed drive the compressed drive is stored.
4. Copy the COMMAND.COM file from your compressed drive to the root of
your uncompressed drive.
5. To delete your DoubleSpace files, make your uncompressed drive current,
and then type the following at the command prompt:
deltree dblspace.*
6. Restart your computer by pressing CTRL+ALT+DEL at the command
prompt.
7. Restore your backed-up files.
After restoring your files, you may want to delete the command in
your CONFIG.SYS that loads the DBLDPACE.SYS driver.
7.12 Your Workgroup Connection persistent drives conflict with your
DoubleSpace drives
-------------------------------------------------------------------
If you did not load your network before running DoubleSpace Setup,
you might have a conflict between your Workgroup Connection
persistent drives and your DoubleSpace drives. Symptoms of this
problem are:
* You cannot get access to the uncompressed drive that contains
your compressed drive. Instead, what should be the uncompressed
drive is a network drive.
* When you type DBLSPACE at the command prompt, DoubleSpace displays
the "A network drive has been connected using drive letter X"
message.
To remedy this problem, carry out the following procedure:
1. Type the following at the command prompt:
net use /p:clear
2. Restart your computer by pressing CTRL+ALT+DEL.
You will need to reestablish your network connections. Make sure
not to use the drive letter of your uncompressed drive.
7.13 DoubleSpace and Windows Permanent Swap Files
-------------------------------------------------
When you install DoubleSpace, it checks for the existence of a Windows
permanent swap file. If DoubleSpace finds a permanent swap file,
it moves the file to your uncompressed drive.
If you install Windows after installing DoubleSpace, or if you use
Control Panel to change the location of your permanent swap file, your
swap file might end up being located on a compressed drive. (When you
specify a drive for your permanent swap file, Windows allows you to
choose a compressed drive.)
If your Windows permanent swap file is located on a compressed drive, then
Windows displays the message "The permanent swap file is corrupt" when it
starts.
To solve this problem:
1. At the "Permanent swap file is corrupt" screen, type Y in response
to the question "Do you want to delete this swap file?", and
then press ENTER.
2. After Windows starts, open Control Panel, and then double-click the 386
Enhanced icon.
3. Choose the Virtual Memory button.
Windows displays a dialog box saying that a corrupt swap file was found,
and asks if you want to set the file's length to zero.
4. Choose the Yes button. Windows displays another Virtual Memory dialog box.
5. Choose the Change button. Windows displays swap-file settings.
6. In the Drive list box, select a drive that is not compressed. In the
Type list box, select "Permanent."
If your uncompressed drive does not have enough free space to create a
permanent swap file, create a temporary swap file on either your
compressed or uncompressed drives. (For information about freeing
space on your uncompressed drive, see the topic "Your uncompressed
drive is out of disk space" later in this file.)
When you have finished specifying swap-file settings, choose OK twice.
Windows displays a dialog box asking if you want to restart Windows now.
7. Choose the Restart Windows button.
7.14 Using Stacker Floppy Disks with DoubleSpace
------------------------------------------------
If you have floppy disks that were compressed by using Stacker,
you must convert them to DoubleSpace format in order to use them
with DoubleSpace.
When DoubleSpace Setup converts your Stacker drives to DoubleSpace
format, it also converts any compressed floppy disks or other
removable media that are currently mounted. After you have completed
DoubleSpace Setup, you can convert other floppy disks and removable
media from Stacker to DoubleSpace format by using the Convert Stacker
command.
If a compressed floppy disk contains at least .9 MB of free space, you can
convert it to DoubleSpace format by choosing the Convert Stacker option
from the Tools menu in DoubleSpace, or by typing DBLSPACE /CONVSTAC
at the MS-DOS command prompt.
If a floppy disk contains less than .9 MB of free space, you can convert it
to DoubleSpace format manually.
To manually convert a Stacker compressed floppy disk to DoubleSpace:
1. Make sure the STACKER.COM file is on your hard drive. If it isn't,
copy it to your hard drive from your Stacker disk.
2. Open your CONFIG.SYS file by using any text editor, and add a
DEVICE command for your STACKER.COM file. At the end of the command
line add a "@" character. For example, the command line should look
like the following:
c:\stacker\stacker.com @
3. Remove disks from all floppy disk drives, and restart your computer
by pressing CTRL+ALT+DEL.
4. Insert the Stacker floppy into a floppy disk drive. Then use the
STACKER command to mount the floppy disk. For example, if the floppy
disk is in drive A, and the STACKER.COM file is in your STACKER
directory, type the following at the command prompt:
c:\stacker\stacker a:
5. Move files from the floppy disk to another drive until you have
enough free space on the floppy disk.
6. Remove the DEVICE command for STACKER.COM from your
CONFIG.SYS file.
7. Remove disks from all floppy disk drives, and restart your computer
by pressing CTRL+ALT+DEL.
8. Run DoubleSpace again, and choose to convert the Stacker floppy
disk.
7.15 If EXTDISK.SYS displays a warning about drive letters
----------------------------------------------------------
If you use DoubleSpace and your CONFIG.SYS file loads the EXTDISK.SYS
device driver, EXTDISK.SYS displays the following message when it loads:
WARNING: EXTDISK.SYS is not the first device driver to assign drive
letters. Physical hard drive letters will not be contiguous.
The EXTDISK.SYS driver still works properly. It displays this message
because it expects to be the first module to assign drive letters,
but since DBLSPACE.BIN loads before the CONFIG.SYS file and assigns
some drive letters, EXTDISK.SYS is no longer first. (EXTDISK.SYS
displays the message regardless of when the DBLSPACE.SYS device
driver is loaded in the CONFIG.SYS file.)
7.16 Novell Networks and DoubleSpace
------------------------------------
When you load netx.com, it establishes a network drive
connection using the drive letter that follows the drive
letter specified with the LASTDRIVE command in your
CONFIG.SYS file. This also applies to any of the following
files:
NET5.COM
BNETX.COM
BNETX.EXE
XMSNET5.EXE
XMSNETX.EXE
EMSNET5.EXE
EMSNETX.EXE
If you don't specify a LASTDRIVE command, MS-DOS uses "E"
as its default, and your network software uses "F" when it
establishes a network connection.
By default, DoubleSpace reserves four drive letters between the
local compressed drive and the host drive for the Compressed
Volume File (CVF). These drive letters are reserved for future use
by such items as a RAMDRIVE, a CD-ROM drive, or a second hard
drive. Thus, a drive letter conflict can arise when you compress
your local drive.
For example, if you have one logical partition C on your hard drive,
and you compress drive C, DoubleSpace reserves drive letters
"D" through "G" for future use and "H" for the drive hosting
the CVF. If you had not specified a LASTDRIVE command, your
network software would use the drive letter following the
host drive--in this case "I". In your AUTOEXEC.BAT file or in the
batch file you use to log on to the nework, any commands that
assume the network drive has a different drive letter will cause
problems.
There are two ways of avoiding drive conflicts:
* When you install DoubleSpace, run it in Custom mode. Then specify
for your host drive a letter that won't conflict with the letter
your network software uses. For example, if your network drive is
currently "F," you could use "E" for your host drive when you
install DoubleSpace.
* Change the drive references in your AUTOEXEC.BAT file or batch file you
use to log on to the network. Make sure the references match
what your network software will default to after you have installed
DoubleSpace. Also, if you log in manually, use a drive letter that
follows the drive letter DoubleSpace uses for the host drive.
7.17 Using the DBLSPACE.INI File
--------------------------------
The DBLSPACE.INI file is a text file with the Read-Only and Hidden
attributes. DoubleSpace stores this file in the root directory of your
startup drive. The DBLSPACE.INI file contains variables that DoubleSpace
uses when your computer starts. Although it is possible to change these
variables yourself, you should do so only if you understand what they do
and what the results might be. Before changing the DBLSPACE.INI file,
you should make a backup copy of the file.
The DBLSPACE.INI file can contain one or more of the following variables:
MaxRemovableDrives=n
Specifies how many additional drives DoubleSpace should
allocate memory for when your computer starts. DoubleSpace
allocates 96 bytes of memory for each additional drive.
The MaxRemovableDrives variable determines how many additional
compressed drives you can create or mount without restarting
your computer.
FirstDrive=X
Set by DoubleSpace each time it modifies the DBLSPACE.INI file.
Do not change the FirstDrive variable yourself.
LastDrive=Y
Specifies the highest drive letter available for use by
DoubleSpace. (If another program uses one of the drive
letters specified for DoubleSpace, the highest drive letter
available to DoubleSpace will be higher than the LastDrive
variable.)
MaxFileFragments=n
Set by DoubleSpace to specify the degree of fragmentation to
allow in all mounted compressed volume files. Do not change
the MaxFileFragments variable yourself.
ActivateDrive=X,Yn
Specifies a compressed volume file that DoubleSpace should
mount automatically when your computer starts. The
ActivateDrive variable requires the following parameters:
X The drive letter to assign to the newly mounted
compressed drive.
Y The drive letter of the HOTLINK("host drive", hlHOST).
n The number of the HOTLINK("compressed volume file",hlCVF).
To determine the CVF number, examine its filename extension.
If the CVF filename is DBLSPACE.000, set n to 0; if the
CVF filename is DBLSPACE.001, set n to 1; and so on.
The DBLSPACE.INI file can contain than one ActivateDrive variable.
7.18 You Receive the Message "A CVF is Damaged" When You Start Your Computer
----------------------------------------------------------------------------
A CVF is a compressed volume file -- a special file that contains a
compressed drive. A CVF is located on an uncompressed drive. DoubleSpace
associates the CVF with a drive letter and makes the CVF's contents
accessible. This is called "mounting" the CVF. You can then use the
files that the CVF contains.
One or more CVFs have been damaged if you receive the following
message when you start your computer:
A CVF is damaged. For more information, see the DoubleSpace section of
the README.TXT file. To continue, press ENTER.
To correct this problem:
1. At the command prompt, change to your compressed drive and then run
Chkdsk to fix errors on that drive. For example, if your compressed
drive is drive C, you would type the following:
c:
chkdsk /f
2. The Chkdsk program checks for logical errors in the file allocation tables
and directory structure of the current drive, and reports any problems it
finds. When Chkdsk is finished, DoubleSpace checks the validity of the CVF's internal
structure, and reports any problems it found. Both Chkdsk and DoubleSpace
also fix as many problems as possible.
3. If Chkdsk found any cross-linked files, it displays a message like the
following:
FILENAME.XXX is cross linked on allocation unit 123.
To fix this problem, copy the specified file or directory by using the
COPY command, and then delete the original file. Some of the information
in a cross-linked file or directory might be lost.
4. If you have more than one compressed drive, repeat steps 1 through
3 for each compressed drive.
5. Restart your computer by pressing CTRL+ALT+DEL.
7.19 You Need a Special Device Driver to Use Your Compressed Startup Drive
--------------------------------------------------------------------------
If your startup hard disk drive requires an installable device driver,
you can compress it by using DoubleSpace. However, you must take a few
extra steps to configure the drive before and after installing DoubleSpace.
If you install DoubleSpace and then restart your computer without following
these steps, DoubleSpace will be unable to provide access to your startup
drive. (This is because MS-DOS loads DBLSPACE.BIN, the portion of MS-DOS
that provides access to compressed drives, before carrying out the commands
in your CONFIG.SYS file.)
To compress a startup hard disk that requires a device driver:
1. Install DoubleSpace by typing DBLSPACE at the command prompt, and choose
Express Setup. (If you choose Custom Setup, have DoubleSpace compress
existing drive C.) When DoubleSpace Setup completes, it lists information
about two drives: drive C (your newly compressed startup drive) and
an uncompressed drive (for example, drive H). Note the drive letter
of the uncompressed drive.
2. Quit DoubleSpace Setup.
3. Change to the uncompressed drive that DoubleSpace Setup listed (for
example, drive H).
4. Type the following at the command prompt:
dir /a
The root directory should contain at least the following files:
IO.SYS
MSDOS.SYS
COMMAND.COM
DBLSPACE.BIN
DBLSPACE.000
5. Change to drive C and open your AUTOEXEC.BAT file. For example, to
change to drive C and open the AUTOEXEC.BAT file by using MS-DOS
Editor, you would type the following commands at the command prompt:
c:
edit c:\autoexec.bat
6. Add the following command to the beginning of your AUTOEXEC.BAT file:
dblspace /mount
Save your changes and quit the text editor.
7. Use the COPY command to copy the following files from your compressed
drive to the root directory of the uncompressed drive:
* DBLSPACE.EXE (located in the directory that contains your MS-DOS files)
* CONFIG.SYS (located in the root directory)
* AUTOEXEC.BAT (located in the root directory)
* Any device drivers loaded by commands in your CONFIG.SYS file
Programs started by commands in your AUTOEXEC.BAT file can remain on
the compressed drive.
7.20 Defragmenting Uncompressed Drives After Changing File Attributes
---------------------------------------------------------------------
You can safely defragment both your compressed or uncompressed drives,
using MS-DOS Defragmenter or another defragmentation program, as long
as you do not change the file attributes of your compressed volume files.
Caution: Do not change a CVF's file attributes and then defragment the
drive containing that CVF. The file attributes of a compressed
volume file must be Read-Only, Hidden and System. If you change
the CVF's attributes and then defragment the uncompressed drive
while that CVF is still mounted, you might lose all the files
on that compressed drive.
7.21 Files DoubleSpace Cannot Compress
--------------------------------------
Some files (such as .ZIP files) are already compressed. DoubleSpace
might not be able to compress such files any further.
Encrypted data files, such as the Microsoft Mail 3.0 .MMF file, are
not compressible and will be stored in uncompressed form, even if
you store such files on a compressed drive.
7.22 DoubleSpace and Microsoft Mail 3.0 .MMF Files
--------------------------------------------------
If you use Microsoft Mail 3.0, you might want to make sure your mail
(.MMF) file is located on an uncompressed drive. Mail works properly
if the .MMF file is located on a compressed drive; however, your system
might run faster if the file is located on an uncompressed drive.
Microsoft Mail normally stores the .MMF file in encrypted, compressed
form. Because DoubleSpace cannot compress such a file, there is no
advantage in storing the .MMF file on a compressed drive.
If your uncompressed drive does not have enough space to accommodate
your .MMF file, you can reduce the size of your compressed drive.
To do this, follow the procedure in section 7.xx, "Your uncompressed
drive is out of disk space."
7.23 Defragmenter Runs Out Of Memory While You Are Compressing a Drive
----------------------------------------------------------------------
If the Defragmenter runs out of memory while you are compressing a drive,
exit DoubleSpace, and then carry out the procedures in "An MS-DOS-based
program displays an out-of-memory message" in the chapter "Diagnosing
and Solving Problems" of the Microsoft MS-DOS 6 User's Guide.
If the Defragmenter still runs out of memory after you have tried
these procedures, your computer might have too many files for the
Defragmenter to reorganize the files on your hard disk. For the
program to work correctly, you might need to delete some files or
move them to a floppy disk or a network drive.
7.24 Free Space Requirements for Converting a Stacker Drive
------------------------------------------------------------
To convert a Stacker drive to DoubleSpace format, the drive must
contain some free space. To convert your startup hard disk, the
drive must contain at least 1.7 MB of free space. To convert other
hard drives and floppy disks, the drive or disk must contain at
least 1.0 MB of free space.
8. Resource Kit
-------------------
The MS-DOS 6 Resource Kit contains a command reference which is
a printed version of MS-DOS Help. The Resource Kit also includes
the MS-DOS 6 Supplemental Disk. The disk contains all the commands that were
included with MS-DOS 5.0 but not MS-DOS 6. In addition, the disk contains
AccessDOS, which provides movemovent- or hearing-disabled users with
better access to computers that run MS-DOS.
To obtain the Resource Kit, send in the coupon at the back of the
Microsoft MS-DOS User's Guide, and then send it in. Other methods for
obtaining the Supplemental Disk are described in "AccessDOS" in "Appendix B"
of the Microsoft MS-DOS User's Guide.
README.TXT
NOTES ON MS-DOS 6
=================
This file provides important information not included in the
MICROSOFT MS-DOS 6 USER'S GUIDE or in MS-DOS Help.
This file is divided into the following major sections:
1. Setup
2. MemMaker and Memory Management
3. Windows
4. Hardware Compatibility with MS-DOS 6
5. Microsoft Programs
6. Third-Party Programs
7. DoubleSpace
If the subject you need information about doesn't appear in
this file, you might find it in one of the following text
files included with MS-DOS:
* NETWORKS.TXT, which describes how to update your network software
for use with MS-DOS 6.
This file contains the following topics:
1. Notes on Setup
1.1 You deleted files from the directory that Setup needs
to install the optional programs.
1.2 You need to install MS-DOS manually.
1.3 How to set up the Icelandic keyboard
2. MemMaker and Memory Management
2.1 Intel Expanded-Memory Driver (EMM.SYS)
2.2 Running MemMaker on a Computer with PC-NFS
2.3 You have a Super VGA display and want to conserve memory.
2.4 Additional MemMaker Troubleshooting
2.5 Using MemMaker with IBM LAN
2.6 MemMaker and Adaptec SCSI devices
3. Windows
3.1 The "Cannot run Windows in standard mode" message appears.
4. Hardware Compatibility with MS-DOS 6
4.1 Hardcard
4.2 Inboard 386/PC
4.3 Olivetti and AT&T Systems with CGA Video Boards
5. Microsoft Programs
5.1 Microsoft Anti-Virus
5.2 Microsoft Backup
5.3 Microsoft CD-ROM Extensions
5.4 Microsoft Defragmenter
6. Third-party Programs
6.1 4DOS and NDOS
6.2 Above Board 286 and Above Board Plus Installation
Programs
6.3 After Dark for DOS (AD-DOS)
6.4 CodeView
6.5 Colorado Tape Backup
6.6 Fastback Plus
6.7 Norton Desktop for Windows 2.0
6.8 Norton Utilities
6.9 PC Tools
6.10 QEMM-386 (6.02 or earlier)
7. DoubleSpace
7.1 Converting Your Disk-Compression Software to DoubleSpace
7.2 DoubleSpace Setup indicates that your computer is running an
incompatible disk-caching program.
7.3 Your compressed drive runs out of disk space.
7.4 Your uncompressed drive runs out of disk space.
7.5 DoubleSpace did not compress all of your files because
the drive ran out of disk space.
7.6 Removing DoubleSpace from Your Computer
7.7 Windows displays the message "The permanent swap file is corrupt."
7.8 EXTDISK.SYS displays a warning about drive letters.
7.9 You need a special device driver to use your startup drive.
7.10 Defragmenting Uncompressed Drives After Changing File Attributes
7.11 Files DoubleSpace Cannot Compress
7.12 Microsoft Defragmenter runs out of memory while you are
compressing a drive.
7.13 DoubleSpace and PC-Vault
7.14 DoubleSpace displayed the "Drive X is too fragmented to resize,"
you followed the message's instructions, and they didn't work.
7.15 Running DoubleSpace on a Windows NT Flexboot System
7.16 Maximum size of a compressed drive
7.17 DoubleSpace displays the message "A CVF is damaged
7.18 DoubleSpace finishes installation, but you cannot access your
Hardcard.
1. NOTES ON SETUP
================
1.1 You deleted files from the directory that Setup needs
to install the optional programs.
---------------------------------------------------------
If you typed SETUP /E at the command prompt, Setup displayed
the "Setup did not find the files it needs in the directory
specified" message, and you think you deleted the files from
your hard disk, carry out the following procedure.
1. Reinstall MS-DOS 6.
Follow the instructions on your screen. When Setup displays
the "This version of MS-DOS 6 is designed for computers that
do not yet have an operating system" message, choose to
continue Setup.
2. After Setup is finished, insert Setup Disk 1 in drive A,
and type A:SETUP /E at the command prompt.
1.2 You need to install MS-DOS manually.
----------------------------------------
If you need to install MS-DOS manually, carry out the following procedure:
1. Insert Setup Disk 1 in drive, and restart your computer.
2. After the first screen appears, quit Setup by pressing F3 twice.
3. Transfer your system files to your hard disk by typing SYS A: C:
at the command prompt.
4. Create a directory on your hard disk that will contain your MS-DOS 6
files.
5. Copy all the decompressed files (files without an underscore in
their extension) on Setup Disk 1 to your MS-DOS directory.
6. Use the EXPAND command to decompress the rest of the files on your Setup
disks and copy them to your MS-DOS directory. You must expand the
compressed files one at a time, and specify a new extension for each
one. For example, to decompress the EGA.SY_ file and copy it to the
DOS directory, type the following at the command prompt:
A:EXPAND EGA.SYS C:\DOS\EGA.SYS
For more information about the EXPAND command and the location and
extensions of specific files, see the PACKING.LST file on the Setup
disks.
7. Create an AUTOEXEC.BAT and CONFIG.SYS file, and store them in the root
directory of drive C. For more information about creating these files,
see the chapter "Configuring Your System" in the MICROSOFT MS-DOS 6
USER'S GUIDE.
8. Restart your computer.
1.3 How to set up the Icelandic keyboard
----------------------------------------
To set up the Icelandic keyboard, carry out the following procedure:
1. Expand and copy the KEYBOARD.IC_, COUNTRY.IC_, and EGA.IC_ files
from your Setup disks to the directory that contains your MS-DOS files.
For the location of the files on the disks and for instructions on how
to use the EXPAND command, see the PACKING.LST file on Setup Disk 1.
When you use the EXPAND command, name the files KEYBOARD.SYS, COUNTRY.SYS,
and EGA.CPI
2. In your CONFIG.SYS file, add the two following lines. For example, if the
directory that contains your MS-DOS files is DOS, add the following
lines:
COUNTRY=354,861,C:\DOS\COUNTRY.SYS
DEVICEHIGH=C:\DOS\DISPLAY.SYS CON=(EGA,,1)
3. In your AUTOEXEC.BAT file, add the following line:
MODE CON CP PREPARE=((861) C:\DOS\EGA.CPI)
MODE CON CP SELECT=861
KEYB IS,,C:\DOS\KEYBOARD.SYS
4. If you also need support for codepage 850, then add the following
to your CONFIG.SYS file:
COUNTRY=354,861,C:\DOS\COUNTRY.SYS
DEVICE=C:\DOS\DISPLAY.SYS CON=(EGA,,2)
Add the following to your AUTOEXEC.BAT file:
NLSFUNC
MODE CON CP PREPARE=((861,850) C:\DOS\EGA.CPI)
MODE CON CP SELECT=861
KEYB IS,,C:\DOS\KEYBOARD.SYS
5. Restart your computer.
2. MEMMAKER AND MEMORY MANAGEMENT
=================================
2.1 Intel Expanded-Memory Driver (EMM.SYS)
------------------------------------------
If you use Intel's EMM.SYS driver with Aboveboard, use EMM.SYS
version 4.0 revision E if you an ISA system, or EMM.SYS version 4.0
revision D if you have an MCA or other system. Contact Intel for a
free upgrade.
2.2 Running MemMaker on a Computer with PC-NFS
----------------------------------------------
If you use PC-NFS network software, carry out the following procedure
before you run MemMaker:
1. Open your MEMMAKER.INF file by using any text editor. This file is
in the directory that contains your MS-DOS files.
2. Add the following line to the file:
*NET
3. Save the file, and then run MemMaker.
2.3 You have a Super VGA display and want to conserve memory.
-------------------------------------------------------------
If you have an 80386 computer with extended memory and a Super
VGA display, you can use the MONOUMB.368 file, in conjunction
with MemMaker, to conserve conventional memory for running programs.
To conserve memory if you have a Super VGA display:
1. Open your Windows SYSTEM.INI file, and find the [386Enh] section.
2. Add a DEVICE command for the MONOUMB.386 file, which is located
in your MS-DOS directory. For example, if your MS-DOS files are in
C:\DOS, add the following line to this section:
DEVICE=C:\DOS\MONOUMB.386
3. Save the file, and restart your computer.
4. After your computer starts, run MemMaker by typing MEMMAKER at the
command prompt.
5. Choose Custom Setup. On the Advanced Options screen, answer Yes to
the question "Use monochrome region (B000-B7FF) for running programs?"
Follow the instructions on your screen.
2.4 Additional MemMaker Troubleshooting Information
---------------------------------------------------
If you tried the troubleshooting procedures in the chapter "Making
More Memory Available," and you were referred to this file,
determine if one of the following conditions applies to your
computer:
o If your computer uses an Adaptec controller card, you might not be
able to use EMM386 unless you have the ADAPTEC.SYS device driver.
To obtain the device driver, contact Adaptec or your user-group
bulletin board (BBS) on the Association of PC User User Groups
(APCUG) network.
o If your computer uses an SCSI (small computer system interface)
hard disk or other device, or an EDSI (enhanced system device
interface), or an MCI (Micro Channel Architecture) device, you
might need to use double-buffering with EMM386.EXE. For more
information about adding double-buffering, restart your computer
with EMM386.EXE, and then type HELP DOUBLE-BUFFERING at the
command prompt.
2.5 Using MemMaker with IBM LAN
-------------------------------
Before you run MemMaker, you might need to make adjustments to the
parameters specified for your IBM LAN support driver, DXMC0MOD.SYS. In
your CONFIG.SYS file, make sure that the DEVICE command that loads
DXMC0MOD.SYS includes one of the following before you run MemMaker:
o The first three parameters, as in the following example:
DEVICE=C:\DXMC0MOD.SYS 400000000001,D800,1
o No parameters, as in the following example:
DEVICE=C:\DXMC0MOD.SYS
o Some parameters and enough commas to fill in the first three
parameters, as in the following example:
DEVICE=C:\DXMC0MOD.SYS 400000000001,,
2.6 MemMaker and Adaptec SCSI devices
-------------------------------------
MemMaker is compatible with Adaptec SCSI devices. However, if you use
the ASPI4DOS.SYS driver to support your SCSI device, MemMaker by default
will exclude this driver from the optimization process. If you don't
use the SCSI device as your startup or boot drive, you can include the
ASPI4DOS.SYS driver in the optimization process. To do so, remove the
*ASPI4DOS entry in the MEMMAKER.INF file, and then run MemMaker.
3. WINDOWS
==========
3.1 The "Cannot run Windows in standard mode" message appears.
--------------------------------------------------------------
If you have a DEVICE=EMM386.EXE command in your CONFIG.SYS file
that includes the RAM or NOEMS switch, you cannot run
Windows 3.0 in standard mode. Either remove the RAM or NOEMS
switch and add the AUTO or OFF switch, or run Windows in real or
enhanced mode.
NOTE Using EMM386 may reduce the amount of extended memory
available to Windows and cause Windows to start in
standard mode. To prevent this, reduce the amount of
extended memory that other device drivers use. For example,
if you are using SMARTDrive, try setting the MinCacheSize
parameter to 0.
4. HARDWARE COMPATIBILITY WITH MS-DOS
=====================================
4.1 Hardcard
------------
To use DoubleSpace on a system that uses its Hardcard drive as its
startup drive, see section 7.9. For additional Hardcard
information, see the following:
a) Hardcard II
If you can't use Plus Development Hardcard II or Hardcard
II XL when running EMM386.EXE, specify the exclude (x=)
switch to prevent EMM386 from conflicting with the card's
BIOS address.
To configure EMM386, run MemMaker.
b) Hardcard 40 or Passport
If you are using Hardcard 40 or a Passport removable
disk, and you have a DEVICE command in your CONFIG.SYS file
for PLUSDRV.SYS, disable or remove the DEVICE command.
Then run MS-DOS 6 Setup. After Setup is complete, reenable or
restore the DEVICE command for PLUSDRV.SYS. Make it the last line
in the file.
c) If you are unable to access your compressed drive after installing
DoubleSpace on your Hardcard, try the following:
1) Add a DBLSPACE /MOUNT command to your AUTOEXEC.BAT file to mount
the compressed volume file on the Hardcard every time you start
your computer.
2) Or, ensure that there is at least one device driver (for example,
ANSI.SYS) loaded in your CONFIG.SYS file AFTER the ATDOSXL.SYS
driver but BEFORE the DBLSPACE.SYS driver.
4.2 Inboard 386/PC
-------------------
The Inboard 386/PC is incompatible with MemMaker and the EMM386
memory manager that comes with MS-DOS 6.
4.3 Olivetti and AT&T Systems with CGA Video Boards
---------------------------------------------------
An Olivetti or AT&T system with a CGA video board might not scroll
correctly. Add the /S switch to the DEVICE=ANSI.SYS command
in your CONFIG.SYS file.
5. MICROSOFT PROGRAMS
=====================
5.1 Microsoft Anti-Virus
------------------------
Before cleaning a program file, make sure you have a backup copy of it.
If you clean a program file, and the program is corrupted, reinstall the
program. If Anti-Virus again detects a virus, there is a chance the
detection is in error; contact your software vendor to determine if an
updated version of the program is available.
5.2 Microsoft Backup
--------------------
The topics contained in this section are "Running Microsoft Backup
for MS-DOS under Windows," "Backup for Windows stops running at the end
of the compatibility test," and "Running Microsoft with TI4000 and
Gateway NOMAD computers."
Running Microsoft Backup for MS-DOS under Windows
-------------------------------------------------
You should not run Backup for MS-DOS while Windows is running. However,
if you do, and if your system is not configured correctly, Backup
might display the following symptoms:
o Backup appears to stop running--for example, the clock runs, but
there is no disk activity.
o Backup reports problems while testing the second floppy disk during
the compatibility test. For example, it might display a "Diskette
not properly seated" message or ask for Disk 1 repeatedly.
o Windows displays a message that the DMA buffer size needs to be
increased.
o Backup quits unexpectedly.
You can correctly configure your system by carrying out the following
procedure.
1. Open your SYSTEM.INI file, and add a DMABufferSize=32 line to the
[386Enh] section.
2. When you run Backup, make sure that you specify with the Settings
command from the Control menu that Backup run with the Exclusive
and Full Screen options.
Backup for Windows stops running at the end of the compatibility test
---------------------------------------------------------------------
If Backup for Windows stops running at the end of the
Compatibility Test, you might be loading an incompatible third-party
backup driver in your SYSTEM.INI file. Carry out the following
procedure.
NOTE This procedure disables your third-party backup program.
1. Open your SYSTEM.INI file, and locate the [386Enh] section.
2. Determine whether any of the following lines are included in this
section:
DEVICE=FASTBACK.386
DEVICE=VFD.386
DEVICE=CPBVXD.386
DEVICE=VIRWT.386
3. If you find any of these lines, add a semicolon (;) to the front
of the line.
4. Save the file, restart Windows, and run Backup for Windows again.
Running Microsoft Backup with TI4000 and Gateway NOMAD computers
----------------------------------------------------------------
To avoid a conflict between the Turbo feature and Microsoft Backup
for Windows or MS-DOS, add a /L0 switch to the DEVICE command in
your CONFIG.SYS that loads the BATTERY.PRO file. Or, before you
run Microsoft Backup, type SETPOWER /L0 at the command prompt.
5.3 Microsoft CD-ROM Extensions
-------------------------------
Use the MSCDEX.EXE file that comes with MS-DOS 6.
If you load MSCDEX.EXE with a batch file or program,
make sure it loads the MSCDEX.EXE file that comes with
MS-DOS 6. The MS-DOS Setup program copies this file
to the directory that contains your MS-DOS files.
5.4 Microsoft Defragmenter
--------------------------
If you carried out the procedures in "An MS-DOS program displays
an out-of-memory message" in the chapter "Diagnosing and Solving
Problems" in the MICROSOFT MS-DOS 6 USER'S GUIDE, and still receive
an out-of-memory message when you run the Defragmenter, there might
be too many files on your hard disk for the Defragmenter to organize.
For the Defragmenter to work correctly, you might need to
delete some files or move them to a floppy disk or a network drive.
6. THIRD-PARTY PROGRAMS
=======================
6.1 4DOS and NDOS
-----------------
4DOS (prior to 4.02) and NDOS (prior to Norton Utilities 7.0) are
compatible with MS-DOS 6. However, to use some of the new features
in MS-DOS 6 (such as MemMaker, the LOADHIGH /L switch, DIR compression
switches, and so on), contact JP Software for an update to 4DOS 4.02 or
later, or Symantec for an update to Norton Utilities 7.0 or later.
If you use multiple configurations, 4DOS or NDOS will not automatically
run your AUTOEXEC.BAT file unless you include a /P on the SHELL line in
your CONFIG.SYS file.
To use MS-DOS 6 Help instead of 4DOS or NDOS Help, start it by using
COMMAND /C HELP, or define a 4DOS or NDOS alias to run HELP.COM from
your MS-DOS 6 directory.
6.2 Above Board 286 and Above Board Plus Installation
Programs
-----------------------------------------------------
Do not use an Above Board installation program dated May 1989
or earlier until you disable programs that use extended memory,
such as SMARTDrive or RAMDrive. You might lose data if you leave
these programs enabled. After you have installed Above Board,
you can reenable these programs.
6.3 After Dark for DOS (AD-DOS)
-------------------------------
If you run After Dark for DOS (AD-DOS) at the same time you
run programs that use DPMI, you might have problems with
MS-DOS--for example, your computer might stop running or you
might receive "packed-file corrupt" messages. Examples of programs
that use DPMI are Microsoft MASM61, C7, and FoxPro25.
6.4 CodeView
-----------
CAUTION Using versions 3.0 to 3.13 of the CodeView CV.EXE
file may cause data loss if your system has an 80386 memory
manager (such as EMM386.EXE) and device drivers or programs
that use extended memory. To determine which version you
have, type CV.EXE at the command prompt.
6.5 Colorado Tape Backup
------------------------
If you receive a message that you have two versions of the
VFINTD.386 file loaded, you probably need to edit your
SYSTEM.INI file. To do so, carry out the following procedure:
1. Open your SYSTEM.INI file and locate the [386Enh] section.
You should see two lines similar to the following:
DEVICE=C:\TAPE\CMSDTAPE.386
DEVICE=C:\DOS\VFINTD.386
2. If you plan to use your Colorado Tape Backup program, add a semi-
colon (;) before the DEVICE command for the VFINTD.386 file. If you
plan to use Microsoft Backup, add a semi-colon before the DEVICE
command for the CMSDTAPE.386 file.
3. Save the file, and restart Windows.
6.6 Fastback Plus
-----------------
If you have a version of Fifth Generation Systems Fastback Pluse earlier
than 3.0, use the LOADFIX command before running Fastback Plus or the
Fastback Plus installation program to ensure that you don't lose data. To
do so, type the following at the command prompt:
LOADFIX FB.EXE
or
LOADFIX FBINSTAL.EXE
6.7 Norton Desktop for Windows 2.0
----------------------------------
Setup adds a second Tools menu which contains Backup and
Antivirus commands (if you installed these Windows programs),
as well as a DoubleSpace Info command.
6.8 Norton Utilities
--------------------
The "Clear Space" option of Norton SpeedDisk (prior to version 7.0)
is incompatible with DoubleSpace drives. For an updated version of
Norton SpeedDisk, contact your software vendor.
Do not use the WipeInfo utility on DoubleSpace drives. It can cause
lost clusters. If you have already used this option, use the
DBLSPACE /CHKDSK /F command to fix the lost clusters.
6.9 PC Tools
-------------
As reported by DoubleSpace CHKDSK, the DISKFIX /SCAN option
in PC Tools can cause lost clusters on DoubleSpace drives. If you
have already used this option, use the DBLSPACE /CHKDSK /F command
to fix the lost clusters.
The FORMAT command of PC Tools version 7.1 conflicts with
MS-DOS 6. Use the FORMAT command that comes with MS-DOS 6.
The COMPRESS command of PC Tools versions 6.0 and 5.5
is incompatible with DoubleSpace.
6.10 QEMM-386 (6.02 or earlier)
-------------------------------
Quarterdeck's QEMM memory manager is compatible with MS-DOS 6.
Quarterdeck has a Technical Note #166, MSDOS6.TEC, which discusses
how to get the most out of running their products with MS-DOS 6. This
technote can be obtained from their BBS, Compuserve (GO QUARTERDECK,
Library 2), BIX (JOIN DESQVIEW), and their Q/FAX automated fax-back
service.
7. DOUBLESPACE
==============
7.1 Converting Your Disk-Compression Software to DoubleSpace
-------------------------------------------------------------
To convert your disk-compression software, carry out the
following procedure.
NOTE If your computer uses XtraDrive disk compression, use its
uninstallation program to remove the compression, and then
install DoubleSpace.
1. Install MS-DOS 6 if you haven't already done so.
2. Use Microsoft Backup for MS-DOS to back up the files on your
hard disk. If you didn't install Backup for MS-DOS during Setup,
see the chapter "Getting Started" in the MICROSOFT MS-DOS 6 USER'S
GUIDE for instructions on installing it.
3. If your Setup disks are compatible with drive A, insert
Setup Disk 1 in drive A, and restart your computer. After
Setup displays the first screen, quit Setup by pressing F3 twice.
If your Setup disks are not compatible with drive A,
create a startup floppy disk for drive A. To do this, insert
Setup Disk 1 in drive B, and a blank floppy disk in drive A.
Then type B:SETUP /F at the command prompt.
When prompted, choose to install MS-DOS on the floppy disk
in drive A. After Setup is finished, leave the disk in drive A,
and restart your computer.
4. Use the FORMAT command to format the drive that contains the
file that contains all of your compressed files. If you don't know
where this file is located, see your disk-compression documentation.
If you are reformatting drive C, include the /S switch to transfer
system files to it.
5. If you formatted drive C, make sure Setup Disk 1 is in drive A
or B, and type A:SETUP or B:SETUP at the command prompt.
Follow the instructions on your screen.
6. After Setup is complete, install DoubleSpace by typing DBLSPACE
at the command prompt. Follow the instructions on your screen.
7. Use Backup for MS-DOS to restore the files you backed up.
NOTE When you run Microsoft Backup, you will have to configure it
again. Also, you will need to retrieve the catalog file from your
backup floppy disks. To do so, choose the Catalog button in the
Restore dialog box.
7.2 DoubleSpace Setup indicates that your computer is running an
incompatible disk-caching program.
----------------------------------------------------------------
If DoubleSpace Setup displays a message indicating your computer
is running an incompatible disk-caching program, open your CONFIG.SYS
or AUTOEXEC.BAT file, and delete the DEVICE command that loads your
disk-caching program. In your AUTOEXEC.BAT file, add a line for the MS-DOS
6 SMARTDRV program. For example, if your MS-DOS files are in a directory
named DOS, add the following line:
C:\DOS\SMARTDRV.EXE
Quit your text editor, and restart your computer. Run DoubleSpace again.
7.3 Your compressed drive runs out of disk space.
-------------------------------------------------
If your compressed drive runs out of free disk space, you can
use the following techniques to free some space on the drive:
o Specify a higher estimated compression ratio for that drive.
o Enlarge that drive.
o Carry out the DBLSPACE /DEFRAG /F and DBLSPACE /DEFRAG commands
on that drive.
The rest of this section explains each technique.
Specifying a Higher Estimated Compression Ratio
-----------------------------------------------
If a compressed drive's estimated compression ratio is too small,
MS-DOS might report that there is no more free space on that drive,
when some space is in fact available. (Raising the estimated compression
ratio is most effective if the files you are trying to store are highly
compressible. It will have no effect if the drive really is out of space.)
To specify a larger estimated compression ratio:
1. Start the DoubleSpace program by typing DBLSPACE at the command
prompt.
2. Select the compressed drive you want to change, and then choose
the Change Ratio command from the Drive menu.
The Change Compression Ratio dialog box appears.
3. Specify a higher compression ratio, and then choose OK. For more
information, choose the Help button.
You can also change the estimated compression ratio from the command prompt.
For more information, type HELP DBLSPACE /RATIO at the command prompt.
Enlarging a Compressed Drive
----------------------------
You can enlarge a compressed drive to make more space available on it.
Enlarging a compressed drive uses free space on the uncompressed (host)
drive.
To enlarge the compressed drive:
1. Start the DoubleSpace program by typing DBLSPACE at the command prompt.
2. Select the compressed drive you want to enlarge, and then choose
the Change Size command from the Drive menu.
The Change Size dialog box appears. The New Free Space line shows how
much free space the compressed and uncompressed drives will have if you
choose OK.
3. Specify a smaller number for New Free Space on the uncompressed
drive. Notice that as you change this number, DoubleSpace adjusts
the New Free Space amount for the compressed drive. When the New Free
Space amount for both drives is what you want, choose OK.
DoubleSpace enlarges the compressed drive.
Carrying Out the DBLSPACE /DEFRAG /F and DBLSPACE /DEFRAG Commands
on your Compressed Drive
------------------------------------------------------------------
You can sometimes free additional space on a compressed drive by
having DoubleSpace defragment that drive twice, once with and once
without the /F switch.
NOTE You might want to carry out the following procedure overnight, since
defragmenting a large or badly fragmented drive can take a long time.
(To carry out the entire procedure overnight, create a batch file that
contains both the commands in the procedure.)
To free space by defragmenting the drive twice:
1. Make the compressed drive your current drive.
2. Type DBLSPACE /DEFRAG /F at the command prompt.
DoubleSpace defragments the drive and fixes any errors it finds.
3. When DoubleSpace finishes, type DBLSPACE /DEFRAG at the command prompt.
DoubleSpace consolidates the free space on the drive so there is as
much free space as possible.
7.4 Your uncompressed drive runs out of disk space
--------------------------------------------------
If your uncompressed (host) drive runs out of free disk space, you
can enlarge it by reducing the size of any compressed drives that are
stored on that uncompressed drive. Of course, this will reduce the
amount of free space on the compressed drive(s).
To enlarge the uncompressed (host) drive:
1. Start the DoubleSpace program by typing DBLSPACE at the command prompt.
2. Select the compressed drive whose size you want to reduce, and then
choose the Change Size command from the Drive menu. (Select
a compressed drive that is stored on the uncompressed drive that's
out of space. To find out which compressed drives are stored
on that uncompressed drive, type DBLSPACE /LIST at the command prompt.)
The Change Size dialog box appears. The New Free Space line shows
how much free space the compressed and uncompressed drives will have
if you choose OK.
3. Specify a larger number for the New Free Space on the uncompressed
drive. Notice that as you change this number, DoubleSpace adjusts
the New Free Space amount for the compressed drive. When the New Free
Space amount for both drives is what you want, choose OK.
DoubleSpace reduces the size of the compressed drive, which makes
more free space available on the corresponding uncompressed drive.
7.5 DoubleSpace did not compress all of your files because
the drive ran out of disk space.
----------------------------------------------------------
If DoubleSpace indicates that it could not compress some
of your files because there was not enough disk space, carry
out the following procedure.
1. To determine which drive is your uncompressed drive, type
DBLSPACE /LIST at the command prompt.
2. Using Microsoft Backup, back up to floppy disks the files
on the uncompressed drive that were not compressed.
3. Delete the files on the uncompressed drive that were not compressed.
4. Type DBLSPACE at the command prompt.
5. From the Drive menu, choose Change Size.
6. To increase the size of your compressed drive, decrease the size
of your uncompressed drive, and choose OK.
7. From the Drive menu, choose Exit, and use Backup to restore
the files you backed up to your compressed drive. If you run out of
space again, repeat steps 5 through 7 until the compressed drive
is large enough.
7.6 Removing DoubleSpace from your computer
-------------------------------------------
There is no method for automatically removing DoubleSpace. There are
two ways to remove it manually:
* Back up the files on all your compressed drives, remove
DoubleSpace, and then restore the backed-up files onto
your uncompressed drive. (Note that all the files currently
on your compressed drive(s) might not fit on your hard disk
after you remove DoubleSpace.)
* Move as many files as possible from your compressed drive
to your uncompressed drive, reduce the size of your
compressed drive to free space on the uncompressed drive,
and keep moving files and shrinking the compressed drive until
no more files remain on the compressed drive. Then, remove
DoubleSpace.
NOTE: The drive letter of your uncompressed drive may change after you
remove DoubleSpace. If it does, any files or programs configured
for use on the uncompressed drive (for example, your Windows permanent
swap file) will need to be reconfigured.
The procedures in this section explain each method of removing DoubleSpace.
To remove DoubleSpace by using the back-up-and-restore method:
1. Delete any unnecessary files from your compressed drives.
2. Back up the files on all compressed drives. If your backup
program is located on a compressed drive, make sure you copy
the backup program files to another uncompressed drive or to a
floppy disk.
If you are using Microsoft Backup for MS-DOS, the program files
you need to copy are the following:
MSBACKUP.EXE MSBACKUP.OVL MSBACKUP.INI MSBACKDB.OVL
MSBACKDR.OVL MSBACKFB.OVL MSBACKFR.OVL MSBCONFG.OVL
DEFAULT.SET MSBACKUP.LOG MSBACKUP.RST
3. To determine which drive is your uncompressed drive, type
DBLSPACE /LIST at the command prompt. The uncompressed drive
is listed under the CVF Filename column. For example, if
H:\DBLSPACE.000 is the CVF Filename associated with drive C,
drive H is the uncompressed drive.
4. If you are removing DoubleSpace from your startup drive, copy the
COMMAND.COM file from your compressed drive to the root directory of
your uncompressed drive.
5. Make your uncompressed drive the current drive. For example,
if drive H is your uncompressed drive, type H: at the command prompt.
To change to the root directory, type CD\ at the command prompt. If
you want to delete all of your DoubleSpace drives, type the following
at the command prompt:
DELTREE DBLSPACE.*
If you want to delete just one of your DoubleSpace drives, use
the DELTREE command to delete the CVF for the drive. (The
DBLSPACE /LIST command also shows the CVF names for your drives.)
For example, if the CVF is DBLSPACE.000, type the following at
the command prompt:
DELTREE DBLSPACE.000
6. Restart your computer.
7. Restore your backed-up files. If your Backup program files are on a
floppy disk, copy them to the hard disk first. Then run the Backup
program from your hard disk.
NOTE You might need to retrieve your catalog file from your backup
floppy disks. To do so, choose the Catalog button in the Restore dialog
box.
To remove DoubleSpace by using the move-and-resize method:
1. Delete any unnecessary files from your compressed drives.
2. To determine which drive is your uncompressed (host) drive, type
DBLSPACE /LIST at the command prompt. The uncompressed drive
is listed under the CVF Filename column. For example, if
H:\DBLSPACE.000 is the CVF Filename associated with drive C,
drive H is the uncompressed drive.
3. Delete any unnecessary files from the uncompressed drive, including
your Windows permanent swap file (if any).
4. Change to your compressed drive, and then type DLBSPACE /SIZE at the
command prompt. DoubleSpace will reduce the drive's size as much as
possible, which will free some space on the uncompressed drive. (If
you have more than one compressed drive, carry out this step for each
one.)
If DoubleSpace cannot reduce a compressed drive's size because the
drive is too fragmented, run Microsoft Defragmenter by typing DEFRAG
at the command prompt. When Defragmenter completes, type
DBLSPACE /SIZE at the command prompt.
5. Use the MOVE command to move files from the compressed drive to the
uncompressed drive until only .5 MB of free space remains on the
uncompressed drive.
Repeat steps 4 and 5 until your compressed drives do not contain any
files you want to keep.
6. If you are removing DoubleSpace from your startup drive, copy the
COMMAND.COM file from your compressed drive to the root directory
of your uncompressed drive.
7. Make your uncompressed drive the current drive. For example,
if drive H is your uncompressed drive, type H: at the command prompt.
To change to the root directory, type CD\ at the command prompt. If
you want to delete all of your DoubleSpace drives, type the following
at the command prompt:
DELTREE DBLSPACE.*
If you want to delete just one of your DoubleSpace drives, use
the DELTREE command to delete the CVF for the drive. (The
DBLSPACE /LIST command also shows the CVF names for your drives.)
For example, if the CVF is DBLSPACE.000, type the following at
the command prompt:
DELTREE DBLSPACE.000
8. Remove all references to DBLSPACE from your CONFIG.SYS and AUTOEXEC.BAT
files.
9. Restart your computer.
7.7 Windows displays the message "The permanent swap file is corrupt."
----------------------------------------------------------------------
If you use a Windows permanent swap file, it must be located on an
uncompressed drive. If your permanent swap file is on a compressed
drive, Windows displays the message "The permanent swap file is corrupt"
when it starts.
When you install DoubleSpace, the DoubleSpace Setup program checks for
the existence of a Windows permanent swap file. If it finds one,
DoubleSpace Setup moves the swap file to your uncompressed drive.
However, if you install Windows after installing DoubleSpace, or if you use
Control Panel to change the location of your permanent swap file, your
swap file might end up on a compressed drive. (When you specify a drive
for your permanent swap file, Windows allows you to choose a compressed
drive.)
To move your permanent swap file to an uncompressed drive:
1. Start Windows.
2. At the "Permanent swap file is corrupt" screen, type Y in response
to the question "Do you want to delete this swap file?", and
then press ENTER.
3. Open Control Panel, and then double-click the 386 Enhanced icon.
4. Choose the Virtual Memory button. Windows displays a dialog box stating
that a corrupt swap file was found and asks if you want to set the
file's length to zero.
5. Choose the Yes button. Windows displays another Virtual Memory dialog box.
6. Choose the Change button. Windows displays swap-file settings.
7. In the Drive list box, select a drive that is not compressed. In the
Type list box, select "Permanent."
If your uncompressed drive does not have enough free space to create a
permanent swap file, create a temporary swap file on either your
compressed or uncompressed drives. (For information about freeing
space on your uncompressed drive, see section 7.4.)
When you have finished specifying swap-file settings, choose OK twice,
and follow the instructions on your screen.
7.8 EXTDISK.SYS displays a warning about drive letters.
-------------------------------------------------------
If you are using DoubleSpace on a Compaq computer, and your CONFIG.SYS file
loads the EXTDISK.SYS device driver, EXTDISK.SYS displays the following
message when it loads:
WARNING: EXTDISK.SYS is not the first device driver to assign drive
letters. Physical hard drive letters will not be contiguous.
The EXTDISK.SYS driver still works properly. It displays this message
because it expects to be the first module to assign drive letters,
but because DBLSPACE.BIN loads before the CONFIG.SYS file and assigns
some drive letters, EXTDISK.SYS is no longer first. (EXTDISK.SYS
displays the message regardless of when the DBLSPACE.SYS device
driver is loaded in the CONFIG.SYS file.)
7.9 You need a special device driver to use your startup drive
--------------------------------------------------------------
If your startup hard disk drive requires a device driver in your CONFIG.SYS
file, do not compress that drive. If you do, your computer will not
start properly, since DoubleSpace will be unable to access your startup
drive. (This is because MS-DOS loads DBLSPACE.BIN, the portion of MS-DOS
that accesses compressed drives, before starting any of the device drivers
in your CONFIG.SYS file.)
To install DoubleSpace on a computer with a startup drive that requires a
special device driver, use DoubleSpace Setup to compress a drive other than
your startup drive, or use DoubleSpace Setup to create a new compressed
drive using free space on any existing drive.
7.10 Defragmenting Uncompressed Drives After Changing File Attributes
---------------------------------------------------------------------
You can safely defragment both your compressed or uncompressed drives,
using the Microsoft Defragmenter or another defragmentation program, as long
as you do not change the attributes of your compressed volume files.
If you change the attributes of a compressed volume file, and then
defragment that uncompressed drive, you might lose data.
7.11 Files DoubleSpace Cannot Compress
--------------------------------------
Some files (such as .ZIP files) are already compressed. DoubleSpace
might not be able to compress such files any further.
Encrypted data files, such as the Microsoft Mail 3.0 .MMF file, are
not compressible and will be stored in uncompressed form, even if
you store such files on a compressed drive.
You might want to store uncompressible files on an uncompressed drive
rather than on a compressed drive. Doing so can sometimes improve
your system's speed.
7.12 Microsoft Defragmenter runs out of memory while you are compressing
a drive.
------------------------------------------------------------------------
If the Defragmenter runs out of memory while you are compressing a drive,
quit DoubleSpace, and then carry out the procedures in "An MS-DOS-based
program displays an out-of-memory message" in the chapter "Diagnosing
and Solving Problems" in the MICROSOFT MS-DOS 6 USER'S GUIDE.
If the Defragmenter still runs out of memory after you have tried
these procedures, there might be too many files on your hard disk
for the Defragmenter to organize. For the program to work correctly,
you might need to delete some files or move them to a floppy disk or a
network drive.
7.13 DoubleSpace and PC-Vault
-----------------------------
The PC-Vault and PC-Vault Plus Hard Disk Protection Systems from
Johnson Computer Systems are compatible with DoubleSpace, except
for the Maximum Floppy Boot Protection feature in versions prior
to 4.6. To avoid losing data, do not use Maximum Floppy Boot Protection
in versions earlier than 4.6 with DoubleSpace. If your version of PC-Vault
or PC-Vault Plus is earlier than 4.6, contact Johnson Computer Systems.
7.14 DoubleSpace displayed the "Drive X is too fragmented to resize,"
you followed the message's instructions, and they didn't work.
---------------------------------------------------------------------
If you followed the instructions, and you are still unable to resize
the drive, you might have system files that are preventing
Microsoft Defragmenter from reorganizing your files. Carry out the
following procedure:
1. Change to the drive that DoubleSpace identified in its message.
2. To find the system files, type DIR /S /A:S|MORE at the
command prompt.
3. For each filename that DIR displays, type ATTRIB -S FILENAME
at the command prompt to remove its system attribute.
4. Run DEFRAG /Q /H DRIVE: again.
5. For each file whose system attribute you removed, type
ATTRIB +S FILENAME at the command prompt to restore the attribute.
6. To change the size of your drive, run DoubleSpace again.
7.15 Running DoubleSpace on a Windows NT Flexboot System
--------------------------------------------------------
The BOOT.INI, BOOTSECT.DOS, NTLDR, and NTDETECT.COM files should not
be compressed. Add these files to the [SpecialFiles] section of the
DBLSPACE.INF before you run DoubleSpace. After DoubleSpace Setup
is finished, copy all the files and subdirectories in your Windows NT
directory on your compressed drive to a Windows NT directory on your
uncompressed drive.
7.16 Maximum size of a compressed drive
---------------------------------------
The maximum size that a DoubleSpace-compressed drive can be is
512 megabytes (MB). For example, if you have a disk drive that is
300 MB, the drive will not be larger than 512 MB after DoubleSpace
compresses it.
7.17 DoubleSpace displays the message "A CVF is damaged"
---------------------------------------------------------
If the message "A CVF is damaged" appears when you start your computer,
then DoubleSpace has detected problems with a compressed volume file (CVF).
The most common cause of this message is crosslinked files on the
compressed drive. DoubleSpace detects a crosslinked file if two files
or directories are recorded in the DoubleSpace file allocation table
as using the same disk space.
To fix this problem:
1. Change to the compressed drive and type DBLSPACE /CHKDSK at the command
prompt.
If DoubleSpace Chkdsk finds a crosslinked file, it reports the problem
and the name of the file.
2. To fix the cross-linked files, copy the specified files or directories
elsewhere and delete the original copies of those files. Some of the
information in these files may be lost.
7.18 DoubleSpace finishes installation, but you cannot access your Hardcard.
-----------------------------------------------------------------------------
See section 4.1, part C.
If this were a real program disk, then this text file might include information about such things as: Installing the program on certain brands of computers Adding updated system files Modifying the program for certain peripherals Tips about using the program efficiently Corrections to the printed manual Anything else the manufacturer wants to say
README.TXT
NOTES ON MS-DOS 6.21
====================
This version of MS-DOS does not support data compression. It differs
from MS-DOS 6.2 as follows:
* DoubleSpace is not included.
* ScanDisk will not run on compressed drives.
* The Backup programs do not compress data while backing up.
* You cannot use the Backup programs to restore backups made with
MS-DOS 6 or 6.2 Backup (unless you disabled the Compress Backup
Data option before backing up). To restore backups made with MS-DOS 6
or 6.2, use the backup programs that came with those versions of MS-DOS.
This file provides important information not included in the
MICROSOFT MS-DOS USER'S GUIDE or in MS-DOS Help.
This file is divided into the following major sections:
1. Setup
2. MemMaker, EMM386, and Memory Management
3. Windows
4. Hardware Compatibility with MS-DOS 6.21
5. Microsoft Programs
6. Third-Party Programs
If the subject you need information about doesn't appear in
this file, you might find it in one of the following text
files included with MS-DOS:
* OS2.TXT, which describes how to remove and save data on your
computer when you replace OS/2 with MS-DOS 6.21.
* NETWORKS.TXT, which describes how to update your network software
for use with MS-DOS 6.21.
For information about features new to MS-DOS 6.21, type HELP WHATSNEW
at the command prompt.
This file contains the following topics:
1. Setup
1.1 SpeedStor
1.2 Incompatible Hard Disk or Device Driver
1.3 AT&T 6300 Computer
1.4 Toshiba with a Hard RAM Disk
1.5 Tandy with ROM DOS
1.6 Setup displays the "Your computer uses a disk-compression
program that is incompatible with Setup" message.
1.7 You deleted files from the directory that Setup needs
to install the optional Windows programs.
1.8 Running Setup if Your Computer Uses Windows NT
1.9 Setup detects that your computer has a non-MS-DOS
partition or non-MS-DOS files, and your computer uses Windows NT.
1.10 Setup displays the "Your computer uses password protection"
screen.
1.11 Setup displays the "Your computer is using an incompatible
delete-protection program" screen.
1.12 Setup detects that your computer uses DR DOS.
1.13 Installing MS-DOS on a Drive Other Than C
1.14 Bypassing the Uninstall Disk and Using Default Setup Options
1.15 Installing MS-DOS 6.21 on a System with a CorelSCSI UNI_ASP.SYS Driver
1.16 Installing MS-DOS 6.21 if you have DrivePro or EZ-Drive
1.17 Additional Keyboard and Codepage Support
1.18 Switching Between Modes on Dual-Mode Keyboards
2. MemMaker, EMM386, and Memory Management
2.1 Intel Expanded-Memory Driver (EMM.SYS)
2.2 Running MemMaker on a Computer with PC-NFS
2.3 You have a Super VGA display and want to conserve memory.
2.4 Using MemMaker with IBM LAN
2.5 MemMaker and Adaptec SCSI devices
2.6 Running MemMaker on a computer with PC Tools RAMBoost
2.7 EMM386 detects an error in an application
2.8 MemMaker no longer aggressively scans upper memory by default
3. Windows
3.1 Your computer uses a Windows 3.0 permanent swap file.
3.2 Using compressed floppy disks with Windows File Manager
4. Hardware Compatibility with MS-DOS 6.21
4.1 Compaq EXTDISK.SYS Driver
4.2 Hardcard
4.3 Toshiba
5. Microsoft Programs
5.1 Microsoft Anti-Virus
5.2 Running Microsoft Backup for MS-DOS under Windows
5.3 Backup for Windows stops running at the end of the
compatibility test
5.4 Running Microsoft Backup with TI4000 and Gateway NOMAD computers
5.5 MS-DOS 6.21 Backup Cannot Restore 6 or 6.2 Backups
5.6 Microsoft Defragmenter
6. Third-party Programs
6.1 4DOS and NDOS
6.2 Above Board 286 and Above Board Plus Installation
Programs
6.3 CodeView
6.4 Colorado Tape Backup
6.5 Fastback Plus
6.6 Norton Desktop for Windows 2.0
6.7 PC Tools
1. SETUP
========
1.1 SpeedStor
-------------
If Setup referred you to this section and your computer has an OS/2
partition created by using the FDISKPM utility in OS/2 2.1, run
MS-DOS Setup by typing SETUP /U at the command prompt.
If Setup referred you to this section and you have neither OS/2
nor a SpeedStor partition on your computer, see the section "Setup
displays the Incompatible Hard Disk or Device Driver screen" in
the "Diagnosing and Solving Problems" chapter of the MS-DOS 6
User's Guide.
If you do have a SpeedStor partition on your computer, Setup
probably referred you to this section for one of the following
reasons:
* Setup could not find in your CONFIG.SYS file a command
for the device driver that supports your SpeedStor partition.
If this is the case, add the command line to your CONFIG.SYS
file, restart your computer, and run Setup. For more information
about adding the command line to your CONFIG.SYS file, see your
SpeedStor documentation.
* Your CONFIG.SYS file has a DEVICE=HARDRIVE.SYS line in it.
If this is the case, carry out the following procedure:
1. Use the EXPAND command to expand and copy the SSTOR.SYS
file to your hard disk. Make sure you copy the SSTOR.SYS
file to the same path as the HARDRIVE.SYS file.
See the PACKING.LST file on Setup Disk 1 for the location
of the SSTOR.SYS file on the Setup disks and for instructions
on how to expand and copy it to your hard disk.
2. Replace the DEVICE=HARDRIVE.SYS command with a DEVICE=SSTOR.SYS
command. For example, if the command that loaded the
HARDRIVE.SYS file was DEVICE=C:\SSTOR\HARDRIVE.SYS, you
would replace it with DEVICE=C:\SSTOR\SSTOR.SYS.
3. Restart your computer.
4. Make sure you can access your hard disk.
5. Run Setup.
1.2 Incompatible Hard Disk or Device Driver
-------------------------------------------
If Setup referred you to this section, and no other section in this
file is relevant to your system, you have a partition that is
incompatible with MS-DOS 6.21. You must delete the partition from your
hard disk. See "Using Fdisk to Configure Your Hard Disk" in the
chapter "Diagnosing and Solving Problems" in the MICROSOFT MS-DOS 6
USER'S GUIDE.
1.3 AT&T 6300 Computer
----------------------
If you use an AT&T 6300 computer and your ROM BIOS is version 1.21,
contact your vendor for a ROM BIOS upgrade. The ROM BIOS version
number is displayed when you start your computer.
1.4 Toshiba with a Hard RAM Disk
--------------------------------
These instructions apply to Toshiba models T1200, T1600,
T1200XE and T1000LE.
To use the hard RAM disk, carry out the following procedure
before you install MS-DOS 6.21:
1. Back up your hard RAM disk.
2. Using the Toshiba Setup program, delete the hard RAM
disk by allocating zero kilobytes (KB) to it. All data on
the hard RAM disk will be lost.
3. Restart your computer
4. Run MS-DOS 6.21 Setup.
5. After Setup is complete, run the Toshiba Setup program to reinstall
the hard RAM disk.
6. Run FDISK, change to drive 2, and create a primary DOS
partition. Quit FDISK.
7. Use the FORMAT command to format drive D.
1.5 Tandy with ROM DOS
----------------------
Contact your hardware manufacturer for information about
upgrading a Tandy computer with ROM DOS to MS-DOS 6.21. This
applies to the following models: 1000EX, 1000HX, 1000SL, 1000SL2,
1000TL, 1000TL2, 1000TL3, 1000RL, 1000RLX, 1000RL-HD, 1000RLX-HD,
1100FD, 2500XL, 2500XL2.
1.6 Setup displays the "Your computer uses a disk-compression
program that is incompatible with Setup" message.
--------------------------------------------------------------
If Setup indicated that your computer has an incompatible
disk-compression program, you must remove it manually before you can
install MS-DOS 6.21. Contact your disk-compression vendor for an
updated version of your software. In most cases, current versions of
disk-compression software are compatible with MS-DOS 6.21.
Alternatively, you can use the procedure below to remove your
current disk-compression software.
1. Back up all the files on your compressed drive. In step 3,
you will format your uncompressed drive, which destroys all the files
on your compressed and uncompressed drives.
2. If your Setup disks are compatible with drive A, insert
Setup Disk 1 in drive A, and restart your computer. After Setup
displays the first screen, quit Setup by pressing F3 twice.
If your Setup disks are not compatible with drive A,
create a startup floppy disk for drive A. To do this, insert
Setup Disk 1 in drive B, and a blank floppy disk in drive A. Then
type B:SETUP /F at the command prompt.
When prompted, choose to install MS-DOS on the floppy disk
in drive A. After Setup is finished, leave the disk in drive A,
and restart your computer.
3. At the command prompt, type FORMAT C: /S to reformat your startup
drive and transfer MS-DOS 6.21 system files to it.
4. Remove the disk from drive A, and restart your computer.
5. Insert Setup Disk 1 in drive A or B, and type A:SETUP or
B:SETUP at the command prompt.
6. After Setup is complete, restore the files you backed up. Do
not restore older versions of MS-DOS files.
1.7 You deleted files from the directory that Setup needs
to install the optional Windows programs.
---------------------------------------------------------
If you typed BUSETUP /E at the command prompt, the "Setup did
not find the files it needs in the directory specified" message
appeared, and you think you deleted the files from
your hard disk, insert Setup Disk 1 in drive A or B, and start
Setup by typing A:SETUP /E or B:SETUP /E at the command prompt.
1.8 Running Setup if Your Computer Uses Windows NT
--------------------------------------------------
If your computer has Windows NT installed, but does not have
MS-DOS installed on it, carry out Procedure 1. If your computer
has Windows NT and MS-DOS installed on it, carry out Procedure 2.
Procedure 1
1. Run Setup by inserting Setup Disk 1 in drive A and restarting
your computer. Complete Setup by following the instructions
on the screen. When Setup is complete, Windows NT will be
disabled.
If Windows NT was installed on a FAT partition, complete steps
2 and 3 of this procedure to reenable Windows NT so that you can
use both the Windows NT and MS-DOS operating systems.
If Windows NT was installed on a non-FAT partition, see section 1.9.
2. Insert your Windows NT Setup disk in drive A or drive B, and then
restart your computer.
3. When the Windows NT Setup screen appears, choose Repair, and then
insert your Windows NT Emergency Repair Disk (which you created when
you installed Windows NT) to repair the Windows NT system files.
Procedure 2
1. When you start your computer, choose MS-DOS as your operating
system.
2. Run Setup by inserting Setup Disk 1 in drive A or B, and typing
A:SETUP or B:SETUP at the command prompt.
1.9 Setup detects that your computer has a non-MS-DOS
partition or non-MS-DOS files, and your computer uses
Windows NT
----------------------------------------------------------
The procedure you use depends on whether you want to preserve
the partition and its files. Find the section below that describes
the configuration you want.
You Don't Want to Preserve the Partition or its Files
------------------------------------------------------
If you don't want to preserve the partition or its files, choose to
remove the partition or files if Setup prompts you to do so. If
Setup doesn't offer you that choice, remove the partition manually
after Setup is complete. For instructions on removing a non-MS-DOS
partition manually, see "Using Fdisk to Configure Your Hard Disk" in
the chapter "Diagnosing and Solving Problems" in the MICROSOFT MS-DOS
USER'S GUIDE.
You Don't Want to Preserve the Partition but Want to Save its Files
-------------------------------------------------------------------
If you want to save the data files, but don't want to preserve the
partition, back up the files, run Setup again, and then choose to
remove the partition or files if Setup prompts you to do so. If Setup
doesn't offer you this choice, remove the partition manually after
Setup is complete. For instructions on removing the partition
manually, see "Using Fdisk to Configure Your Hard Disk" in the
chapter "Diagnosing and Solving Problems" in the MICROSOFT MS-DOS 6
USER'S GUIDE.
You Want to Preserve the Partition and Its Files
------------------------------------------------
Carry out the following procedure.
NOTE If the non-MS-DOS partition takes up all the space on your hard
disk, you must reconfigure your hard disk. You can either let Setup do
it for you, as described in the preceding section, or reconfigure it
yourself manually. For instructions on reconfiguring your hard disk
manually, see your Windows NT documentation.
To install MS-DOS 6.21 and preserve your partition or files:
1. Run MS-DOS Setup.
2. When prompted, choose to continue Setup without removing the
partition or files.
3. After Setup is complete, insert your Windows NT Setup disk
in drive A or drive B, and then restart your computer.
4. When the Windows NT Setup screen appears, choose Repair, and then
insert your Windows NT Emergency Repair Disk (which you created when
you installed Windows NT) to repair the Windows NT system files.
1.10 Setup displays the "Your computer uses password protection"
screen.
----------------------------------------------------------------
See section 1.12.
1.11 Setup displays the "Your computer is using an incompatible
delete-protection program" screen.
---------------------------------------------------------------
See section 1.12.
1.12 Setup detects that your computer uses DR DOS.
--------------------------------------------------
If you have DR DOS installed on your computer, take the following
precautions before restarting Setup:
o If your system has any security features, including password protection,
disable them. For more information, see "Setup displays the 'Your
computer uses password protection' screen" in the chapter "Diagnosing
and Solving Problems" in the MICROSOFT MS-DOS USER'S GUIDE.
If you have protected any files or directories with a password,
remove the password protection, particularly if you have protected
your CONFIG.SYS or AUTOEXEC.BAT files, or your DR DOS directory.
o If you have DELWATCH installed on your computer, carry out
the procedure "Setup displays the 'Your computer is using an
incompatible delete-protection program' screen" in the chapter
"Diagnosing and Solving Problems" in the MICROSOFT MS-DOS
USER'S GUIDE.
o If your CONFIG.SYS or AUTOEXEC.BAT files use any conditional commands--
such as the "?" or GOTO commands--remove them and adjust the order of
commands in your startup files accordingly.
o If your CONFIG.SYS file uses the CHAIN command, remove it and
adjust the order of commands in the file accordingly.
o If your computer uses disk compression, but drive C is not compressed,
run Setup as described in the chapter "Getting Started" in the
MICROSOFT MS-DOS USER'S GUIDE. When Setup displays the "Your
CONFIG.SYS file contains commands that are not valid MS-DOS commands"
message, choose the "Modify original files" option.
If drive C is compressed, carry out the following procedure:
1. Determine which drive is your original uncompressed drive. For more
information, see your DR DOS documentation.
2. Make backup copies of the CONFIG.SYS and AUTOEXEC.BAT files on your
compressed drive, and the DCONFIG.SYS file on your uncompressed drive.
3. Combine the two configuration files. For example, if drive D is your
uncompressed drive, type the following at the command prompt:
COPY D:\DCONFIG.SYS+C:\CONFIG.SYS D:\CONFIG.SYS
4. Copy the combined CONFIG.SYS file to drive C. For example, if drive
D is your uncompressed drive, type the following at the command
prompt:
COPY D:\CONFIG.SYS C:\CONFIG.SYS
5. Copy your AUTOEXEC.BAT to your uncompressed drive. For example, if
drive D is your uncompressed drive, type the following at the
command prompt:
COPY C:\AUTOEXEC.BAT D:\AUTOEXEC.BAT
6. Run MS-DOS 6.21 Setup.
7. When Setup displays the "Your CONFIG.SYS file contains commands
that are not valid MS-DOS commands" message, choose the "Modify
original files" option.
When Setup displays the "Because you are currently using the
DR DOS operating system" message, choose Continue.
8. After Setup is complete, MS-DOS displays an "Unrecognized command"
message on your screen for each command in your AUTOEXEC.BAT and
CONFIG.SYS files that is not a valid MS-DOS command. Remove these
commands from your CONFIG.SYS and AUTOEXEC.BAT files.
9. Add the DEVICE=HIMEM.SYS command to the beginning of your
CONFIG.SYS file, and the restart your computer.
1.13 Installing MS-DOS on a Drive Other Than C
----------------------------------------------
As described in the following procedure, you can install MS-DOS
on a drive other than C by using the /M switch to copy the system
files to your startup drive and then using the /Q switch to copy your
MS-DOS files to a different drive.
NOTE This procedure is designed for advanced users. If your computer
uses disk-compression software, modify the procedure as appropriate.
NOTE If your computer uses disk-partitioning software, such as Disk
Manager, SpeedStor, Priam, or Everex, do not carry out the procedure until
you have carried out steps 1 through 3 of "You need to install MS-DOS
manually" in the chapter "Diagnosing and Solving Problems" in the
MICROSOFT MS-DOS USER'S GUIDE. If your software uses a driver to
enable the drive on which you want to install MS-DOS, make sure you create
a startup disk with the driver in a CONFIG.SYS or AUTOEXEC.BAT file.
After you have carried out these steps, skip to step 3 of the following
procedure.
1. Run Setup by inserting Setup Disk 1 in drive A or B, and
typing A:SETUP /M or B:SETUP /M at the command prompt.
NOTE Your CONFIG.SYS and AUTOEXEC.BAT files were saved as CONFIG.NEW
and AUTOEXEC.NEW.
2. Run Setup by inserting Setup Disk 1 in drive A or B, and typing
A:SETUP /Q or B:SETUP /Q at the command prompt. Follow the
instructions on your screen.
3. When Setup displays the system settings screen, choose the MS-DOS
Path option. Type the drive and directory where you want
to install MS-DOS, and press ENTER. Continue Setup.
4. After Setup is complete, open your CONFIG.NEW and AUTOEXEC.NEW files
and ensure that their commands specify the correct path. Save the files
as CONFIG.SYS and AUTOEXEC.BAT. Then restart your computer.
1.14 Bypassing the Uninstall Disk and Using Default Setup Options
-----------------------------------------------------------------
To keep Setup from creating an Uninstall Disk, use the /G switch
with the Setup command.
To bypass the Uninstall disk and use default Setup options
instead of choosing them yourself, use both the /H and /G switches
with the Setup command.
WARNING The primary purpose of the Uninstall disk is to safeguard
your files during and after Setup. If Setup doesn't create
an Uninstall disk, you will not be able to restore your previous
version of DOS. If Setup should render your hard disk inaccessible,
you will not be able to use the Uninstall disk to make it accessible
again.
NOTE If you have a version of MS-DOS earlier than 5.0, and you use
the /G switch or the /H and /G switches together, Setup will not
prompt you if you need to update your network files.
1.15 Installing MS-DOS 6.21 on a System with a CorelSCSI UNI_ASP.SYS Driver
--------------------------------------------------------------------------
If your system uses the CorelSCSI UNI_ASP.SYS device driver for optical
drives, and Setup stops running when you try to install MS-DOS 6,
delete the DEVICE command in your CONFIG.SYS that loads the Corel
UNI_ASP.SYS driver. Then run Setup again. After Setup is complete,
reinstall the Corel UNI_ASP.SYS driver as you originally installed it.
If you continue to have problems, contact Corel Customer Service.
1.16 Installing MS-DOS 6.21 if you have DrivePro or EZ-Drive
------------------------------------------------------------
If your hard disk was set up using Micro House DrivePro(TM) or
EZ-Drive(TM), you must carry out one of the following procedures
before you can install MS-DOS 6.21.
o If your DrivePro or EZ-Drive floppy disks include the DOS6INST.EXE
file, run the DOS6INST program and follow the instructions on the
screen. (This program is also available on the Micro House BBS at
(303) 443-9957.)
o If you don't have the DOS6INST program, run the MHDRIVE program (if
you have DrivePro) or the EZ-RESET program (if you have EZ-Drive).
Press ENTER to accept the default answers until the program prompts
you to insert MS-DOS Setup Disk 1. Insert the disk and then press
ENTER. At the second Setup screen, choose "Continue Setup and
replace your current version of DOS." (Note that this procedure
will replace your current CONFIG.SYS and AUTOEXEC.BAT files with
basic versions of these files.)
For additional information, or if you encounter problems, contact
Micro House Technical Support.
1.17 Additional Keyboard and Codepage Support
----------------------------------------------
MS-DOS 6.21 includes the KEYBRD2.SYS and EGA2.CPI files, which
offer additional keyboards and codepages. You use these files just
as you would the KEYBOARD.SYS and EGA.CPI files. MS-DOS also
includes new country settings in COUNTRY.SYS.
The KEYBRD2.SYS file is essentially similar to KEYBOARD.SYS.
The differences between KEYBOARD.SYS and KEYBRD2.SYS are:
o KEYBRD2.SYS contains support for the following keyboards, which
are not supported by KEYBOARD.SYS:
Country/Language Keyboard layout Keyboard ID
---------------- --------------- -----------
Canada (standard CAN/CSA-Z keyboard) cf 243.200-92
Brazil (secondary standard keyboard) br 274, 275
Greece gk 319
Iceland is 161
Romania ro 333
Turkish tr 440, 179
o The KEYBRD2.SYS file does not include support for the following
keyboards supported by KEYBOARD.SYS:
Switzerland (German)
Switzerland (French)
Japan
o The KEYBRD2.SYS file provides access to a few keyboards by keyboard
layout (two-letter code) only. KEYBOARD.SYS provides access to these
keyboards by either keyboard layout or keyboard ID. The affected
keyboards are:
Poland
Czechoslovakia (Czech)
Czechoslovakia (Slovak)
Yugoslavia
Hungary
o KEYBRD2.SYS contains changes to the German keyboard that are
not in KEYBOARD.SYS. In the German keyboard, the SHIFT lock
behavior of the top row of the keyboard now remains unaffected,
and is now functionally the same as the US keyboard (that is,
"typewriter mode" has been removed).
The EGA2.CPI file is similar to the EGA.CPI file, except that the two
files contain different code pages. EGA2.CPI contains the following:
850 - Multilingual (in both EGA2.CPI and EGA.CPI)
852 - Eastern European (in both EGA2.CPI and EGA.CPI)
857 - Turkish
861 - Icelandic
869, 737 - Greek
MS-DOS 6.21 includes new country settings in COUNTRY.SYS that use the
new keyboards and code pages. COUNTRY.SYS contains the following
countries with their supported code pages:
Country or language Country Character sets
code
------------------------------------------------------
Greece 030 869, 737
Iceland 354 861, 850
Romania 040 852, 850
Turkish 090 857, 850
You use the KEYBRD2.SYS and EGA2.CPI files just as you would
KEYBOARD.SYS and EGA.CPI. These files can be used in any combination.
For example, to use the new Icelandic settings, carry out the following
steps:
1. Add the following commands to your AUTOEXEC.BAT file:
REM ICELAND SETTINGS
MODE CON CP PREPARE=((861) C:\DOS\EGA2.CPI)
MODE CON CP SELECT=861
KEYB IS,,C:\DOS\KEYBRD2.SYS
2. If you also need support for codepage 850 (Multilingual), add
the following commands to your CONFIG.SYS file:
REM ICELAND SETTINGS
COUNTRY=354,861,C:\DOS\COUNTRY.SYS
DEVICE=C:\DOS\DISPLAY.SYS CON=(,,2)
Add the following commands to your AUTOEXEC.BAT file:
REM ICELAND SETTINGS
NLSFUNC
MODE CON CP PREPARE=((861,850) C:\DOS\EGA2.CPI)
MODE CON CP SELECT=861
KEYB IS,,C:\DOS\KEYBRD2.SYS
3. Restart your computer.
1.18 Switching Between Modes on Dual-Mode Keyboards
----------------------------------------------------
MS-DOS 6.21 includes dual-mode keyboard support for Greek and French
Canadian keyboards. These keyboards allow you to easily switch between
two different keyboard modes. When your computer starts with the
Greek or French Canadian keyboard, the primary mode is active.
To switch modes, press the appropriate key combination (listed below).
The key combinations for the Greek keyboard are as follows:
Mode description Key combination
---------------- ---------------
Primary mode Latin ALT+RIGHT SHIFT
Secondary mode Greek ALT+LEFT SHIFT
The key combinations for the French Canadian keyboard are as follows:
Mode description Key combination
---------------- ---------------
Primary mode Latin CTRL+RIGHT SHIFT
Secondary mode Latin II CTRL+LEFT SHIFT
2. MEMMAKER AND MEMORY MANAGEMENT
=================================
2.1 Intel Expanded-Memory Driver (EMM.SYS)
------------------------------------------
If you use Intel's EMM.SYS driver with Aboveboard, use EMM.SYS
version 4.0 revision E if you an ISA system, or EMM.SYS version 4.0
revision D if you have an MCA or other system. Contact Intel for a
free upgrade.
2.2 Running MemMaker on a Computer with PC-NFS
----------------------------------------------
If you use PC-NFS network software, carry out the following procedure
before you run MemMaker:
1. Open your MEMMAKER.INF file by using any text editor. This file is
in the directory that contains your MS-DOS files.
2. Add the following line to the file:
*NET
3. Save the file, and then run MemMaker.
2.3 You have a Super VGA display and want to conserve memory.
-------------------------------------------------------------
If you use Microsoft Windows on an 80386 computer with extended
memory and a Super VGA display, you can use the MONOUMB.386 file, in
conjunction with MemMaker, to conserve conventional memory for
running programs.
To conserve memory if you have a Super VGA display:
1. Open your Windows SYSTEM.INI file, and find the [386Enh] section.
2. Add a DEVICE command for the MONOUMB.386 file, which is located
in your MS-DOS directory. For example, if your MS-DOS files are in
C:\DOS, add the following line to this section:
DEVICE=C:\DOS\MONOUMB.386
3. Save the file, and restart your computer.
4. After your computer starts, run MemMaker by typing MEMMAKER at the
command prompt.
5. Choose Custom Setup. On the Advanced Options screen, answer Yes to
the question "Use monochrome region (B000-B7FF) for running programs?"
Follow the instructions on your screen.
2.4 Using MemMaker with IBM LAN
-------------------------------
Before you run MemMaker, you might need to make adjustments to the
parameters specified for your IBM LAN support driver, DXMC0MOD.SYS. In
your CONFIG.SYS file, make sure that the DEVICE command that loads
DXMC0MOD.SYS includes one of the following before you run MemMaker:
o The first three parameters, as in the following example:
DEVICE=C:\DXMC0MOD.SYS 400000000001,D800,1
o No parameters, as in the following example:
DEVICE=C:\DXMC0MOD.SYS
o Some parameters and enough commas to fill in the first three
parameters, as in the following example:
DEVICE=C:\DXMC0MOD.SYS 400000000001,,
2.5 MemMaker and Adaptec SCSI devices
-------------------------------------
MemMaker is compatible with Adaptec SCSI devices. However, if you use
the ASPI4DOS.SYS driver to support your SCSI device, MemMaker by default
will exclude this driver from the optimization process. If you don't
use the SCSI device as your startup or boot drive, you can include the
ASPI4DOS.SYS driver in the optimization process. To do so, remove the
^ASPI4DOS entry in the MEMMAKER.INF file, and then run MemMaker.
2.6 Using MemMaker on a computer with PC Tools or PC-DOS RAMBoost
-----------------------------------------------------------------
You can use MemMaker or RAMBoost with MS-DOS, but not both at the
same time. MemMaker will prevent RAMBoost from loading, but not
remove its DEVICE= command from your CONFIG.SYS.
2.7 EMM386 detects an error in an application
---------------------------------------------
If EMM386 displays a message such as "EMM386 has detected error
#12 in an application," this indicates that the processor
has reported an exception error to EMM386. An exception error
typically occurs when an application gives the processor an
instruction under invalid or unexpected conditions. In most cases,
these errors are related to a specific program. If you are receiving
an error that does not occur with any particular application, the
error might be caused by a device driver or a memory-resident
(terminate-and-stay-resident) program.
To avoid these errors:
o Try to identify the program involved. One way to do this is
to see if the error occurs when the program is not running.
If you suspect a memory-resident program or device driver,
try bypassing it when your computer starts.
o Try disabling EMM386. If a particular application is to blame,
disabling EMM386 might allow that application to generate an
error message. Disabling EMM386 might also change
your memory configuration so that the error no longer occurs.
o Try changing the order in which you load device drivers and
memory-resident programs. This might help because some
errors occur only under specific memory conditions.
o If error 12 is occurring, this indicates that a stack is being used
incorrectly. Try adding the following command to your CONFIG.SYS
file:
STACKS=18,512
o If error 13 is occurring, the program may be trying to use protected
mode without cooperating with EMM386. You may need to obtain a
VCPI-compliant version of the program, or not load EMM386 when
using this application.
2.8 MemMaker no longer aggressively scans upper memory by default
------------------------------------------------------------------
By default, the MS-DOS 6.21 version of MemMaker does not scan upper
memory aggressively. Instead, the MemMaker option "Scan the upper
memory area aggressively?" is set to No, and MemMaker limits its search
for available UMBs to memory addresses C600 through EFFF. In contrast,
the MS-DOS 6 version of MemMaker did scan upper memory aggressively
by default: in addition to scanning memory in the C600-EFFF range,
it also scanned addresses in the range F000 through F7FF.
To make more memory available for running programs, run MemMaker in
Custom mode and change the "Scan the upper memory area aggressively?"
option to Yes. (Note that, on some computers, putting UMBs in this
range prevents the computer from starting properly.)
Note: If you last ran MemMaker with the "Scan the upper memory
area aggresively" option set to Yes, then the next time
you run MemMaker, it leaves that option set to Yes.
3. WINDOWS
==========
3.1 Your computer uses a Windows 3.0 permanent swap file.
---------------------------------------------------------
If your computer uses a Windows 3.0 permanent swap file, run
the SPATCH.BAT program to make the swap file compatible with MS-DOS 6.
To do so, carry out the following procedure:
1. Copy the SPATCH.BAT file to your hard disk. To determine the location of
the file on the Setup disks, view the PACKING.LST file on Setup Disk
1.
2. Type the following at the command prompt:
SPATCH [DRIVE]:[PATH]SWAPFILE.EXE
For the DRIVE and PATH parameters, specify the location of
your SWAPFILE.EXE file.
3. Follow the instructions on your screen.
The program modifies the SWAPFILE.EXE for use with MS-DOS 6
and saves a backup copy as SWAPFILE.SAV. After you have confirmed
the file works correctly, you can delete the SWAPFILE.SAV file.
3.2 Using compressed floppy disks with Windows File Manager
-----------------------------------------------------------
If you are using compressed floppy disks with automounting enabled,
you might encounter error messages or other problems while using File
Manager. To work around these problems, press the F5 key twice.
For example, if you change from a compressed to an uncompressed floppy
disk, the drive button for the compressed floppy disk's host drive
remains until you press the F5 key twice.
4. HARDWARE COMPATIBILITY WITH MS-DOS
=====================================
4.1 Compaq EXTDISK.SYS Driver
-----------------------------
The Compaq EXTDISK.SYS driver version 3.00 or later is
compatible with MS-DOS 6. If you have a version earlier
than 3.00, contact your vendor for an upgrade.
4.2 Hardcard
------------
a) Hardcard II
If you can't use Plus Development Hardcard II or Hardcard
II XL when running EMM386.EXE, specify the exclude (x=)
switch to prevent EMM386 from conflicting with the card's
BIOS address.
To configure EMM386, run MemMaker.
b) Hardcard 40 or Passport
If you are using Hardcard 40 or a Passport removable
disk, and you have a DEVICE command in your CONFIG.SYS file
for PLUSDRV.SYS, disable or remove the DEVICE command.
Then run MS-DOS 6.21 Setup. After Setup is complete, reenable or
restore the DEVICE command for PLUSDRV.SYS. Make it the last line
in the file.
4.3 Toshiba
-----------
If you used the MS-DOS 5.0 version of EMM386 before you ran
Setup, and you use the Power Management function, use
the VRESUME program or device driver to avoid problems with
the Resume feature. Carry out the following procedure:
1. Make sure the VRESUME.COM or VRESUME.SYS file is on your hard disk.
To load the TSR, add a command for VRESUME.COM to your AUTOEXEC.BAT file.
To load the device driver, add a command for the VRESUME.SYS file to
your CONFIG.SYS file.
2. Save the file, and restart your computer.
NOTE For information about using VRESUME with Windows 3.0, see the
WRESUME.TXT file on your Toshiba MS-DOS 5.0 disks.
5. MICROSOFT PROGRAMS
=====================
5.1 Microsoft Anti-Virus
------------------------
Before cleaning a program file, make sure you have a backup copy of it.
If you clean a program file, and the program is corrupted, reinstall the
program. If Anti-Virus again detects a virus, there is a chance the
detection is in error; contact your software vendor to determine if an
updated version of the program is available.
5.2 Running Microsoft Backup for MS-DOS under Windows
-----------------------------------------------------
You should not run Backup for MS-DOS while Windows is running. However,
if you do, and if your system is not configured correctly, Backup
might display the following symptoms:
o Backup appears to stop running--for example, the clock runs, but
there is no disk activity.
o Backup reports problems while testing the second floppy disk during
the compatibility test. For example, it might display a "Diskette
not properly seated" message or ask for Disk 1 repeatedly.
o Windows displays a message that the DMA buffer size needs to be
increased.
o Backup quits unexpectedly.
You can correctly configure your system by carrying out the following
procedure.
1. Open your SYSTEM.INI file, and add a DMABufferSize=32 line to the
[386Enh] section.
2. When you run Backup, make sure that you specify with the Settings
command from the Control menu that Backup run with the Exclusive
and Full Screen options.
5.3 Backup for Windows stops running at the end of the compatibility test
--------------------------------------------------------------------------
If Backup for Windows stops running at the end of the Compatibility
Test, you might be loading an incompatible third-party backup driver
in your SYSTEM.INI file. Carry out the following procedure.
NOTE This procedure disables your third-party backup program.
1. Open your SYSTEM.INI file, and locate the [386Enh] section.
2. Determine whether any of the following lines are included in this
section:
DEVICE=FASTBACK.386
DEVICE=VFD.386
DEVICE=CPBVXD.386
DEVICE=VIRWT.386
3. If you find any of these lines, add a semicolon (;) to the front
of the line.
4. Save the file, restart Windows, and run Backup for Windows again.
5.4 Running Microsoft Backup with TI4000 and Gateway NOMAD computers
---------------------------------------------------------------------
To avoid a conflict between the Turbo feature and Microsoft Backup
for Windows or MS-DOS, add a /L0 switch to the DEVICE command in
your CONFIG.SYS that loads the BATTERY.PRO file. Or, before you
run Microsoft Backup, type SETPOWER /L0 at the command prompt.
5.5 MS-DOS 6.21 Backup Cannot Restore 6 or 6.2 Backups
------------------------------------------------------
The Backup programs included with MS-DOS version 6.21 cannot usually
restore backups made with MS-DOS version 6 or 6.2. To restore backups
made with the MS-DOS 6 or 6.2 Backup utilities (either the MS-DOS or
Windows versions) use the MS-DOS 6 or 6.2 versions of Backup.
Backup does successfully restore 6 and 6.2 backups made without data
compression. If you unchecked the Compress Backup Data box in the
Backup Options dialog before you backed up, you should have no
problems restoring your data using the MS-DOS version 6.21 Backup
programs.
Backup for Windows
------------------
If you try to use MS-DOS 6.21 Backup for Windows to retrieve the
catalog of a 6 or 6.2 Backup created using compression, you will see
the following error message:
The compression header for the catalog is corrupt.
Use rebuild to reconstruct the catalog.
Backup for Windows will be able to rebuild the catalog, since it does
not have to decompress data to do so. However, attempting to restore
the backup will probably display one of the following error messages:
The file [pathname] could not be properly restored. Do you
want to skip this file?
or
The compression header for the file [pathname]
is corrupt. Restore cannot process this file and must stop.
In either case, the specified file will not be restored, although
other files (which were stored in the backup uncompressed) might have
been restored. Use a 6 or 6.2 Backup utility (either the MS-DOS or
Windows version) to restore this backup.
Backup for MS-DOS
-----------------
If you try to use MS-DOS 6.21 Backup for MS-DOS (MSBACKUP) to retrieve
the catalog of a 6 or 6.2 Backup created using compression, you will
see the following error message:
Cannot retrieve catalog (name) on drive (x).
You can use Backup for MS-DOS to rebuild the catalog, since it does
not have to decompress data to do so. However, attempting to restore
the backup data using Backup for MS-DOS will probably display the
following error message:
Compression failure within file [FILENAME].
The specified file will not be restored, although other files (which
were stored in the backup uncompressed) might have been restored. Use
a 6 or 6.2 Backup utility (either the MS-DOS or Windows version) to
restore this backup.
Note: If you try to restore a compressed backup that is located on a
drive other than a floppy disk (for example, a network drive or a
Bernoulli drive), Backup for MS-DOS will not display any error
messages and will simply skip any compressed files. The Restore
summary screen lists the files that were skipped.
5.6 Microsoft Defragmenter
--------------------------
If you received the "Insufficient Memory" message from Microsoft
Defragmenter, use the MEM command to determine how much conventional,
upper, and extended (XMS) memory is available. In addition to using
all available conventional memory, Defragmenter can make use of up
to 384K of extended memory and 12K of upper memory.
To increase available memory, carry out the procedures in "An MS-DOS
program displays an out-of-memory message" in the chapter "Diagnosing
and Solving Problems" in the MICROSOFT MS-DOS USER'S GUIDE.
If less than 384K of extended memory is available, carry out
the procedures in "Freeing Extended Memory" in the "Making More
Memory Available" chapter in the MICROSOFT MS-DOS USER'S GUIDE.
6. THIRD-PARTY PROGRAMS
=======================
6.1 4DOS and NDOS
-----------------
4DOS and NDOS are compatible with MS-DOS 6. However, to use some of the
new features in MS-DOS 6.21 (such as MemMaker, the LOADHIGH /L switch,
DIR compression switches, and the ability to bypass startup commands),
contact JP Software to obtain 4DOS 4.02 or later, or Symantec to obtain
Norton Utilities 7.0 or later.
If you use multiple configurations, 4DOS or NDOS will not automatically
run your AUTOEXEC.BAT file unless you include a /P on the SHELL line in
your CONFIG.SYS file.
To use MS-DOS 6.21 Help instead of 4DOS or NDOS Help, start it by using
COMMAND /C HELP, or define a 4DOS or NDOS alias to run HELP.COM from
your MS-DOS 6.21 directory.
6.2 Above Board 286 and Above Board Plus Installation
Programs
-----------------------------------------------------
Do not use an Above Board installation program dated May 1989
or earlier until you disable programs that use extended memory,
such as SMARTDrive or RAMDrive. You might lose data if you leave
these programs enabled. After you have installed Above Board,
you can reenable these programs.
6.3 CodeView
-----------
CAUTION Using versions 3.0 to 3.13 of the CodeView CV.EXE
file may cause data loss if your system has an 80386 memory
manager (such as EMM386.EXE) and device drivers or programs
that use extended memory. To determine which version you
have, type CV.EXE at the command prompt.
6.4 Colorado Tape Backup
------------------------
If you receive a message that you have two versions of the
VFINTD.386 file loaded, you probably need to edit your
SYSTEM.INI file. To do so, carry out the following procedure:
1. Open your SYSTEM.INI file and locate the [386Enh] section.
You should see two lines similar to the following:
DEVICE=C:\TAPE\CMSDTAPE.386
DEVICE=C:\DOS\VFINTD.386
2. If you plan to use your Colorado Tape Backup program, add a semi-
colon (;) before the DEVICE command for the VFINTD.386 file. If you
plan to use Microsoft Backup, add a semi-colon before the DEVICE
command for the CMSDTAPE.386 file.
3. Save the file, and restart Windows.
6.5 Fastback Plus
-----------------
If you have a version of Fifth Generation Systems Fastback Pluse earlier
than 3.0, use the LOADFIX command before running Fastback Plus or the
Fastback Plus installation program to ensure that you don't lose data. To
do so, type the following at the command prompt:
LOADFIX FB.EXE
or
LOADFIX FBINSTAL.EXE
6.7 Norton Desktop for Windows 2.0
----------------------------------
Setup adds a second Tools menu which contains Microsoft Backup and
Antivirus commands.
6.8 PC Tools
------------
If PC Shell does not show all of the files or directories on your drive,
quit PC Shell immediately and contact Central Point Software for an update.
CAUTION: Do not attempt to use PC Shell on that drive; severe data
loss might occur.
The FORMAT command of PC Tools version 7.1 conflicts with MS-DOS
6.21. Use the FORMAT command that comes with MS-DOS 6.21.
Installing OS/2 2.1
Welcome to OS/2* 2.1. This document provides
you with information you need before you
install OS/2 2.1. It contains helpful hints
found in our testing as well as updates and
corrections to the "OS/2 2.1 Installation
Guide".
Use the information in conjunction with the
"OS/2 2.1 Installation Guide" and the "OS/2 2.1
Using the Operating System" manual.
****************Important!*****************
If you are installing OS/2 2.1 over a
product release such as OS/2 1.x, OS/2
2.0, OS/2 2.0 with the Service Pak, DOS,
or DOS and Windows**, you do
not need to reformat the OS/2 partition.
If you are installing OS/2 2.1 over an
existing OS/2 2.0 system in which you
have application programs on the desktop,
you should not elect to migrate these
applications during your installation.
Your current application set will
continue to be available to you after
installation.
If you have a version of the OS/2 2.1 beta
installed, you need to reformat the OS/2
partition. Installing OS/2 2.1 over a
previous beta version is not supported.
Do not use any OS/2 system files (such as
OS2.INI or OS2SYS.INI) from a previous
beta version.
If you have a DOS system with compression
activated, do one of the following:
1. Decompress the disk
2. Select a different partition
3. Format the disk
If you are installing OS/2 2.1 on a non-Micro Channel (MCA)
system, change the settings in your CMOS to the following:
o Turbo/System Speed should be OFF/Slow
o Caching (External) should be OFF
o ROM Shadowing (System and Video) should be OFF
These settings affect the way that OS/2 2.1 installs.
Failure to change these settings might result in OS/2 not
installing at all; installing and then booting to a Trap 2;
or what seems to be a good install and later have unexplainable
random Traps (from a few days to a few months later).
To improve system performance after you have installed OS/2,
all of the above settings can be changed back without causing
damage to OS/2.
*******************************************
SCSI-BASED CD-ROM SUPPORT
_________________________
The majority of SCSI-based CD-ROM drives and
adapters are supported by OS/2 2.1.
("SCSI-based" refers to the small computer
system interface (SCSI), a standard
input/output interface used by personal
computers.)
A complete list of the CD-ROM drives and SCSI
adapters tested on OS/2 2.1 can be found in the
"Hardware Support" chapter of the "OS/2 2.1
Using the Operating System" manual. (Note that
Panasonic** MC521 support is not shipped with
OS/2 2.1. Please contact Panasonic to receive
this support.)
OBTAINING ADDITIONAL CD-ROM SUPPORT
If, after reviewing the list in "OS/2 2.1 Using
the Operating System", you find that your
CD-ROM drive or SCSI adapter is not supported
within the OS/2 product, you can contact the
manufacturer and obtain an OS/2 Adapter Device
Driver (.ADD) file. After you receive the .ADD
file, follow the instructions in the "Before
You Begin" section of the "OS/2 2.1
Installation Guide" to add this file to
Diskette 1.
As an alternative, you can create installation
diskettes from the diskette images that are on
the OS/2 CD, if you have DOS support for your
CD-ROM drive.
If support for your CD-ROM was not properly
installed during initial installation of OS/2
2.1, then you will need to use the Selective
Install program located in the System Setup
folder to reinstall the CD-ROM support
appropriate for your CD-ROM.
CREATING DISKETTES FROM THE OS/2 CD
You use the LOADDSKF utility program to create
the diskettes. (LOADDSKF.EXE is in the
\DISKIMGS directory of the CD. LOADDSKF can be
run from either the DOS or OS/2 operating
system.)
In the following sections, you will see lists
of the product diskettes for OS/2 2.1 and the
actual diskette names as they exist on the CD.
For each diskette image file, use LOADDSKF to
expand the image to its own diskette. (Note
that you must use formatted diskettes for this
procedure.)
For example:
cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\OS2\size\disk_name d:
where:
cddrive is the drive letter of the CD-ROM
size is 35 for 3.5-inch diskettes or 525
for 5.25-inch diskettes
disk_name is the diskette image file name
(for example, DISK0.DSK, PMDD1.DSK.)
d is the drive letter of your diskette
drive (A: or B:)
After you create all the diskettes (23 for
3.5-inch diskettes or 28 for 5.25-inch
diskettes), insert the DISK0 diskette in drive
A:, restart your system, and follow the
instructions to install OS/2 2.1.
List of 3.5-Inch Diskette Images
DISKIMGS\OS2\35\DISK0.DSK -- INSTALLATION Diskette
DISKIMGS\OS2\35\DISK1.DSK -- Diskette 1 of 17
DISKIMGS\OS2\35\DISK2.DSK -- Diskette 2 of 17
DISKIMGS\OS2\35\DISK3.DSK -- Diskette 3 of 17
DISKIMGS\OS2\35\DISK4.DSK -- Diskette 4 of 17
DISKIMGS\OS2\35\DISK5.DSK -- Diskette 5 of 17
DISKIMGS\OS2\35\DISK6.DSK -- Diskette 6 of 17
DISKIMGS\OS2\35\DISK7.DSK -- Diskette 7 of 17
DISKIMGS\OS2\35\DISK8.DSK -- Diskette 8 of 17
DISKIMGS\OS2\35\DISK9.DSK -- Diskette 9 of 17
DISKIMGS\OS2\35\DISK10.DSK -- Diskette 10 of 17
DISKIMGS\OS2\35\DISK11.DSK -- Diskette 11 of 17
DISKIMGS\OS2\35\DISK12.DSK -- Diskette 12 of 17
DISKIMGS\OS2\35\DISK13.DSK -- Diskette 13 of 17
DISKIMGS\OS2\35\DISK14.DSK -- Diskette 14 of 17
DISKIMGS\OS2\35\DISK15.DSK -- Diskette 15 of 17
DISKIMGS\OS2\35\DISK16.DSK -- Diskette 16 of 17
DISKIMGS\OS2\35\DISK17.DSK -- Diskette 17 of 17
DISKIMGS\OS2\35\PMDD1.DSK -- Printer Drivers Diskette 1 of 3
DISKIMGS\OS2\35\PMDD2.DSK -- Printer Drivers Diskette 2 of 3
DISKIMGS\OS2\35\PMDD3.DSK -- Printer Drivers Diskette 3 of 3
DISKIMGS\OS2\35\DISP1.DSK -- Display Drivers Diskette 1 of 2
DISKIMGS\OS2\35\DISP2.DSK -- Display Drivers Diskette 2 of 2
List of 5.25-Inch Diskette Images
DISKIMGS\OS2\525\DISK0.DSK - INSTALLATION Diskette
DISKIMGS\OS2\525\DISK1.DSK - Diskette 1 of 21
DISKIMGS\OS2\525\DISK2.DSK - Diskette 2 of 21
DISKIMGS\OS2\525\DISK3.DSK - Diskette 3 of 21
DISKIMGS\OS2\525\DISK4.DSK - Diskette 4 of 21
DISKIMGS\OS2\525\DISK5.DSK - Diskette 5 of 21
DISKIMGS\OS2\525\DISK6.DSK - Diskette 6 of 21
DISKIMGS\OS2\525\DISK7.DSK - Diskette 7 of 21
DISKIMGS\OS2\525\DISK8.DSK - Diskette 8 of 21
DISKIMGS\OS2\525\DISK9.DSK - Diskette 9 of 21
DISKIMGS\OS2\525\DISK10.DSK - Diskette 10 of 21
DISKIMGS\OS2\525\DISK11.DSK - Diskette 11 of 21
DISKIMGS\OS2\525\DISK12.DSK - Diskette 12 of 21
DISKIMGS\OS2\525\DISK13.DSK - Diskette 13 of 21
DISKIMGS\OS2\525\DISK14.DSK - Diskette 14 of 21
DISKIMGS\OS2\525\DISK15.DSK - Diskette 15 of 21
DISKIMGS\OS2\525\DISK16.DSK - Diskette 16 of 21
DISKIMGS\OS2\525\DISK17.DSK - Diskette 17 of 21
DISKIMGS\OS2\525\DISK18.DSK - Diskette 18 of 21
DISKIMGS\OS2\525\DISK19.DSK - Diskette 19 of 21
DISKIMGS\OS2\525\DISK20.DSK - Diskette 20 of 21
DISKIMGS\OS2\525\DISK21.DSK - Diskette 21 of 21
DISKIMGS\OS2\525\PMDD1.DSK - Printer Drivers Diskette 1 of 4
DISKIMGS\OS2\525\PMDD2.DSK - Printer Drivers Diskette 2 of 4
DISKIMGS\OS2\525\PMDD3.DSK - Printer Drivers Diskette 3 of 4
DISKIMGS\OS2\525\PMDD4.DSK - Printer Drivers Diskette 4 of 4
DISKIMGS\OS2\525\DISP1.DSK - Display Drivers Diskette 1 of 2
DISKIMGS\OS2\525\DISP2.DSK - Display Drivers Diskette 2 of 2
If you want to create diskettes for the
Multimedia support that is part of OS/2 2.1,
note that the images are located in the
\DISKIMGS\MMPM2 directory. Use LOADDSKF to
expand each image to its own diskette. For
example:
cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\MMPM2\size\disk_name d:
where:
cddrive is the drive letter of the CD-ROM
size is 35 for 3.5-inch diskettes or 525
for 5.25-inch diskettes
disk_name is the diskette image file name
(for example, DISK1.DSK)
d is the drive letter of your diskette
drive (A: or B:)
NOTE: Use previously formatted diskettes for
the target (d:).
List of 3.5-Inch Multimedia Diskette Images
DISKIMGS\MMPM2\35\DISK1.DSK - Diskette 1 of 2
DISKIMGS\MMPM2\35\DISK2.DSK - Diskette 2 of 2
List of 5.25-Inch Multimedia Diskette Images
DISKIMGS\MMPM2\525\DISK1.DSK - Diskette 1 of 3
DISKIMGS\MMPM2\525\DISK2.DSK - Diskette 2 of 3
DISKIMGS\MMPM2\525\DISK3.DSK- Diskette 3 of 3
HARDWARE CONSIDERATIONS
_______________________
If you have a Quantum hard card, you must make
a modification to the BASEDEV=IBM1S506.ADD line
in the CONFIG.SYS file of Diskette 1 before you
install OS/2 2.1. The BASEDEV statement should
be modified as follows:
BASEDEV=IBM1S506.ADD /A:1 /IRQ:11
(These are the default settings for the Quantum
hard card.)
If you have added a device driver statement to
the CONFIG.SYS file on diskette 1 and later
migrate your old CONFIG.SYS file, make sure
there are not two copies of this statement in
your file. If you have two copies of this
statement in your file, REM one statement out.
If you have a Logitech** TrackMan**, select one
of the two Logitech mouse choices during
installation.
INSTALLING OS/2 2.1 FROM A CD ON AN IBM THINKPAD ATTACHED TO A DOCKING STATION
______________________________________________________________________________
If you are installing OS/2 2.1 on an IBM*
ThinkPad* 700, 700C, 720, or 720C attached to a
3550 Docking Station, you need to replace the
ABIOS files on the OS/2 Installation Diskette
with files from the Reference Diskette. Do the
following:
1. Detach the ThinkPad from the Docking
Station.
2. Create a Reference Diskette (if you have
not already done so) by following the
documentation that came with the ThinkPad.
3. Make a copy of the OS/2 Installation
Diskette.
4. Insert the original OS/2 Installation
Diskette into drive A.
5. Turn on the computer. If it is already on,
press Ctrl+Alt+Del.
6. When you are prompted to do so, remove the
Installation Diskette, insert Diskette 1,
and press Enter.
7. When the Welcome screen is displayed, press
Esc to display the command prompt.
8. Insert the copy of the Installation
Diskette into drive A.
9. Type:
DEL *.BIO
and press Enter.
10. Remove the copy of the Installation
Diskette, and insert the Reference Diskette
you created in step 2 into drive A.
11. If your computer has more than one diskette
drive, insert the copy of the Installation
Diskette into drive B. Otherwise, in the
next two steps, you will be prompted to
insert diskettes into both drive A and
drive B. When you are asked to insert a
diskette into drive A, insert the Reference
Diskette. When you are asked to insert a
diskette into drive B, insert the copy of
the Installation Diskette.
12. Type:
COPY A:\*.BIO B:\
and press Enter.
13. Type:
COPY A:\ABIOS.SYS B:\
and press Enter.
14. Power off the ThinkPad and return it to the
Docking Station.
15. Restart the installation procedure by
inserting the copy of the Installation
Diskette into drive A.
INSTALLING OS/2 2.1 USING RIPL
______________________________
When installing OS/2 2.1 using the IBM LAN
Server 2.0 and 3.0 Remote Installation Program
Load (RIPL), the 2.1 version of RIPLINST.EXE is
dependent upon the 2.1 version of UNPACK.EXE.
Therefore, if you are using the 2.1 version of
RIPLINST.EXE on a client machine with OS/2
version 2.0 or lower, then you must copy the
UNPACK.EXE file to the client machine. To do
this, do the following:
1. Insert OS/2 2.1 Diskette 2 into drive A
2. At an OS/2 command prompt type:
copy a:\unpack.exe \os2\unpack.exe
After copying the file to the client
machine, you can now execute the 2.1
version of the RIPLINST.EXE program.
EXTENDED SERVICES (ES) 1.0
__________________________
o If you installed OS/2 2.1 on a system that
already had Extended Services installed,
replace the existing ESSTART.CMD file with
the ESSTART.BAK file that was installed by
OS/2 2.1. (The ESSTART.BAK file is located
in the OS2\INSTALL subdirectory.)
o If you are installing Extended Services
over OS/2 2.1 for the first time (that is,
there is no Extended Services on the
workstation), or if you are installing
Extended Services from diskettes, rename
the existing ESSTART.CMD file from the
Extended Services Diskette 1. Then, copy
the file ESSTART.BAK from the \OS\INSTALL
directory to Extended Services Diskette 1.
Finally, rename the ESSTART.BAK file
ESSTART.CMD, and begin the installation of
Extended Services.
VIDEO CONSIDERATIONS
____________________
The following information pertains to video
support for OS/2 2.1.
INSTALLING SUPER VGA (SVGA) SUPPORT
After the VGA installation is complete, follow
the procedure "Installing Support for Super VGA
(SVGA)" in Appendix A of the "OS/2 2.1
Installation Guide".
INSTALLATION ON SPECIFIC VIDEO ADAPTERS
In the "OS/2 2.1 Installation Guide",
instructions are given for configuring the
ATI** Graphics Ultra Pro. These instructions
state that the monitor type for 640 x 480 must
be configured to IBM DEFAULT. Note that this
setting might be referred to as 60Hz rather
than IBM DEFAULT.
The Radius XGA display adapter is supported on
PS/2* Models 35 and 40 and PS/ValuePoint* 486
systems. If you are using the display adapter
on a PS/ValuePoint system, the VPXGA.EXE
utility is required. For a copy of this
utility program, check your Radius installation
diskette or contact Radius.
The OS/2 2.1 operating system cannot restore
the state of a Sigma Legend** display adapter
after you switch sessions or video modes.
Also, the Sigma Legend video adapter might
cause the system to stop when using 1024 x 768
x 256 color mode. Use only 640 x 480 or 800 x
600 mode with this adapter.
CORRECTION TO INSTALLATION GUIDE APPENDIX B
___________________________________________
Appendix B of the "OS/2 2.1 Installation Guide"
presents information on how to respond to
messages that begin with "TRAP". The
information in the appendix pertains only to
TRAP0002 messages.
TRADEMARKS
__________
The following terms, denoted by an asterisk (*)
in this README, are trademarks or registered
trademarks of the IBM Corporation in the United
States or other countries:
IBM
-----------------------------------------------
OS/2
-----------------------------------------------
PS/2
-----------------------------------------------
PS/ValuePoint
-----------------------------------------------
ThinkPad
-----------------------------------------------
XGA
-----------------------------------------------
The following terms, denoted by a double
asterisk (**) in this README, are trademarks of
other companies as follows:
Trademark: Owner:
--------------------------------------------------------------
Adaptec Adaptec, Inc.
--------------------------------------------------------------
ATI ATI Technologies, Inc.
--------------------------------------------------------------
Legend Sigma Designs Inc.
--------------------------------------------------------------
Logitech Logitech, Inc.
--------------------------------------------------------------
Panasonic Matsushita Electric Industrial Co., Ltd.
--------------------------------------------------------------
TrackMan Logitech, Inc.
--------------------------------------------------------------
Windows Microsoft Corporation
--------------------------------------------------------------
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED
OR IMPLIED, INCLUDING WITHOUT LIMITATION,
WARRANTIES OF FITNESS AND MERCHANTABILITY WITH
RESPECT TO THE INFORMATION IN THIS DOCUMENT.
BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.
Copyright IBM Corporation, 1993, all rights
reserved.