Is there a way to avoid a requirement to re-indexing when following the "Quick Install for Multiple
I understand from http://wiki.logos.com/Quick_Installation_onto_multiple_computers that there is a way to avoid downloading all the resources when setting up Logos 4 on a second computer. However, is it also posible to avoid the "Indexing" process? I followed Dave Hooton's "Method 1" in the above procedure, thinking I would not have to re-index. But that seems not to be the case as the resources do not open up although they are in the Library listing. Dave's procedures seem to imply that only "Method 3" requires re-indexing. If so, then I did something wrong. Can anyone elaborate, please? Might there be a specific procedure to follow that avoids having to re-index on the second computer, or some particular pitfall I need to avoid with "Method 1" to prevent needing to re-index? The reason I want to avoid re-indexing, if I can, is that my second computer is essential for my day-to-day work, but is quite old and the hard drive might not last much longer after such an intensive indexing process and I need to postpone upgrading this PC a little longer if at all possible...thank you.
I would expect Method 1 to avoid indexing since you are copying a complete index. Did you have logging turned on? If you post your Logos4Indexer.log file I could probably tell you why it was indexing.
Peter, I see part of the problem now when looking through the attached log file. For example, the error: "ResourceManager Resource of type ClauseVisualizer could not be found at location C:\Documents and Settings\Owner\Local Settings\Application Data\Logos4\Data\...." (in the Logos4Indexer.log file) thinks my local computer ID is "Owner", which it is on the other (first) PC, but should instead be "tlord" on my second PC that I want to get working. If that is the main problem, you may have a solution. Otherwise, I could go to my primary PC and create a new computer ID "tlord" (then reinstall and re-index everything on the primary PC) so that the two PCs then match. However, they will still have diffferent "{random}" directory names. Maybe you have some advice. Also, Damian seems to be indicating that it was not a full re-index that needed to be done, but just a rebuilding of the resourcemanger.db file. If that is a much faster process to go through than a full index, then I could go that route as an alternative. But it sure would be nice if there was a way to get the second PC going without long hours of either indexing or rebuilding files. Thanks much for your suggestions.
Tim,
Did you see in the wiki, under method 1 where it says:
[quote] * if you get a message that resources cannot be found delete ResourceManager.db from Logos4\Data\{random}\ResourceManager folder and restart L4.
Rebuilding the resource manager database takes a while but nothing like indexing... it depends on the size of your setup.
Rebuilding the resource manager database takes a while but nothing like indexing... it depends on the size of your setup.
Damian, I think you are right, I did see that. At the time I thought my second PC was indexing, but apparently it was only rebuilding the resource manager database. And perhaps only because the user ID on my second PC is different from the user ID on my first PC, (and maybe because the "{RANDOM}" directory name is different between the two PCs, too). I'm going to go ahead and let it run and see how long it takes.
Every user on every machine has a different "random" directory name... you just copy its contents into the corresponding directory.
Peter, thank you, I figured that. As to my Logos4Indexer.log file, I did upload my earlier log file via this forum, but couldn't tell whether you were able to access it or not. Back to my original concern, apparently what I thought was "re-indexing" was only the rebuilding the Resource Manager DB. What misled me was that I saw "Logos4Indexer.exe" appear in the Task Manager, and assumed that the indexing process launched. Maybe the program always launches just to check to see if indexing is needed at all and then shuts down if it decides no indexing is needed, and I didn't realize that. Meanwhile, I am wondering if the process of rebuilding the Resource Manager DB could be sped up by doing anything more, such as making the Windows account user IDs the same on both PCs. But maybe not, since the "{RANDOM}" directory names have to be different on each PC. No problem, I can repeat David Hooton's Method 1 procedure again from scratch (since my resources have now changed) and let the rebuild run...