XP error checker?

  • Thread starter Thread starter jll
  • Start date Start date
J

jll

Hi,
Is there a way to make the XP disk error checker generate a short summary
report the way scandisk does in Win 98?
Thanks,
jll
addy is fake
 
What do both of you mean? Everyone else gets a summary.

C:\Program Files\Support Tools>chkdsk d:
The type of the file system is NTFS.
Volume label is Setup.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

17647370 KB total disk space.
15510428 KB in 65626 files.
15580 KB in 5031 indexes.
0 KB in bad sectors.
151622 KB in use by the system.
65536 KB occupied by the log file.
1969740 KB available on disk.

4096 bytes in each allocation unit.
4411842 total allocation units on disk.
492435 allocation units available on disk.

C:\Program Files\Support Tools>
 
Thanks, that was fast. Now for a followup. How can I extract scandisk. exe
from the Win 98 CD and will it work in XP?
Thanks,
 
jll said:
Thanks, that was fast. Now for a followup. How can I extract scandisk. exe
from the Win 98 CD and will it work in XP?

I doubt it would work... Assuming your drivers are NTFS (drive properties
in my computer) and not FAT32 you really don't need to worry about this sort
of stuff anymore, as NTFS is far more resilient.

If you are after a summary, like David said, run checkdisk through the
command prompt.

--
Paul Smith,
Yeovil, UK.
http://www.windowsresource.net/

*Remove 'nospam.' to reply by e-mail*
 
That's what appears whilst it's running but what I and I think the OP means
is a text file with the results of the scan telling what, if any, errors
were fixed, bad sectors etc.

--
Kenny Cargill


"David Candy" <.> wrote in message
What do both of you mean? Everyone else gets a summary.

C:\Program Files\Support Tools>chkdsk d:
The type of the file system is NTFS.
Volume label is Setup.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

17647370 KB total disk space.
15510428 KB in 65626 files.
15580 KB in 5031 indexes.
0 KB in bad sectors.
151622 KB in use by the system.
65536 KB occupied by the log file.
1969740 KB available on disk.

4096 bytes in each allocation unit.
4411842 total allocation units on disk.
492435 allocation units available on disk.

C:\Program Files\Support Tools>
 
I've been doing it my old way, i.e. highlight the drive> properties> tools>
error checking. When I do that I don't get the summary. I'll try the
suggested way. As for the second question, I'm using NTFS and as you say it
won't work.
Thanks,
 
If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | OK |
Click System | Look at any Windows File Protection
entries

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
It doesn't matter how you run chkdsk.exe, you still get the log in Event
Viewer.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | OK
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration. But
there is no reason to do this, unless you just want to compare what is in
the Bootex.log and what you see in the Event Viewer.
-----

Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the drive you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

Automatically fix file system errors
Runs Chkdsk by using the /f parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked.]]

Scan for and attempt recovery of bad sectors
Runs Chkdsk by using the /r parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All files
must be closed for this program to run. If the drive is currently in use, a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not need
to select Automatically fix file system errors. Windows fixes any errors on
the disk.]]
-----

The following will create an actual, separate chkdsk log in Notepad.

Assuming the drive is C:...

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From:
Doug Knox <[email protected]>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
It will not work. The program in XP is Chkdsk. Scandisk is for the
Win9x/ME architecture. Chkdsk is for the WinNT family. XP is not descended
from Win98 at all. Different OS.
 
It's only in event viewer if it runs at boot.

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
Wesley Vogel said:
It doesn't matter how you run chkdsk.exe, you still get the log in Event
Viewer.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | OK
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration. But
there is no reason to do this, unless you just want to compare what is in
the Bootex.log and what you see in the Event Viewer.
-----

Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the drive you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

Automatically fix file system errors
Runs Chkdsk by using the /f parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked.]]

Scan for and attempt recovery of bad sectors
Runs Chkdsk by using the /r parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All files
must be closed for this program to run. If the drive is currently in use, a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not need
to select Automatically fix file system errors. Windows fixes any errors on
the disk.]]
-----

The following will create an actual, separate chkdsk log in Notepad.

Assuming the drive is C:...

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From:
Doug Knox <[email protected]>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
jll said:
I've been doing it my old way, i.e. highlight the drive> properties>
tools> error checking. When I do that I don't get the summary. I'll try
the suggested way. As for the second question, I'm using NTFS and as you
say it won't work.
Thanks,
 
