[sword-devel] KJV Update

2016-01-30 Thread David Troidl
Hi, I updated to the most recent KJV module, without paying much attention to it. Today I was trying to access Genesis 49 in BPBible, and got the message: Genesis 49 is not in the current book. I opened BibleCS and found the KJV wouldn't access John 1. So I checked the install manager for

Re: [sword-devel] KJV Update

2016-01-30 Thread DM Smith
Does dumping the module with mod2imp have the correct references for the chapters you are having problems? (i.e. is it a module problem) > On Jan 30, 2016, at 9:00 AM, David Troidl wrote: > > Hi, > > I updated to the most recent KJV module, without paying much attention to it. > Today I was

Re: [sword-devel] KJV Update

2016-01-30 Thread David Troidl
I'm not sure how to use mod2imp on the installed module, but I looked at it, and the only content in the directory is this: "C:\Program Files (x86)\CrossWire\The SWORD Project\modules\texts\ztext\kjv\nt.bzs" "C:\Program Files (x86)\CrossWire\The SWORD Project\modules\texts\ztext\kjv\nt.bzv" "C

Re: [sword-devel] KJV Update

2016-01-30 Thread David Troidl
Hi, On further checking, I found that the other updated books, Byz and WHNU, had the same problem. Their module directories were empty. So I tried downloading the KJV from the website, and installing it directly in BPBible. Now that works fine. Apparently the problem narrows down to the Bi

Re: [sword-devel] KJV Update

2016-01-30 Thread David Haslam
Looks like the previously installed module got corrupted. Maybe this can happen with jSword front-ends if two different modules have the same Description? http://crosswire.org/wiki/DevTools:conf_Files#Uniqueness Yet BPBible and BibleCS are SWORD based, so that's not an explanation here. The symp

Re: [sword-devel] KJV Update

2016-01-30 Thread Greg Hellings
Let's not assume we can rule out the possibility of Windows 10 being the culprit. It has been known to remove user data and programs without warning with some recent updates. --Greg On Jan 30, 2016 10:13 AM, "David Haslam" wrote: > Looks like the previously installed module got corrupted. > > Ma

Re: [sword-devel] KJV Update

2016-01-30 Thread DM Smith
Glad you figured it out that you had an incomplete download. Guessing: The FTP mechanism of InstallMgr can create partially downloaded modules. Alternatively, you can unzip the cached zip (from ftp/pub/sword/packages/rawzip) and unzip it to the proper folder. I’ve only ever used it on Un*x. Bas

Re: [sword-devel] The OSIS s grain operator?

2016-01-30 Thread David Haslam
Still waiting for a SWORD coder to answer my earlier question, repeated below. cf. DM Smith & I are planning to make use of it in the next release of the KJV module. - Does SWORD support the s grain operator within osisRef ? From the OSIS 2.1.1 Reference (page 148) The s grain operator is

Re: [sword-devel] KJV Update

2016-01-30 Thread David Troidl
Thanks for the replies. It seems BibleCS itself was somehow corrupted. I reinstalled it, and my settings took affect again, and all the modules I downloaded from the new Install Manager seem to work fine. Thanks, David On 1/30/2016 11:27 AM, DM Smith wrote: Glad you figured it out that you