Re: CONFIG_VFAT_FS_DUALNAMES regressions

[Jamie Lokier]

Jan Engelhardt wrote:
> 
> On Monday 2009-07-06 20:55, Jan Engelhardt wrote:
> >>How did things go with your mp3 players?
> >[...]
> >As it stands, my two devices always want a valid 8.3 name.
> 
> On or about June 26, James Bottomley exchanged these words to Andrew Tridgell:
> >So the patch has been tested with Vista, Windows 7 and Windows XP
> 
> 
> Vista, 7... nothing special.
> 
> So let me fill in.
> 
> Windows 98 can't make anything of the stunted vfat entries either[3],
> and there's blanks for 16-bit programs[4]. They too, it seems, always
> want an 8.3 entry in any case.
> It does not crash, but neither of these results is usable.
>
> This dualnames patch just won't fly in practice.
> 
> 
> [3] http://picpaste.de/w98dualnames.png
> [4] http://picpaste.de/xpwith16bit.png
> (pics kept for 7 days from now)

Summary of pics, for posterity:

[3] shows an MS-DOS window on a Windows 98 desktop, listing the A:
    drive:

      Microsoft(R) Windows 98
         (C)Copyright Microsoft Corp 1981-1998.

      A:\>Dir

       Datantrager in Laufwerk A: hat keine Bezeichnung
       Seriennummer des Datentragers: 4A52-570A
       Verzeichnis von A:\

      SHORT    TXT            12  06.07.09  21:57 SHORT.TXT
                              12  06.07.09  21:57 
                              12  06.07.09  21:57 
               3 Datai(en)                    36 Bytes
               0 Verzeichnis(se)       1.456.128 Bytes frei

      A:\>

Question: In Windows 98, is it just the MS-DOS box which cannot see
some of the filenames, or is the normal file explorer affected too?

[4] shows a old-looking Windows application, presumably 16-bit running
    on XP, with a File Selection box listing the a:\ drive.  Four
    files are shown on the a:\ drive in a selection box, but the first
    of them is completely blank.

In Windows XP, it suggests to me that the Windows API function
GetShortPathName() returns the 8.3 file name entry.  Call it an
educated guess, and I'll guess the same applies in Server 2003, Vista,
Server 2008 and Windows 7.

All those Windows versions also have GetLongPathName() which does the
reverse transformation.  Presumably that also expects the 8.3 entry to
exist.

The fact these were added in Windows 2000 implies they're not an
ancient thing from the Windows 95 era, but specifically used by
applications since Windows 2000.

-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/