Bible Analyzer User's Forum

I am using Windows 10, and I invoked Bible Analyzer from a TCC (like 4DOS) command line as follows:

bibleanalyzer://search+av/"mark iniquities"

It did successfully invoke Bible Analyzer, and searched the Authorized Version. However, two problems occurred:

(1) It only searched for the single word "mark", and it did not search for the quoted string "mark iniquities".

(2) When I tried to invoke the internal help by pressing function key F1, it emitted an error: "Bible Analyzer cannot find the User Manual (help.chm). It is expecting to find it in this folder: [followed by whatever directory is the current working directory]. Try reinstalling Bible Analyzer."

What do I have to do to get the //search function to search for a "double-quoted string" ?

What is wrong that BIble Analyzer cannot find the User Manual? The help message is a little concerning, because BA should be searching the same directory as BibleAnalyzer5.exe (not the currently logged directory), and the User Manual is named manual.chm, not help.chm. I suppose I could copy "manual.chm" to a new file named "help.chm" and see if it works, but I think I should notify you so the issue can be fixed in the code with the next version of Bible Analyzer.

I am using BA for Windows, version 5.6.5.13

Kind regards,

You need to assign the .chm extension to a book viewer. I have it registered to the Calibre book viewer. There are probably others.

You can do it under Apps/personalization/choose a default app for an extension

You can use the built-in Microsoft HTML Help Executable (hh.exe) on Windows, or third-party viewers like SumatraPDF, Okular, Calibre, or CHM Viewer.

wsbones wrote: ↑

Wed Sep 23, 2026 4:00 pm

You need to assign the .chm extension to a book viewer. I have it registered to the Calibre book viewer. There are probably others.

You can do it under Apps/personalization/choose a default app for an extension

You can use the built-in Microsoft HTML Help Executable (hh.exe) on Windows, or third-party viewers like SumatraPDF, Okular, Calibre, or CHM Viewer.

Thank you, my brother, for at least responding to my appeal for help, but I fear that I did not explain the problem correctly. The problem is not that the help file did not come up at all. The problem was caused by invoking the command from any random directory.

Thankfully, I was able to resolve the problem! I modified the TCC alias to change to the directory containing BibleAnalyzer5.exe before continuing with the program, and also to replace all spaces with an underscore. Now it works as expected.

This is the TCC (Take Command Console) alias that works correctly:


Tim, you still might want to change that error message about "help.chm". BibleAnalyzer looks for and finds "manual.chm" when F1 is pushed. BA does not look for "help.chm".

Kind regards,

I'll look into this for v5.7 but it works as expected on my systems and I haven't received any other issues about it that I recall.

wsbones is correct that the .chm extension must be assigned by the OS to reader. The Win help viewer is usually selected by default, but if none is selected the error dialog comes up.

I did fix the name in the error dialog. Years ago it was called "help.chm". I changed it to "manual.chm". The path listed is the same.

Tim wrote: ↑

Thu Sep 24, 2026 10:13 am

wsbones is correct that the .chm extension must be assigned by the OS to reader. The Win help viewer is usually selected by default, but if none is selected the error dialog comes up.

This is what I see in my Windows 10 installation (yes, I am aware that Windows 10 is currently out-of-support by Microsoft). I am able to view and edit the configuration by going to "Settings > Default Apps > Choose default apps by file type". The filetype is currently associated with "Microsoft HTML Help Executable". What would be the advantage (if any) of changing the association to a third-party e-book reader?

Tim wrote:

I did fix the name in the error dialog. Years ago it was called "help.chm". I changed it to "manual.chm". The path listed is the same.

Hmmm ... I can no longer reproduce the original error, even when I follow the same steps that created it last week! That's one of the strange things about computers. (smile)