This file provides information about the following topics: Notes on Setup Creating the Uninstall disk(s) A directory called OLD_DOS is created by Setup Setup may create multiple OLD_DOS directories Using CLEANUP to remove old DOS information Old LINK.EXE versions may be left in path WINA20.386 file Manually Unpacking MS-DOS 5.0 files Setting up MS-DOS 5.0 on OS/2 systems Running the upgrade on an OS/2 system MS-DOS 5.0 and OS/2 dual boot Notes on Windows 2.x Running Windows/286 with MS-DOS 5.00 Using Windows 2.1 run-time applications with MS-DOS 5.0 Notes on Windows 3.x Windows 386 debugger and MS-DOS 5.00 Running Windows 3.0 real mode in an enhanced mode window The SETVER command Disk Partitioning Software Identifying the Disk Utility Upgrading to MS-DOS 5.0 Upgrading Disk Manager Upgrading SpeedStor Upgrading Multivol or Volume Expansion Upgrading Vfeature Deluxe Hard drive partitions with logical sectoring Making your hardware compatible with MS-DOS 5.0 Intel Aboveboard HP Vectra CS Model 20 Logitech C7 mouse Adaptec controller boards 101-key keyboards and Qbasic/Edit Corel Systems drives Plus Development Hardcard II Video 7 video cards ProComm Floppy Drives Making your software compatible with MS-DOS 5.0 Soft Ice by Nu-Mega Software Carousel Metro and Displaywrite III MS-DOS Multitasking Software Asynchronous I/O and DOSSHELL.EXE task switching Gazelle Systems QDOS II Microsoft CodeView 3.0 Raid and MS-DOS 5.0 Quarterdeck Manifest Quarterdeck QEMM Kingston Memory Board EMS driver Software that accesses extended memory via INT 15 386 To The Max (386MAX) Tandy Deskmate Northnet Atlast! PC-Tools Backtalk Microsoft CD-ROM extensions Softlogic Solution's Disk Optimizer Mountain High's autorun.exe Borland's Turbo Debugger 386 For more information about Upper Memory Block support, see the UMB.TXT file. For more information about Networks, see the NETWORK.TXT file. NOTES ON SETUP------------------------------------------------------------- CREATING THE UNINSTALL DISK(S) If you use a bad disk to create the Uninstall disk during Setup, you may not be able to successfully uninstall MS-DOS 5.0. Be sure to use an unformatted or newly formatted disk. A DIRECTORY CALLED OLD_DOS.1 IS CREATED BY SETUP A directory called OLD_DOS.1 is created by Setup during the installation of MS-DOS 5.0. The files in this directory, in combination with the files on your Uninstall disk, can be used to restore your old DOS. Do not remove or alter the OLD_DOS.1 directory on your hard disk if you think you might reinstall your old DOS. After you remove the directory, reinstalling your old DOS is not possible. You can delete the OLD_DOS.1 directory at any time by typing CLEANUP at the command prompt. SETUP MAY CREATE MULTIPLE OLD_DOS DIRECTORIES If you upgrade to MS-DOS 5.0 more than once, without using CLEANUP to delete previous OLD_DOS directories, a new directory will be created each time you upgrade. Subsequent OLD_DOS directories will be named OLD_DOS.2, OLD_DOS.3, and so on. If you have run the upgrade several times on the same system and have created several Uninstall disks in the process, be sure to use the most recent Uninstall disk to recover your system. USING CLEANUP TO REMOVE OLD DOS INFORMATION After you have used MS-DOS 5.0 and are confident that you will not need to restore your previous version of DOS, you can use the CLEANUP program to remove your old DOS from your hard disk. To remove the old DOS from your hard disk, type CLEANUP at the command prompt, press ENTER, and follow the directions. You will not be able to restore your previous DOS after running CLEANUP. OLD LINK.EXE VERSIONS MAY BE LEFT IN PATH If you are running a compiler and it fails, you may have an old version of LINK.EXE in your DOS subdirectory. MS-DOS Setup puts the DOS directory at the front of the path in your AUTOEXEC.BAT file. The LINK.EXE file that was in the DOS directory before you installed MS-DOS 5.0 may be put ahead of the location of the LINK.EXE file you want to use. LINK.EXE is not shipped with MS-DOS 5.0. WINA20.386 FILE When installing upon systems capable of running Windows in Enhanced mode MS-DOS 5.00 will place a read only file called WINA20.386 in the root directory. This file provides support for Windows when it is running in the enhanced mode and has to stay in the root. MANUALLY UNPACKING MS-DOS 5.0 FILES: Files on MS-DOS 5.0 master disks that have extensions ending with an underscore (_) are in a compressed format. To retrieve a single file from the MS-DOS 5.0 master disks, use the EXPAND utility located on Disk 5. Syntax: expand [drive1:][path1]infile [drive2:][path2]outfile [drive1:][path1]infile Specifies the location and name of the compressed file you want to expand [drive2:][path2]outfile Specifies the destination and new name of the expanded file Example: expand a:\redir.ex_ c:\dos\redir.exe SETTING UP MS-DOS 5.0 ON OS/2 SYSTEMS---------------------------------- RUNNING THE UPGRADE ON AN OS/2 SYSTEM If you install the upgrade over IBM OS/2 1.0 you will not be able to uninstall. This is not a problem for MS OS/2 1.0 or for IBM and MS OS/2 1.1 and later versions. You can work around this by renaming the IBM OS/2 1.0 system files, IBMBIO.COM and IBMDOS.COM, to something else so the setup program does not confuse them with DOS system files If you run the uninstall on a system which had OS/2 on it before the upgrade running chkdsk may show some lost extended attributes. This will happen whenever a file which had extended attributes under OS/2 was altered under dos before the uninstall MS-DOS 5.0 AND OS/2 DUAL BOOT OS/2 1.1 and Compaq OS/2 1.21 dual boot installation programs don't work with MS-DOS 5.00. MS OS/2 1.21 dual boot works fine. NOTES ON WINDOWS 2.X------------------------------------------------------- RUNNING WINDOWS/286 WITH MS-DOS 5.0 If you run Windows/286 on a computer with MS-DOS 5.0, you will need to run COMMAND.COM from a program information file (PIF). Winoldapp allocates only about 39K for the COMMAND.COM file, which is not enough for the MS-DOS 5.0 COMMAND.COM. USING WINDOWS 2.1 RUN-TIME APPLICATIONS WITH MS-DOS 5.0 If you are using Windows 2.1 run-time applications, there may be older, incompatible, versions of SMARTDRV.SYS and HIMEM.SYS on your hard disk. An older version of SMARTDRV.SYS will cause an "Incorrect DOS version" error message to appear on your screen, and SMARTDrive will not install. An older version of HIMEM.SYS will cause the run-time application not to run, and may cause other incompatibility problems. Be sure to change your CONFIG.SYS file so the SMARTDRV.SYS and HIMEM.SYS files supplied with MS-DOS 5.0 are used instead of those supplied with your Windows application. NOTES ON WINDOWS 3.X----------------------------------------------------- WINDOWS/386 DEBUG VERSION AND MS-DOS 5.0 If you are running the debug version of Windows/386 with DOS=LOW, the DOS segment will be below the BIOS segment, causing your system to fail. Call Microsoft Product Support Services at (206)454-2030 for a solution to this problem. RUNNING WINDOWS 3.0 REAL MODE IN AN ENHANCED MODE WINDOW If your computer hangs or gets an application error when running win /r in an Enhanced Mode VM, it may help if you remove the line "ebios=*EBIOS" in the 386ENH section of the SYSTEM.INI file. However, this may make it impossible to run other programs after exiting. THE SETVER COMMAND--------------------------------------------------- With the SETVER command, you can control what version MS-DOS reports to certain programs. SETVER "fools" programs that rely on a certain version of DOS into running under MS-DOS 5.0. DISK PARTITIONING SOFTWARE------------------------------------------- MS-DOS 5.0 Setup may not be able to directly upgrade your hard disk if one of the following disk utilities was used to set up hard disks on your system: Manufacturer Name Device Driver --------------------------------------------------------------------- Ontrack Disk Manager DMDRVR.BIN Storage Dimensions SpeedStor SSTOR.SYS or HARDRIVE.SYS Golden Bow Systems Vfeature Deluxe FIXT_DRV.SYS Hewlett-Packard MultiVol MULTIVOL.SYS Hewlett-Packard Volume Expansion HARDRIVE.SYS If MS-DOS 5.0 Setup detects a disk partition created by one of the above utilities, it will refuse to upgrade your hard disk automatically. In order to install MS-DOS 5.0, follow the detailed steps outlined below. IDENTIFYING THE DISK UTILITY You may already know which disk utility was used to set up your hard disk. If not, look in your CONFIG.SYS file for one of the device driver names in the above table. For example, if the line "DEVICE=SSTOR.SYS" appears in your CONFIG.SYS file, the SpeedStor disk utility was used to set up your hard disk. If you find HARDRIVE.SYS in your CONFIG.SYS file, you must determine whether the device driver came from Hewlett-Packard (HP DOS 3.3) or Storage Dimensions. UPGRADING TO MS-DOS 5.0 Procedures to determine whether you can upgrade your system and to carry out the upgrade vary between the disk utilities. Each is discussed separately below. Note: MS-DOS 5.0 Setup requires at least 2.5 MB of free space in your boot partition (drive C). If you have a very small boot partition, you may need to repartition your hard disk to create a larger boot partition before upgrading to MS-DOS 5.0. Setup utility comments out the device driver line in your CONFIG.SYS file after the installation is successfully completed. UPGRADING DISK MANAGER If you are currently running DOS version 4.0 or 4.01, you can upgrade your hard disk to MS-DOS 5.0 by running Setup with the /u switch, as follows: setup /u If you are running an earlier version of DOS, you should contact Microsoft Beta support for DOS 5.0 compatible disk manager drivers (provided to MS by Ontrack systems). UPGRADING SPEEDSTOR If you are currently running DOS version 4.0 or 4.01, you should have no difficulty upgrading to MS-DOS 5.0 by running setup with the /u switch, as follows: setup /u If you are running an earlier version of DOS, you should contact Microsoft Beta support for DOS 5.0 compatible disk manager drivers (provided to MS by storage dimension). UPGRADING MULTIVOL or VOLUME EXPANSION These disk utilities were distributed with HP DOS versions 3.2 and 3.3. Hewlett-Packard recommends that you repartition and reformat your hard disk with MS-DOS 5.0, eliminating the need for MultiVol or Volume Expansion. To do this, carry out the following steps: * Install MS-DOS 5.0 on floppy disks. You can do this by running MS-DOS 5.0 Setup. Although Setup will refuse to upgrade your hard disk, it will install DOS on floppy disks. * Back up your hard disk using the HDBACKUP program provided with MS-DOS 5.0 or some other backup utility. The program HDBACKUP.EXE can be found on UPGRADE DISK 1 and can be run by typing in HDBACKUP at the A:> prompt. Backups created this way can be restored with the dos RESTORE command. * Boot from the MS-DOS 5.0 startup floppy disk you created. * Run FDISK. * Delete non-DOS partitions. * Create new partitions. * From the MS-DOS 5.0 floppy disk, run FORMAT to format each new partition. * Restart your system from the hard disk (remove floppy disks from drives first). * Run MS-DOS 5.0 Setup. Setup will upgrade your hard disk. * Restore the files from the deleted partitions, using the backup copies you created. UPGRADING VFEATURE DELUXE Current versions of Vfeature Deluxe is not compatible with MS-DOS 5.0. Golden Bow Systems is planning to upgrade the software to take advantage of MS-DOS 5.0 advanced features. Contact Golden Bow system for information about Vfeature upgrades. Until the upgrade is available, you can install MS-DOS 5.0 on floppy disks. However, you may not be able to access your hard disk while running MS-DOS 5.0. HARD DRIVE PARTITIONS WITH LOGICAL SECTORING--------------------------- If the version of DOS you were using before upgrading to dos 5 used logical sectoring partitions that were larger than 32MB on the hard drive you should never boot with your previous dos and then access the hard drive. Because dos 5 upgrade has changed the structure of your hard drive partition doing this could very easily destroy information on the drive. At this point in time we know that NEC, Toshiba, Wyse and Zenith Dos' use logical sectoring on large hard drive partitions. This is by no means a complete list and will be enlarged. MAKING YOUR HARDWARE COMPATIBLE WITH MS-DOS 5.0---------------------------- INTEL ABOVEBOARD If you have an Intel Aboveboard in your system you will need to run Intel's Aboveboard setup program after installing dos 5 in order to access the memory on the board. This needs to be done because the Dos 5 installation program overwrites the Aboveboard's initilization information which is stored on your harddrive. HP VECTRA CS MODEL 20 The Hewlett Packard portable Vectra CS Model 20 requires a 1.44Mfloppy in drive A at boot time for MSDOS FORMAT, DISKCOPY and DISKCOMP to recognize the drive as a 1.44MB floppy drive. Failure to do so will make FORMAT, DISKCOPY and DISKCOMP think that the drive is a 720K floppy drive and prevent their proper operation with 1.44MB floppies. Hewlett Packard's version of MS-DOS 5.0 will not have this requirement. LOGITECH C7 MOUSE If you are unable to use a Logitech C7 mouse, contact the company to obtain an updated mouse driver. You will need to get version 5.0 or later. ADAPTEC CONTROLLER BOARDS If you are using an Adaptec controller board with two hard drives attached and are using expanded memory (EMS), you may need to obtain Adaptec's adaptec.sys device driver. For more information, contact your Adaptec dealer or distributor or call Adaptec's technical support hotline at 408/945-2550. 101-KEY KEYBOARDS AND QBASIC/EDIT If you are unable to use the arrow keys on your numeric keypad when running Qbasic or EDIT, Microsoft offers a TSR called FIXSHIFT.COM which may help. To obtain FIXSHIFT.COM call Microsoft Product Support at (206)454-2030 COREL SYSTEMS DRIVERS If you are having trouble with a Corel System driver for a large capacity drive (WORM, Winchester, etc.) you may need to obtain an updated driver from Corel Systems. PLUS DEVELOPMENT HARDCARD II If you are having trouble with Plus Development's Hardcard II when running EMM386.EXE, you will need to add the option X=D700-D7FF on the DEVICE= line for EMM386. VIDEO 7 VGA CARDS If you are having trouble with MS-DOS Shell and the Microsoft mouse when using a Video7 VGA card, it may help if you use the /Y option on the mouse. PROCOMM FLOPPY DRIVES If you have trouble with ProComm floppy drives you may need to obtain an updated driver from ProComm. MAKING YOUR SOFTWARE COMPATIBLE WITH MS-DOS 5.0---------------------------- SOFT ICE BY NU-MEGA If you are using Nu-Mega's Soft Ice program you should not load it after HIMEM.SYS on a Compaq system when you are using SMARTDRV.SYS. Soft Ice can corrupt the disk cache in this situation, resulting in a corrupted hard drive. SOFTWARE CAROUSEL Software Carousel will lock up when running under MS-DOS 5.0 unless SETVER has been used to report version 4.00 to it. Example: SETVER C: CAROUSEL.EXE 4.00 LOTUS METRO, LOTUS EXPRESS, AND IBM DISPLAYWRITE III These software packages do not support the extended ROM BIOS for 101-key keyboards. If you have trouble with them, add the following line to your CONFIG.SYS file and restart your computer: SWITCHES=/K This will instruct MS-DOS 5.0 not to use the extended ROM BIOS. The applications will work, but you will not be able to access the F11 or F12 keys through MS-DOS. MS-DOS MULTITASKING SOFTWARE: If you are using software that provides multitasking support for MS-DOS, do not enable the switcher in MS-DOS Shell. The multitasking system and MS-DOS SHELL task swapping are likely to conflict. ASYNCHRONOUS I/O and DOSSHELL.EXE TASK SWITCHING The MS-DOS Shell task switcher does not support switching of programs performing asynchronous communications. This includes all terminal emulation software such as SmartCom, Procomm Plus, and server/client software such as Laplink and Blast. The MS-DOS Shell task switcher should not be enabled if you are using asynchronous communications programs. GAZELLE SYSTEMS QDOS II: QDOS II is a DOS version-specific application. Only versions of QDOS II that support MS-DOS 4.xx will work correctly with MS-DOS 5.0. MICROSOFT CODEVIEW 3.00: If you are using Microsoft Codeview 3.0 to debug applications that use expanded memory, and are using the EMM386.SYS memory manager of MS-DOS 5.0 in AUTO mode, you may experience some problems. Whenever using Codeview to debug EMS applications you should either turn EMM386 on before debugging or use the /d or /e switches on Codeview 3.0. RAID AND MS-DOS 5.O (IBETA) If you are a raid user and are upgrading from MS-DOS 3.x, copy the NISAMR.EXE file from \\dos5server\beta. If you are upgrading from DOS 4.x, you probably have this file and will not need to get it. QUARTERDECK MANIFEST: Versions of this application previous to 1.01 are closely tied to internals specific to earlier versions of DOS and do not work with MS-DOS 5.0. Quarterdeck Manifest v1.01 will work on MS-DOS 5.00. For an upgrade to v1.01 contact Quarterdeck QUARTERDECK QEMM Versions of Qemm prior to 5.11 have problems when the HIMEM.SYS file is loaded with the /INT15=xxxx option. Add the QEMM option MEMORY=yyyy to the DEVICE=QEMM.SYS line in your CONFIG.SYS file, where yyyy = xxxx - 64. Or can update your Qemm to version 5.11. The buffers program supplied with some versions of Qemm should not be used with MS-DOS 5. If you were using this program previous to upgrading to MS-DOS 5.0 you will need to increase your dos BUFFERS= line in your config.sys. We suggest BUFFERS=20 as a new setting. KINGSTON MEMORY BOARD EMS DRIVER: The Kingston EMSDRVR.SYS driver is incompatible with the MS-DOS 5.0 HIMEM.SYS file. You can use the MS-DOS 5.0 EMM386.SYS file to access EMS memory instead of the Kingston diver. SOFTWARE THAT ACCESSES EXTENDED MEMORY VIA INT 15 Some software that uses extended memory, such as Paradox, Oracle, QEMM, or Turbo EMS, does so using interrupt 15. To use this type of software with MS-DOS 5.0 loaded high, you can use the HIMEM.SYS /INT15=xxxx switch. The /INT15 switch allocates the specified amount of extended memory for the INT15h interface. It may also be necessary to use options on the particular software to specify the amount of extended memory accessible through INT15. This can be done using the /M switch with Turbo EMS, and the MEMORY option with QEMM. 386MAX: In some cases, after loading a program high with 386LOAD.COM, the loaded program will report "Incorrect DOS version." If this occurs use the SETVER command to set the version number for 386MAX to the lower version required by the program reporting the error. If a program is loaded high using 386LOAD.COM, the DOS version number reported by SETVER will not be passed to it by 386MAX . This happens because the 386MAX reports the version it sees to programs that have been loaded high, not the version they see. WARNING: After this has been done, all programs loaded by 386LOAD.COM will be reported this new version number The Maxhi.exe program supplied with versions of 386MAX prior to 5.0 should not be used with MS-DOS 5.0 as it will cause the machine to hang. TANDY DESKMATE Versions of Deskmate prior to 3.0.2 incorrectly calculated disk space size for large disks. If problems occur writing files to a disk because Deskmate reports that there is not enough disk space, contact Tandy to get the most recent version of Deskmate. NORTHNET ATLAST! If you experience problems with Northnet's Atlast! upper memory manager, contact Northnet for an upgrade. PC-TOOLS BACKTALK Loading PC-Tools Backtalk into upper memory blocks with the LOADHIGH command may cause your machine to hang. Usually this will only happen if you have filled up the rest of the UMB space with other device drivers and TSR's. You should load Backtalk in conventional memory and fill the UMB space with other device drivers or TSR's. MICROSOFT CD-ROM EXTENSIONS While any version of MSCDEX.EXE that worked under MS-DOS 4.x will function in most situations under MS-DOS 5, there are known problems with MSCDEX.EXE when using it with the /s option to run a CD-ROM drive as a network server. This function will not work in MS-DOS 5.00 until a new version of MSCDEX.EXE is written. SOFTLOGIC SOLUTION'S DISK OPTIMIZER Versions of Softlogic Solutions Disk Optimizer prior to 4.05 would give the message "File Allocation Table Contains Invalid Information. Run CHKDSK". If you encounter this problem you will need to contact Softlogic for an upgrade. MOUNTAIN HIGH'S AUTORUN.EXE If you experience problems with autorun.exe, a tape drive backup program written by Mountain High, you will need to contact the company to obtain an upgrade BORLAND'S TURBO DEBUGGER 386 Borland's Turbo Debugger 386 is configuration dependent and will need to be reinstalled after upgrading to MS-DOS 5.00 or you may experience machine hangs while running the debugger.