2 replies to this topic

[bjlord]

I converted a couple of bibles to e-Sword many, many years ago. When version 9 came out I ran them through the converter program for 9 and they were successfully converted to bblx files with no hitch. I just upgraded to version 10 last week and my bibles are not there. I went back and converted them again a second time, but they still will not come up.

 

Is there something in version 10 that prevents these home-made files from working? I'm not an expert at making modules. When I created mine, e-Sword was I think at about version 4 or 5 and was a lot simpler overall. I used a template that Rick provided online at the time and just plugged in the versions I wanted. That method was under a different database system, which isn't being used today.

 

I like version 10 and will sacrifice the bibles if I have to rather than going back to version 9. But thought I would ask before I just give up.

[LarryG]

Years ago, as I recall, when eSword was in V7 there was a tool that could stream different versions from Crosswire and other sites - then compile an eSword module.  I have used the converter to update those Bibles into V9 and V10 and they worked fine.

 

The main problem, usually, has been how the module was defined (either on the eSword tab, or on the hard drive).  The file name must be both unique to itself and not like a paid module. 

 

Example:  For the Amplified (from Crosswire) rename the C drive module : Amp (Cross).bblx and the tab Amp (Cross).  Then it should appear.  You can change tab names with this handy little tool.

 

http://www.biblesupp...ibrary-manager/

[bjlord]

Thank you Larry G. It worked. All is restored to harmony. I appreciate your help.