jll said:
Thanks, that was fast. Now for a followup. How can I extract scandisk. exe
from the Win 98 CD and will it work in XP?

Perhaps, and no.

--

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
 
You have a point there. My statement was wrong.

I have never run chkdsk at any other time but at boot. Why would you run
chkdsk except at boot? Why would you run chkdsk at all except to fix
errors on the disk?

[[If you want chkdsk to correct disk errors, you cannot have open files on
the drive.]] You have to reboot in order for chkdsk to correct any disk
errors.

I suppose you could run Chkdsk /X. I'll have to try that and see what
happens.
-------

C:\>CHKDSK C: /X
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
David Candy said:
It's only in event viewer if it runs at boot.

--
-------------------------------------------------------------------------- ------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
Wesley Vogel said:
It doesn't matter how you run chkdsk.exe, you still get the log in Event
Viewer.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | OK
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled
it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked. The
Winlogon service then moves the contents of each Bootex.log file to the
Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt
and is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration.
But there is no reason to do this, unless you just want to compare what
is in the Bootex.log and what you see in the Event Viewer.
-----

Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the drive you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

Automatically fix file system errors
Runs Chkdsk by using the /f parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive
is currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is not available to run other tasks while the disk is being
checked.]]

Scan for and attempt recovery of bad sectors
Runs Chkdsk by using the /r parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All
files must be closed for this program to run. If the drive is currently
in use, a message asks if you want to reschedule the disk checking for
the next time you restart your computer. Your drive is not available to
run other tasks while the disk is being checked. If you select this
option, you do not need to select Automatically fix file system errors.
Windows fixes any errors on the disk.]]
-----

The following will create an actual, separate chkdsk log in Notepad.

Assuming the drive is C:...

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From:
Doug Knox <[email protected]>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
jll said:
I've been doing it my old way, i.e. highlight the drive> properties>
tools> error checking. When I do that I don't get the summary. I'll try
the suggested way. As for the second question, I'm using NTFS and as you
say it won't work.
Thanks,

jll wrote:
Thanks, that was fast. Now for a followup. How can I extract
scandisk. exe from the Win 98 CD and will it work in XP?
Thanks,

I asked the same question here recently and was told no.

--
Kenny Cargill


Hi,
Is there a way to make the XP disk error checker generate a short
summary report the way scandisk does in Win 98?
Thanks,
jll
addy is fake

will it work in XP?

NO!
 
But if you have multiple partition ....

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
Wesley Vogel said:
You have a point there. My statement was wrong.

I have never run chkdsk at any other time but at boot. Why would you run
chkdsk except at boot? Why would you run chkdsk at all except to fix
errors on the disk?

[[If you want chkdsk to correct disk errors, you cannot have open files on
the drive.]] You have to reboot in order for chkdsk to correct any disk
errors.

I suppose you could run Chkdsk /X. I'll have to try that and see what
happens.
-------

C:\>CHKDSK C: /X
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
David Candy said:
It's only in event viewer if it runs at boot.

--
-------------------------------------------------------------------------- ------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
Wesley Vogel said:
It doesn't matter how you run chkdsk.exe, you still get the log in Event
Viewer.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | OK
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled
it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked. The
Winlogon service then moves the contents of each Bootex.log file to the
Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt
and is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration.
But there is no reason to do this, unless you just want to compare what
is in the Bootex.log and what you see in the Event Viewer.
-----

Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the drive you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

Automatically fix file system errors
Runs Chkdsk by using the /f parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive
is currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is not available to run other tasks while the disk is being
checked.]]

Scan for and attempt recovery of bad sectors
Runs Chkdsk by using the /r parameter.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All
files must be closed for this program to run. If the drive is currently
in use, a message asks if you want to reschedule the disk checking for
the next time you restart your computer. Your drive is not available to
run other tasks while the disk is being checked. If you select this
option, you do not need to select Automatically fix file system errors.
Windows fixes any errors on the disk.]]
-----

The following will create an actual, separate chkdsk log in Notepad.

Assuming the drive is C:...

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From:
Doug Knox <[email protected]>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In jll <[email protected]> hunted and pecked:
I've been doing it my old way, i.e. highlight the drive> properties>
tools> error checking. When I do that I don't get the summary. I'll try
the suggested way. As for the second question, I'm using NTFS and as you
say it won't work.
Thanks,

