 | |
10-05-2003, 12:53 PM
|
#1 (permalink)
| | Registered User
Join Date: Aug 2003 Location: Canada
Posts: 197
| » 
WinXP Error-Checking question
I'm designing a program with numerous options and capabilities, one of these capabilities is opening Error-Checking. but i don't know the path to it, i know what it is for the Disk Defragmenter, but I also need the error checking path, does anyone know it?
Example:
Disk Defragmenter:
C:\WINDOWS\system32\dfrag.msc
I don't know if Error-checking is in the system32 folder, if it is, I'm blind because I couldn't find it in there. Where is it???
|
| |
10-07-2003, 11:46 PM
|
#2 (permalink)
| | Registered User
Join Date: May 2003 Location: Neo Japan
Posts: 1,175
|
Well i think you might want to reinstall your OS to recover stuff you lost in your computer. im sure you cant even defrag. all stuff looks like, becoming unstable. reinstalling wont harm any data in ur hdd. it'll be okay. inform us again if it turns back to normal
__________________
|c3R
|
| |
10-08-2003, 12:30 AM
|
#3 (permalink)
| | Registered User
Join Date: Aug 2003 Location: Canada
Posts: 197
|
huh? lol uh i think u're a bit confused, but thanks for replying
please re-read my question |
| |
10-09-2003, 02:00 AM
|
#4 (permalink)
| | Registered User
Join Date: May 2003 Location: Neo Japan
Posts: 1,175
|
Oh Sorry 
Well, what I mean is, after reinstalling ur Win xp, im sure the error-checking will be no longer exist. I do occur that sort of problem before though and I fixed it by reinstalling it. But there could be a better and easier way.
Somehow, last night after log on a cd, a serious error occured in my computer. It wanted to restart my pc again, to see whether the problem can be fixed. After restarting my pc, I cannot get into my Window but a message appears at msdos saying that my "/windows/system32/system.config/" may have been corrupt or missing. It then want me to fix that booting up CD-ROM first and press 'R' to repair the problem.
But the repairing is manually  I guess I have to make a new thread out of this one. At least, you still can access into your Window, well I can't! 
Gomen nasai meaning I'm sorry
__________________
|c3R
|
| |
10-09-2003, 10:50 AM
|
#5 (permalink)
| | Registered User
Join Date: Aug 2003 Location: Canada
Posts: 197
|
Okay, sorry. I think I may have asked the wrong question or I did not speficy what I was looking for...
I am looking for the Target Path of Error-Checking. What I mean by this, is the exact location where the Error-Checking Location is. For instance, if I had a shortcut on my desktop that was for Netscape, the Target Path would be "C:\Program Files\Netscape\Netscape\Netscp.exe". So, I would like to know the Target Path for Error-Checking. I don't want to know how to run Error-Checking because I know how, I would just like the exact path to Error-Checking for the WinXP Operating System.
I am not experiencing any problems with my computer, nor do I need help repairing anything, I would just like to know if anyone could tell me the Error-Checking path.
|
| |
10-09-2003, 11:22 AM
|
#6 (permalink)
| | Registered User
Join Date: Feb 2002 Location: midvale, utah
Posts: 1,296
|
Not sure of the Error-Checking your talking about, but I hope this helps when writing it.
Not every one has windows on c:\, so instead try pointing to %windir%\system32
|
| |
10-09-2003, 08:30 PM
|
#7 (permalink)
| | Registered User
Join Date: May 2003 Location: Neo Japan
Posts: 1,175
|
Well, it seems you're getting so much closer to solve the problem
I have a similar like that one at: http://www.techimo.com/forum/t83824.html
Hope any of you lads could help me this one out. Thanks.
__________________
|c3R
|
| |
10-09-2003, 09:09 PM
|
#8 (permalink)
| | Registered User
Join Date: Feb 2002 Location: midvale, utah
Posts: 1,296
|
I'm scratching my head on this one.
Maybe you should reread what firewolf is asking? His system is perfectly fine, he doesn't need a repair, he is asking where the Error-Checking for xp(Exactly located in the system32\xxxx.exe is at, not how to do a system restore.
What sort of error checking are you talking about red wolf? There are the system logs of errors and reports. Not real sure what other error checking your talking about.
Last edited by Jeordiewhite; 10-09-2003 at 09:12 PM.
|
| |
10-10-2003, 12:07 AM
|
#9 (permalink)
| | Registered User
Join Date: Aug 2003 Location: Canada
Posts: 197
|
I'm not that advanced with computers, so try to rule out any Logs or Reports of applications
Okay, all I would like is the path that leads to the Error-Checking program/system tool. I would like to enter the path in the Start Menu>Run command window and have it pop up. If you have WinXP, enter this into the Run command:
dfrg.msc
... Disk Defragment should pop up. I would like this to happen if I enter in the path to Error-Checking, but I don't know the path, that's what I would like to find out. The Error-Checking that I'm talking about is like ScanDisk (Win98). I have attached a screenshot of the program/system tool.
I hope this has clarified any miscommunications  if not... jus holla
|
| |
10-10-2003, 12:26 AM
|
#10 (permalink)
| | Registered User
Join Date: Feb 2002 Location: midvale, utah
Posts: 1,296
|
ChkdskCreates and displays a status report for a disk based on the file system. Chkdsk also lists and corrects errors on the disk. Used without parameters, chkdsk displays only the status of the disk in the current drive; it does not fix errors. To fix errors, you must include the /f parameter.
Important
Running chkdsk without parameters on an active system or boot volume or on a data volume that is in use by another program or process might incorrectly report errors when none are present.
To avoid this, close all programs or processes that have open handles to the volume. If the volume is a system or boot volume, use the chkntfs /c command to schedule the volume to be checked the next time the computer is restarted. Use the fsutil dirty set command to set the volume's dirty bit (indicating corruption) so that Windows runs chkdsk when the computer is restarted.
While inspecting or repairing volumes, chkdsk locks the volume, making any data stored on the volume unavailable until chkdsk is finished. As a rule, run chkdsk only on volumes that are known to be corrupt. On volumes marked as "dirty," Windows automatically runs chkdsk when the computer is restarted. On servers that are infrequently restarted, use the chkntfs or the fsutil dirty query commands to determine whether the volume's dirty bit is set before running chkdsk.
Syntax
chkdsk [Volume:][[Path] FileName] [/f] [/v] [/r] [/x] [/i] [/c] [/l[:Size]]
Parameters
Volume:
Specifies the drive letter (followed by a colon), mount point, or volume name.
[Path] FileName
Use with file allocation table (FAT) and FAT32 only. Specifies the location and name of a file or set of files that you want chkdsk to check for fragmentation. You can use wildcard characters (that is, * and ?) to specify multiple files.
/f
Fixes errors on the disk. The disk must be locked. If chkdsk cannot lock the drive, a message appears that asks you if you want to check the drive the next time you restart the computer.
/v
Displays the name of each file in every directory as the disk is checked.
/r
Locates bad sectors and recovers readable information. The disk must be locked.
/x
Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f.
/i
Use with NTFS only. Performs a less vigorous check of index entries, reducing the amount of time needed to run chkdsk.
/c
Use with NTFS only. Skips the checking of cycles within the folder structure, reducing the amount of time needed to run chkdsk.
/l[:Size]
Use with NTFS only. Changes the log file size to the size you type. If you omit the size parameter, /l displays the current size.
/?
Displays help at the command prompt.
Remarks
Running chkdsk
To run chkdsk on a fixed disk, you must be a member of the Administrators group.
Checking a locked drive at restart
If you want chkdsk to correct disk errors, you cannot have open files on the drive. If files are open, the following error message appears:
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)
If you choose to check the drive the next time you restart the computer, chkdsk checks the drive and corrects errors automatically when you restart the computer. If the drive partition is a boot partition, chkdsk automatically restarts the computer after it checks the drive.
Reporting disk errors
Chkdsk examines disk space and disk use for the FAT and NTFS file systems. Chkdsk provides information specific to each file system in a status report. The status report shows errors found in the file system. If you run chkdsk without the /f command-line option on an active partition, it might report spurious errors because it cannot lock the drive. You should use chkdsk occasionally on each disk to check for errors.
Fixing disk errors
Chkdsk corrects disk errors only if you specify the /f command-line option. Chkdsk must be able to lock the drive to correct errors. Because repairs usually change a disk's file allocation table and sometimes cause a loss of data, chkdsk sends a confirmation message similar to the following:
10 lost allocation units found in 3 chains.
Convert lost chains to files?
If you press Y, Windows saves each lost chain in the root directory as a file with a name in the format Filennnn.chk. When chkdsk finishes, you can check these files to see if they contain any data you need. If you press N, Windows fixes the disk, but it does not save the contents of the lost allocation units.
If you do not use the /f command-line option, chkdsk sends a message if a file needs to be fixed, but it does not fix any errors.
If you use chkdsk /f on a very large disk (for example, 70 gigabytes) or a disk with a very large number of files (for example, millions of files), chkdsk might take a long time to complete. The computer is not available during this time because chkdsk does not relinquish control until it is finished.
Checking a FAT disk
Windows displays chkdsk status reports for a FAT disk in the following format:
Volume Serial Number is B1AF-AFBF
72214528 bytes total disk space
73728 bytes in 3 hidden files
30720 bytes in 12 directories
11493376 bytes in 386 user files
61440 bytes in bad sectors
60555264 bytes available on disk
2048 bytes in each allocation unit
35261 total allocation units on disk
29568 available allocation units on disk
Checking an NTFS disk
Windows displays chkdsk status reports for an NTFS disk in the following format:
The type of the file system is NTFS.
CHKDSK is verifying files...
File verification completed.
CHKDSK is verifying indexes...
Index verification completed.
CHKDSK is verifying security descriptors...
Security descriptor verification completed.
12372 kilobytes total disk space.
3 kilobytes in 1 user files.
2 kilobytes in 1 indexes.
4217 kilobytes in use by the system.
8150 kilobytes available on disk.
512 bytes in each allocation unit.
24745 total allocation units on disk.
16301 allocation units available on disk.
Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message if there are open files on the disk. If you do not specify the /f command-line option and open files exist, chkdsk might report lost allocation units on the disk. This could happen if open files have not yet been recorded in the file allocation table. If chkdsk reports the loss of a large number of allocation units, consider repairing the disk.
Finding physical disk errors
Use the /r command-line option to find physical disk errors in the file system. For information about recovering physically damaged files with recover, see Related Topics.
Reporting bad disk sectors
Bad sectors reported by chkdsk were marked as bad when your disk was first prepared for operation. They pose no danger.
Understanding exit codes
The following table lists the exit codes that chkdsk reports after it has finished.
Exit code Description
0 No errors were found.
1 Errors were found and fixed.
2 Disk cleanup, such as garbage collection, was performed, or cleanup was not performed because /f was not specified.
3 Could not check the disk, errors could not be fixed, or errors were not fixed because /f was not specified.
The chkdsk command, with different parameters, is available from the Recovery Console.
Examples
If you want to check the disk in drive D and have Windows fix errors, type:
chkdsk d: /f
If it encounters errors, chkdsk pauses and displays messages. Chkdsk finishes by displaying a report that lists the status of the disk. You cannot open any files on the specified drive until chkdsk finishes.
To check all of files on a FAT disk in the current directory for noncontiguous blocks, type:
chkdsk *.*
Chkdsk displays a status report, and then lists the files matching the file specification that have noncontiguous blocks.
Formatting legend
Format Meaning
Italic Information that the user must supply
Bold Elements that the user must type exactly as shown
Ellipsis (...) Parameter that can be repeated several times in a command line
Between brackets ([]) Optional items
Between braces ({}); choices separated by pipe (|). Example: {even|odd} Set of choices from which the user must choose only one
Courier font Code or program output
|
| | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | | Thread Tools | | | | Display Modes | Linear Mode |
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts HTML code is Off | | | | Most Active Discussions  | | | | | Recent Discussions  | | | | | |