Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Long filename error
4 views
Skip to first unread message
Axel Berger
Dec 10, 2011, 8:23:45 AM12/10/11
to
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
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
Dec 10, 2011, 9:58:40 PM12/10/11
to
"Axel Berger" <Axel....@Gmx.De> wrote in message news:4EE36525...@Gmx.De...
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 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
> 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
> filename error on the system partition and tells me to run Scandisk in
> Windows. The latter tells me no errors found.
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 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.
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
Dec 11, 2011, 5:39:19 AM12/11/11
to
Ben Myers wrote:
> 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.
> 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.
> 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.
Danke
Axel
Axel Berger
Dec 27, 2011, 3:00:56 PM12/27/11
to
Ben Myers wrote:
> 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
> 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.
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
Dec 30, 2011, 1:57:20 AM12/30/11
to
"Axel Berger" <Axel....@Gmx.De> wrote in message news:4EFA23F8...@Gmx.De...
Scandisk for DOS can't do this, but Scandisk for Windows can.
http://www.mdgx.com/newtip18.htm#SHS
Ben
http://www.mdgx.com/newtip18.htm#SHS
Ben
Axel Berger
Dec 31, 2011, 5:17:13 AM12/31/11
to
Ben Myers wrote:
> Scandisk for DOS can't do this
It did here, when being autostarted while booting.
> Scandisk for DOS can't do this
Axel
0 new messages