Recent Posts

1

Feature Requests and Suggestions / Re: searching text inside PDFs

« Last post by kctech on Today at 02:52:07 »

I recommend Agent Ransack / FileLocator Pro for searching folders of PDFs.
IMHO it doesn't make sense for Matthias to put development effort into a feature that other specialised tools have invested years of effort into and therefore can perform that function much better.

2

Feature Requests and Suggestions / Re: searching text inside PDFs

« Last post by Matthias515566 on Yesterday at 19:35:12 »

You can do this with PDF software such as Adobe Reader or PDF-XChange Editor using the advanced search or folder search feature. This allows you to perform a full-text search across all files in a folder.

3

Feature Requests and Suggestions / searching text inside PDFs

« Last post by JeanneMarie on September 01, 2026, 18:40:38 »

I think this is a pretty big ask, but I've got a whole lot of PDFs and would love to be able to search contents. As it is, you can't help with those that are just scans, but still a lot have text or could be converted.

I have nothing more intelligent to say about this. But if a question comes to mind, I'll try to answer.

Thanks for listening.

4

Support and Feedback / Re: File Verifier start of calculation

« Last post by Mathias (Author) on September 01, 2026, 10:10:03 »

Strange.
Not sure why the behavior is different.

Anyway.. I got it on my list to look over how that extension works.

5

Support and Feedback / Re: File Verifier start of calculation

« Last post by SwissKnife64 on September 01, 2026, 08:08:16 »

When I double click a checksum file, the "File Verifier" opens and the entry is ready for running the check.
When I double click a second checksum file, the second entry is added, but the firs entry gets calculated and shows green the success of verification.

I have to start only the verify of the newest entry by hand.

6

Support and Feedback / Re: File Verifier start of calculation

« Last post by Mathias (Author) on August 31, 2026, 15:53:26 »

"adding a check starts automatically the check of the previous added check..." ?? Dont understand that.

I mean add some settings things that does not require a whole settings framework and UI.. maybe a registry setting or something simple.

7

Support and Feedback / Re: File Verifier start of calculation

« Last post by SwissKnife64 on August 31, 2026, 15:41:50 »

Your comment contradicts the current implementation: adding a check starts automatically the check of the previous added check...
Version (x64) v16.2 (build 3211)

8

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on August 31, 2026, 12:40:09 »

Use-case for text mode
A text file is created in linux. and that file is open on Windows, in an OLD editor so when file is saved (without any changed) it replaces LF with CRLF,  the checksum would still be the same. even if filesize is different and the file content has changed.

Now If you create a file in text mode on linux and compare it on Windows in Binary mode.. they will match.  Only the above very narrow use case will fail.

9

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on August 31, 2026, 12:18:38 »

No it is not a hack. It is an unsupported mode that nobody uses. There is no official spec.

Text mode will not be supported, (Require to much work for something that nobody uses) , it is too weird of a use-case, to much can go wrong.  I never seen anyone support it,  You have checksum to check if file is valid and not changed. Then you want a checksum of entire file. not only some parts of it.

10

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by SwissKnife64 on August 31, 2026, 12:03:01 »

To ignore the format marker for SHA checksum is a HACK, that will work in most cases, but not in all.

SHA1 file can be generated in text or binary mode, and on Linux the default is text!

Command in Linux for text mode: sha1sum -t filename.sha1, the resulting checksum file has "  " as format marker in front of the file name
Command in Linux for binary mode: sha1sum -b filename.ext, the resulting checksum file has " *" as format marker in front of the file name
Without an option, text mode is used

So only reading the marker and calling the calculation in the correct mode is the 100% solution.