Home > Updates, exf > exf 1.0.1.6 released

exf 1.0.1.6 released

June 15th, 2009

A new build of the console application exf has been posted.

Version 1.0.1.6 (download, info) fixes problems with batch files.

Due to the way Windows handles Unicode output in consoles, exf was “terminating” batch files any time exf was called from a batch file. The only way I could find to fix this problem was to have exf revert the output mode to ANSI after the work is complete. What this means is that visually, Unicode characters in the console window will appear as boxes, but the actual data is still being written as Unicode. So, if you are redirecting output to a file, nothing is lost as the output is still UTF-8. It’s only what appears in the console window that is altered.

Anyway, this means you can now use exf properly in a batch file. Yay!

Brandon Updates, exf , ,

  1. ps
    June 24th, 2009 at 20:30 | #1

    A app such as this one that works with Unicode files would be great. In fact, your program incorporates several features my current sumcheck application does not. I hesitate to install it, however, because it does not validate one of the most common (for me in any case) sumcheck values – TTH. Is there any plan to employ the TTH format in a future version?

  2. Brandon
    June 25th, 2009 at 07:49 | #2

    I don’t have any current plans to implement TTH support, but I’ll add it to the wish list.

  3. ps
    June 27th, 2009 at 13:52 | #3

    Thank you for your reply, and thanks for considering TTH as a format. Incorperating it into a future version (even a distant one) would be much appreciated.

  4. Johan
    July 13th, 2009 at 12:27 | #4

    Thanks for the unicode, I’m using 1.0.1.6 command line version. Creation of checksum files works fine, as you say, the redirected output to a file is fine. Both from cmd line and script.

    However, if you redirect the output of the CHECKING of a checksum file (exf.exe -c theChecksumFileInCWD > c.txt) it sometimes corrupts the command prompt, yet the file turns out OK. The main problem is that if you do the same from a script the output file messes up the unicode chars.

    So it seems, the creation of of checksum file is fine for unicode, but checking the checksum file is still buggy as far as unicode goes. It works with > at the command line, but not from a script… the unicode chars get corrupted in the output txt file.

    Perhaps add the -otf argument to checking as well?

  5. Jake
    July 16th, 2009 at 02:42 | #5

    Just wanted to thank you for creating this app!

  6. Feroze
    July 28th, 2009 at 22:23 | #6

    Hey Brandon,
    I really like your program and its GUI. One thing which would make it great is a deselect all button in the make checksums. It’s rather painful deselecting each box.

    Also it would be nice if you could make a native Linux port. I use Ubuntu often and find the BASH commands too long. There is NO GUI app in linux to do this. It would be great if yours could be the first :D

  7. Brandon
    July 29th, 2009 at 08:28 | #7

    There is a deselect option. Right-click the checksum methods area and select “Select None.”

    It is highly unlikely there will ever be a Linux version of ExactFile.

  1. No trackbacks yet.