TECHNICAL NOTES ON USING MS-DOS 5.0 AS PUBLISHED BY COMPAQ

NOTICE

THE FOLLOWING INFORMATION HAS BEEN PROVIDED BY MICROSOFT CORPORATION AND
COMPAQ COMPUTER CORPORATION.  WHILE THE INFORMATION INCLUDED IS INTENDED
TO BE ACCURATE, IT MAY NOT BE A COMPLETE LISTING OF ISSUES ASSOCIATED WITH
RUNNING MS-DOS 5 AS PUBLISHED BY COMPAQ.  PLEASE CONTACT YOUR LOCAL DEALER
IF YOU HAVE QUESTIONS OR NEED ASSISTANCE RUNNING YOUR APPLICATION WITH
MS-DOS 5 AS PUBLISHED BY COMPAQ.

Information in this document is subject to change without notice.

Compaq Computer Corporation shall not be liable for technical or editorial
errors or omissions made herein; nor for incidental or consequential
damages resulting from the furnishing, performance, or use of this
material.

Product names mentioned herein are used for identification purposes only
and may be trademarks and/or registered trademarks of their respective
companies.

1. NOTES ON MEMORY MANAGEMENT

1.1 Problems Loading into the Upper Memory Area

Some computers with hard disk controllers, specifically busmaster DMA
controllers, may not be able to load device drivers or programs into the
upper memory area. Try adding a  DEVICE=CACHE.EXE command before any
DEVICEHIGH commands in your CONFIG.SYS file.

1.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.

2. NOTES ON WINDOWS

2.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=CEMM.EXE command in
your CONFIG.SYS file.

2.2 "Unable to start Enhanced Mode Windows" Message

If you start Windows enhanced mode 3.0, and get a message stating
"Unable to start Enhanced Mode Windows due to invalid path specification
for CEMM", add the /y=path switch to the  DEVICE=CEMM.EXE command in
your CONFIG.SYS file. "Path" specifies the location of the CEMM.EXE file
when you start Windows.

For example, if the CEMM.EXE file is in the \DOS directory on drive C,
your command would look like this:
	DEVICE=CEMM.EXE /y=c:\dos\cemm.exe

2.3 WINA20.386 File

If you have Windows 3.0 and you would like to move the file WINA20.386
out of the root directory of your boot drive then add the statement,
SWITCHES=/W, to your CONFIG.SYS and the statement,
DEVICE=C:\DOS\WINA20.386, to your Windows 3.0 SYSTEM.INI file. This will
tell Windows 3.0 enhanced mode where to find this file when starting.

If you want to 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.

2.4 "High Memory Area in Use" Message and Windows/386 2.1

You cannot run Windows/386 2.1 when MS-DOS 5.0 is loaded into the high
memory area.

2.5 "Cannot run Windows in standard mode" Message

If you have a DEVICE=CEMM.EXE command in your CONFIG.SYS file, you
cannot run Windows 3.0 in standard mode. Either remove the
DEVICE=CEMM.EXE command or run Windows in real or enhanced mode.

NOTE: Using CEMM 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 CACHE, try setting the minimum cache
size parameter to 0.

3. USING A MOUSE WITH THE MS-DOS SHELL

If you have a Logitech or Microsoft mouse, use the following driver
versions with MS-DOS Shell:
	Logitech mouse version 5.01 or later
	Microsoft mouse version 6.21 or later

If your system supports 132 column text modes then you need the
following driver:
	Microsoft mouse version 8.01 or later

4. XGA and CEMM.EXE

If you use an XGA display with CEMM.EXE, you may need to exclude certain
memory ranges with the CEMM EXCLUDE option (x=). To determine which
memory ranges to exclude, use your reference disk to view the memory
map.

5. NOTES ON NETWORKS

5.1 Version Specific Network Software

A lot of network software is version checked for specific MS-DOS
versions and will therefore not work immediately with MS-DOS 5.0.
Loading the SETVER.EXE device driver will solve many of these problems,
at least temporarily. One problem is that many network programs "take
over" DOS functions and these may not match the new functionality of
5.0. Another problem is that the software may be tightly coupled to the
structure of MS-DOS and will not work exactly right with any other
version. A better solution is to obtain updated software from the
network vendor.

MS-DOS 5.0 has new functionality in the EXEC program loader for loading
programs high and handling exepacked programs. Since some network
software provides their own loaders, these functions will not work
properly after the network software is loaded.

5.2 Memory Addressing Problems

