Securing and Maintaining MS‑DOS Systems: Tools & Techniques

Troubleshooting MS‑DOS: Common Issues and Fixes for IT Professionals

1. Boot failures (no boot, NTLDR missing, or “Bad command or file name”)

• Cause: Missing or corrupt MS‑DOS system files (IO.SYS, MSDOS.SYS, COMMAND.COM) or wrong boot sector.
• Fix:
  1. Boot from a DOS boot floppy or MS‑DOS installation media.
  2. Run:

     Code
     Copy CodeCopied
     SYS C: 

     to transfer system files and rewrite the boot sector.

  3. If specific files are missing, copy them:

     Code
     Copy CodeCopied
     COPY A:\COMMAND.COM C:
     
     COPY A:\IO.SYS C:
     
     COPY A:\MSDOS.SYS C:
     
     

  4. If the boot sector is damaged, use a disk utility (FDISK /MBR on later DOS versions or a dedicated boot sector repair tool) to repair it.

2. File system errors and directory corruption

• Cause: Unexpected shutdowns, bad sectors, or disk aging leading to FAT corruption.
• Fix:
  1. Run CHKDSK (or SCANDISK on later DOS) from the boot floppy:

     Code
     Copy CodeCopied
     CHKDSK C: /F 

  2. If CHKDSK fails, image the disk and attempt repair with third‑party FAT recovery tools (e.g., PC‑Tools, Norton Utilities).
  3. Replace failing media and migrate data to a new drive; avoid continued writes to a failing disk.

3. Memory problems (UMB/XMS/EMS conflicts, “Out of memory”)

• Cause: Incorrect CONFIG.SYS or AUTOEXEC.BAT settings, TSRs consuming conventional memory, or faulty XMS/EMS drivers.
• Fix:
  1. Optimize CONFIG.SYS:
     • Use DEVICEHIGH for drivers where supported.
     • Load HIMEM.SYS for XMS memory:

       Code
       Copy CodeCopied
       DEVICE=C:\DOS\HIMEM.SYS 

     • Use EMM386.EXE for EMS/UMB if needed:

       Code
       Copy CodeCopied
       DEVICE=C:\DOS\EMM386.EXE NOEMS 

  2. Use LOADHIGH (LH) for TSRs in AUTOEXEC.BAT:

     Code
     Copy CodeCopied
     LH MOUSE.COM LH SMARTDRV.EXE 

  3. Remove unnecessary TSRs and drivers; test with a minimal boot (rename CONFIG.SYS/AUTOEXEC.BAT) to isolate the problem.

4. Hardware detection and driver issues (printers, mice, SCSI)

• Cause: Incorrect or missing device drivers, IRQ/DMA conflicts, or unsupported hardware.
• Fix:
  1. Verify correct drivers for the device and place them in C:\DOS or the device’s folder.
  2. Check CONFIG.SYS for proper DEVICE lines and AUTOEXEC.BAT for INIT or driver loads.
  3. For IRQ/DMA conflicts, reconfigure jumpers or BIOS settings (if present) or change driver parameters to use a different IRQ.
  4. For SCSI controllers, ensure proper SCSI host adapter DOS drivers and terminate SCSI chain correctly.

5. Slow disk performance

• Cause: No disk caching, fragmented files, or low‑quality drives.
• Fix:
  1. Enable SMARTDRV:

     Code
     Copy CodeCopied
     LH C:\DOS\SMARTDRV.EXE 

  2. Defragment files using DEFRAG utilities (third‑party defragmenters for DOS).
  3. Replace aging drives and use faster controllers where possible.

6. Boot floppy won’t read or floppy errors

• Cause: Dirty heads, bad media, or incompatible disk format.
• Fix:
  1. Try multiple known‑good floppies; clean drive heads.
  2. Recreate boot floppy from installation media: format and copy system files:

     Code
     Copy CodeCopied
     FORMAT A: /S COPY C:\DOS\COMMAND.COM A:
     
     COPY C:\DOS\IO.SYS A:
     
     COPY C:\DOS\MSDOS.SYS A:
     
     

  3. Verify disk type (720K vs 1.44MB) and use matching drive.

7. Configuring networking (NetBIOS, IPX, TCP/IP)

• Cause: Missing network drivers, incorrect protocol stacks, or incompatible client software.
• Fix:
  1. Install proper network card drivers and protocol stacks (e.g., Microsoft TCP/IP or IPX/SPX for Novell).
  2. Configure NET.CFG or PROTOCOL.INI as required; ensure NET START or relevant startup commands are in AUTOEXEC.BAT.
  3. Test with simple tools (PING, NET VIEW) and verify cabling and server compatibility.

8. Application incompatibilities and crashes

• Cause: Programs expecting specific DOS versions, memory model, or hardware.
• Fix:
  1. Run applications with recommended memory settings; provide required drivers.
  2. Use TSRs and CONFIG.SYS tweaks per vendor documentation.
  3. If possible, run the application in a clean DOS environment to isolate conflicts.

9. Keyboard layout and regional issues

• Cause: Wrong keymaps or country settings.
• Fix:
  1. Load the correct keyboard driver or keycode translation in CONFIG.SYS/AUTOEXEC.BAT.
  2. Replace or reconfigure COUNTRY.SYS if available:

     Code
     Copy CodeCopied
     DEVICE=C:\DOS\COUNTRY.SYS COUNTRY=044,850,C:\DOS\COUNTRY.SYS 

10. Preventive maintenance checklist

• Keep boot media and recovery tools updated and tested.
• Maintain at least one known‑good boot floppy and a system file backup.
• Document CONFIG.SYS and AUTOEXEC.BAT configurations for each machine.
• Regularly run CHKDSK and defragmentation on active systems.
• Replace aging storage and use stable power (UPS) where possible.

If you want, I can produce sample minimal CONFIG.SYS and AUTOEXEC.BAT files tailored to a common MS‑DOS 6.22 setup.