-
Sorry, I wrote the wrong one. I did in fact mean the update resources command, which (maybe) should take 10-20 minutes but is instantaneous in my computer.
-
C:\Users\richard\AppData\Local\Logos4\Data\dka0tw4u.xue\UpdateManager\Resources is empty. Here is the zipped updates.db file. 4341.Updates.zip Thanks for your help.
-
I recently obtained a copy of the J. Vernon McGee Electronic Bible Study Library . It is actually a Logos2 disk, but it installed into Logos3 as well, and I synchronised licenses. I am able to view the books on www.biblia.com and library.logos.com, so the Logos servers know that I own the book. However, there is no way that I can get it to install in
-
It had the same effect as the other times I have used the scan command: when Logos reboots it shows Step 1 of 3 of preparing the library, but nothing new is installed, and the books are still not present in Logos.
-
I deleted 17 pairs of these files, in the various sub-folders of the ResourceManager folder. When I rebooted Logos, it didn't try to download anything and the update resources command did not find anything. I think at this point that the best thing to do is to give up, say it is an unresolved problem with Logos, then copy the existing resources in another
-
There is a list at http://www.laparola.net/greco/manoscritti.php as well.
-
Thanks for the video, which was interesting and useful. Just one comment: Rom-2Tim does not search all of Paul's letters, it leaves out the last two.
-
The LEB site does not have a contact address, so I'll mention it here, hoping that someone appropriate reads this. Luke 2:44 has acquantances instead of acquaintances Luke 12:1 has Pharisess instead of Pharisees John 6:12 has satisified instead of satisfied Acts 17:23 has observeing instead of observing James 15:10 has perseverence instead of perseverance
-
Yes, it was James 5:10. I missed some more however: Acts 19:13 iterant instead of itinerant 1Cor 1:16 maybe Stephanus; in 1Cor 16:15,17 it is Stephanas Eph 6:11 strategems instead of stratagems Rev 9:11 maybe Abbadon; almost all other English versions have Abaddon, and the critical text that LEB says it follows has Ἀβαδδὼν (although the Byzantine text
-
Almost... I ran the downloadable text and XML files through the LaParola program (see my signature), and with that I can pick up words that aren't used in any other English translation in the program. This is better than using a spell checker, because it doesn't flag all the names (like a spell checker does), but it does show the names that are wrong
-
[quote user="Ron Keyston Jr"]If you read this, would you mind providing instructions for how you did this with the program?[/quote] It was not as simple as I made out. First of all, the program can't import this type of OSIS file (that uses paragraph markers as the structure with the verses indicated as milestones, rather than using the verses as the
-
The missing font is TransRomanAH - you can find that out looking at the HTML code of this page. Obviously Tom Reynolds has this font, so can not see the problem neither on this page nor in Logos. See the discussion at http://community.logos.com/forums/p/45638/339621.aspx on the cause of the problem and how to fix it.
-
Mostly by hand, but it isn't as hard as it seems. I show the table of contents on the left hand side of the pane, click each section in turn, copy as Wiki (CTRL+ALT+C), and then in Word type the reference (which is where errors can come in, thanks for the correction) and copy the link in Logos.
-
I'm still working on improving it. In about a week I should have another version ready, with all the books in Platinum (version 5). So it will be a lot bigger. Personally I use it when preparing Bible studies. After I have read a few commentaries on the passage, I look up the references in this file, which often give me other ideas for the Bible study
-
Yes, it does take a while to compile. But it is big, with big tables, and it does seem that the PB compiler works harder on the tables. So most of the 12,000 errors are about the tables, and can be ignored. You can change the font if you wish, just make sure that it has all the Greek Unicode characters, and aleph.
-
Bible Apparatus works well, I think the only difference between it and Bible Commentary is where it ends up in the Passage Guide, and when you jump to a parallel resource. I suppose you could also use the type Bible, again the only difference is where it shows up in the program.
-
The 200 volume Bible Reference Bundle has now lost its dynamic pricing, as has the 179 volume Upgrade unlock, but strangely the 501 Book unlock still has dynamic pricing. So for me at least the Upgrade, which contains only a part of the full 501 unlock, costs more that the 501 unlock. I thought it might be because the Word Biblical Commentary is no
-
Name: Richard Wilson Where you call home (general or specific): Italy Occupation: Missionary Age: 47 How long you've been using Logos Bible Software: 5 years Your most-used Logos resource (other than the Bible): Word Bible Commentary Your #1 use for Logos: Preparing Bible studies Favorite non-Logos pastime: play clarinet Random fact that gives others
-
Thanks for the suggestions. They all do just what I wanted. The forum works again.
-
When I have a quick question on a verse, I usually go to one particular commentary to read what it says. So I don't want to do a Passage Guide, too much information. I have a favourite commentary on each book of the Bible, that are in different series, sometimes Word, sometimes Pillar, etc. So at the moment I have to remember or look up my favourite