If you are using CEMM.EXE to provide either EMS or UMB support and
experience problems with your network you may need to explicitly exclude
the memory address of your network adapter card. This is extremely
important with some network adapter that cannot be detected while the
system is booting. To exclude a memory address range, use the "X="
switch on the DEVICE=CEMM.EXE line in your CONFIG.SYS as in the
following example:

	DEVICE=CEMM.EXE X=<memory address range>

To determine the memory address range to exclude, consult your network
adapter card documentation.  Your network software may provide a utility
for determining the proper address range to be excluded. If you have a
COMPAQ EISA system or compatible you can use the System Configuration
utility to determine the address range used by your network adapter.
Otherwise, you can look at the DIP switches or jumpers on your network
adapter card and use the reference manual to determine their values. Some
common memory address ranges are:

	C000-C7FF
	C800-CFFF
	D000-D7FF
	D800-DFFF

Note:  The address range to be excluded depends upon the particular
adapter type and manufacturer. Some 8K Ethernet cards actually need to
exclude 16K.

5.3 Banyan VINES Version 4.0x

The Banyan VINES version 4.0x network software is loaded as a TSR
program. The BAN program cannot be loaded high. INTR2BAN is not version
specific and will load high. REDIRALL.EXE will work with MS-DOS 5.0 and
can be loaded high, but only supports MS-DOS 4.0 functions. Alternatively,
the SETVER facility may be loaded to use REDIR4.EXE. Use the following
commands to load Banyan VINES support into UMBs:

	ban /nc
	loadhigh intr2ban
	loadhigh redirall
	login

Note1: After loading a REDIRALL program that does not support MS-DOS 5.0
the LOADHIGH (LH) commands will no longer load programs high.

Note2: If you are receiving "Controller Failure" error messages then add
the proper exclude (x=) to your CEMM statement in the CONFIG.SYS. Use
the Banyan PCCONFIG utility to determine the address range to exclude.

5.4 Microsoft LAN Manager, MS-Net, and Compatibles

The 100% compatible LAN Managers include the following:

	3Com 3+Open version 1.1 through 2.0
	Hewlett-Packard LAN Manager version A.02.00 or earlier
	Microsoft LAN Manager version 2.0 or earlier
	NCR LAN Manager
	Olivetti Olinet-LM version 2.0 or earlier
	Ungermann-Bass Net/One LM version 1.1 through 2.0.

To determine if you are running basic or enhanced version of the Lan
Manager look at LANMAN.INI  file to see which redirector is being
started. If it contains a reference to NETWKSTA.EXE then you are running
enhanced version of the Lan Manager. If it contains a  reference to
REDIR.EXE then you are running basic Lan Manager. Which ever is being
used, you need a new version of that supports MS-DOS 5.0. To locate your
LANMAN.INI, or any other file, use the following DIR command with the /S
switch to search subdirectories from the root of the drive containing
your network files.

    DIR LANMAN.INI /S

You must obtain an updated version of the network files from your
network vendor and follow their upgrade instructions.

If you are running Microsoft MS-Net or 100% compatible network then
follow the instructions for the basic version. These include the
following:

	Microsoft MS-Net
	Hewlett-Packard Office Works
	NCR PC LAN
	Olivetti Olinet-LAN version 1.23 or earlier
	Ungermann-Bass Net/One PC version 2.0 through 2.1

5.5 Novell NetWare

If you are currently using Novell NetWare with a MS-DOS version less than
5.0, you may need to obtain new network software from your network
administrator or network vendor to use with MS-DOS 5.0. After upgrading
to MS-DOS 5.0, if you are having difficulty logging on to your network
then you may need updated versions of one or more of the following files:

    NET*.COM
    EMSNET*.COM
    XMSNET*.COM
    IPX.OBJ

The "*" signifies the MS-DOS version for which your network software is
designed. To locate your current NETx.COM, or any other file, use the
following DIR command with the /S switch to search subdirectories from the
root of the drive containing your network files.

    DIR <drive:><path><filename> /S

After upgrading your network software, remember to change any batch files
that reference the old filenames.

5.6 Artisoft LANtastic Versions 2.5 Through 3.02

You will have to install the SETVER facility by adding the statement,
DEVICE=SETVER.EXE or DEVICEHIGH=SETVER.EXE, to your CONFIG.SYS. Type the
following command at the prompt:

	SETVER REDIR.EXE 4.00
	SETVER SERVER.EXE 4.00

If you are using CEMM then you may have to add an exclude statement (X=)
to your CEMM statement in your CONFIG.SYS. This must exclude the memory
address range used by your network adapter.

After making these modifications you must restart your system before
they become effective.

5.7 AT&T StarGROUP

