Microsoft Diagnostics

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:Microsoft Diagnostics Screenshot.png
Screenshot of the MSD utility displaying operating system information.

MSD (Microsoft Diagnostics) was a software tool developed by Microsoft to assist in the diagnostics of 1990s-era computers. Users primarily deployed this tool to provide detailed technical information about the user's software and hardware and to print the gathered information, usually for use by support technicians in troubleshooting and resolving problems.[1][2][3] The assumptions made by the program were valid until the late 1990s: it does not handle plug-and-play USB or other new technologies that appeared around 2000.

In PC DOS 6.1 and above, QCONFIG.EXE provides similar functionality.[4][5] Commercial alternatives include Manifest MFT.EXE from Quarterdeck's QEMM.

History

MSD first shipped with MS-Word for Windows, and was later included in Windows 3,[1] MS-DOS 6,[1][2][3] and on the Windows 9x CD-ROMs. Because OS/2 and Windows NT contain code forked from DOS at the DOS 5 level, the versions of MSD included here correspond to that of that era (i.e. version 2.0).

Windows NT 3 and 4 have WINMSD, a program with similar features.[6] However, the DOS/Windows specific functions were replaced by similar Windows NT concerns.[6] WINMSDP.EXE, included in the resource kits, provides the print functionality of MSD for WINMSD. Since NT 5 (Windows 2000), WINMSD.EXE has been a loader for MSINFO32.EXE.

Usage

Users generally started the program from the DOS Command Prompt using the command MSD.EXE.[1] Starting the program under a DOS window in either Windows or OS/2 shows only the DOS details allocated for that DOS session, not for the machine in general.[1]

Scope

Aspects of the system for which MSD provided technical information:

  1. computer brand and processor information[1][2][3]
  2. memory (total, EMS, and XMS)[1][2][3]
  3. video (type such as VGA and manufacturer)[1][2][3]
  4. network[1][2][3]
  5. operating-system versions[1][2][3]
  6. type of mouse (if installed)[1][2][3]
  7. disk drives (and partitions), excluding CD-ROM drives etc.
  8. LPT ports[1][2][3]
  9. COM ports[1][2][3]
  10. IRQ status[1][2][3]
  11. TSR programs[1][2][3]
  12. device drivers[1][2][3]
  13. other adapters[1][2][3]

Successor software

Microsoft replaced MSD with MSINFO32.EXE.[7] This has similar features, but targets more recent machines. It first appeared in MS-Word, and later was distributed with Plus! for Windows 95 and Windows 98.[7] MSINFO32.EXE under Windows XP stores system history from WMI in the XML files in Windows\PCHealth\HelpCtr\Datacoll.[8] In the interest of backward compatibility, WINMSD became a loader for MSINFO32.

See also

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 3.13 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.