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
|
|||
|
|||
Long filename error
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 |
#2
|
|||
|
|||
Long filename error
On 12/10/2011 07:56 AM, Axel Berger wrote:
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 Dos has a limitation as to the number of characters a file can be. Either rename the file with a shorter name or just run scandisk from Windows if you ever need to again |
#3
|
|||
|
|||
Long filename error
Axel Berger wrote in :
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? I'll let you know if I come up with anything after my third imaginasry pipe. This is a good one... Problem. Not pipe. Go with what Philo said for now, and also consider that you might have placed a whole directory full of subdirectories into some new subdirectory, extending the entire path for some file beyond safe limits. It may not cause this specific problem but it's related, possibly, and worth watching out for. One other thought: try building a DVD ISO from the subdirectory you think contains the files. Some ISO tools might find the error and report it better. |
#4
|
|||
|
|||
Multi-posting vs Cross-posting (was: Long filename error)
Axel Berger wrote:
(...) Why did you multi-post this separately to microsoft.public.win98.gen_discussion and alt.windows98 (and god knows where else) ? Where did you learn to multipost? Do you understand why it is not a good practice? Cross-post next time. This avoids creating separate, isolated conversations on the same topic between different groups of people. |
#5
|
|||
|
|||
Long filename error
On Dec 10, 6:56*am, Axel Berger wrote:
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 I only found 'long filename' errors if I ran ScanDisk in FULL COMPLETE mode, or whatever. Scandisk takes long enough but complete will probably take all day, but YOU WILL FIND the offending fileame. PS: One of our systems has some 120+ too long filenames, yet not been a problem too often.Perhaps, the filename being contiguous valid alphs characters has saved us. ...no spaces, punctuation, etc. |
#6
|
|||
|
|||
Long filename error
In message , philo
writes: On 12/10/2011 07:56 AM, Axel Berger wrote: 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 Dos has a limitation as to the number of characters a file can be. Either rename the file with a shorter name Yes, but he doesn't know which file it is. or just run scandisk from Windows if you ever need to again He's done that, and it found no fault. -- J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf Live Faust, die Jung. |
#7
|
|||
|
|||
Multi-posting vs Cross-posting (was: Long filename error)
In message ,
MotoFox confucius-say@enlightenment!to!him!lead!it!for!bangpath!foll ow!man!wise. UUCP writes: And it came to pass that 98 Guy delivered the following message unto the people, saying~ Axel Berger wrote: (...) Why did you multi-post this separately to microsoft.public.win98.gen_discussion and alt.windows98 (and god knows where else) ? Where did you learn to multipost? Do you understand why it is not a good practice? Cross-post next time. This avoids creating separate, isolated conversations on the same topic between different groups of people. Seriously, dude, why not just answer the question? In case you missed He didn't for the same reason _you_ didn't: he saw something he thought it would be helpful to give advice about, even if he didn't have an answer to the particular question. Multiposting wastes _everybody's_ time, as it can cause lots of different people to follow the thread in however many newsgroups the problem is posted to, without those people being aware of what each other are suggesting. it, the scenario is: he's running Scandisk in DOS, the programme stops when it hits what he believes to be a long file name or path, and he needs to know what an easy way is to trace this path and clear it up. Correct. Now, if you'd spend less time bitching about why and how people posted things in certain areas and concentrate more of your energy on fixing the actual problems, it's amazing how much you'd accomplish........and you'll find you'd come off being less of a troll and more of a useful sort....... Like you have. $20 says "98 Guy" has OCD. (And yes: I'll admit I haven't given a solution either!) -- J. P. Gilliver. UMRA: 1960/1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf Live Faust, die Jung. |
#8
|
|||
|
|||
Long filename error
"Axel Berger" wrote in message ...
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. 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 |
#9
|
|||
|
|||
Long filename error
|
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
What happens when the filename is too long? | Robert Macy | General | 2 | August 15th 10 05:45 PM |
What happens when the filename is too long? | Robert Macy | General | 1 | July 19th 10 07:45 AM |
Repeated scandisk long filename error in TIF folder | Code-Curious Mom | General | 8 | January 26th 06 08:41 PM |
Scandisk-long filename error | christina | General | 2 | October 20th 05 04:42 PM |
Scandisk: filename too long | Daniel L Newhouse | General | 4 | August 18th 04 08:56 PM |