If your AT&T StarGROUP version does not support MS-DOS 5.0, contact your
AT&T representative or the AT&T National Systems Support Hotline for
information about required modifications or upgrades.

5.8 PC-NFS 3.0

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

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

5.9 TOPS Version 3.0 or Earlier

Do not use the LOADHIGH command with a TOPS network.

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

5.10 DCA 10Net Versions 3.0 Through 4.2

If you have MS-DOS loaded into high memory (DOS=HIGH) then you can use
the LOADFIX command to load your network software above the first 64K of
memory. Do this if you receive the message "Packed file is corrupt" when
you load your network software. Also, see the section on exepacked
programs.

5.11 DEC PATHWORKS and PCSA Version 3.x

To use DEC PATHWORKS or PCSA network software with MS-DOS 5.0 you must
load the SETVER facility in your CONFIG.SYS and type the following
command before restarting your system:

	SETVER REDIR.EXE 4.00
	SETVER USE.EXE 4.00
	SETVER EMSLOAD.EXE 4.00
	SETVER SCH.EXE 4.00
	SETVER NETSETUP.EXE 4.00
	SETVER NCP.EXE 4.00
	SETVER DNNETHAT.EXE 4.00
	SETVER LAD.EXE 4.00
	SETVER DLL.EXE 4.00
	SETVER MEMMAN.EXE 4.00
	SETVER DNNETHLD.EXE 4.00
	SETVER SHOW.EXE 4.00

5.12 3Com 3+Share Version 1.6

You must obtain an updated version of MSREDIR.EXE from your network
vendor.

5.13 IBM PC LAN Version 1.3 or Earlier

You must obtain an updated version of REDIR.EXE from your network
vendor. Replace any MS-DOS commands (such as MODE or PRINT) in your
network subdirectory (PCLP). If you were previously using MS-DOS 4.x
then you must delete the following line from your CONFIG.SYS:

	IFS=REDIR.SYS
	INSTALL=IFSFUNC.EXE

5.14 IBM DOS LAN Requestor Version 1.2

You must obtain an updated version of REDIR33.EXE from your network
vendor.

5.15 Expanded and Extended Memory

Some of the network software that is explicitly designed to make use of
extended/expanded memory may not work with MS-DOS 5.0.

5.16 Using the MS-DOS SHELL Task Switcher

Some of the earlier versions of the network software may not work with the
Task Switcher enabled in MS-DOS Shell. If you experience difficulties,
disable task switching.

6. EXEPACKed Programs and the "Packed file is corrupt" Message

Exepacked programs are compressed programs that expand automatically
upon execution. They can be recognized because they contain the text
string "Packed file is corrupt" near the end of the program file. Due to
the nature of the unpacking code they contain, they do not expand
correctly in the first 64K of memory, i.e. 0-0FFFFH. With most previous
DOS versions, the first 64K was always in use by the system kernel and
device drivers. MS-DOS 5.0's ability to load high opens up this area for
use by application programs. Exepacked programs are normally checked for
and corrected by the MS-DOS 5.0 EXEC function. The exceptions are when
the EXEC function is "taken over" by a version 4.0 network redirector or
when the exepacked program is an unrecognizable version. When exepacked
programs do not run you will receive the "Packed file is corrupt"
message.

One way to run packed programs, when all else fails,  is to use the
LOADFIX utility which loads them above the first 64K. Some third party
software is also available for unpacking packed programs.

7. INSTALLING MS-DOS 5.0 ON AN MS OS/2 DUAL-BOOT SYSTEM

If you use COMPAQ MS OS/2 or a similar MS OS/2 dual-boot system that
prompts you at startup to select an operating system, do the following:

	1. Insert the COMPAQ MS-DOS 5.0 FASTART diskette and restart your
       system.

If you want to perform a manual installation of COMPAQ MS-DOS 5.0 on an
MS OS/2 dual-boot system of the type mentioned above then do the
following:

	1. Make sure that MS OS/2 was the last operating system booted.
	2. Insert the MS OS/2 INSTALL diskette of the version you are
       running and restart your system.
	3. Type the Escape key to exit to the prompt and enter the
       following command: SYSINSTX C:
	4. Insert the MS-DOS 5.0 SYSTEM diskette and restart your system.
       (Do not run SYS.)
	5. Move to the C drive by typing C:<enter>.
    6. Rename your CONFIG.DOS and AUTOEXEC.DOS files to have a different
       extension.
    7. Switch to the dual-boot subdirectory by typing CD \DUALBOOT<enter>.
        8. Run the DUALBOOT program and follow the instructions.                 9. Copy the MS-DOS files to the subdirectory where you keep your
       system files (\DOS).

