4.5b (4.52.0.2176) is available for download.
If you have automatic updates turned on, 4.5b will be downloaded automatically the next time your system checks for updates. To install it right away, enter the Update Now command. If you encounter problems with the auto update, download 4.5b from this link.
Release Notes
This release includes Community Notes, social sharing, and initial support for video resources.
Diagnostic Logging
Thanks for the new note icons.
What Does God Say and How Does He Say It? | Learn to Study the Bible Using the Inductive Method
Very excited for social sharing!
Samsung Series 7; Windows 8 64 bit; Intel Core i7-3635QM @2.4GHz; 8 GB RAM; 1 GB NVIDIA GeForce GT640M
I have attempted to install the new update on my Windows 7 laptop twice from the link, and twice from the download. Each time I received an access error from Logos for C:\Users\User\AppData\Local\Logos4\System\Libronix.DigitalLibrary.Guides.dll. I have double-checked permissions for all of the directories, as well as disabled my firewall and anti-virus software. Fifth attempt resulted in a blue-screen data dump.
Any other suggestions?
Rob.
Rob: I have attempted to install the new update on my Windows 7 laptop twice from the link, and twice from the download. Each time I received an access error from Logos for C:\Users\User\AppData\Local\Logos4\System\Libronix.DigitalLibrary.Guides.dll. I have double-checked permissions for all of the directories, as well as disabled my firewall and anti-virus software. Fifth attempt resulted in a blue-screen data dump. Any other suggestions?
Same directory, but different file compared to thread => "Error writing to file" when attempting to install an update.
Keep Smiling
Logos Wiki Getting Started Logos 5 Beta
Keep Smiling 4 Jesus :): Rob: I have attempted to install the new update on my Windows 7 laptop twice from the link, and twice from the download. Each time I received an access error from Logos for C:\Users\User\AppData\Local\Logos4\System\Libronix.DigitalLibrary.Guides.dll. I have double-checked permissions for all of the directories, as well as disabled my firewall and anti-virus software. Fifth attempt resulted in a blue-screen data dump. Any other suggestions? Same directory, but different file compared to thread => "Error writing to file" when attempting to install an update. Keep Smiling
Try this:
When you run Logos to install an update, right-click on the Logos icon and Select "Run as Administrator". When you get asked to restart Logos to complete the installation, shut Logos down and follow the same method to start again "right-click and "Run as Administrator").
Randal M Lane: Try this: When you run Logos to install an update, right-click on the Logos icon and Select "Run as Administrator". When you get asked to restart Logos to complete the installation, shut Logos down and follow the same method to start again "right-click and "Run as Administrator").
Note: "Run as Administrator" may change location of Logos 4 folder (to reside within administrator's account).
Personally using Logos 4.5b on a standard account in Windows 7. Elevation to administrator has been requested a couple times by Logos 4 installer for software prerequisites.
If need to "Run as Administrator", then suspect folder permission issues, wiki has => Fixing Logos 4 folder Ownership
Keep Smiling 4 Jesus :): Randal M Lane: Try this: When you run Logos to install an update, right-click on the Logos icon and Select "Run as Administrator". When you get asked to restart Logos to complete the installation, shut Logos down and follow the same method to start again "right-click and "Run as Administrator"). Note: "Run as Administrator" may change location of Logos 4 folder (to reside within administrator's account). Personally using Logos 4.5b on a standard account in Windows 7. Elevation to administrator has been requested a couple times by Logos 4 installer for software prerequisites. If need to "Run as Administrator", then suspect folder permission issues, wiki has => Fixing Logos 4 folder Ownership Keep Smiling
I've never known a single instance where "Run As Administrator" changes location. If you log into Windows as "Administrator" and install Windows logged in with that Account, yes, there could/will be location issues, of course.
Randal M Lane: Keep Smiling 4 Jesus :): Randal M Lane: Try this: When you run Logos to install an update, right-click on the Logos icon and Select "Run as Administrator". When you get asked to restart Logos to complete the installation, shut Logos down and follow the same method to start again "right-click and "Run as Administrator"). Note: "Run as Administrator" may change location of Logos 4 folder (to reside within administrator's account). Personally using Logos 4.5b on a standard account in Windows 7. Elevation to administrator has been requested a couple times by Logos 4 installer for software prerequisites. If need to "Run as Administrator", then suspect folder permission issues, wiki has => Fixing Logos 4 folder Ownership Keep Smiling I've never known a single instance where "Run As Administrator" changes location. If you log into Windows as "Administrator" and install Windows logged in with that Account, yes, there could/will be location issues, of course.
The purpose of Windows "Run As Administrator" functionality is to not allow unprompted installation of software, and other activity, so as to prevent viruses and malware from installing unwanted prgrams. It does not change the installation location/etc. Unattended installations are prevented by requiring right-click/Run-As-Administrator usage, or getting the myriad of annoying UAC prompts you could recall from using Vista if you were so unfortumate to have had a Vista installation previously.
I installed Logos while logged in with my primary account. And every time there is an update, I follow the procedure above, and I never have a problem or falure at all. Using "Run AS Administrator" when you start an instance of Logos that will prompt you to install an update is not really necessary. When it is necessary is when a Logos update has been downloaded and the tray icon says "an Update to Logos Bible Software 4 is ready to be installed". That is when you will likely never have failures like the one you have written about if you shut down Logos (if it is running still) and the use the right-click/Run-As-Administrator function to start Logos and install the update.
I followed the routine for this update, and it went smooth as silk. It took a few minutes, but no issues. I do like that the Logos engineers, when distributing a software update (does not apply to resource updates), stopped prompting users with "Restart Logos Now" in the tray, which, if followed, would restart Logos with teh option to Run-As-Administrator. However, now the Logos software update completes and shuts down Logos, but gives not user feedback stating that the update is finished and Logos can be restarted again.
Randal M Lane:The purpose of Windows "Run As Administrator" functionality is to not allow unprompted installation of software, and other activity, so as to prevent viruses and malware from installing unwanted prgrams. It does not change the installation location/etc.
Observation: Windows "Run As Administrator" changes registry key HKEY_CURRENT_USER to the administrator account and associated environment variables, including %LOCALAPPDATA% that is the default location for your Logos 4 folder (includes logos4.exe software).
Logos 4 is installed for each user, which allows one computer user to install stable Logos 4 while a different user can install beta Logos 4.
In contrast, Libronix 3 to standard program files location so one installation could be used by all users on a computer. For license syncing using Libronix 3, personally use "Run As Administator" since license syncing does not work for my non-privileged user account.
Randal M Lane:I installed Logos while logged in with my primary account. And every time there is an update, I follow the procedure above, and I never have a problem or falure at all.
Appears two different approaches both work: one uses "Run As Administrator" a lot while the other does not.
Caveat: personally have experienced a number of Logos 4 Beta crashes, with subsequent reporting in PC Beta forum: e.g. => Crash in Home Page
Keep Smiling 4 Jesus :):In contrast, Libronix 3 to standard program files location so one installation could be used by all users on a computer. For license syncing using Libronix 3, personally use "Run As Administator" since license syncing does not work for my non-privileged user account.
You can use \Libronix DLS\System\LDLSAdmn.exe to give that permission to any user from an elevated Command prompt eg.
LDLSAdmn /s /a UserId
(you can remove that permission with /d instead of /a)
Keep Smiling 4 Jesus :):Observation: Windows "Run As Administrator" changes registry key HKEY_CURRENT_USER to the administrator account and associated environment variables, including %LOCALAPPDATA% that is the default location for your Logos 4 folder (includes logos4.exe software).
Whilst I haven't verified that, problems arise whenever Logos is installed with "Run As Administrator" as it usually requires the same permission for subsequent software updates (but not resource updates). Normally, if elevation is required the Logos installer will request it (usually in a Standard User account). I have no problems running Logos in Standard User and Administrator accounts on the same computer.
If the Take Ownership procedure does not permanently correct the OP's problem then it is best to reinstall after completely removing Logos 4.
Dave===
Windows PC, Android phone
Well, you guys are far more informed than myself. I know in previous updates, I had to do a right-click/administrator to avoid an install error (it's located under my account; not admin).
But this time I didn't have to do a right-click/administrator install. I assume they fixed something?
Many Thanks to everyone for your input. The "run as Administrator" routine worked. Just hope I'll remember it next time!!
Just a note about a fishy Logos upgrade, especially one done as Administrator. My pastor threw in a story this morning about him doing a Bible software upgrade. He told us of an especially long upgrade he was doing. While he was in the midst of it, he received a phone call. It was from someone with a foreign accent saying he was from Microsoft and that they had determined pastor had a virus on his computer and that the caller could help him get rid of it.
The caller spoke for awhile, pastor didn't go into detail, but when he was asked for his e-mail address, pastor suddenly got wise to what was going on. The way I understand it, he ended the call, however the next thing that happened was his PC screen suddenly changed color and the mouse pointer began moving without his help - apparently someone had taken control of his computer.
When I got home, my netbook wanted to do a Logos upgrade. As it is seldom connected to the internet, I allowed it. Then, a little while later, when it wanted to do another much longer upgrade, I got wise and checked first here on the forum and then I sent pastor a quick note on Facebook. Here's the exchange.
You may do as you please, but as for me I think I'll wait till Monday when I can check with Logos before I do any more upgrades.
Gerry
Gerald P. Swetsky: While he was in the midst of it, he received a phone call. It was from someone with a foreign accent saying he was from Microsoft and that they had determined pastor had a virus on his computer and that the caller could help him get rid of it.
While he was in the midst of it, he received a phone call. It was from someone with a foreign accent saying he was from Microsoft and that they had determined pastor had a virus on his computer and that the caller could help him get rid of it.
This is a nasty scam that's been running for a number of years: http://www.guardian.co.uk/world/2010/jul/18/phone-scam-india-call-centres
Most likely, one of the "diagnostic" steps they asked him to perform installed malware on his computer.
All programs produced by Logos are digitally signed, so if you're concerned about their authenticity, you can check the digital signature (right-click the file, choose Properties, then choose the Digital Signatures tab).
But if the caller is a child who says "Seven Days", you'd better run.
HP Pavilion dv6, i3, 4GB RAM, Win 8 Pro (64b)
Samsung Galaxy S 4G - OS ver 2.3.6
Seeing the Kingdom
Bradley Grainger (Logos):All programs produced by Logos are digitally signed, so if you're concerned about their authenticity, you can check the digital signature (right-click the file, choose Properties, then choose the Digital Signatures tab).
Just out of curiosity, how does one find this on Mac? Can't seem to figure it out.
Mac Mini late 2010 8GB RAM 10.6.8
fgh:Just out of curiosity, how does one find this on Mac? Can't seem to figure it out.
I don't know. That would be interesting to find out. I do know that Apple will release a new digital signing program with 10.8 "Mountain Lion" this summer.
Mac | iOS | L5 Gold | Win Logs | Mac Logs
alabama24: fgh:Just out of curiosity, how does one find this on Mac? Can't seem to figure it out. I don't know. That would be interesting to find out. I do know that Apple will release a new digital signing program with 10.8 "Mountain Lion" this summer.
On Mac OS X, can right click on Application, then click Get Info to show version and copyright (albeit does not have digital signature).
Also can enable diagnostlc logging on Mac and PC, then look in Indexer.log to see MD5 sum check for downloaded application update. Mac has one dmg (disk image) file to verify using MD5 while PC had 8 files to verify for update from Logos 4.5b Release Candidate 1 to Logos 4.5b Release Candidate 2.
Wikipedia has MD5 information => https://en.wikipedia.org/wiki/MD5 that includes recommendation to use SHA-2 instead of MD5.
fgh: Just out of curiosity, how does one find this on Mac? Can't seem to figure it out.
Logos 4 isn't digitally signed on Mac yet, but will be in the future.
As far as I know, the only way to verify an app's digital signature is by using "codesign -v". (See http://developer.apple.com/documentation/security/Conceptual/CodeSigningGuide/Procedures/Procedures.html.) It's possible that Apple will make this more visible in 10.8 since they're introducing Gatekeeper (but I'm not running Mountain Lion, so I haven't checked).