Page 1 of 1
Output Log Update Trigger?
Posted: 13 Oct 2022, 03:58
by mz1888
Hi, AllDup would fail given certain archive type i.e. RAR. When investigating which exact file failed the entire search, I noticed the output log does not capture the scanned file process periodically. It would only save after the scan is completed. But a bad file causing AllDup to fail would never allow AllDup search to complete...
It's the portable version and the option "Log every x munites the search statistic of the search progress info" is set to 5 mins.
Re: Output Log Update Trigger?
Posted: 13 Oct 2022, 09:42
by Administrator
Can you explain "fail" in more detail?
Re: Output Log Update Trigger?
Posted: 13 Oct 2022, 12:07
by mz1888
The app would crash leaving no trace, no debug window appeared and the output console displaying the problem files also disappear.
When checking the log file i.e. AllDup4.txt, there's no record as the output file only gets updated if a scan is completed i.e. not crash.
Re: Output Log Update Trigger?
Posted: 13 Oct 2022, 18:27
by Administrator
Go to the options and open the temp folder of AllDup.
You will find some temporary log files (*.txt) from your last file scans.
The last scanned archive file is only shown at the progress window.
I guess a screen recorder tool would help to identify the last scanned archive file.