If you install your operating system by using the BOOT /OS2 or BOOT /DOS
command, install MS-DOS 5.0 first and then reinstall MS OS/2 and the
dualboot capability. If you have a bootable MS-DOS diskette then it will
also have to be upgraded.

8. Hercules Display Adapter Support

If you use MS-DOS Editor or QBasic with a Hercules display adapter, run
MSHERC.COM before you run either program.

9. Disk Manager Partitions

If you are using MS-DOS 3.x and have a Disk Manager partition larger than
512MB, then you must contact Ontrack Computer Systems to get an upgraded
version of Disk Manager that is compatible with MS-DOS 5.0.

10. Western Digital SCSI Hard-Disk Controller

If you are using a Western Digital WD 7000 FASST or AT/XT SCSI controller
with a ROM version of 3.35 or earlier, then contact your vendor for an
upgrade before installing MS-DOS 5.0.

11. Hardcard II

If you have problems using Plus Development's Hardcard II or Hardcard II
XL when running CEMM.EXE, then add an exclude switch (X=) to your CEMM
configuration statement. See your Hardcard manual to determine the
addresses that need to be excluded.

12. Western Digital VGA Card

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

13. Un-Installing Compaq MS-DOS 5.00

Ulitmately, no un-install process is foolproof.  The most general advice
is, of course, back up the system before a new operating system is
installed.  In the case where many systems are involved, DOS 5.0 should be
tested on a small number of units before all machines are upgraded.

The un-install process should rarely be necessary.  The most common
difficulty will be not having network drivers, etc. which are compatible
with DOS 5.0.  In these scenerios there will be a loss of the network link
until the files are obtained.

If the previous version of DOS (e.g. 3.31 or 4.01) was isolated in a
subdirectory on the fixed disk (e.g. C:\DOS), FASTART 5.0 was used to
install DOS 5.0 over the previous version of DOS, and the user has an
original copy of the DOS diskettes, then to un-install:

    STEP 1:  Restore the original AUTOEXEC.BAT and CONFIG.SYS FILES.

    FASTART will have renamed the original files to AUTOEXEC.BAK and
    CONFIG.BAK and created new AUTOEXEC.BAT and CONFIG.SYS files. The new
    files should be deleted and the original ones renamed as appropriate.

    STEP 2:  DELETE THE DOS 5.0 FILES.

    STEP 3:  Reinstall the old version of DOS using its FASTART program.

If the previous version of DOS (e.g. 3.31 or 4.01) was isolated in a
subdirectory on the fixed disk (e.g. C:\DOS), FASTART 5.0 was used to
install DOS 5.0 in a different subdirectory, and the previous version of
DOS still exists in its original location, then to un-install:

    STEP 1:  Restore the original AUTOEXEC.BAT and CONFIG.SYS FILES.

    FASTART will have renamed the original files to AUTOEXEC.BAK and
    CONFIG.BAK and created new AUTOEXEC.BAT and CONFIG.SYS files. The new
    files should be deleted and the original ones renamed as appropriate.

    STEP 2:  Delete the new subdirectory and the DOS 5.0 files it 
    contains.

    STEP 3:  Execute SYS.COM from the original DOS STARTUP diskette to
    place the original DOS system files on the fixed disk.

    STEP 4:  Copy the COMMAND.COM file from the STARTUP diskette of the
    old version of DOS over the DOS 5.0 COMMAND.COM file in the root 
    directory of the fixed disk.

14. Installing Compaq MS-DOS 5.00 onto network workstations

To install Compaq MS-DOS 5.00 onto a large number of network workstations
you must do the following:

    STEP 1. Copy all of the Compaq MS-DOS 5.00 files into a subdirectory
    on each server using the command:

         XCOPY  <A: or B:>  <network subdirectory>  /I

         The /I parameter will copy all of the hidden system files.

    STEP 2. Next you must make sure that each workstation has the correct
    network support software before upgrading to MS-DOS 5.00.

    STEP 3. Use the following Compaq MS-DOS 5.00 SYS command from each
    workstation:

         <network subdirectory>SYS <network subdirectory> <A: or C:>

         The network subdirectory specifies the drive and path of files
         created in step 1.

    STEP 4. Copy the rest of the Compaq MS-DOS 5.00 files replacing all of
    the old MS-DOS files.

    STEP 5. Update the CONFIG.SYS and AUTOEXEC.BAT as necessary, ie
    DOS=HIGH, etc.

    STEP 6. At this point, if all of the MS-DOS 5.00 network support files
    have been configured, the system is ready to restart under Compaq 
    MS-DOS 5.00.

