Complete with full download of resources!
See http://community.logos.com/forums/t/18189.aspx
I feel lucky. It hasn't done that to me. On the other hand, I haven't reindexed it yet either. Should I hold off on that, or do you think the damage was done from the time of installation?
The way I've read it, its set the installed-directory-path back to default, rather than whatever it was.
If thats what it is, then anyone using defaults will be OK, but everyone with a custom install directory will be impacted!!!
If it affects you, you'l know, because you won't be able to view any resources, and Logos will prompt you to download all your resources.
I've now told Logos where to find the resources, but I have to go through the full index and preparing library stages
I've now told Logos where to find the resources
How did you do this? (As I expect others might get the same problem)
Some built in command or a registery entry or something?
The same way you tell L4 to scan a DVD for resources, except tell it to look for your resource folder on your harddrive. i.e. type in the command bar "scan [resource location]
For me it was "scan C:\Program Files (x86)\Logos4\Data\ggufvktp.4kl\ResourceManager\Resources"
I now have all my resources back, and am in the final minutes of indexing. I think after this I'll resort back to the default update channel, as this series of updates is only bug fixes anyway.
Sorry, but I've been out since my brief foray this morning. I'm not sure about the effect of an upgrade to a standard installation but it is disastrous for custom installations like mine! If you see the Sign In dialogue and you have a custom installation then you are in for a bad time! But I wouldn't do any sort of installation of Beta 3 until Logos tells us that Setup is fixed.
I found a simple registry fix http://community.logos.com/forums/p/18189/137127.aspx#137127 - so hopefully the developers can get any other affected users up and running with the same ease!
Bump this thread for the Warning.
Another BUMP
The way I've read it, its set the installed-directory-path back to default, rather than whatever it was. If thats what it is, then anyone using defaults will be OK, but everyone with a custom install directory will be impacted!!!
I use a custom install and have gone from 4.0cSR2 to 4.0dB3 without any extra downloads...
dont know why it didnt for me but rejoicing..
All the more reason to know that Setup is safe for all users (I think you are the first not updating from a Beta).
Sorry for the trouble. A problem with the Logos4.msi caused Windows Installer to delete the Logos4 registry key, as Dave has pointed out, though it only affected certain users updating along a certain update path.
There are several affected keys, Logging, LastWindowPlacement and InstallDirectory. The first means that if you want logging, which as Rosie pointed out you probably do, you'll need to enable logging again by running EnableLogging.js. The second means that you may need to relocate your Logos 4 main window when you run Logos 4, if you had a special placement for it. The third has the deepest implication but affects only certain users who have installed Logos 4 to a custom location.
If you have installed Logos 4 to a custom location and you update to Beta 3, your existing installation will be fully intact and will be upgraded to Beta 3. However, for some users, when Logos 4 starts, it won't find your custom location and will instead look for its data files in the default install location. Since there won't be any files there (they're in your custom install location), it will assume that you have done a fresh install, will ask you to sign in, will download your licenses and will start downloading all your resources. It will then index them.
As Dave has pointed out at http://community.logos.com/forums/p/18189/137127.aspx#137127, the solution to this problem is simple: you just need to reset the missing registry value. Here are detailed instructions:
If you have a version prior to Beta 2 installed, or you installed Beta 2 from scratch, you should be able to update to Beta 3 with no trouble.
If you have Logos 4 installed to the default location (typically C:\Documents and Settings\<user>\Local Settings\Application Data\Logos4 on XP, C:\Users\<user>\AppData\Local\Logos4 on Vista and Windows 7), you can update to Beta 3 and you should be fine (though you will have to enable logging again).
If you have a custom install location, installed or updated to Beta 1, then updated to beta 2 and you can't wait for Beta 4, you can still update to Beta 3: update as normal, then when you see the Sign in screen, close it with the X button in the upper right. Then follow the instructions above and restart Logos 4.
Please respond back here if you have questions.
Bryan
However, for some users, when Logos 4 starts, it won't find your custom location and will instead look for its data files in the default install location. Since there won't be any files there (they're in your custom install location), it will assume that you have done a fresh install, will ask you to sign in, will download your licenses and will start downloading all your resources.
Bryan, having recovered my custom installation I intend to delete the folders that were created in the default Logos4 location EXCEPT for the \Install folder! However, is it safe to retain any of those setup files, particularly the Beta 3 msi i.e. would they cause problems for uninstallation now or in the future?
I'm thinking ...
If those that really MUST change their install path to a new location ... maybe ...
1) Copy the current resource files to somewhere like an external USB drive, or a 2nd disk that has space to burn ...
2) Change the path in the registry to the new desired location
3) Start L4 and go online, but stop the downloads early on, once its woken up
4) Run "Scan<dirname>" where the files are in (1)
5) Restart and go online to tidy up
6) Let indexing run, and for user content to download from Logos Sync (Cloud)
I really don't think its in any way better, and maybe much worse, than one of the methods to installed to a 2nd PC.
I am NOT suggesting anyone try it this way, until after Logos or Dave has replied. Its possible the above is a really dumb idea and not worth anything. I', just thinking is all ...
Then there's all the other registry entries that point to the old location (at least 30). So you have to re-install with one of the Quick Methods or use an NTFS symbolic link.
Bump
Sorry to take so long to get back to you, I've been a little busy! Technically, when Windows Installer uninstalls, I'm pretty sure it uses cached versions of the msi files it keeps around for uninstallation, so you should be find deleting even the msi files in the default location. I'd wait until Beta 4 is up and running, though, just in case...
I'd wait until Beta 4 is up and running, though, just in case...
Beta 4 installation went smoothly and sub-keys of the Logos4 registry key are fine. New logos4.msi has been placed in default location
