Long Filename

What is the cause of the message below when using Windows 98? How are invalid long filenames created or how do they come into existence?
Can this message be seen when the wrong version of scandisk is being used?
For example the DOS 6.2 version of scandisk.exe running after an improper shutdown?
What can be done to be sure invalid long filenames are not created.
Does running ScanDisk for Windows (as the message suggests)correct the invalid long filename message below?
"Scandisk detected an invalid long filename entry on this drive but was unable to fix it. To fix this problem, run Scandisk for Windows.
What should be done?

You cannot run DOS scandisk from inside of Windows as it checks Windows files that would be in use.

Windows Scandisk probably does a better job then DOS, I would run Windows Scandisk and it should fix the Long File Names problem.

Or it could be something as simple as you havea file in a directory that is many levels deep eg c:\program files\macromedia\macromedia shockwave\shockwave player\shockwave player.exe

I think there is a combined limit of 66 characters for a file location +name

I dig into dos quite a bit and know how to handle long filenames.
Here is probably a lot more information than you'll ever need:
http://users.iafrica.com/c/cq/cquirke/lfns.htm
Long read but does explain it well.
Good luck.
Nick:cool:

Thanks everyone.
Not sure if I understand some of it.
Murph, Are you saying that running scandisk from a MS-DOS command prompt after the desktop is presented can cause this message immediately? Or, causes the invalid name condition and the message to appear after the next improper shutdown?

Nix,
My understanding is that a long filename can be as long as 256 characters including its path.
Don't understand this 66 character stuff.


What is an example of an invalid long file name as far as the version of Scandisk included with 98 which runs after an improper shutdown is concerned? (DOS version of scandisk included with 98)

The message is because the path to the file is too long...over 66?

Bump

I'll let you know later tonight when I'm at home.

I can then run a scandisk to produce the 66 character thing.

I'm sure it's the default installtion of Macromedia Shockwave or flash.

Quote:

---

Originally posted by Robert M
Thanks everyone.
Nix,
My understanding is that a long filename can be as long as 256 characters including its path.
Don't understand this 66 character stuff.


What is an example of an invalid long file name as far as the version of Scandisk included with 98 which runs after an improper shutdown is concerned? (DOS version of scandisk included with 98)

The message is because the path to the file is too long...over 66?

---

So if you got a message about it being over 66 that's what I'm talking about.

message

Quote:

---

The 'C:\WINDOWS\APPLIC~1\MACROM~1\FLASHP~1\MACROM~1.COM\SUPPORT\FLASHP~1' folder cannot be opened in MS-DOS mode because its MS-DOS name, including the names of any folders it is in, is longer than 66 characters.

---

being for this folder C:\WINDOWS\Application Data\Macromedia\Flash Player\macromedia.com\support\flashplayer\sys

Thanks Nix,

I am not getting the message about 66 characters.

The message I'm getting on a friends machine with Windows 98 installed when the computer boots up is below.

Why does this message appear?
I can't find any good info.

Stumbled across a Microsoft article about the FAT 16 512 root entry limitation. I understand that some filenames and directory names take up more than one entry.

Can the ScanDisk message below be related to the limitation?
For example, if the 512 entries are already used, is that why scandisk cannot fix the invalid long filename?


"Scandisk detected an invalid long filename entry on this drive but was unable to fix it. To fix this problem, run Scandisk for Windows."

Does anyone know the steps necessary to reproduce this error?
The message appears when the DOS mode version of scandisk runs on a Windows 98 system.(For example after improper shutdown).
Cannot find the message at the Microsft Knowledge Base!
Is it a BIOS/CMOS problem?
Is it the wrong version of ScanDisk?
Is it options set in the scandisk.ini file?
Is it an orphaned long file name without a DOS alias name or similar?
Is it a file name which didn't obey the naming rules?
Is it because the root drive is full?
Is it because the entire drive is full?
Is the file marked read only?

Bump

I must really be stupid... what does "bump" mean in these forums?

lol..
"bump" is the text you put into a reply if you have no information to add..., and you want to move the thread to the top of the forum.., so people will notice it again...

so you are bumping the thread to the top...

O.I.C. !!!