Re: Finding short file names?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Fri, 1 Jul 2005 22:46:46 -0400, "Richard Urban"
<richardurbanREMOVETHIS@xxxxxxxxxxx> wrote:

>Windows XP has migrated well past "short filenames". That was a restriction
>with fat16 file systems - NOT a benefit!
>
>Because Windows 98 was built on top of DOS (could use either fat16 or fat32)
>it is only natural that there was a built in capability to use short
>filenames (the 8.3 nomenclature) easily. There is no DOS in windows XP and
>therefore there is no need for short filenames.

Normally there is no need for them. However...

It's still one of the reasons that doing a straight copy of a system
partition can fail. While the kernel/drivers are loading they often
refers to shortened file names (SFNs). They're all over the registry.

When someone does a copy or xcopy of the system partition, the SFNs
are recreated on the fly. The new ones, of course, often don't match
the older registry entries.

This is why programs like Dos32/Backmagic were created. They copy
everything with the SFNs intact. The only logistic problem that may
have induced MS NOT to keep them intact is that you'd have two
possible types of name collisions when copying files into a non-empty
folder: a dupe'd LFN which you're prompted for (overwrite/cancel) or a
dupe'd SFN which would have baffled grandma.

---

To the OP: As mentioned, 'Dir /x' does it via command line, but I
believe the only way to display them in a normal folder window would
be to write a 'Shell Extension.' This is done often when programmers
need a column that shows specifics about a file (like the MP3 stats
you can choose by R-clicking the header on a Details display).
Unfortunately, I don't remember seeing one that was designed for SFNs.
It's a good idea, and it could be done. Search CodeProject for key
"Shell Extensions" if you have some programming chops and patience.




.

Relevant Pages

  • Re: The case insensitive #include statement horror...
    ... like the case-insensitivity of the Windows file system, ... it's more like asking the programmer switching case sensitivity in their ... It enlarges the namespace of possible filenames... ... If there really were no reason to have upper ...
    (microsoft.public.vc.language)
  • Re: Got it working, kind of. was Re: Adding network and internet to Warp 4
    ... Windows Explorer and I see long filenames. ... from an OS/2 window, ... Advanced install when I installed it, and I don't remember there being ...
    (comp.os.os2.misc)
  • Re: Got it working, kind of. was Re: Adding network and internet to Warp 4
    ... Windows Explorer and I see long filenames. ... Firefox ver 3 shows up as Firefox_.zip. ... Advanced install when I installed it, and I don't remember there being ...
    (comp.os.os2.misc)
  • Re: XP exec background process
    ... On DOS and Windows systems... ... When working with paths and filenames, ... DOS used to save all paths and filenames as 100% uppercase. ... Passing switches/parameters on the command-line for different commands ...
    (comp.lang.php)
  • Re: MCI API capabilities
    ... We do it routinely for file servers. ... performance hit from Windows having to maintain short file ... The system for generating SFNs from LFNs completely breaks down ... No DOS apps, no 16-bit or other ...
    (microsoft.public.vb.winapi)