README.TXT NOTES ON MS-DOS VERSION 5.0 =========================== This readme provides important information not included in the Microsoft MS-DOS User's Guide and Reference or in online 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 MS-DOS 5.0. +++++++++++++++++++++++++++++++++++++++++++++ For information about using applications with MS-DOS 5.0, see the APPNOTES.TXT file. The following topics are discussed in this file: 1. Readme Conventions 2. Notes on Setup 2.1 Priam and Everex Disk-Partitioning Software 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 Partition 2.11 286 Accelerator Card 2.12 Bernoulli Cache 2.13 AT&T 6300 Computer 2.14 Western Digital SCSI Hard-Disk Controller 2.15 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 2.16 Toshiba T1600 and a Hard RAM Disk 2.17 Unix and Xenix Partitions 2.18 Apricot XEN-S Computer 2.19 Installing MS-DOS 5.0 on an OS/2 Dual-Boot System 2.20 4DOS 2.21 8514 Display Adapters 3. Notes on Memory Management 3.1 386MAX (5.11 or Earlier) 3.2 All Computers Inc. Expanded-Memory Driver (ALLEMM4.SYS) 3.3 Problems Loading into the Upper Memory Area 3.4 Installing HIMEM.SYS 3.5 Intel Expanded-Memory Driver (EMM.SYS) 3.6 Phoenix BIOS and HIMEM.SYS 3.7 XMAEM.SYS and XMA2EMS.SYS 4. Notes on Windows 4.1 DOS Applications in Expanded Memory 4.2 "Unable to start Enhanced Mode Windows" Message 4.3 WINA20.386 File 4.4 Windows/286 2.1 4.5 "High Memory Area in Use" Message (Windows/386 2.1) 4.6 "Cannot run Windows in standard mode" Message 5. Making Your Hardware Compatible with MS-DOS 5.0 5.1 Acer 1100/33 and CTRL+ALT+DEL 5.2 Amstrad Systems and KEYB.COM 5.3 Apricot Qi 386 Systems 5.4 Arrow Keys and QBasic/MS-DOS Editor 5.5 AT&T Computer with an VDC 750 Display Adapter Card 5.6 Commodore PC III and Task Swapper 5.7 Compaq EXTDISK.SYS Driver 5.8 Corel System Disk Drivers 5.9 External Floppy Disk Drives * Nth * Procomm * Sysgen 5.10 Hardcard II 5.11 NCR VGA BIOS 5.12 Olivetti System with a CGA Video Board 5.13 Toshiba T3100SX 5.14 Using a Mouse with MS-DOS Shell * Logitech * Microsoft 5.15 Western Digital VGA Card 5.16 Wondercard 3.x 5.17 XGA and EMM386.EXE 5.18 Zenith Computer 5.19 Zeos 486 and Task Swapper 6. Making Your Network Compatible with MS-DOS 5.0 6.1 MS-DOS Shell and Networks 6.2 3+Share 6.3 AT&T StarGROUP 6.4 Microsoft LAN Manager 2.0 Enhanced 6.5 Net/One PC 6.6 Novell Networks 6.7 PC-NFS 3.0 6.8 TOPS Network 7. Documentation Corrections and Additions 7.1 New CV.COM for CodeView 7.2 Documentation Corrections 7.3 Hercules Display Adapter (MSHERC.COM) 7.4 QBasic "On Error" Command 7.5 SMARTDrive 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 Microsoft MS-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 MS-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 MS-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 MS-DOS User's Guide and Reference for more information about using the EXPAND command. 2. NOTES ON SETUP ================= 2.1 Priam and Everex Disk-Partitioning Software ----------------------------------------------- If your system uses Priam or Everex disk-partitioning software, and Setup has referred you to this section, 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. Back up your DOS directory. 3. Start MS-DOS 5.0 by using the floppy disks you created. 4. Make sure you can access all your drives. 5. If you can access all drives, insert the floppy disk that contains the SYS.COM file into drive A and type the following command: sys c: 6. Create a DOS directory on your hard disk. 7. Copy all files on your floppy disks to the DOS directory. 8. Update your CONFIG.SYS and AUTOEXEC.BAT files to refer to the new DOS files. See Chapter 12 of the MS-DOS User's Guide and Reference for more information about updating your CONFIG.SYS file. 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 the DEVICE=SYQ55.SYS command from your CONFIG.SYS file. 2. Restart your system. 3. Run Setup. After installing MS-DOS 5.0, 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 before you install MS-DOS 5.0 to get information about an updated RCD.SYS device driver. 2.4 Disk Manager ---------------- If you are using DOS 3.x on a system that has a Disk Manager partition greater than 512MB, contact Ontrack Computer Systems to get an upgraded version of Disk Manager and instructions for making the partition compatible with MS-DOS 5.0. Otherwise, do the following: 1. Back up your current DMDRVR.BIN and XBIOS.OVL device drivers. 2. Replace the DMDRVR.BIN and XBIOS.OVL files by using the EXPAND command to expand and copy the DMDRVR.BI_ and XBIOS.OV_ files from Disk 6 for 5.25" disks or from Disk 3 for 3.5" disks. 3. Type the following: setup /u 2.5 SpeedStor and Volume Expansion ---------------------------------- If you have a Novell partition, and Setup referred you to this section, see section 2.6. If you have a Xenix partition and Setup referred you to this section, see section 2.17. If your system is an IBM PS/2 or has MicroChannel architecture, contact your software vendor for disk-partitioning software that is compatible with MS-DOS 5.0. Otherwise, do the following to upgrade Storage Dimensions' SpeedStor or Hewlett-Packard's Volume Expansion: 1. Use the EXPAND command to expand and copy the driver named SSTOR.SY_ to your hard disk from Disk 6 for 5.25" disks or Disk 3 for 3.5" disks. Name the driver SSTOR.SYS. 2. If you have a DEVICE=HARDRIVE.SYS command in your CONFIG.SYS file, replace it with a DEVICE=SSTOR.SYS command. 3. Type the following: setup /u 2.6 Novell Partitions --------------------- If your system includes Novell partitions, upgrade to MS-DOS 5.0 by typing the following: setup /u 2.7 Vfeature Deluxe ------------------- Contact Golden Bow Systems for information about Vfeature upgrades. Alternately, you can install MS-DOS 5.0 on floppy disks or delete Vfeature partitions by repartitioning your hard disk. For information about installing on floppy disks and deleting partitions on your hard disk, see the Microsoft MS-DOS Getting Started guide. 2.8 Columbia Data Systems Device Driver --------------------------------------- If you use a Columbia Data Systems device driver, do the following: 1. Remove the DEVICE=SSTBIOS.SYS and DEVICE=SSTDRIVE.SYS commands from your CONFIG.SYS file before running Setup. 2. Restart your system. 3. Run Setup. 4. Reinstall the device drivers by returning the DEVICE= commands to your CONFIG.SYS file and restarting your system. 2.9 Incompatible Partition -------------------------- If Setup referred you to this section, and no other section in part 2 of the readme is relevant to your system, you have a partition that is incompatible with MS-DOS 5.0. You must delete the partition from your hard disk. See the procedure for repartitioning your hard disk in Chapter 4 of the Microsoft MS-DOS Getting Started guide. 2.10 WYSE Partition ------------------- If you have partitions created by WYSE DOS 2.11 or 3.1, you must delete them from your hard disk before running Setup. See the procedure for repartitioning your hard disk in Chapter 4 of the Microsoft MS-DOS Getting Started guide. 2.11 286 Accelerator Card ------------------------- If your system includes a 286 accelerator card, Setup may not be able to determine the amount of extended memory you have and may incorrectly install MS-DOS 5.0. If this occurs, disable the card before running Setup. If you can't disable the card, install MS-DOS 5.0 manually. For information about manually installing MS-DOS 5.0, see the Microsoft MS-DOS Getting Started guide. 2.12 Bernoulli Cache -------------------- Before running Setup, do the following: 1. Remove the CONFIG.SYS DEVICE= command that installs the caching software for your Iomega Bernoulli drive. 2. Restart your system. 3. Run Setup. 4. Reinstall the caching software by returning the DEVICE= command to your CONFIG.SYS file and restarting your system. 2.13 AT&T 6300 Computer ----------------------- If you use an AT&T 6300 computer and your ROM BIOS is version 1.20 or earlier, contact your vendor for a ROM BIOS upgrade. The ROM BIOS version number is displayed when you start your computer. 2.14 Western Digital SCSI Hard-Disk Controller ---------------------------------------------- If you are using a Western Digital WD 7000 FASST or AT/XT SCSI controller with hard-disk ROM version 3.35 or earlier, contact your vendor for an upgrade before installing MS-DOS 5.0. The ROM version number is displayed when you start your computer. 2.15 Machine-Specific HIMEM.SYS Switches ---------------------------------------- Before you install MS-DOS 5.0 on a system listed in this section, you must edit your CONFIG.SYS file as follows: 1. If there is no DEVICE=HIMEM.SYS command, add it to your CONFIG.SYS file, provided you have extended memory and don't have an extended-memory manager. 2. 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 3. 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 Toshiba 5100 /machine:7 UNISYS PowerPort /machine:2 2.16 Toshiba T1600 and a Hard RAM Disk -------------------------------------- To use the hard RAM disk, do the following before installing MS-DOS 5.0: 1. Back up your hard RAM disk. 2. Using the Toshiba Setup program, delete the hard RAM disk by allocating zero KB to it. All data on the hard RAM disk will be lost. 3. Restart your system. 4. Install MS-DOS 5.0. 5. Use 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. 2.17 Unix And Xenix Partitions ------------------------------ If your system includes Unix or Xenix partitions in addition to standard DOS partitions, and you receive a message saying a partition is incompatible with MS-DOS 5.0, install MS-DOS 5.0 by typing the following: setup /u 2.18 Apricot XEN-S Computer --------------------------- To install MS-DOS 5.0 on an Apricot XEN-S computer: 1. Remove the DEVICE=AEMM386.SYS command from your CONFIG.SYS file. 2. Restart your system. 3. Run Setup. 4. Put the DEVICE=AEMM386.SYS command back in your CONFIG.SYS file and restart your system. 2.19 Installing MS-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 MS-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 MS-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). 2.20 4DOS --------- Setup replaces the SHELL command in your CONFIG.SYS file with one that invokes COMMAND.COM. To recover your 4DOS SHELL command, retrieve it from the original CONFIG.SYS file, which is saved as CONFIG.DAT on your Uninstall disk. If external DOS utilities display messages that refer to error numbers, contact JP Software for an upgrade. 2.21 8514 Display Adapters -------------------------- If you install MS-DOS 5.0 on a system that includes an 8514 display adapter, do the following after completing the MS-DOS 5.0 installation: 1. Check the PACKING.LST file to determine which disk has VGA.GR_ and EGA.VI_ files. 2. Use the EXPAND command to expand and copy the VGA.GR_ file from the disk to your DOS directory. Name the file DOSSHELL.GRB. 3. Use the EXPAND command to expand and copy the EGA.VI_ file from the disk to your DOS directory. Name the file DOSSHELL.VID. 3. NOTES ON MEMORY MANAGEMENT ============================= 3.1 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, see Chapter 14 of the MS-DOS User's Guide and Reference. 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 5.0. 3.2 All Computers Inc. Expanded-Memory Driver (ALLEMM4.SYS) ----------------------------------------------------------- Version 2.5 or later of the All Computers expanded-memory driver (ALLEMM4.SYS) is compatible with MS-DOS 5.0 HIMEM.SYS. Contact All Computers to get an updated driver. 3.3 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. 3.4 Installing HIMEM.SYS ------------------------ Setup does not install HIMEM.SYS if another extended-memory manager is active. If you want to install HIMEM.SYS, copy it to your disk by doing the following: 1. Check the PACKING.LST file to determine which disk has the HIMEM.SY_ file. 2. Use the EXPAND command to expand and copy the file to your hard disk. Name the file HIMEM.SYS. 3.5 Intel Expanded-Memory Driver (EMM.SYS) ------------------------------------------ Use the Intel expanded-memory driver NE or E switch when installing an Aboveboard driver. See your Aboveboard documentation for more information. 3.6 Phoenix BIOS and HIMEM.SYS ------------------------------ If your system includes a Phoenix BIOS and MS-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. 3.7 XMAEM.SYS and XMA2EMS.SYS ----------------------------- Setup disables the CONFIG.SYS commands that load 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 includes an XMA card, remove the REM command that precedes the DEVICE=XMA2EMS.SYS command in your CONFIG.SYS file. 4. NOTES ON WINDOWS =================== 4.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. 4.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 4.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. 4.4 Windows/286 2.1 ------------------- If you run Windows/286 2.1 with MS-DOS 5.0, use PIF Editor to specify a value of 128 in the KB Required option for COMMAND.COM. For information about using PIF Editor and PIF options, see the Microsoft Windows User's Guide. 4.5 "High Memory Area in Use" Message (Windows/386 2.1) ------------------------------------------------------- You cannot run Windows/386 2.1 when MS-DOS 5.0 is loaded into the high memory area. Also, the MS-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 MS-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. 4.6 "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 SMARTDrive, try setting the MinCacheSize parameter to 0. 5. MAKING YOUR HARDWARE COMPATIBLE WITH MS-DOS 5.0 ================================================== 5.1 Acer 1100/33 and CTRL+ALT+DEL --------------------------------- If you have an Acer 1100/33 computer with an Award BIOS, you may not be able to restart your system by using CTRL+ALT+DEL. Contact Acer for a ROM BIOS upgrade. 5.2 Amstrad Systems and KEYB.COM -------------------------------- If your Amstrad system has a ROM BIOS version earlier than 1.4, and you can't use your keyboard after loading KEYB.COM, contact your vendor for a ROM BIOS upgrade. 5.3 Apricot Qi 386 Systems -------------------------- If your Apricot Qi 300 fails to start while loading EMM386.EXE, contact Apricot for a ROM BIOS upgrade. Some Apricot Qi660 and Qi900 computers may not work if MS-DOS 5.0 is loaded into the high memory area. Run MS-DOS 5.0 in conventional memory, or contact Apricot Computers for more information. 5.4 Arrow Keys and QBasic/MS-DOS Editor --------------------------------------- If you can't use the arrow keys on your numeric keypad when running QBasic or MS-DOS Editor, a memory-resident program named FIXSHIFT.COM may help. To obtain FIXSHIFT.COM, call Microsoft Product Support Services; see your registration card for the phone number. 5.5 AT&T Computer with an VDC 750 Display Adapter Card ------------------------------------------------------ Before using the MS-DOS Shell Task Swapper on an AT&T computer with a VDC 750 display adapter card, remove the DEVICE=EGA.SYS command from your CONFIG.SYS file. 5.6 Commodore PC III and Task Swapper ------------------------------------- You may not be able to use Task Swapper in MS-DOS Shell on a Commodore PC III. 5.7 Compaq EXTDISK.SYS Driver ----------------------------- The Compaq EXTDISK.SYS driver is incompatible with MS-DOS 5.0. Contact your system vendor for an upgrade. 5.8 Corel Systems Disk Drivers ------------------------------ If your Corel Systems disk driver doesn't work correctly, contact your vendor for an upgrade. 5.9 External Floppy Disk Drives ------------------------------- If you can't use your Nth, Procomm, or Sysgen external floppy disk drive, contact your vendor for an update. 5.10 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 the BIOS addresses that Hardcard II or Hardcard II XL uses. See the MS-DOS User's Guide and Reference for more information about the exclude switch. 5.11 NCR VGA BIOS ----------------- If you have an NCR VGA BIOS and can't switch between screens when running MS-DOS Shell or QBasic, see your NCR manual for information about making your VGA BIOS PS/2 compatible. 5.12 Olivetti System with a CGA Video Board ------------------------------------------- An Olivetti 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. 5.13 Toshiba T3100SX -------------------- Toshiba T3100SX computer's suspend/resume feature is incompatible with EMM386.EXE. Either disable the feature or do not use EMM386.EXE. 5.14 Using a Mouse with 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 5.15 Western Digital VGA Card ----------------------------- If you have a Western Digital VGA card and are using RAMBIOS.EXE and RAMBIOS.SYS, load RAMBIOS.SYS before ANSI.SYS and DISPLAY.SYS in your CONFIG.SYS file, and RAMBIOS.EXE before GRAPHICS.COM in your AUTOEXEC.BAT file. 5.16 WonderCard 3.x ------------------- Using MS-DOS 5.0 with an ATI WonderCard 3.x in 50-line mode may cause the lower part of your display to be truncated. Contact your vendor for more information. 5.17 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. 5.18 Zenith Computer -------------------- To use the GRAPHICS command with a Zenith computer, set the STACKS command in your CONFIG.SYS file to at least STACKS=9,256. For information about the STACKS command, see Chapter 14 of the MS-DOS User's Guide and Reference. 5.19 Zeos 486 and Task Swapper ------------------------------ If you have a Zeos 486 computer with a Mylex BIOS, you may not be able to use Task Swapper in MS-DOS Shell. Contact Zeos for a ROM BIOS upgrade. 6. MAKING YOUR NETWORK COMPATIBLE WITH MS-DOS 5.0 ================================================= 6.1 MS-DOS Shell and Networks ----------------------------- Most network software won't work correctly if you start it from a MS-DOS Shell command prompt. Start your network before starting MS-DOS Shell. 6.2 3+Share ------------ If you installed 3Com 3+Share with minimal NetBIOS implementation, do one of the following: * Reinstall with a complete NetBIOS implementation. * Use the REDIR.400 file to replace the MSREDIR.EXE file on your hard disk. * Call Microsoft Customer Service and request the LAN Manager 2.0 supplemental disk; see your registration card for the phone number. 6.3 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. 6.4 Microsoft LAN Manager 2.0 Enhanced -------------------------------------- If you are running Microsoft LAN Manager 2.0 Enhanced or an OEM version of LAN Manager 2.0 Enhanced, you may want to take advantage of any remaining space in the upper memory area to load LAN Manager services such as NETPOPUP in this area. Call Microsoft Customer Service to request the LAN Manager 2.0 supplemental disk and technical notes. See your registration card for the phone number. If you are running Microsoft LAN Manager 2.0 Enhanced and get a "NET3055" message, do one of the following: * Use the EMM386 /ram switch and the LIM=YES command in the [workstation] section of your LANMAN.INI file. OR * If you use the EMM386 /noems switch, use the LIM=NO command in the [workstation] section of your LANMAN.INI file. 6.5 Net/One PC -------------- If Ungermann-Bass 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. 6.6 Novell Networks ------------------- NetWare Shell Version: The NetWare workstation shell software is Novell's basic DOS shell and is included with MS-DOS 5.0. You may require a different shell for a specific application. Contact your authorized Novell reseller if you believe another shell may be needed. EMSNET5.EXE and XMSNET5.EXE, alternate shells, are available from Novell. Novell Remote Workstations (RPLFIX.COM): If you can't load MS-DOS 5.0 on your remote-boot workstation, contact Novell for an upgrade of your remote-boot software. Drive Mapping Utilities: If you run LOGIN.EXE, MAP.EXE, and SESSION.EXE from MS-DOS Shell or while MS-DOS Shell is running, a search path is not added to the existing path. Use these programs before starting MS-DOS Shell. COMSPEC Variable: If you use the Novell login program to set the COMSPEC variable after starting MS-DOS 5.0, and you can't reload the COMMAND.COM file, 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. TBMI2.COM and Task Swapper: If you can't use Task Swapper in MS-DOS Shell when running a Novell network, do the following: 1. Expand and copy the IPX.OB_ and TBMI2.CO_ files from Disk 6 for 5.25" disks or from Disk 3 for 3.5" disks. 2. Rename the files IPX.OBJ and TBMI2.COM. 3. Use the IPX.OBJ file to create a new IPX.COM file. For information about creating an IPX.COM file, see your Novell documentation. 4. Start your network, using the new IPX.COM and NET5.COM files. 5. Start TBMI2.COM. 6. Start the application that may be causing problems with Task Swapper. Run the application and then exit. 7. Display diagnostic information by typing the following: tbmi2 /d 8. If the value in the field named Far Call Usage is not 0, you need to run TBMI2.COM before using Task Swapper. To get help with TBMI2.COM, type the following: tbmi2 /? The default configuration for TBMI2.COM is correct for most applications. If you need help configuring the program, contact Novell. TBMI2.COM and Windows: Don't run TBMI2.COM if you are using Windows 3.0. 6.7 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. 6.8 TOPS Network ---------------- If your system is a TOPS workstation, the MS-DOS Shell MOVE command may not work. Don't use the LOADHIGH command with a TOPS network. 7. DOCUMENTATION CORRECTIONS AND ADDITIONS ========================================== 7.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. 7.2 Documentation Corrections ----------------------------- The following are corrections to the Microsoft MS-DOS User's Guide and Reference: COMP /? Help: Online help for the COMP command /d switch should state that the default format is hexadecimal. EXPAND Command: The example in Chapter 4 of the Microsoft MS-DOS Getting Started guide refers to the wrong 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. 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 MS-DOS Shell. UNFORMAT Command: The UNFORMAT /p switch is not compatible with the /j switch. 7.3 Hercules Display Adapter (MSHERC.COM) ----------------------------------------- If you use MS-DOS Editor or QBasic with a Hercules display adapter, run MSHERC.COM before you run either program. 7.4 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 7.5 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 by the system's ROM BIOS. If you have partitions created by using third-party disk-partitioning software, 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.