Re: strange ntfs filename restriction (by design?)
From: Tim Slattery (Slattery_T_at_bls.gov)
Date: 05/13/04
- Next message: Will Denny: "Re: XP Resource Kit?"
- Previous message: Tumbleweed: "Re: Uninstalling Kazaa"
- In reply to: Alex Nichol: "Re: strange ntfs filename restriction (by design?)"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 May 2004 12:34:01 -0400
Alex Nichol <alexn.mvpdts@ntlworld.delete.com> wrote:
>Rob Schneider wrote:
>
>>Clearly there is rule in the file system which prevents use of so many
>>full stops (.). Probably by design else it would work.
>
>a period (.) is considered in windows file systems as a separator
>between fields, and you are not allowed a null field in between. There
>are some other characters that have restricted special use - or are
>totally prohibited, too
I don't think so. I just saved a file named "odd..filename.txt" on my
WinXP Pro system. It's sitting there on my disk, I can double-click it
and it opens in the associated program, just like it should.
The directory structure in DOS allowed eleven characters for a file
name. That was separated into two fields, one eight bytes and one
three bytes. DOS expected a file name to have a root part and an
extension, separated by a dot. More than one dot in a file name was
not allowed.
NTFS certainly doesn't care about extra dots (as my experiment
proves). I don't have Win9x system here to experiment on, but I think
it would handle also. It would create a DOS-style 8.3 name (as it does
for all file names that don't fit the 8.3 spec), and would store both
that name and the full name.
-- Tim Slattery MS MVP(DTS) Slattery_T@bls.gov
- Next message: Will Denny: "Re: XP Resource Kit?"
- Previous message: Tumbleweed: "Re: Uninstalling Kazaa"
- In reply to: Alex Nichol: "Re: strange ntfs filename restriction (by design?)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
