To immediately update to the current beta enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Release Notes
Mac
Windows
Well...
Events are still missing their icon (Context menu), and the central vertical slider is still difficult to operate with its sensitive zone being offset to the left.
Sorry. Double post
Question/Suggestion:
In the release notes of beta 1 there was a link to a nice table for helping typing greek / Hebrew.
https://wiki.logos.com/Logos_8.8_Beta_1
I don't see this link anymore.
Can this table also be made available in the help file? It's really helpful!!
Hans
The update will not work on my machine (Windows 10) - it will stop requiring administrator privileges, but regardless on how I try to run it as administrator, it will claim not to have those privileges and abort the update installation.
Running Logos as admin:
I accept Win10's question to make changes, nevertheless:
I use the download of LogosSetup linked above, and I run as administrator from explorer, again confirming UAT - same issue:
I can use the L8.8 Beta 4 just fine, but see no way to install RC1
Question/Suggestion: In the release notes of beta 1 there was a link to a nice table for helping typing greek / Hebrew. https://wiki.logos.com/Logos_8.8_Beta_1 I don't see this link anymore. Can this table also be made available in the help file? It's really helpful!! Hans
This is the plan, we're working on getting the images right now.
To immediately update to the current beta enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates. The update will not work on my machine (Windows 10) - it will stop requiring administrator privileges, but regardless on how I try to run it as administrator, it will claim not to have those privileges and abort the update installation. Running Logos as admin: I accept Win10's question to make changes, nevertheless: I use the download of LogosSetup linked above, and I run as administrator from explorer, again confirming UAT - same issue: I can use the L8.8 Beta 4 just fine, but see no way to install RC1
N.B. Mick,
Do you have logs?
sorry, forgot to add them earlier:
8510.Logos.zip
The setup log says:
Logging started: 2019-09-25T11:09:19Z
DateTime ThreadID Severity Category Message2019-09-25T11:09:19Z 0xb48 Info Module Initializing module (version 8.8.0.36).2019-09-25T11:09:19Z 0xb48 Info IsSupportedWindowsVersion Current OS version: Major Version 10, Minor Version 0, Major Service Pack 0, Minor Service Pack 0, Build Number 183622019-09-25T11:09:19Z 0xb48 Info IsSupportedWindowsVersion Required OS version: Major Version 10, Minor Version 0, Major Service Pack 0, Minor Service Pack 0, Build Number 143932019-09-25T11:09:19Z 0xb48 Error GetSpecialFolder SHGetFolderPath returned 0x80070003. Did user RunAs... on XP with "Protect my computer and data from unauthorized program activity" checked?2019-09-25T11:09:19Z 0xb48 Error GetSpecialFolder Special folder number 5 could not be determined, using ::GetTempPath.2019-09-25T11:09:19Z 0xb48 Info LogosMessageBox Displaying message box with title 'Logos Bible Software Setup', message 'The selected user does not have sufficient privileges to complete the setup. Please choose Administrator from the Run As… dialog.' and a warning icon.
Thanks, Philana! When this keyboard switcher would be implemented in the notebook, I would be even more excited. These are the things we need imho.
If you disable "Run as admin" on Logos.exe does that fix things?
N.B. Mick, If you disable "Run as admin" on Logos.exe does that fix things?
I normally don't run it as admin at all, just did so manually since the installer requested it.
N.B. Mick, If you disable "Run as admin" on Logos.exe does that fix things? I normally don't run it as admin at all, just did so manually since the installer requested it.
Can you try running with "Run as admin" disabled and let me know what happens?
Edit: and running it again in normal mode does not fix things.
N.B. Mick, If you disable "Run as admin" on Logos.exe does that fix things? I normally don't run it as admin at all, just did so manually since the installer requested it. Edit: and running it again in normal mode does not fix things.
Does your user account have permissions for your Logos folder and all sub folders?
clicking Ja=Yes
Setup log is identical to above, just with a different timestamp. This happens prior to restart of a new Logos.log
If I answer Nein/No, the program will start, and will nevertheless try the installation in the background (as it does normally) and will come up with the same error message as I inserted directly above. This will show up in the logos log as
2019-09-25 22:39:15.7180 25 Error InstallUpdateStageBase Expected the download job status of 'Logos Bible Software 8.8, RC 1' to be Finished, but it was Failed.
8407.Logos.zip
I fully believe so. And even if not, wouldn't the "run as administrator" take care of that?
Does your user account have permissions for your Logos folder and all sub folders? I fully believe so. And even if not, wouldn't the "run as administrator" take care of that?
There can be problems if you run as admin, can you recheck your permissons? I've not been able to reproduce this.
Does your user account have permissions for your Logos folder and all sub folders? I fully believe so. And even if not, wouldn't the "run as administrator" take care of that? There can be problems if you run as admin, can you recheck your permissons? I've not been able to reproduce this.
I checked this, and made sure I have the rights, and tried with and without admin elevation (even Win8 compatibility mode) with no different results. Could it be that it's simply that I'm installed on F:\ rather than on C:\? - just tried something else:
Remembering that I used to have another external HD on \ , I reattached this. Kaboom, it started to install (from the running Logos application) and updated itself to 8.8 RC1 without me instructing it! The documents folder (which in the past used to hold the Logos logs) had been put onto this HD under \ and thus was not present in my prior installation efforts for RC1 (but used to be throughout the betas). Is it possible that an old routine checks write access to the documents folder?
Anyway, I'm glad it's working now. Logs attached in case someone finds something in them: 0167.Logos.zip
EDIT: Thanks a lot, Philana, for your support!
Remembering that I used to have another external HD on \ , I reattached this. Kaboom, it started to install
This is one of the reasons we don't support installing to removable media. If the InstallDirectory registry key doesn't match where you currently have Logos installed you will have a bad time. :-(
