locked
Windows 7 Folders RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    When you put a "dot" in the last character in a Folder, the folder dissapears.
    If you press F5, the folder appears again.
    Can you explain me why, please? This is not a expected behavior.

    Thank you and Regards,

       Alvarez Arigós Roberto Miguel
    Sunday, September 6, 2009 7:47 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote
    I'm not sure 'why' Windows 7 does this?
    Windows 95, 98, NT,...etc... Windows 7. 

    14 years old


    "Do not end a file or directory name with a trailing space or a period. Although the underlying file system may support such names, the operating system does not. However, it is acceptable to start a name with a period."
    Untitled 1

    Jose Manuel Tella Llop news://jmtella.com

    • Proposed as answer by Brian Borg Sunday, September 6, 2009 10:19 PM
    • Marked as answer by Dale Qiao Tuesday, September 15, 2009 2:09 AM
    Sunday, September 6, 2009 8:57 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    When you put a "dot" in the last character in a Folder, the folder dissapears.
    If you press F5, the folder appears again.
    Can you explain me why, please? This is not a expected behavior.

    Thank you and Regards,

       Alvarez Arigós Roberto Miguel
    Hi Roberto

    A 'dot' or 'space' at the end of a folder name are considered illegal characters for a folder name.

    However, unlike other illegal characters, Windows does not display an error when you use these 2 characters. It will let you name the folder with a space at the end and it simply removes the space. In the case of the dot, when you press the F5 (Refresh) key, the illegal character (dot) is removed and the folder will display.

    I'm not sure 'why' Windows 7 does this?

    Hope this helps.


    Thank You for testing Windows 7
    Ronnie Vernon MVP



    Sunday, September 6, 2009 8:29 PM
  • Question
    Sign in to vote
    2
    Sign in to vote
    I'm not sure 'why' Windows 7 does this?
    Windows 95, 98, NT,...etc... Windows 7. 

    14 years old


    "Do not end a file or directory name with a trailing space or a period. Although the underlying file system may support such names, the operating system does not. However, it is acceptable to start a name with a period."
    Untitled 1

    Jose Manuel Tella Llop news://jmtella.com

    • Proposed as answer by Brian Borg Sunday, September 6, 2009 10:19 PM
    • Marked as answer by Dale Qiao Tuesday, September 15, 2009 2:09 AM
    Sunday, September 6, 2009 8:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks.
    Can you give me an adress for suggest correction of this issue?

    Regards,

       Alvarez Arigós Roberto Miguel

    Sunday, September 6, 2009 9:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Windows 95, 98, NT,...etc... Windows 7.

    14 years old


    "Do not end a file or directory name with a trailing space or a period. Although the underlying file system may support such names, the operating system does not. However, it is acceptable to start a name with a period."

    I wouldn't doubt if it goes back all the way to CP/M.
    Sunday, September 6, 2009 10:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks.
    Can you give me an adress for suggest correction of this issue?

    Regards,

       Alvarez Arigós Roberto Miguel

    issue?.... :-)

    by design.  All operating systems

    Untitled 1

    Jose Manuel Tella Llop news://jmtella.com

    Monday, September 7, 2009 10:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The system cannot display a message with a text "You can't put a dot"??
    In 2009?? In Microsoft Windows 7??
    By DESIGN???
    I'm generating an script for this and sending you...
    My god...

       Regards,

         Alvarez Arigós Roberto Miguel
    Monday, September 7, 2009 3:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    In 2009?? In Microsoft Windows 7??
    By DESIGN???

    nope... by design: 1995.

    Untitled 1

    Jose Manuel Tella Llop news://jmtella.com

    Monday, September 7, 2009 3:54 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    A dot at the end of a raw folder name would indicate to the sytem that is in fact a file not a folder. When placing the dot after the raw folder name and no extension is found it can't create it as a file so the folder can not be displyed during the naming correction process. Inserting illegal charecters into a folder or file name is easily detected and an error messege is displayed but the dot is a more of an instruction than a charecter which is why the folder disappears untill it's refreshed.
    Monday, September 7, 2009 5:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I don't know.  A dot within a folder name is perfectly legal.  It doesn't even, by itself, cause a long filename to ge generated.

    C:\Users\Brian>md folder.new

    C:\Users\Brian>dir/ad/x
    . . .
    08/11/09  11:20 AM    <DIR>          DOWNLO~1     Downloads
    09/07/09  02:57 PM    <DIR>                       folder.new
    08/31/09  05:48 PM    <DIR>          LOCALS~1     Local Settings

    If you try to generate a folder name ending in dot in a command window, the dot is ignored.

    C:\Users\Brian>md folder.

    C:\Users\Brian>dir/ad/x
    . . .
    08/11/09  11:20 AM    <DIR>          DOWNLO~1     Downloads
    09/07/09  03:01 PM    <DIR>                       folder
    08/31/09  05:48 PM    <DIR>          LOCALS~1     Local Settings

    I think it's a throwback to earlier times, possibly kept for backward compatibility.  How far back?  As long as the beginning of 8.3 filenames.

    I think it is no longer needed and could be abolished.  I also think that if it is illegal, there is no reason why Windows shouldn't tell us.  It does for other ilegal characters, such as colon:

    C:\Users\Brian>md folder:
    The filename, directory name, or volume label syntax is incorrect.

    Monday, September 7, 2009 8:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    A dot on within a folder name is not an illegal charecter. Only if it is the last charecter so an error messege can't be displyed if a dot is entered like it would be for a backslash becouse there is a possibility more charecters will follow the dot thus making it an acceptible folder name. The only time windows can detemine the final dot is illegal is when the rename command is executed but not during the time the charecter is enterered.

    Monday, September 7, 2009 8:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    My whole point is that it does not need to be illegal to end a folder name with a dot.

    Using that as a flag for differentiating folders from files goes back to 8 bit operating systems.
    Monday, September 7, 2009 8:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    When you have a dot at the end of a raw file name it just removes it but the file stays on the desktop no need to refresh. A file with a dot at the end of a raw file name would have null value for the extension so the dot is remaved.
    It would be impossible to change how folders are named without files along with it so making a final dot legal for a folder is unsolvable.
    Monday, September 7, 2009 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No one is arguing here. Why don't you mind your own business derosnic.  Your a trouble maker and can mark my post as helpful or just leave me alone for that matter and please keep your nasty comments to your self.



    I was trying to bring some friendly levity into the conversation.  I thought everyone adores Manhatten Transfer.

    The famous wholesome musical group, that is.




    Regarding this silly little problem with embedded dots, I agree with bnborg's assessment.


    Please stay on topic.
    Monday, September 7, 2009 8:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You can't have a null value file extension. Dot nothing.
    Folder name rules are linked to file naming rules because the're both part of the file system - according to my Pentium D a folder is actually a file that refers to a subgroup of categorized files.
    Monday, September 7, 2009 8:50 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Please stay on topic.




    Mr Zyklon B, why'd you just change your name from Mr Manhatten Transfer ?  I hardly had chance to get used to Mr Seven.


    Of course you can have a null extension.  That is by definition what a filename without any dot has.  A null extension.

    Monday, September 7, 2009 8:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You can't have a null value file extension. Dot nothing.
    Folder name rules are linked to file naming rules because the're both part of the file system - according to my Pentium D a folder is actually a file that refers to a subgroup of categorized files.

    I realize that the dot is not really part of the name in 8.3 FAT file systems.

    But NTFS?  Really?
    Monday, September 7, 2009 9:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It's more of an instruction if it's the last dot in the string.
    The problem could be solved if there was a special charecter reserved for dividing file extensions and raw file names.

    Monday, September 7, 2009 9:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Please stay on topic.




    Mr Zyklon B, why'd you just change your name from Mr Manhatten Transfer ?  I hardly had chance to get used to Mr Seven.


    Of course you can have a null extension.  That is by definition what a filename without any dot has.  A null extension.


    So, what applications should we assign to open these files with null extensions?

    This would be a file with no extension not null extension.
    Monday, September 7, 2009 9:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually, there is a registry entry for that.  Just a dot.  Or, is it dot-space?  I forget.

    I have to search back, but quite some time ago, somebody in this forum posted a workaround for dealing with Indexing it.  It was a clever hack.  In fact, I vaguely recall bnborg suggesting some global way to get Word to open in a similar fashion.  bnborg, do you remember that thread?


    Oh, I just took a quick look in the registry.  The first entry in HKCR is  * 



    But that's not the point anyway.  This thread is not about applications' recognition of extensions.  Mr nameoftheday, you've evasively changed the subject.

    Monday, September 7, 2009 9:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    In the classes root file list? I haven't seen that type of file. Would it look like  "filename."? 
    Monday, September 7, 2009 9:21 PM