If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
scandisk errors
If you uncheck the automatic fix scandisk errors, a prompt pops up and three
options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. |
#2
|
|||
|
|||
scandisk errors
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... "Jim" wrote in message .. . If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. |
#3
|
|||
|
|||
scandisk errors
I did find answers to many of my questions in:
http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... "Jim" wrote in message .. . If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. |
#4
|
|||
|
|||
scandisk errors
On 01/20/2010 03:29 PM, Jim wrote:
I did find answers to many of my questions in: http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? Only if the file is intact, as in original condition. Not usually the case. Simplified explanation: cross-linked files - files in which segments may contain parts of other files due to some corruption caused by disk errors [bad clusters or otherwise] or FAT issues [two or more files supposedly in the same cluster segments]. File fragments - parts of data which appears to be part of some file but are not determined to be part of an existing file or belonging to an unknown folder. Perhaps you can help us help you by describing what you are trying to fix and what OS? The DOS Name Length errors are typical for scandisk as it does *not* support the full 255 name length of Windows. That includes both the folders AND the actual file name. It is NOT recommended to check for this with scandisk. "Report MS-DOS Mode Name Length Errors - MS-DOS does not allow paths to files or folders to be longer than 66 characters. By default, ScanDisk for Windows does not check for MS-DOS mode name length errors. To force ScanDisk for Windows to detect these errors, click the "Report MS-DOS mode name length errors" check box to select it. This causes ScanDisk for Windows to detect folders that cannot be opened in MS-DOS mode because the MS-DOS patch is longer than 66 characters. If you have not selected the Automatically Fix Errors check box, ScanDisk for Windows prompts you to ignore this error and continue, repair the error by moving the folder, or delete the affected folder. Note that the default action (regardless of whether the Automatically Fix Errors check box is selected) is to ignore this error and continue. For additional information about this issue, please see the following article in the Microsoft Knowledge Base: 132883 (http://support.microsoft.com/kb/132883/EN-US/ ) Err Msg: Drive C Contains Errors That Must Be Corrected... http://support.microsoft.com/kb/132883/EN-US/" "Windows allows paths with more than 66 characters. However, MS-DOS does not allow these long paths. When you use the Automatically Fix Errors option in ScanDisk, a path that is longer than 66 characters is considered valid to Windows and invalid to MS-DOS." The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... "Jim" wrote in message .. . If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. -- MEB http://peoplescounsel.org/ref/windows-main.htm Windows Info, Diagnostics, Security, Networking http://peoplescounsel.org The "real world" of Law, Justice, and Government ___--- |
#5
|
|||
|
|||
scandisk errors
On 01/20/2010 03:29 PM, Jim wrote:
I did find answers to many of my questions in: http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? Only if the file is intact, as in original condition. Not usually the case. Simplified explanation: cross-linked files - files in which segments may contain parts of other files due to some corruption caused by disk errors [bad clusters or otherwise] or FAT issues [two or more files supposedly in the same cluster segments]. File fragments - parts of data which appears to be part of some file but are not determined to be part of an existing file or belonging to an unknown folder. Perhaps you can help us help you by describing what you are trying to fix and what OS? The DOS Name Length errors are typical for scandisk as it does *not* support the full 255 name length of Windows. That includes both the folders AND the actual file name. It is NOT recommended to check for this with scandisk. "Report MS-DOS Mode Name Length Errors - MS-DOS does not allow paths to files or folders to be longer than 66 characters. By default, ScanDisk for Windows does not check for MS-DOS mode name length errors. To force ScanDisk for Windows to detect these errors, click the "Report MS-DOS mode name length errors" check box to select it. This causes ScanDisk for Windows to detect folders that cannot be opened in MS-DOS mode because the MS-DOS patch is longer than 66 characters. If you have not selected the Automatically Fix Errors check box, ScanDisk for Windows prompts you to ignore this error and continue, repair the error by moving the folder, or delete the affected folder. Note that the default action (regardless of whether the Automatically Fix Errors check box is selected) is to ignore this error and continue. For additional information about this issue, please see the following article in the Microsoft Knowledge Base: 132883 (http://support.microsoft.com/kb/132883/EN-US/ ) Err Msg: Drive C Contains Errors That Must Be Corrected... http://support.microsoft.com/kb/132883/EN-US/" "Windows allows paths with more than 66 characters. However, MS-DOS does not allow these long paths. When you use the Automatically Fix Errors option in ScanDisk, a path that is longer than 66 characters is considered valid to Windows and invalid to MS-DOS." The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... "Jim" wrote in message .. . If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. -- MEB http://peoplescounsel.org/ref/windows-main.htm Windows Info, Diagnostics, Security, Networking http://peoplescounsel.org The "real world" of Law, Justice, and Government ___--- |
#6
|
|||
|
|||
scandisk errors
"Jim" wrote in message
... I did find answers to many of my questions in: http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... A couple of things you might try; first use FIND (winkey-F) and type in the filename you restored. Then search the drive the file came from. You may actually be in luck and find a file by the same name in the right directory. Second, give us the filename because it may be a filename one of us is familiar with and can tell you what directory it belongs in. For the future I would highly recommend letting SCANDSKW automatically do repairs and make sure you always have a good recent backup of your system. When I've gotten into trouble I've sometimes had the backup software restore missing files, but not overwrite existing files. It's saved my hide more than once! |
#7
|
|||
|
|||
scandisk errors
"Jim" wrote in message
... I did find answers to many of my questions in: http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... A couple of things you might try; first use FIND (winkey-F) and type in the filename you restored. Then search the drive the file came from. You may actually be in luck and find a file by the same name in the right directory. Second, give us the filename because it may be a filename one of us is familiar with and can tell you what directory it belongs in. For the future I would highly recommend letting SCANDSKW automatically do repairs and make sure you always have a good recent backup of your system. When I've gotten into trouble I've sometimes had the backup software restore missing files, but not overwrite existing files. It's saved my hide more than once! |
#8
|
|||
|
|||
scandisk errors
you have bad clusters time to get a new Hard Drive
You will not be able to repair this file myself....... "Jim" wrote in message ... If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. |
#9
|
|||
|
|||
scandisk errors
you have bad clusters time to get a new Hard Drive
You will not be able to repair this file myself....... "Jim" wrote in message ... If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. |
#10
|
|||
|
|||
scandisk errors
Do not configure Scandisk to automatically fix anything. If there are
problems, you need to know about them - you do not want them silently disposed of. The 'fix' usually doesn't fix it the way you were hoping, and it can make the problem much worse. If Scandisk detects a problem and offers to fix it, it is usually best to decline. Manually fixing the problem is often a better solution. You may wish to allow Scandisk to repair files when you know that an illegal shutdown has left some files in an invalid state. You will invariably then delete those files, although in some cases it may be possible to repair them or at least recover some data from them. But whatever the circumstance, do not let Scandisk 'fix' anything unless you are sure that you understand exactly what the 'fix' is going to do, and that you can handle the result. The MSDOS length errors can be ignored. The fix for this problem should only be used when you are attempting recovery of a complete disk and you are forced to use DOS to do it, and some parts of some folders are inaccessible. When you have recovered everything else, these inaccessible files can be recovered after running Scandisk to adjust the filename length so you can get at them from DOS. It has no other use. -- Jeff Richards ---------------------------------------- "Jim" wrote in message ... I did find answers to many of my questions in: http://support.microsoft.com/kb/186365 I did not find out how to restore the file to its original folder location after [ move to repair] option. If I just place the file in the root path folder it appears to have come from will this work? The KB article above suggests that user of this option write down the root path to folder file before moving the file. Unfortunately, I did not think to do this prior to the move/repair selection and there was no warning to user. My first attempt to restore was to use {scanreg / restore} in dos-mode and no luck... "Jim" wrote in message .. . If you uncheck the automatic fix scandisk errors, a prompt pops up and three options are allowed. The choices are ignore, move and repair and delete the file. If I chose the [move and repair] option, the program moves the file to the top of the host local drive C: . My question(s) are what is repaired and how do I restore the file to its proper folder location? Do I have to repair this file myself? When and why would I want to delete the file? The only errors that scandisk reports are MS-Dos name length errors that exceed 66 characters in length. Why does win98 name some MS-Dos files like this? Is this the only error that scandisk reports? It seems easier to just leave the program to autofix everything it finds, but then I would never learn what all it fixes. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Scandisk errors/hard drive problem | Joe K | General | 3 | November 16th 05 12:38 AM |
Scandisk causes BSOD, character map causes errors, clipboard viewer crashs | bswarm | General | 5 | October 3rd 05 05:57 PM |
SCANDISK on 6GB drive producing Errors at 2.09GB to end. | Jerry | Disk Drives | 15 | July 21st 05 07:00 PM |
Recurring Scandisk Errors | vegeddabowdit | General | 2 | October 12th 04 02:55 PM |
Scandisk errors | Peter Brown | General | 15 | September 5th 04 10:40 AM |