ExamDiff is a slim, lightweight software tool to load and compare two different versions of the same document, or two related documents, to see where changes were made. It is a good tool for both students and teachers to review the changes that have been made to a document.
Quickly compares files for review: Whether you're checking for the first time or comparing files that have been updated a handful of times, ExamDiff will quickly check for differences and display them for you in a visual format that, while not cutting edge in terms of graphics, is very effective in laying out key differences.
Developer friendly output of your files: Saving differences in a standard UNIX DIFF file, the software is designed to display and save content in a format friendly to developers. Settings are highly customizable, and the interface is quick and responsive for moving between changes rapidly.
Lacks manual or tutorial: While the README file outlines each of the features and most of the options for using them, ExamDiff is limited when it comes to training or tutorials. For non tech-savvy users, the software will be tough to use to its fullest capacity.
While not a perfect solution and only a nominal replacement for online tools that do the same, ExamDiff is effective for basic comparison functions of text content. Whether you are grading papers or writing your own and need to compare it to another version, ExamDiff will handle the basics effectively.
ExamDiff is a Freeware Windows tool for visual file comparison. Features: Toggles between the first and second files. Automatically detects file changes and prompts the user to re-compare files. One push re-compare function which attempts to leave the viewer's focus in the same place as before the re-compare. Saves the standard UNIX DIFF file.
What's new in this version:
Version 1.9 of ExamDiff adds an new command line options, Windows 7 support.
It can erroneously report that some files are mismatched and thus non-identical during binary compare. You get a list of such files, which might bring you to conclude something failed during a previous backup or copy job. No indication is giving about a possible failure in the program. Only on digging further do you get a message back that there was actually some type of "out of memory" error during the comparison. So, the mismatch error is not generated by an actual mismatch but by the program's inability to perform its task. It should at least tell you this straight up. Researching this problem on the net leads nowhere.