title: Why does comparing two files using FC.exe with /b option produce different results between manual and batch execution?
body: <p>I try to compare two files byte by byte using <code>fc.exe</code> with option <code>/b</code> for a binary compare.</p>
  
  <p>When I run the command from within a command prompt window, the output lists the binary differences.</p>
  
  <p>For example the command:</p>
  
  <pre><code>C:\Work\jan21\script&gt;fc.exe /b C:\abc\2.0\common.c C:\Users\rakeshk\Desktop\download_break\final\common.c &gt;b.txt
  </code></pre>
  
  <p>results in <code>b.txt</code> containing:</p>
  
  <pre><code>Comparing files C:\ABC\2.0\common.c and C:\USERS\RAKESHK\DESKTOP\DOWNLOAD_BREAK\FINAL\COMMON.C
  00000994: 20 09
  00000995: 20 69
  00000996: 49 6E
  00000997: 4E 74
  00000998: 20 0D
  00000999: 20 0A
  0000099A: 55 20
  ...
  </code></pre>
  
  <p>And at end <strong>FC</strong> printed: </p>
  
  <pre><code>C:\USERS\RAKESHK\DESKTOP\DOWNLOAD_BREAK\FINAL\COMMON.C longer than C:\ABC\2.0\common.c
  </code></pre>
  
  <p>But when I run in batch file for example this command line</p>
  
  <pre><code>fc.exe /b !FILE1! !FILE2!&gt;c.txt
  </code></pre>
  
  <p>the file <code>c.txt</code> contains</p>
  
  <pre><code>Comparing files C:\USERS\RAKESHK\DESKTOP\DOWNLOAD_BREAK\FINAL\COMMON.C longer than C:\ABC\2.0\common.c
  FC: no differences encountered
  </code></pre>
  
  <p>Why is <strong>FC</strong> printing that there are no differences encountered although the files have different contents?</p>