Help and Support

"No Such File or Directory" Message with File Compare (FC.EXE)

Article ID:134571
Last Review:November 15, 2006
Revision:1.1
This article was previously published under Q134571

SYMPTOMS

When you use the file compare command, Fc.exe, and you use wildcards in the second argument of the command, the Fc.exe command reports that there is no such file or directory.

For example, if you have two files in a directory, one named a_long_file_name and the other named a_really_long_file_name, when you carry out the command
   fc a_long_file_name a_really_*
				
the fc command reports
   Comparing files a_long_file_name and a_really_le_name
   FC:cannot open a_really_le_name - No such file or directory
				
instead of the expected action of comparing the a_long_file_name file to the a_really_long_file_name file.

Back to the top

CAUSE

When you use wildcards in the second argument, the Fc.exe command matches the second argument against the first argument instead of matching the files in the current directory.

Back to the top

RESOLUTION

Type the second argument in full if you do not intend to match the second argument against the first argument.

Back to the top


APPLIES TO
Microsoft Windows 95

Back to the top

Keywords: 
KB134571

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.