3 replies to this topic

[Starkman]

Hey all,

 

Say, is the e-Sword Module Installer 0.6 (http://www.biblesupp...0#commentsStart

) still working fine for e-Sword ver 12?

 

Thanks.

[Olaf Bacon]

Module Installer 0.6 can be downloaded. It will run if you also download a new module; then will install that module in the drive and directory folder where you have decided e-Sword is to be installed. The Module Installer can be allowed to install in 64-bit PC in the Program Files\ where it will install into e-Sword Module Installer folder; or into a 32-bit PC in the folder Program Files (x86)\ where it would create a suitable folder for itself. The module Installer will then also link all the default apps for type of file, correctly, while it moves your newly downloaded e-Sword file to the relevant folder. After I reloaded e-Sword to v. 12.1.0 (updated 2019-10-04) I reloaded the Module Installer, and it worked fine, and the file entries were updated on the PC. My PC is running Microsoft Windows 10 Pro; v. 1903.

[Starkman]

Great, thanks.

[Olaf Bacon]

I have Microsoft (64-bit) PC Edition Windows 10 Pro, Version 2004, installed 2020/06/10 with Windows Feature Experience Pack 120.2202.130.0  All e-Sword downloads entered from inside e-Sword now load to C:\Users\<username>\AppData\Local\VirtualStore\Program Files (x86)\e-Sword folder. This includes the following lexicon or dictionary files,

bdb.lexx and

kjc.lexx and

thayer.lexx  

 

From  Microsoft Start > Settings, in the search box, enter "type", then select the option "Choose a default app for each type of file".

Then, in the "Choose default applications by file type", where we are not usually able to Associate file types with specific applications, browse down to check that all the following file-types have been linked to moduleinstaller.exe

.bbli .bblx .brpi .brpx .cmti .cmtx .dcti .dctx .devi .devx .hari .harx .jnli .jnlx .lexi .lsti .lstx .mapi .mapx .memi .memx .noti .notx .refi .refx .topi .topx

 

PLEASE NOTICE that Rick Meyer is using the filename.lexx and not filename.lexi for some of the lexicons. However, in the 64-bit Microsoft there is a filetype .lex, which not linked to anything, and a filetype .lexi  which is linked to Moduleinstaller.exe but no filetype .lexx  which ought then to be linked to Moduleinstaller.exe NOTE: I have just reloaded Module Installer 0.6 from http://www.biblesupp...dule-installer/

and let this run, and once again, this has not been modified to cater for the filetype .lexx files which are loaded by Rick Meyer. 

Rick Meyer says that the file goes into the Virtual Store when the e-Sword program directory does not have the appropriate folder properties to allow the files to download into it. He also says, that BBLI and BBLX files are not the same, but HTML has little to do with their differences. The "version" number in the Details table is set to 4 when it is HTML.

 

QUERY: How is a person to authorize the PC to allow the e-Sword files to go to the address listed in e-Sword on "Option", "Resource settings",  in the "Resources Location" window, and in the "User Files Location" window.

 

REQUEST: Please arrange to update Module Installer to cater for the filetype .lexx files, so that the user, who might not be very computer literate, does not have to experiment and to browse around to find the appropriate file to process the .lexx files, which is located at C:\Program Files\e-Sword Module Installer\ModuleInstaller.exe And please arrange to update the Module Installer documentation accordingly.

(Olaf Bacon)