Microsoft KB Archive/102505

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:02, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


Filename Doesn't Appear As Expected After File Operation

Article ID: 102505

Article Last Modified on 10/31/2006



APPLIES TO

  • Microsoft Windows NT Advanced Server 3.1
  • Microsoft Windows NT Workstation 3.1
  • Microsoft Windows NT Advanced Server 3.1



This article was previously published under Q102505

SUMMARY

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 KB102505