MS-DOS 5.0

README.TXT NOTES ON MS-DOS VERSION 5.0 =========================== In this file the following topics are covered: 1. Introduction 2. Solving Setup Problems 2.1 Priam and Everex Hard Disks 2.2 SyQuest Removable Hard Disk 2.3 Bernoulli Drive 2.4 Disk Manager 2.5 SpeedStor and Volume Expansion 2.6 Novell Partitions 2.7 Vfeature Deluxe 2.8 Columbia Data Systems Device Driver 2.9 Incompatible Partition 2.10 WYSE Partitions 2.11 286 Accelerator Cards 2.12 Bernoulli Cache 2.13 AT&T 6300 Computers 2.14 LANtastic 2.15 Western Digital SCSI Hard-Disk Controllers 2.16 Change CONFIG.SYS File 2.17 Toshiba T1600 and a Hard RAM Disk 3. Installing MS-DOS 5.0 on OS/2 Systems 3.1 Installing MS-DOS 5.0 and OS/2 Dual-Boot Systems 3.2 Using the Uninstall Program on an OS/2 System 4. Solving Memory Problems 4.1 386MAX 4.2 All Computers Expanded-Memory Driver 4.3 Bus Master DMA Controller 4.4 HIMEM.SYS Location 4.5 INT15 Access to Extended Memory 4.6 Intel LIM Driver 4.7 Phoenix BIOS and HIMEM.SYS 4.8 QEMM 4.9 XMAEM.SYS and XMA2EM.SYS 5. Solving Problems with Windows 5.1 DOS Applications in Windows Enhanced Mode 5.2 EMM386.EXE Location 5.3 WINA20.386 File 5.4 Windows 3.0 Enhanced Debug Version 5.5 Windows 2.03 5.6 Windows/286 2.1 5.7 Windows 386 and the Upper Memory Area 6. Making Your Hardware Compatible with MS-DOS 5.0 6.1 101-key Keyboards and QBasic/MS-DOS Editor 6.2 Acer 1100/33 6.3 Adaptec Controller Boards 6.4 Amstrad Systems and KEYB.COM 6.5 Hardcard II 6.6 COMPAQ EXTDISK.SYS Driver 6.7 Corel System Drivers 6.8 External Disk Drives 6.9 Mice and MS-DOS Shell 6.10 NCR VGA BIOS 6.11 Olivetti Systems 6.12 Toshiba T3100SX 6.13 Western Digital VGA Card 6.14 Zenith Computers 7. Making Your Network Compatible with MS-DOS 5.0 7.1 3+Share 7.2 AT&T StarGROUP 7.3 DCA 10Net and Word5 7.4 DOS LAN Requester 7.5 IBM PC LAN 1.31 7.6 LAN Manager and the Upper Memory Area 7.7 Net/One PC 7.8 Netware 7.9 Novell Networks 7.10 Novell Networks and IPX 7.11 PC-NFS 3.0 7.12 TOPS Network 8. New Information About MS-DOS 5.0 8.1 EXPAND Command 8.2 FORMAT and MIRROR Commands 8.3 QBasic "On Error" Command 8.4 SMARTDrive and Third-Party Partitions 8.5 SYS Command 8.6 UNDELETE Command 8.7 UNFORMAT /J Switch 1. INTRODUCTION =============== This document provides important information that is not included in the Microsoft MS-DOS User's Guide and Reference or in online Help. The readme includes notes on procedures you may have to do before running Setup and information about using Windows, memory, and hardware with MS-DOS 5.0. It also contains updates to the User's Guide and Reference. For information about using applications with MS-DOS 5.0, see the APPNOTE.TXT file. 2. SOLVING SETUP PROBLEMS ========================= 2.1 Priam and Everex Hard Disks ------------------------------- If your hard disk contains a Priam or Everex hard disk, you must do the following to install MS-DOS 5.0: 1. Install MS-DOS 5.0 on floppy disks by typing the following command: setup /f 2. Start MS-DOS 5.0 by using the floppy disks you created. 3. Make sure that you can access all your hard-disk partitions. 4. If you can access all the partitions, insert the floppy disk that contains the SYS.COM file into drive a: and type the following command: sys c: 5. Create a DOS directory on your hard disk. 5. Copy all files on your floppy disks to the DOS directory. 6. Modify your CONFIG.SYS and AUTOEXEC.BAT files as necessary. 2.2 SyQuest Removable Hard Disk ------------------------------- If your system contains a SyQuest removable hard disk, use the following procedure to install MS-DOS 5.0: 1. Remove or comment out the DEVICE=SYQ55.SYS command from your CONFIG.SYS file. 2. Restart your system. 3. Run Setup. After installing MS-DOS 5.0, you can put the DEVICE=SYQ55.SYS command back in your CONFIG.SYS file. 2.3 Bernoulli Drive ------------------- If Setup refers you to this section, contact Iomega at (801) 778-3000 before you install MS-DOS 5.0 to get information about an updated RCD.SYS device driver. 2.4 Disk Manager ---------------- To upgrade Ontrack Computer System's Disk Manager, do the following: 1. Use the EXPAND command to expand and copy the DMDRVR.BI_ file from Disk 6 to your DOS directory and the XBIOS.OV_ file from Disk 6 to your root directory. 2. Name the files DMDRVR.BIN and XBIOS.OVL. 3. Run Setup with the /u switch, as follows: setup /u 2.5 SpeedStor and Volume Expansion ---------------------------------- To upgrade Storage Dimensions' SpeedStor, or Hewlett-Packard Volume Expansion, do the following: 1. If your system has non-MicroChannel architecture (non-PS/2 compatible), use the EXPAND command to expand and copy the driver named SSTOR.SY_ from Disk 6 to your hard disk. If your system has MicroChannel architecture, contact your vendor for an updated driver. 2. If you are upgrading SpeedStor, name the driver SSTOR.SYS. If you are upgrading Volume Expansion, replace the DEVICE=HARDRIVE.SYS command with a DEVICE=SSTOR.SYS command in your CONFIG.SYS file. 3. Run Setup with the /u switch, as follows: setup /u 2.6 Novell Partitions --------------------- If your system includes Novell partitions, upgrade to MS-DOS 5.0 by running Setup with the /u switch, as follows: setup /u 2.7 Vfeature Deluxe ------------------- Contact Golden Bow Systems for information about Vfeature upgrades. Until the upgrade is available, you can either install MS-DOS 5.0 on floppy disks or delete Vfeature partitions by repartitioning your hard disk. To install MS-DOS 5.0 on floppy disks, run Setup with the /f switch, as follows: setup /f To delete Vfeature partitions your hard disk, see the procedure called "To repartition your hard disk" in Chapter 4 of the Microsoft MS-DOS Getting Started guide. 2.8 Columbia Data Systems Device Drivers ----------------------------------------- If you use a Columbia Data Systems device driver, you may experience problems running Setup. If you do, remove the DEVICE=SSTBIOS.SYS and DEVICE=SSTDRIVE.SYS commands from your CONFIG.SYS file and run Setup again. After completing Setup, install the device drivers by returning the DEVICE= commands to your CONFIG.SYS file and restarting your computer. 2.9 Incompatible Partition -------------------------- If you have a partition that is incompatible with MS-DOS 5.0, you must delete it from your hard disk. Incompatible partitions are listed as "Non-DOS" partitions in FDISK. See the procedure for repartitioning hard disks in Chapter 4 of the Microsoft MS-DOS Getting Started guide. 2.10 WYSE Partitions -------------------- If you have a partition created by WYSE DOS 2.11 or 3.1, you must delete the DOS partitions from your hard disk. See the procedure for repartitioning hard disks in Chapter 4 of the Microsoft MS-DOS Getting Started guide. 2.11 286 Accelerator Cards -------------------------- If your system includes a 286 accelerator card, Setup may not be able to determine the amount of extended memory you have. To avoid this problem, disable the card before running Setup. 2.12 Bernoulli Cache -------------------- Before running Setup, open the CONFIG.SYS file and remove or comment out the DEVICE command that installs the caching software for your Iomega Bernoulli drive. 2.13 AT&T 6300 Computers ------------------------ If you use an AT&T 6300 computer, contact AT&T to upgrade your ROM BIOS to version 1.21 or later. The ROM BIOS version number is displayed when you start your computer. 2.14 LANtastic -------------- If you use a LANtastic network, disable it before running Setup. 2.15 Western Digital SCSI Hard-Disk Controllers ----------------------------------------------- If you are using a Western Digital WD Fast 700 or AT/XT SCSI controller, before upgrading to MS-DOS 5.0 contact Western Digital to get an updated device driver and a new hard-disk ROM (version 3.36 or later). The ROM version number is displayed when you start your computer. 2.16 Change CONFIG.SYS File --------------------------- If you are installing MS-DOS 5.0 on one of the systems listed below, you must add the specified /machine switch to the DEVICE=HIMEM.SYS command in your CONFIG.SYS file before you run Setup. After changing the CONFIG.SYS file, run Setup. 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 UNISYS PowerPort /machine:2 UNISYS 800/20c /machine:1 2.17 Toshiba T1600 and a Hard RAM Disk -------------------------------------- To use the hard RAM disk, do the following before installing MS-DOS 5.0: 1. Using the Toshiba Setup program, delete the RAM disk by allocating zero KB to it. All data on the RAM disk will be lost. 2. Restart your system. 3. Install MS-DOS 5.0. 4. Use the Toshiba setup program to reinstall the RAM disk. 5. Run FDISK, change to drive 2, and create a primary DOS partition. Exit FDISK. 6. Use the FORMAT command to format drive D. 3. INSTALLING MS-DOS 5.0 ON OS/2 SYSTEMS ======================================== 3.1 Installing MS-DOS 5.0 on OS/2 Dual Boot Systems --------------------------------------------------- To use MS-DOS 5.0 with the OS/2 dual-boot version that prompts you at system startup time to select an operating system, do the following, making sure that you complete all steps of the procedure: 1. Install MS-DOS 5.0 on your hard disk. 2. Create a system floppy disk by using 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. Install the OS/2 operating system on your hard disk. 7. Insert the system disk you created in drive A and restart your computer. 8. Run the dual-boot program (C:\DUALBOOT\DUALBOOT.EXE). 3.2 Using the Uninstall Program on an OS/2 System ------------------------------------------------- You can run the Uninstall program on systems that have MS OS/2 1.0, or IBM and MS OS/2 1.1 and later versions. However, if you install MS-DOS 5.0 over IBM OS/2 1.0, you will not be able to run the Uninstall program. You can work around this problem by renaming the IBM OS/2 1.0 system files IBMBIO.COM and IBMDOS.COM, so that Setup does not confuse them with DOS system files. If you run the Uninstall program on a system that 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 you ran the Uninstall program. 4. SOLVING MEMORY PROBLEMS ========================== 4.1 386MAX ---------- In some cases, after loading a program high with 386LOAD.COM prior to version 5.11, the loaded program reports "Incorrect DOS version." If this occurs, do one of the following: * Use the SETVER command to set the version number for Qualitas' 386MAX to the lower version required by the program reporting the error. * Use the LOADFIX command, as follows: 386LOAD LOADFIX <program> Then use the SETVER command to set the version number for each application. For example, use the following two commands to load REDIR4.EXE: 386LOAD LOADFIX REDIR4.EXE SETVER REDIR4.EXE 4.01 WARNING: All programs loaded by 386LOAD.COM use the new version number. Do not use the MAXHI.EXE program supplied with versions of 386MAX prior to 5.0 with MS-DOS version 5.0 because it will cause your system to lock up. 4.2 All Computers Expanded-Memory Driver ----------------------------------------- You must have version 2.5 or later of the All Computers expanded-memory driver (ALLEMM4.SYS) to work with MS-DOS 5.0 HIMEM.SYS. Contact All Computers to get an updated driver. 4.3 Bus Master DMA Controller ----------------------------- If you have a bus master DMA controller and you have problems using the upper memory area, add a DEVICE=SMARTDRV.SYS command to your CONFIG.SYS file before any DEVICEHIGH commands. 4.4 HIMEM.SYS Location ---------------------- Setup does not install HIMEM.SYS if another XMS memory manager is active when you are running Setup. If Setup did not install HIMEM.SYS, you can copy it to your disk by using the EXPAND command. For information about using the EXPAND command, see Chapter 14 of the Microsoft MS-DOS User's Guide and Reference. 4.5 INT15 Access to Extended Memory ----------------------------------- Software such as older versions of Borland's Paradox, Oracle's Oracle, Quarterdeck's QEMM, and Lantana Technology's Turbo EMS may use interrupt 15 to access extended memory. To use this type of software with MS-DOS 5.0 loaded high, specify the HIMEM.SYS /int15=xxxx switch in your CONFIG.SYS file. The switch allocates the specified amount of extended memory for the INT15h interface. You may also have to use switches with the particular software to indicate the amount of extended memory accessible through INT15. For example, you can specify the /m switch with Turbo EMS. 4.6 Intel LIM Driver -------------------- Use the Intel LIM driver NE or E switch when installing the Intel EMM.SYS LIM driver for Aboveboard. 4.7 Phoenix BIOS and HIMEM.SYS ------------------------------ If your system includes a Phoenix BIOS and you have problems using HIMEM.SYS, add a /machine:1 or /machine:8 switch to the HIMEM.SYS command in your CONFIG.SYS file. 4.8 QEMM --------- Versions of Quarterdeck's QEMM prior to version 5.11 have problems when the HIMEM.SYS file is loaded with the INT15=xxxx option. If you have a problem, do one of the following: * Add the QEMM MEMORY=yyyy option to the DEVICE=QEMM.SYS line in your CONFIG.SYS file, where yyyy = xxxx - 64. * Use the LOADFIX command, as follows: LOADFIX QEMM.SYS Then use the SETVER command to set the version number for each application. * Update your QEMM to version 5.11. 4.9 XMAEM.SYS and XMA2EMS.SYS ----------------------------- Setup comments out the CONFIG.SYS commands that load IBM XMAEM.SYS and XMA2EMS.SYS. If your system uses both drivers, replace the commands with a DEVICE=EMM386.EXE command in your CONFIG.SYS file. If your system has physical expanded memory, remove the comment that disables XMA2EMS.SYS. 5. SOLVING PROBLEMS WITH WINDOWS ================================ 5.1 DOS Applications in Windows Enhanced Mode --------------------------------------------- If you run DOS applications that use EMS memory under Windows enhanced mode, use the EMM386.EXE /ram switch instead of the /noems switch. 5.2 EMM386.EXE Location ----------------------- When Windows enhanced mode starts, it finds EMM386.EXE by using the path specified in the DEVICE=EMM386.EXE command in your CONFIG.SYS file. If the command does not specify the correct location of the file, use the following command to specify the new path: device=emm386 /y=path 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 enhanced section of your Windows SYSTEM.INI file. 5.4 Windows 3.0 Enhanced Debug Version -------------------------------------- If you are running the debug version of Windows 3.0 enhanced mode with DOS=LOW, you may have problems with the display of debug information on your serial terminal. Contact Microsoft Product Support Services for help. See your registration card for the product support number. 5.5 Windows 2.03 ---------------- Windows 2.03 386 version is incompatible with MS-DOS versions 4.0 and 5.0. 5.6 Windows/286 2.1 ------------------- If you run Windows/286 version 2.1 on a computer with MS-DOS 5.0, you need to run COMMAND.COM from a program information file &#40;PIF&#41; that specifies enough memory for COMMAND.COM to run. The default value in the PIF file is not large enough. 5.7 Windows 386 and the Upper Memory Area ----------------------------------------- If you are using EMM386 with the /ram or /noems switch, you cannot run Windows in standard mode. 6. MAKING YOUR HARDWARE COMPATIBLE WITH MS-DOS 5.0 ========================================================== 6.1 101-key Keyboards and QBasic/MS-DOS Editor ---------------------------------------------- If you are unable to use the arrow keys on your numeric keypad when running QBasic or MS-DOS Editor, Microsoft offers a memory-resident program called FIXSHIFT.COM that may help. To obtain FIXSHIFT.COM, call Microsoft Product Support Services. See your registration card for the product support number. 6.2 Acer 1100/33 ---------------- If you have an Acer 1100/33 computer with an Award BIOS, your system may lock up if you are using EMM386. Contact Acer for a ROM upgrade. 6.3 Adaptec Controller Boards ----------------------------- If you are using Adaptec controller board model ACB2372, A, B, C or model ACB2322B with two hard disk drives attached, and you are using expanded memory (EMS), you need to obtain Adaptec's ADAPTEC.SYS device driver and add a DEVICE=ADAPTEC.SYS command to your CONFIG.SYS file. Contact your Adaptec dealer or distributor for more information. 6.4 Amstrad Systems and KEYB.COM -------------------------------- If you have problems using KEYB.COM an Amstrad system, check the version number of your BIOS. If it is less than 1.4, contact your vendor for a BIOS upgrade. 6.5 Hardcard II --------------- If you have trouble with Plus Development Hardcard II or Hardcard II XL when running EMM386.EXE, you need to use the x switch to prevent EMM386 from conflicting with the card's BIOS address. For example, if your Hardcard II or Hardcard II XL uses BIOS address D700-D7FF, add the x=D700-D7FF switch to the DEVICE= command for EMM386. See your Hardcard II manual to determine the BIOS addresses that Hardcard II or Hardcard II XL uses. 6.6 COMPAQ EXTDISK.SYS Driver ----------------------------- Versions 4.0 or 5.0 of the COMPAQ EXTDISK.SYS driver are needed to work with MS-DOS 5.0. 6.7 Corel Systems Drivers ------------------------- If you have trouble with a Corel Systems driver for a large capacity drive (WORM, Winchester, etc.), you may need to obtain an updated driver from Corel Systems. 6.8 External Disk Drives ------------------------ If you have trouble using an Nth external disk drive, contact Nth Group to get the latest version of the driver. If you have trouble using ProCom floppy disk drives, you may need to obtain an updated driver from ProCom. If you have trouble using Sysgen floppy disk drives, contact Sysgen to get the latest version of the driver (3.41 or later). If you receive an error message when using the DISKCOMP command with Sysgen external drives, retry the operation. 6.9 Mice and MS-DOS Shell ------------------------- If you are using a Logitech or Microsoft mouse with MS-DOS Shell, you may experience problems if you are not using the following versions: Logitech mouse version 5.01 or higher Microsoft mouse version 6.21 or higher 6.10 NCR VGA BIOS ----------------- If you have an NCR VGA BIOS and have trouble switching between screens when running MS-DOS Shell or QBasic, see your NCR PC User Manual for information about making your VGA BIOS "PS/2 Compatible." 6.11 Olivetti Systems --------------------- Some Olivetti systems with CGA video boards may have problems scrolling. If you have a scrolling problem, use the ANSI.SYS /s switch in your CONFIG.SYS file. 6.12 Toshiba T3100SX -------------------- Users of Toshiba T3100SX computers should either disable the suspend/resume feature or not use EMM386.EXE. 6.13 Western Digital VGA Card ----------------------------- If you have a Western Digital VGA card and your system locks up when you use RAMBIOS.EXE and RAMBIOS.SYS, load those files before loading ANSI.SYS, DISPLAY.SYS, and GRAPHICS.COM in your CONFIG.SYS file. 6.14 Zenith Computers --------------------- If you have difficulty using the GRAPHICS command on a Zenith computer, increase stack space by using the STACKS command in your CONFIG.SYS file. 7. MAKING YOUR NETWORK COMPATIBLE WITH MS-DOS 5.0 ================================================= 7.1 3+Share ------------ If you have installed 3Com Corporation 3+Share with minimal netbios implementation, do one of the following: * Run a complete netbios implementation. * Use the REDIR.400 file. * Call Microsoft Product Support Services and request the LAN Manager 2.0 supplemental disk. 7.2 AT&T StarGROUP ------------------- AT&T StarGROUP software is compatible with MS-DOS 5.0. If your version of StarGROUP does not include support for MS-DOS 5.0, contact your AT&T representative or the AT&T National Systems Support Hotline for information on required modifications or upgrades. 7.3 DCA 10Net and Word5 ----------------------- IF you run Microsoft Word5 on a net drive created by using DCA 10Net, and you start MS-DOS Shell from a local drive, your system may lock up if you use the Task Swapper to switch from Word5 to an application that is running on the local drive. To prevent this from happening, either run Word5 on the local drive or run MS-DOS Shell on the net drive. 7.4 DOS LAN Requester --------------------- If you have problems using the FC command with the IBM DOS LAN Requester, specify a lower value for the /nbc parameter. 7.5 IBM PC LAN 1.31 -------------------- Chapter three of the Microsoft MS-DOS Getting Started guide includes a section on updating IBM PC LAn version 1.3 or earlier. The procedures described in this section apply also to version 1.31. 7.6 LAN Manager Enhanced and the Upper Memory Area -------------------------------------------------- If you are running Microsoft LAN Manager Enhanced, use the EMM386 /ram switch and the LIM=YES command in your LANMAN.INI file. However, if you use the EMM386 /noems switch, add the LIM=NO command to your LANMAN.INI file. If you are using LAN Manager Enhanced version 2.0, you can load the redirector (NETWKSTA.EXE) and NetBEUI transport (NETBEUI.DOS) into the upper memory area. If your system includes sufficient space in the upper memory area, you may also be able to move LAN Manager services such as NETPOPUP.EXE, MSRV.EXE, and ENCRYPT.EXE out of conventional memory. If you want LAN Manager software and documentation about loading these services into the upper memory area, Contact Microsoft Product Support Services to request the MS-DOS 5.0 Supplemental Disk. See your registration card for the product support number. 7.7 Net/One PC --------------- If Ungermann-Bass, Inc., Net/One PC does not load with MS-DOS 5.0, do one of the following: * Contact your vendor to get an updated LOADNIU.EXE file. * Put a UBPAUSE command between the LOADNIU and XNSBIOS lines of the MSNET.INI file. * Issue network commands from a batch file that includes a PAUSE command between the LOADNIU and XNSBIOS lines. 7.8 NetWare ----------- Novell NetWare remote boot software is incompatible with MS-DOS 5.0. Contact Novell for an upgrade. Do not use NetWare LOGIN.EXE, MAP.EXE, and SESSION.EXE files after starting MS-DOS Shell. 7.9 Novell Networks ------------------- If you are running a Novell network and you set the COMSPEC variable after starting MS-DOS 5.0, either remove the c:\dos\ entry from the SHELL= command in your CONFIG.SYS file or contact your Novell vendor to get a new login program. 7.10 Novell Networks and IPX ---------------------------- If you experience problems switching between some applications, you may need to use TBMI.COM to allow switching between peer-to-peer applications that run under NetWare with a multitasking environment such as MS-DOS 5.0. To determine if you need TBMI, run your application for a period of time then enter the command TBMI /D. If the value in the field Far Call Usage is zero, you do not need TBMI. Start TBMI by entering the command "TBMI" on the command line, followed by any optional command line before starting the DOSSHELL. Type TBMI /? at the command line to display the valid command line parameters. Normally, the default configuration for TBMI is correct for most applications. If you experience problems, contact Novell for information on TBMI configuration parameters. NOTE: You must update to IPX 3.02 before you can use TBMI. 7.11 PC-NFS 3.0 --------------- Sun Microsystems, Inc., PC-NFS 3.0 is compatible with MS-DOS 5.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 correct this problem, use the PC-NFS /d switch to specify the number of drives you are using. If you have trouble using the COPY or XCOPY command on PC-NFS 3.01, contact Sun Microsystems to get an updated version of the PCNFS.SYS device driver. 7.12 TOPS Network ----------------- If your system is a TOPS workstation, the MS-DOS Shell MOVE command may not work. Current versions of TOPS network are incompatible with the MS-DOS 5.0 LOADHIGH command. 8. NEW INFORMATION ABOUT MS-DOS 5.0 =================================== 8.1 EXPAND Command ------------------- The EXPAND command example in chapter four of the Microsoft MS-DOS User's Guide and Reference incorrectly refers to installation and upgrade disks. The disk referred to as "Disk 1" should be Disk 2; the disk referred to as "Disk 2" should be Disk 3. 8.2 FORMAT and MIRROR Commands ------------------------------ If you have problems using the FORMAT command to format an unformatted disk, try using the /u switch. You cannot use the FORMAT /q switch or the MIRROR command with 160K and 320K disks that have been formatted with versions of DOS other than MS-DOS 5.0. You cannot use the MIRROR command with a network drive or any drive that you have created using the ASSIGN, SUBST, or JOIN command. 8.3 QBasic "On Error" Command ----------------------------- Online help for Microsoft QBasic incorrectly states that ON ERROR RESUME NEXT is a valid statement. The correct syntax is as follows: ON ERROR GOTO <LINE/LABEL> 8.4 SMARTDrive and Third-party Partitions ----------------------------------------- If your system includes a third-party disk partition and you try to use SMARTDrive, you may receive a message stating that you cannot load SMARTDrive. You can force SMARTDrive 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 directly by the system's ROM BIOS. If you have a Disk Manager partition, use the following two procedures to determine if either condition is true for your system. To determine if your hard drive has more than 1024 cylinders, do the following: 1. At the command prompt, type dm /m. 2. Type c to display the disk configuration. 3. If any disk displayed has an Actual Cylinder Count of more than 1024, you are at risk when using SMARTDrive. To determine whether or not your hard disk is supported by the system's ROM BIOS, do the following: 1. At the command prompt, type ver to display the version of DOS you are running. If it is earlier than 3.30, you are not at risk. Otherwise, continue. 2. Type dm /m to invoke Disk Manager in manual mode. 3. Type c to display the disk configuration. 4. If the display states "Parameters Are Replaced," continue. Otherwise, you are not at risk. 5. For each disk in your system, compare the Setup Parameters with the Actual Parameters displayed. If all disks displayed have a Setup Head Count that matches the Actual Head Count, and a Setup Sector Count that matches the Actual Sector Count, you are not at risk. When the values do not match, the drive is non-homogeneous. 6. From the Disk Manager main menu, type s to select the non- homogeneous drive. 7. Type p to display the partition table for the drive. 8. If the drive contains a partition with the type "DOS," and if one or more partitions are type "Write-Read" or "Read-Only," you are at risk. 9. Repeat steps 6 through 8 for each non-homogenous disk on your system. If you have partitions created by using third-party disk partitioning software other than Disk Manager, use SMARTDrive ONLY if you are sure your hard disk contains 1024 or fewer cylinders AND it is supported directly by the system's ROM BIOS. 8.5 SYS Command --------------- The SYS command copies the COMMAND.COM file to the root directory of the target disk. Make sure the SHELL= and COMSPEC= commands in your CONFIG.SYS file point to the root directory, or move the COMMAND.COM file to directory pointed to by those commands. 8.6 UNDELETE Command -------------------- You should 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 the MS-DOS Task Swapper 8.7 UNFORMAT /J Switch ---------------------- You cannot use the UNFORMAT /p switch with the /j switch.