Discussion:
Long filename error
(too old to reply)
Axel Berger
2011-12-10 13:23:45 UTC
Permalink
Scandisk for DOS, when started automatically on booting, reports a long
filename error on the system partition and tells me to run Scandisk in
Windows. The latter tells me no errors found.

I wouldn't mind, but Scandisk stops at the error and waits for a key to
be pressed. This means I can't go and make coffee and come back with
booting finished and the restart after a power outage won't work.

Scandisk does not tell me which file is wrong and looking over a DIR
listing nothing struck the eye - of course it's far to long to read line
by line. I'm prety sure I can repair the problem manually, but I first
need to find the culprit file. Any ideas how to do that?

Danke
Axel
Ben Myers
2011-12-11 02:58:40 UTC
Permalink
Post by Axel Berger
Scandisk for DOS, when started automatically on booting, reports a long
filename error on the system partition and tells me to run Scandisk in
Windows. The latter tells me no errors found.
Start Scandisk for Windows, click on "Advanced" and make sure that "Report
MS-DOS mode name length errors" and "Invalid file names" are checked. If not,
check them and click "OK". Then let Scandisk check the drive.
Post by Axel Berger
I wouldn't mind, but Scandisk stops at the error and waits for a key to
be pressed. This means I can't go and make coffee and come back with
booting finished and the restart after a power outage won't work.
<snip>

Open "C:\Windows\command\scandisk.ini" with Notepad, go to the "[Environment]"
section, find "LfnCheck" and see if it is set to "On". If so, change it to "Off". Be
sure to save the change.

Ben
Axel Berger
2011-12-11 10:39:19 UTC
Permalink
Post by Ben Myers
Start Scandisk for Windows, click on "Advanced" and make sure that "Report
MS-DOS mode name length errors" and "Invalid file names" are checked. If not,
check them and click "OK". Then let Scandisk check the drive.
I might have said, those are active, still don't find a thing.
Post by Ben Myers
Open "C:\Windows\command\scandisk.ini" with Notepad, go to the "[Environment]"
section, find "LfnCheck" and see if it is set to "On". If so, change it to "Off". Be
sure to save the change.
Thanks, good idea. done that.

Danke
Axel
Axel Berger
2011-12-27 20:00:56 UTC
Permalink
Post by Ben Myers
Open "C:\Windows\command\scandisk.ini" with Notepad, go to the "[Environment]"
section, find "LfnCheck" and see if it is set to "On". If so, change it to "Off". Be
sure to save the change.
That setting did, what it was supposed to - no more unidentifiable LFN
errors. Unfortunately it has deleted all LFNs on several drives and thus
effectively deleted all data. I'm currently in the middle of the repair
process. Don't do it!

Axel
Ben Myers
2011-12-30 06:57:20 UTC
Permalink
Post by Axel Berger
Post by Ben Myers
Open "C:\Windows\command\scandisk.ini" with Notepad, go to the "[Environment]"
section, find "LfnCheck" and see if it is set to "On". If so, change it to "Off". Be
sure to save the change.
That setting did, what it was supposed to - no more unidentifiable LFN
errors. Unfortunately it has deleted all LFNs on several drives and thus
effectively deleted all data. I'm currently in the middle of the repair
process. Don't do it!
Scandisk for DOS can't do this, but Scandisk for Windows can.

http://www.mdgx.com/newtip18.htm#SHS

Ben
Axel Berger
2011-12-31 10:17:13 UTC
Permalink
Post by Ben Myers
Scandisk for DOS can't do this
It did here, when being autostarted while booting.

Axel

Loading...