I am sitting at a coffee house right now and doing some programming..On a Saturday… I am a little dorky I know. I ran into a need for a file comparer utility. I had used some differnt ones before but being that i just updgraded to windows 7. I  didnt have the one that used to have and i needed a new one.

Low and behold there is a file comparer utility in visual studio that i didnt know about.

WinDif a tool that graphically compares the contents of two ASCII files, or the contents of two folders that contain ASCII files, to verify whether they are the same. The file byte count and the creation date are not reliable indications

To compare two files by using Windiff.exe, follow these steps:

1. Start Windiff.exe. - C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\x64\WinDiff.Exe deppending your settup
2. On the File menu, click Compare Files.
3. In the Select First File dialog box, locate and then click a file name for the first file in the comparison, and then click Open.
4. In the Select Second File dialog box, locate and then click a file name for the second file in the comparison, and then click Open.
   The information in the right pane indicates whether there is a file difference.
5. To view the actual file differences, click the first line in the Windiff.exe output results, and then on the Expand menu, click Left File Only, Right File Only, or Both Files.
   The color-coded results indicate what the file differences are.

To compare two folders by using Windiff.exe, follow these steps:

• Start Windiff.exe.
• On the File menu, click Compare Directories.
• In the Select Directories dialog box, type the two folder names that you want to compare in the Dir1 and Dir2 boxes. If you want to include subfolders, click to select the Include subdirectories check box.
  The information in the right pane indicates the differences between the two folders.
• To view the actual file differences, click the line that you want in the Windiff.exe output results, and then on the Expand menu, click Left File Only, Right File Only or Both Files.
  The color-coded results indicate what the file differences are.

You can also run Windiff.exe from the command line. For information about how to do so, or for more information about how to use Windiff.exe, see the Windiff.exe Help file (Windiff.hlp).
There are other utilities that are available besides Windiff.exe that you can use to compare local ASCII and binary files, or to compare a local file to a questionable file at a remote site.
To compare two files or groups of files at a local site, you can use the Fc.exe and the Comp.exe file compare commands. Both commands are run from a command prompt.
You can use Fc.exe to compare two ASCII or binary files on a line-by-line basis. It offers several command-line options. For example, use the fc /b command to compare two binary files. For a complete list of options, type fc /? at a command prompt.
You can use Comp.exe to compare ASCII and binary files and to compare groups of files in two different folders. For example, to compare all the .dll files in one folder to all the .dll files in the same folder on a different computer, type the following at a command prompt:

comp C:\Winnt\System32\*.dll \\DifferentComputerName\C$\Winnt\System32\*.dll

To compare a local file to a remote file, you can use a utility such as the third-party compression utility Pkzip.exe. To do so, use Pkzip.exe to zip the file at both the local and the remote sites. Because zipping a large file can take time, it is faster to use the pkzip -e0 (no compression) option. After you have zipped the files, use the pkzip -v command to examine the cyclic redundancy check (CRC32) value for the .zip files. If the CRC32 values are the same for the remote and local sites, the files are the same.
Note If you use Pkzip.exe to zip a file before you send the file to a remote site, because of the embedded CRC32, you will receive an error message during the unzip process if the file is damaged in transit. If you receive no error message, the file was conveyed without damage.
 

Woot free software and I didnt have install nada…