Jump to content

Please read the Forum Rules before posting.

Photo
- - - - -

Updated to 10.3 and all modules inaccessible


6 replies to this topic

#1 michaelpready

michaelpready

    New to Bible Support

  • Veterans
  • Pip
  • 4 posts
Offline

Posted 01 August 2014 - 02:45 PM

Hi

I have been running E-Sword 10.1 for a long time.  I just downloaded 10.3 - the full install, which it stated was required for any existing installation < 10.2.  The program says it successfully installed, but upon start-up I get a series of pop-ups stating "Error encountered opening bible / dictionary/whatever file blahblah.bblx/dctx/etc. There are _no_ modules accessible from the program, including the defaults that come with the install.  I'm about to save off all the modules I've accumulated over the years and do a complete uninstall / reinstall.  Before I do that, is there a 10.1 installer anywhere so I can just go back to what I already had?

 

Thanks,

Mike Ready

mready@austin.rr.com



#2 Tim Butterfield

Tim Butterfield

    e-Sword Fanatic

  • Veterans
  • PipPipPipPipPip
  • 463 posts
  • LocationDes Moines Iowa
Offline

Posted 01 August 2014 - 03:00 PM

You didn't by chance have the modules in a location other than the default did you? 

Top row is a tool bar, select Options, select Resources, at the bottom of that window is a line reading Location.  That is where e-Sword is looking for all of the modules that you can't write to (like Bible, Commentary and Dictionary).  Check to see that it is indeed where the modules are. If not, show e-sword where they are using the file folder icon to locate them.


Thus says the LORD, "Let not a wise man boast of his wisdom, and let not the mighty man boast of his might, let not a rich man boast of his riches; but let him who boasts boast of this, that he understands and knows Me, (Jeremiah 9:23-24a)
 

"Defenders of the faith are inclined to be bitter until they learn to walk in the light of the Lord. When you have learned to walk in the light of the Lord, bitterness and contention are impossible." --Oswald Chambers, in Biblical Psychology from The Quotable Oswald Chambers.

 

 

 


#3 michaelpready

michaelpready

    New to Bible Support

  • Veterans
  • Pip
  • 4 posts
Offline

Posted 01 August 2014 - 03:18 PM

Well, it couldn't even read the modules it created itself when installing (e.g. kjv.bblx), and says "Error encountered opening bible file C:\Program Files (x86)\e-Sword\kjv.bblx"  I uninstalled, reinstalled, and now after the "can't open" messages, the program hangs and starts using up more and more RAM - right now it's at 200 MB and climbing.  Never had any problrm like this w/ E-Sword in the past.



#4 Josh Bond

Josh Bond

    Administrator

  • Administrators
  • PipPipPipPipPip
  • 2,891 posts
  • LocationGallatin, TN
Offline

Posted 01 August 2014 - 03:54 PM

What operating system is this?

 

Can you right click e-Sword and run it as Administrator?

 

It sounds like a permissions problem.



#5 michaelpready

michaelpready

    New to Bible Support

  • Veterans
  • Pip
  • 4 posts
Offline

Posted 01 August 2014 - 04:40 PM

Just gave it a try - same result.



#6 michaelpready

michaelpready

    New to Bible Support

  • Veterans
  • Pip
  • 4 posts
Offline

Posted 01 August 2014 - 04:41 PM

And I'm running Win7, which I forgot to say.



#7 Josh Bond

Josh Bond

    Administrator

  • Administrators
  • PipPipPipPipPip
  • 2,891 posts
  • LocationGallatin, TN
Offline

Posted 01 August 2014 - 07:28 PM

The issue here is something on your PC is denying e-Sword read access to the modules--even the modules that e-Sword itself installs.

 

The cause could be any number of security related products. For example, look at this older thread with the same issue. Here the user reported that a security program called Comodo that was denying e-Sword access: http://www.biblesupp...-empty/?p=19775

 

I would try temporarily disabling all security software, anti-virus, malware, firewalls, etc--anything that locks down a computer--just to see if that fixes it. Then once you figure out which program is causing the issue, work within that program to authorize e-Sword.





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users




Similar Topics



Latest Blogs