Bible Analyzer User's Forum

BA 5.6.1.10 portable, Windows 11

Using AVs and I have the options II "Make Bible Italics Gray" option unchecked and "Show Red letters" checked. In Luke chapter 16 (and more chapters, easiest to see in chapters with lots of red letters) italicized words are changed to black (they turn to gray if the option is turned on).

Yes, it defaults to black but needs to use the current line color. Will put it on the fix list.

Thanks

Tim wrote: ↑

Fri Aug 30, 2024 2:28 pm

Yes, it defaults to black but needs to use the current line color. Will put it on the fix list.

Thanks

Thank you!!

5.6 will not launch on fully updated Windows 7 64bit (SP1 with offline update pack installed).

Error: "This program can't start because api-ms-win-core-path-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem".

The download link for the older version has the same problem as the Mac OS link for the older version (the URL is invalid but can easily be fixed by copying/pasting and removing the extra www.bibleanalyzer.com).

5.5.1.18 runs fine on the same Windows 7 machine.

I fixed the link. It looks like v5.5 may be the latest Bible Analyzer version for Win 7.

I wrote too soon. After installing the offline update pack, Windows update now wants to work (I mistakenly assumed the update pack had all the updates available for Win7). It's quite a few updates and I have a busy day today but I'll try 5.6 again after I'm sure it's fully updated.

So, the motherboard fried on that Windows 7 machine and I had to recreate the whole environment in a virtual machine. This time it was actually fully updated. I installed the offline update pack and then ran windows update installing every update available (including optional). The result was the same: BA 5.6.1 will install but will not launch due to the same error. BA 5.5.1.18 installs and runs fine.

I also tried again on the same Windows 7 but on an iMac 7.1 (analog recording machine from something someone was throwing away - I repurposed this one after the mobo fried in the other one) and BA 5.6 will not launch for the same reason.

I did a little more digging into the error itself (to see if it could be fixed) and found this:

https://superuser.com/questions/1660386 ... r-computer

which leads to this:

https://bugs.python.org/issue41412

and this:

https://peps.python.org/pep-0011/

The gist of it all is that Python 3.9 dropped support for Windows 7 ~4 years ago. Python 3.11 (and thus BA 5.6) requires a minimum of Windows 8.1 according to multiple sources. Just confirming that indeed 5.5 is the last version (available for download from the main web site) for Windows 7 and the minimum requirement for 5.6 is Windows 8.1.