2.4.26 vfat mounted fs will not reqcognize 8,3 file IF extention part (ONLY) is lower case.

2.4.26 vfat mounted fs will not reqcognize 8,3 file IF extention part (ONLY) is lower case.

[Floydsmith]

When a ANY linux command (running under 2.4.26) ("ls", "grep", "find", etc) tryies to access a file in a "vfat" mounted fs with a filename such that it meets real mode DOS's "8.3" requirement EXCEPT (under windoze, of course), the file has has ONLY its extention part as lower case (that is, base is all UPPER), then the file will not be accessable (that is, it will appear NOT TO EXIST under linux.)

Here is an example of what I mean.
In one FAT32 dir (say dir1) under REAL MODE DOS we have a file nameed "checkfix.exe". Then a dir executed therein will show:
    CHECKFIX EXE        34,448  05-27-03  3:05a CHECKFIX.EXE
Then all linux commands will be able to see this file (if in a DOS WINDOW, the "dir" command shows EXACTLY the same thing).

But, if in another dir (again in a FAT32 partition) there is a "copy" of the file (EXCEPT it's extention part [ONLY] is lower case), then linux will not be able to access the file (but of course, both REAL MODE DOS and windoze will).
That is, (if while in a windoze (NOT REAL MODE DOS) DOS WINDOW, this other file in shows up as:
    CHECKFIX EXE        34,448  05-27-03  3:05a CHECKFIX.exe
A DOS WINDOW's "dir" command will display the "long filename info" in the 5th column which shows where the problem occurs.

The only workarrond I know of is IN REAL MODE DOS ONLY, copy the the file somewhere else, the copy it back - it will loose its' "long filename" properties, in this case - and will thus become accesible to all.

Please "cc" me, I am NOT on the "list" anymore.

Floyd,