Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently developing an application and compile it to create a .exe file. Then our operations team copy the compiled application in our test client computer.

Now, an error occur when testing the application in the client and the possible cause would be because the complied application in the client is not the latest one.

How can I check that the .exe file in the client and in my development environment are identical?

The file size was the same even when a different compile was made so I can't verify it by comparing the file size. I cant also compare it using the created date because obviously it was only the date when the file is created, in our client's case, the date when the file is copied. We do not implement version yet and I can't use a file comparing application since the client's PC is at different location.

Both mine and the client's OS is in Windows XP.

Please help. Thanks in advance.

share|improve this question
up vote 5 down vote accepted

You can use fc or comp for comparing files. Both will tell you whether or not they are identical.

share|improve this answer
How can I use it if the files that I compare is at different locations, although at the same private network? – John Isaiah Carmona Apr 19 '12 at 5:39
Just specify the location along with the file name? E.g. fc foo.exe \\someserver\share\foo.exe? – Joey Apr 19 '12 at 5:40
Thanks. It seems like they are identical. Now back to debugging. – John Isaiah Carmona Apr 19 '12 at 5:58

You can use a file hash utility like md5 (command line) or HashTab (GUI).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.