Search results
Results from the WOW.Com Content Network
The chkdsk command on Windows XP. CHKDSK can be run from DOS prompt, Windows Explorer, Windows Command Prompt, Windows PowerShell or Recovery Console. [10] On Windows NT operating systems, CHKDSK can also check the disk surface for bad sectors and mark them (in MS-DOS 6.x and Windows 9x, this is a task done by Microsoft ScanDisk).
CHKDSK verifies a storage volume (for example, a hard disk, disk partition or floppy disk) for file system integrity. The command has the ability to fix errors on a volume and recover information from defective disk sectors of a volume. The command is available in MS-DOS versions 1 and later. [1]
It can be used to create/remove Host Protected Area (HPA) (using command SET MAX) and create/remove DCO hidden area (using command DCO MODIFY). It also can do other functions on the DCO. Data Synergy's freeware ATATool utility can be used to detect a DCO from a Windows environment. Recent versions allow a DCO to be created, removed or frozen. [3]
Also, while earlier versions of the technology only monitored hard drive activity for data that was retrieved by the operating system, this latest S.M.A.R.T. tests all data and all sectors of a drive by using "off-line data collection" to confirm the drive's health during periods of inactivity.
However, ScanDisk cannot check NTFS disk drives, and therefore it is unavailable for computers that may be running NT based (including Windows 2000, Windows XP, etc.) versions of Windows; for the purpose, a newer CHKDSK is provided instead. On Unix-like systems, there are tools like fsck_msdosfs [8] and dosfsck to do the same task.
The software is designed to find, test, diagnose and repair hard disk drives, reveal problems, display health and avoid failures by using S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) function of hard disk drives. [34] [35] [36] The detected information can be saved to file in formats such as HTML, text, or XML. [37] [38] [39]
The exact behaviors of various fsck implementations vary, but they typically follow a common order of internal operations and provide a common command-line interface to the user. On modern systems, fsck simply detects the type of filesystem and calls the specialized fsck. type (Linux) or fsck_ type (BSD, macOS) program for each type.
This could run many DOS and variously Win32, OS/2 1.x and POSIX command-line utilities in the same command-line session, allowing piping between commands. The user interface, and the icon up to Windows 2000, followed the native MS-DOS interface. The Command Prompt introduced with Windows NT is not actually MS-DOS, but shares some commands with ...