Scandisk vs. CHKDSK


R

Richard Fangnail

Did CHKDSK basically phase out Scandisk?

XP does not have Scandisk at all. Did some OSs have both?

Before Windows 2000, didn't Scandisk automatically run if there was an
abnormal shutdown?
 
Ad

Advertisements

R

Richard Urban

Windows XP has a most comprehensive help system that tells you all about
chkdsk.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
C

ColTom2

Hi:

Yes - Prior to XP it was Scandisk and with XP it's CHKDSK. No systems have
both and yes again to your last question about abnormal shutdown.



Did CHKDSK basically phase out Scandisk?

XP does not have Scandisk at all. Did some OSs have both?

Before Windows 2000, didn't Scandisk automatically run if there was an
abnormal shutdown?
 
B

Bruce Chambers

ColTom2 said:
Hi:

Yes - Prior to XP it was Scandisk and with XP it's CHKDSK.


That's incorrect. WinXP is descended from WinNT, via Win2K, neither of
which ever had Scandisk. Chkdsk has always been the norm. Scandisk was
used on the now defunct Win9x family of operating systems.




--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
 
Ad

Advertisements

K

Ken Blake, MVP

ColTom2 said:
Hi:

Yes - Prior to XP it was Scandisk and with XP it's CHKDSK. No
systems have both and yes again to your last question about abnormal
shutdown.


It's not a matter of "Prior to XP." In all versions of Windows NY, including
Windows 2000 and WIndows XP, it's always been chkdsk. It was also chkdsk in
DOS.

In Windows 9X, it was scandisk.
 
G

Gerry Cornell

Bruce

IMO scandisk had a better user interface than chkdsk.

--


Regards.

Gerry

~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
 
D

David Candy

This is from my reference to scandisk at www.mvps.org/serenitymacros/winprogs.html
It shows the difference between Scandisk for Dos and Scandisk for Windows. Without knowing how Chkdsk fixes disks (dos or windows fashion) I hypothsis that it may be better to use this to rescue a disk.
Runs the ScanDisk disk-repair program.

To check and repair a drive, use the following syntax:

Scandisk
SCANDISK [drive: | drive:\DRVSPACE.nnn]

Drive: Drive to check
drive:\DRVSPACE.nnn The unmounted drivespace drive to check. This is the only way to check an unmounted drivespace in Windows.
None Checks and repair the current drive
/All Checks and repairs all local drives.
/Autofix Fixes damage without prompting.
/Checkonly Checks a drive, but does not repair any damage.
/Custom Configures and runs ScanDisk according to SCANDISK.INI settings.
/Nosave With /AUTOFIX, deletes lost clusters rather than saving as files.
/Nosummary With /CHECKONLY or /AUTOFIX, prevents ScanDisk from stopping at summary screens.
/Surface Performs a surface scan after other checks.
/Mono Configures ScanDisk for use with a monochrome display.
/Fragment [drive:][path] filename Examine a file for fragmentation: Works in Windows
/Undo [drive:] To undo repairs you made previously. Where [drive:], specifes the drive containing your Undo disk.
/Time Monitor the average read, write, and seek times during surface analysis. This detects sectors that are about to go bad but can still be read. This is the same as ScanTimeOuts in scandisk.ini.
/Text Runs Scandisk as a MS-Dos prompt command. Can check but not fix problems.
/Help Displays command line help.
/Noui /Clip /Nolost /Mount /New

Scandisk at Startup
When Windows detects that it hasn't shut down properly it sets the bit 4 of byte 8 of the FAT, if it detects a disk error it sets bit 3. Win.com will run Scandisk at the next boot.

By coping another file and calling it Scandisk.alt into the Windows\Command directory Win.com will execute this file instead.

Editing MSDos.sys in the root directory can control if Scandisk is run or not. The [Options] section should be there already, don't duplicate.

[Options]
Autoscan=20 Never
1 After prompting
2 Always.

