When I start Logos 4 after installing today's update it ignores my original install and wants to download 11.9 GB of resources to a new directory structure.
Were you under a different Windows user account at the time, or signed into Logos 4 under a different account? Had you removed any folders before the update?
Hi Melissa
I was on my normal user account and was signed in using my normal Logos account I was prompted to restart after the update downloaded and Logos 4 displayed a screen that said it was downloading 11.9 GB!
same here
Melissa
My install location is c:\users\public\logos4
The update is writing to c:\users\graham owen\app data\local\logos4
It seems to have corrupted my customer install location and created a new default
Melissa My install location is c:\users\public\logos4 The update is writing to c:\users\graham owen\app data\local\logos4 It seems to have corrupted my customer install location and created a new default
I'll let development know, thanks.
Graham -- Devs will want to see your setup logs. Can you attach those here? If you don't have logging enabled, they may be in your Temp folder.
0407.Logos4Beta3Setup.zip
This has messed up my custom install as well - new structure at standard C:\Users\{Dave}\AppData\Local\Logos4 instead of \Beta\Logos4.
It wanted to me to sign-in & then was going to download 7.77 GB which I cancelled. It started indexing but with less than half my actual resources in the new structure.
I had closed L4 before the installation at approx. 0710, gone out and found the Sign-In at approx 1045.
Logging was reset in the Registry so there is no log for the Indexing that took place after 1045 (not in Temp either).
I think I know how to get out of this, but we obviously need to know that the Setup program has been fixed.
The effect of the installation seems to be restricted to the Registry key HKEY_CURRENT_USER\Software\Logos4, where the "InstallDirectory" value was removed in addition to resetting the Logging sub-key and removing the other sub-keys. The Logos4 shortcut was unaffected, the custom System folder was updated to Beta 3 but the lack of a value for the installation directory causes L4 to look in the default user location! Net result - it tried to re-download resources and index them.
I re-created the correct "InstallDirectory" value in the Registry and Beta 3 seems to be running OK with all my resources!
Glad I saw this before I let beta3 install since I have mine installed in d:\logos4. Now I'll just have to not forget and accidently click on the install button since it's downloaded and ready to install. I trust this will be fixed in beta4.
What will happen when beta4 comes out? Will it download that, overwriting the beta3 that I have downloaded but not installed? Or do I need to clear out a cache or something?
Now I'll just have to not forget and accidently click on the install button since it's downloaded and ready to install.
You can delete it from \UpdateManager\Installers in d:\logos4.
Dave ~ Thanks for the logs and for providing a way to 'undo' the change.
This is unfortunate since it affects everyone, not just those who had a custom install directory (I wasn't affected by the install path problem, but my logging had stopped). Everyone in the beta will need to be told to re-enable logging (unless the next beta re-enables it automatically).
veryone in the beta will need to be told to re-enable logging
Thanks for the heads up, Todd. I have now re-enabled logging.
The effect of the installation seems to be restricted to the Registry key HKEY_CURRENT_USER\Software\Logos4, where the "InstallDirectory" value was removed in addition to resetting the Logging sub-key and removing the other sub-keys
I wish that I had seen this before I started trying to reinstall Logos 4... My efforts so far have failed with Logos continuing to insist that it download my resources no matter what I do...
I think my days with Beta Vwrsiosn are over, at least for now.
Compared to a Version 3 reinstall this is a nightmare!
The effect of the installation seems to be restricted to the Registry key HKEY_CURRENT_USER\Software\Logos4, where the "InstallDirectory" value was removed in addition to resetting the Logging sub-key and removing the other sub-keys.
Grumble. What other sub-keys were there that we've lost?
I will send out an all-points alert (or at least all points who read the forums regularly) that people who have upgraded to Beta 3 need to re-enable logging.
Do you have what keys to put in place? I go to the registry and only see:
under Logos4 and Logging:
default REG_SZ (value not set)
If I change Logos4 to E:\Logos4\
it still wants to download so I do not think it is seeing the install directory correctly.
If I change Logos4 to E:\Logos4\ it still wants to download so I do not think it is seeing the install directory correctly.
I hope you can undo what you have done! Logos4 is the key name that refers to the product and must not be changed. Earlier in this thread I referred to a Value name for the Installation Directory that had been deleted and this needs to be restored.
Copy the 4 lines between the ++++++ lines into a new text file, change the folder name using \\ separator (NOT single \) and save it as L4DirFix.reg. Double click the file to update your registry.
Please NOTE: you do this entirely at your own risk!
;++++++++++++++++++++++++++++++++++++++
Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\Logos4]"InstallDirectory"="E:\\Logos4"
after I thought about it I took out what I did an created another sub key and was able to get Logos to start up without wanting to do an install.
Please share what you did.
I deleted the original E:\Logos4\ from:
Default REG_SZ
Created another key by right clicking and selecting "new" "String Value" named it "InstallDirectory" and gave it the value of "E:\Logos4\"
So far so good it seems. Recognized my saved log in, settings and resources installed on the PC. The resource folder has 2,444 files but Logos Library only reports 2,309 resources is this correct?
Please see my response at http://community.logos.com/forums/p/18200/137456.aspx#137456
Thanks,
Bryan
I always track things by remembering what Library says I have. It is always less than the number of files in the Resource folder, so your figures could be OK.
I would really prefer to wait for a FIX in the next beta. I was having a hard time with crashes initially, then everything just settled down.It took some perseverance getting through, but after about 5-6 crashes I experienced a calm. I don't know about the inner workings or what has been written or unwritten there, but its been smooth sailing since the calm. L4 seems to be working well and without crashing.
Question: why should I not wait to see what the next beta brings before going into the internal workings of directories and registries ???
If you had a custom installation and Beta 3 messed it up then a registry fix as described (and endorsed by Logos) is the sure way to get back on track - see http://community.logos.com/forums/p/18200/137730.aspx#137730
I think Beta 4 will be a normal update and assume your installation is correct, but you can confirm that by asking Bryan in the above thread.
My "clever" plan of skipping beta 3 and going direct to beta 4 didn't help any. The beta 4 installer also deleted the key. The only difference from what was described in beta 3 is that beta 4 wouldn't run at all without the key rather than trying to redownload everything.
My "clever" plan of skipping beta 3 and going direct to beta 4 didn't help any
Having got Logos 4 up and running again my clever plan is to avoid the Beta Channel for a while...
Jeffrey, I'll look into this and get right back to you.
Jeffrey,
When you say that it won't run at all, what exactly does it do? When you launch it from the shortcut, do you see the splash screen? Do you see the Sign In screen? Do you get an error message?
From the tests that I've run, I believe that if you add the Logos4 registry key and InstallDirectory value back to your registry that you should be fine--Logos 4 should start like nothing happened. Here are instructions:
If this doesn't work, please post back an explanation of what went wrong, and your log files, and I'll have a look.
I got the dialog message that Windows had to shut down the program. This happened repeatedly. I added the missing registry key and Logos 4 came back up without a problem. I apologize that I didn't make it clear in the original post that I added the "InstallDirectory" string and everything started working OK. I was suprised though that going from Beta 2 to Beta 4 (I even cleared out the UpdateManager directory and downloaded fresh before allowing the update to happen) still deleted the registry entry. Would going from a fixed Beta 3 to Beta 4 have broken it again? Or was this just an artifact of how you build up cumulative updates?
Would going from a fixed Beta 3 to Beta 4 have broken it again?
My fixed Beta 3 updated to Beta4 without a problem. I surmise the key had been removed by Setup in B3 even though you did not allow the actual Update program to run.
