Downloading New Resources
I've been using the Logos 4 Mac Alpha for a few weeks now (currently version 11) and it did all of its downloading and indexing already. However, just yesterday I purchased the upgrade to the Platinum library. The CS rep said he'd give me the download and the CDs for it and when I opened up Logos 3 I was able to sync my licenses and open up some resources that had been on some of my Scholar's library DVD. Now I'm trying to get access to the new resources in L4, but to no avail. I've typed in the "Update Resources" command several times and (when it finally works instead of doing a search) it says downloading *% of 7GB for about 10min and then completes and none of the new resources are there. Am I doing something wrong? Any ideas?
Thanks!
Comments
-
Wonder if "Set Automatically Download Updates to Yes" does any better ?
http://community.logos.com/forums/p/9512/75953.aspx
Keep Smiling
0 -
Brian,
Please see the FAQ for how to set up logging and post logs. It sounds like the indexer is having some issues and crashing. if you post your logs we can track down the problem.
Tom
Mobile Development Team Lead
0 -
I tried the "Set Automatically Download Updates to Yes" but no success.
OK Tom, going on your post I did a "Rebuild Index" and after that finished "Update Resources" still no success so attached is the log files. Thanks for taking your time to help.
0 -
I have the same issue - ordered some new resources but the d/l freezes up - also tried to set automatic downloading but it goes into search mode...trying to be patient [8-|]
0 -
Just as a test I moved the /Library/(user)/Application Support/Logos4 folder; deleted the plist files and installed an old Alpha version which had downloaded resource files before. When I fired it up, it churned for a while and then proceeded to do the same thing as A11 of seeming to download "*% of 8GB" but was finished in 20 min. The Console log was similar to the A11. It generates this proper list of resouces to download and then, Failed downloads for every one. Seems like this may not be an app problem, but perhaps a server issue.
0
