Filename Doesn't Appear As Expected After File Operation

 Last reviewed: April 4, 1997
Article ID: Q102505
The information in this article applies to:
  • Microsoft Windows NT operating system, version 3.1
  • Microsoft Windows NT Advanced Server, version 3.1

When you locate or group files in File Manager and CMD.EXE, files are identified by the filename extension that comes after the LAST period in the filename. However, when you perform a file operation, such as copying a file, File Manager and CMD.EXE use the filename extension that comes after the FIRST period.

This situation may produce undesired results when you rename a file using wildcards (such as *). For example, when you rename a file called MY.TEST.DOC.TXT by typing, *.BAK, the new filename for MY.TEST.DOC.TXT will be MY.BAK.

Additional query words: prodnt
Keywords : kbother ntfilesys
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.