Well, as long as no severe errors occur, this thing MAY run half an hour or one full hour for thousands of images.
The .bat files work well on Windows, and also helped me to not delay the release until next year because true recursion *within* the app is no 5-minute job.
BTW, if you really DO want one log file with probably hundreds of megabytes, you can run
or also redirect the error output by
Currently I'm using by-file logging, which probably puts 1000's of log files into the \logs\ folder, BUT can be read with any editor, or better, viewer
Another good idea would be to fire lots of those logs to a good multi-file capable ASCII text viewer and then simply browse through all the information.