Scandisk.Ini
See Scandisk.ini in the Windows\Command directory for customising how Scandisk runs when started with the /custom switch. This is a fully commented file.

Only Scandisk uses Scandisk.ini, Scandskw doesn't.

Click here for your Scandisk.ini (assumes you've installed Windows to C:\Windows)

ScandskW.
Scandskw should be used if you have disk problems and can start Windows. There are two copies of the FAT on every disk. These track what parts of the disk the file is on. Where the beginning of the file starts is stored in the directory and the rest of it including the end is stored in the FAT. Dos and Windows only use the first FAT and copies it to the second as a backup.

Scandisk only uses the first FAT to repair disks and copies it over the second after it repairs it. Scandskw uses both FATS to make repairs, using the best information from each.

Scandskw [Drive] [/Allfixeddisks] [/Noninteractive] [/Preview] [/Oldfs] [/Silent] [/Sageset:x] [/Sagerun:x]

Drive The drive or drives to test.
/Allfixeddisks Test all fixed disks.
/Noninteractive Doesn't pause for additional user information. Displays summary screens.
/Preview Test but doesn't fix any errors.
/Oldfs Changes the File System to normal Dos. Removes all long file names.Destructive, can't be undone.Must be run from a Command Prompt.
/Silent Exits without displaying summary screens.
/Sageset:x Display the System Agent-Aware Setting dialog box and store the settings in the SETn registry key.
/Sagerun:x Runs in unattended mode using the System Agent-aware settings in the SETn registry key.

Scandskw is only a starter application. Dskmaint.dll does all the work.

Registry Settings
Scandskw stores it's settings under the following registry key.

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Applets\CheckDrive "Settings"=hex:nn,nn,nn,nn

Where the numbers read from right to left.

Add the numbers from the chart below using calculator in hex mode, pad it out to 8 digits with leading zeros and reverse it.

Type of test
Standard test &1
Through test &0
Automatically fix errors
Areas of the disk to scan
Scan system & data areas &0
Scan system areas only &80
Scan data areas only &40
Do not perform write testing Not stored
Do not repair sectors in hidden and system files &3 000
Display Summary
Always &0
Never &10
Only if errors found &40 000
Log file
Replace log &0
Append to log &10 000 000
No log &80 000
Cross linked files
Delete &4 000
Make copies &2 000
Ignore &0
Lost file fragments
Free &0
Convert to files &2
Check files for
(Don't check) Invalid file names &4
Invalid dates and times &8
Duplicate names &2 000 000
(Don't check) Check Host &2 000
Report MS-Dos mode name length errors &40 000
Can only be set in registry
Retest sectors marked badThis is not a setting that should be used unless you have marked sectors bad accidently.Normally sectors are marked bad because they are unreliable. &40 000 000

Task Scheduler
This section tell Task Scheduler that Scandskw is a Task Scheduler aware program (it recognises sageset and sagerun command line parameters).

REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Plus!\SystemAgent\SAGE\Scandisk for Windows]
"Settings"=hex:01
"Program"="SCANDSKW.EXE"
"FriendlyName"="ScanDisk for Windows"
These are the codes scandskw returns when it finishes running. Task Scheduler prints the string in schedlog.txt.

[HKEY_LOCAL_MACHINE\Software\Microsoft\Plus!\SystemAgent\SAGE\Scandisk for Windows\Result Codes]
"Success"="1"
"0"="No errors found"
"1"="Errors found and all were fixed"
"249"="One or more drives could not be checked"
"250"="Drive could not be checked - could not load or find DSKMAINT.DLL"
"251"="Drive could not be checked - insufficient memory"
"252"="Errors were found and some were not fixed"
"254"="Check was canceled"
"255"="Check was stopped because of an error"
;This section is where the drives and options selected in the Task Scheduler Settings button are stored. The settings are the same as the table above. Set0 is the first Scandisk task in Task Scheduler, Set1 is the second, ect.
[HKEY_LOCAL_MACHINE\Software\Microsoft\Plus!\SystemAgent\SAGE\Scandisk for Windows\Set0]
"Settings"=hex:31,02,40,61
"DrivesToCheck"=hex:04,00,00,80
Batch files can also use these codes. Scandisk returns the same error codes. If running Scandskw use.

;Start /w scandskw <command line parameters fom table above eg /all /non /nosummary>or if running scandisk use

;scandisk <command line parameters fom table above eg /all /autofix /nosummary>and on the following line use this test. The second errorlevel test should always be one higher than the first.

If errorlevel 1 if not errorlevel 2 echo Errors found and all were fixed
 
G

Gerry Cornell

David

Are you recommending run the Windows 98 Scandisk in Windows XP?

Wouldn't the computer need to be dual booting and not NTFS formatted?
Can you install the Windows 98 Scandisk on to a Windows XP box?

The point I was making was that the chkdsk user interface in Windows XP
needs a total makeover!

--


Regards.

Gerry

~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~



"David Candy" <.> wrote in message
This is from my reference to scandisk at
www.mvps.org/serenitymacros/winprogs.html
It shows the difference between Scandisk for Dos and Scandisk for
Windows. Without knowing how Chkdsk fixes disks (dos or windows fashion)
I hypothsis that it may be better to use this to rescue a disk.
Snipped
 
Ad

Advertisements

D

David Candy

I meant to say on Fat32 drives. I posted it as a hypothsis.

It's pretty critical that repairs are conducted using both fats (if one is corrupted that will have errors and the other one doesn't then bingo your disk as good as new). Using one Fat can trash a disk. Scandisk for Windows and Norton's for Dos do both fat repairs. Scandisk for Dos doesn't. Chkdsk for XP is unknown.

What conclusion could be drawn from the above.
 
B

Bruce Chambers

Gerry said:
Bruce

IMO scandisk had a better user interface than chkdsk.


Scandisk may have had a prettier intererface, but that did nothing but
slow down the process.


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
 
N

NobodyMan

Wrong.

Scandisk was never supported in the NT family.

Scandisk Not currently supported. Use the chkdsk command, which enables
you to create and display a status report for a disk based on the file
system. Chkdsk also lists and corrects errors on the disk. For more
information about the chkdsk command:-
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx

regards,
S.Sengupta[MS-MVP]

Richard said:
Did CHKDSK basically phase out Scandisk?

XP does not have Scandisk at all. Did some OSs have both?

Before Windows 2000, didn't Scandisk automatically run if there was an
abnormal shutdown?
 
Ad

Advertisements

S

S.Sengupta

I know.I was speaking exclusively for XP in my post.

regards,
S.Sengupta[MS-MVP]


Wrong.

Scandisk was never supported in the NT family.

Scandisk Not currently supported. Use the chkdsk command, which enables
you to create and display a status report for a disk based on the file
system. Chkdsk also lists and corrects errors on the disk. For more
information about the chkdsk command:-
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx

regards,
S.Sengupta[MS-MVP]

Richard Fangnail wrote:

Did CHKDSK basically phase out Scandisk?

XP does not have Scandisk at all. Did some OSs have both?

Before Windows 2000, didn't Scandisk automatically run if there was an
abnormal shutdown?
 
G

Gerry Cornell

Bruce

Neither prettier interface or process speed are essential to a good
tool! A good tool is one that the user finds easy to use and understand
AND which does a good job. It is not easy for a user to know what chkdsk
is going to do or what it has found and done about it! It fails on "and
understand". It is relatively easy to use and probably does a good job.

--


Regards.

Gerry

~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
 
Ad

Advertisements

B

Bruce Chambers

Gerry said:
Bruce

A good tool is one that the user finds easy to use and understand
AND which does a good job.


I'd say that we have conflicting views of what a good tool is. A good
tool is one that does exactly what it is designed to do (no more and no
less) with a minimum of fuss and superfluousness.

A "tool-user" too lazy to learn how to understand and safely use a tool
shouldn't use it. This principle applies whether one is discussing a
hammer, power saw, or a software utility.



--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top