jll wrote:
Thanks, that was fast. Now for a followup. How can I extract
scandisk. exe from the Win 98 CD and will it work in XP?
Thanks,

I asked the same question here recently and was told no.

--
Kenny Cargill


Hi,
Is there a way to make the XP disk error checker generate a short
summary report the way scandisk does in Win 98?
Thanks,
jll
addy is fake

will it work in XP?

NO!
 
Aha!

I have to start learning to think outside the box.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
David Candy said:
But if you have multiple partition ....

--
-------------------------------------------------------------------------- ------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
Wesley Vogel said:
You have a point there. My statement was wrong.

I have never run chkdsk at any other time but at boot. Why would you run
chkdsk except at boot? Why would you run chkdsk at all except to fix
errors on the disk?

[[If you want chkdsk to correct disk errors, you cannot have open files
on the drive.]] You have to reboot in order for chkdsk to correct any
disk errors.

I suppose you could run Chkdsk /X. I'll have to try that and see what
happens.
-------

C:\>CHKDSK C: /X
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
David Candy said:
It's only in event viewer if it runs at boot.

--
------------------------------------------------------------------------ --
------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
================================================= "Wesley Vogel"
It doesn't matter how you run chkdsk.exe, you still get the log in
Event Viewer.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | OK
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID,
and volume name or serial number to help determine what volume Chkdsk
ran against. Also included is whether Chkdsk ran because a user
scheduled it or because the dirty bit was set.]]

[[When Autochk runs against a volume at boot time it records its output
to a file called Bootex.log in the root of the volume being checked.
The Winlogon service then moves the contents of each Bootex.log file
to the Application Event log.]]

[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt
and is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration.
But there is no reason to do this, unless you just want to compare what
is in the Bootex.log and what you see in the Event Viewer.
-----

Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the drive you want
to check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

Automatically fix file system errors
Runs Chkdsk by using the /f parameter.
[[Specifies whether Windows repairs file-system errors found during
disk checking. All files must be closed for this program to run. If
the drive is currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is not available to run other tasks while the disk is being
checked.]]

Scan for and attempt recovery of bad sectors
Runs Chkdsk by using the /r parameter.
[[Specifies whether Windows repairs file-system errors found during
disk checking, locates bad sectors, and recovers readable information.
All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule the disk
checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked. If
you select this option, you do not need to select Automatically fix
file system errors. Windows fixes any errors on the disk.]]
-----

The following will create an actual, separate chkdsk log in Notepad.

Assuming the drive is C:...

Paste this into a command prompt...

CHKDSK C: /F > C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From:
Doug Knox <[email protected]>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In jll <[email protected]> hunted and pecked:
I've been doing it my old way, i.e. highlight the drive> properties>
tools> error checking. When I do that I don't get the summary. I'll
try the suggested way. As for the second question, I'm using NTFS and
as you say it won't work.
Thanks,

jll wrote:
Thanks, that was fast. Now for a followup. How can I extract
scandisk. exe from the Win 98 CD and will it work in XP?
Thanks,

I asked the same question here recently and was told no.

--
Kenny Cargill


Hi,
Is there a way to make the XP disk error checker generate a short
summary report the way scandisk does in Win 98?
Thanks,
jll
addy is fake

will it work in XP?

NO!
 
Hi All,
Apparently my layout is different. I'm using XP Home SP 2. I don't have D.
Candy's Program arrangement. I have "Accessories"> System Tools and neither
Checkdsk nor error checker is listed. In Win 98, a tool could be added using
the 98 CD in Add/Remove. Can the same thing be done in XP? Can I use my
restore disks fromDell for this purpose?
Thanks,
 
Sorry if we're going around in circles, but that is what I do and have done
since Win 98. In 98 I got a brief summary of the scandisk results. In XP I
don't. You described a way to get the same thing in your version of XP. My
version is different. I don't have "support tools". I have "system tools" in
"Accessories" and chkdsk.exe is not there. Will typing chkdsk.exe in "run"
do it for me?
Thanks for going through this with me.
jll

"David Candy" <.> wrote in message
R/C the Drive and choose Properties - Tools
 

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

Transfer data SE to XP? 8
User accounts 1
New Motherboard 8
XP Part I 8
XP to Vista 13
DOS expert? 3
OE 6 8
Virtumonde spyware 2

Back
Top