Sun, 13 Jan 2002 15:21:27 -0500
I just recently joined the list, and expressed a similar problem
installing locked modules. If you find out the solution, I'd appreciate
hearing about it, if it isn't published on the list.
On 12 Jan 2002, at 11:51, Lloyd N. Landers, Jr. wrote:
> I sent the following message last Friday, 1/4, and now again today,
> Saturday, 1/12. Since I'm new at this, I don't know what protocols
> you follow in answering questions/responding to bug reports. If I'm
> getting in too big a hurry, I'm sorry, I'm just anxious to be able to
> get on with testing this software.
> Since I can not get a good install of any locked file, I uninstalled
> the program and started from scratch. This time I used the InstallMgr
> to download and install add-in modules. I selected a number of Bible
> translations, both locked and unlocked as well as some commentaries.
> I added the KJV w/Strong's numbers (something I had not done
> The installation went smoothly until it hit NASB95; KJV w/Strong's had
> already completed installing. When it encountered NASB95, a box
> opened with the message that the version appeared to be ciphered. I
> entered the lock code with a cut-and-paste from the supersecret file.
> At that point, I didn't know what to do: should I click on "TRY" or
> I ended up trying both on different runs. When I clicked on TRY, my
> machine simply sat there with no indication of any activity of any
> sort (no disk activity, no Internet activity, nothing). After about 7
> minutes, I clicked on OK. The installation immediately opened a
> window indicating it was ready to try to install NIV (opened the
> cipher window). I cancelled the installation.
> I looked at the /modules/texts/ directory to see what had been created
> this time since on prior install attempts there was no rawtext
> directory, only a ztext directory. This time there was a rawtext
> directory containing KJV. I then looked at the mods.d directory to
> see what .conf files had been created. There was one for KJV which
> pointed to /rawtext/ via DataPath. There was also one for NASB95. It
> contained the correct CipherKey and DataPath, but there was no NASB95
> directory in /rawtext/.
> I tried unzipping the NASB95 file I had previously downloaded from the
> beta section and ran the Setup.Exe. No NASB95 was created under
> My conclusion is that the installation works just great using either
> InstallMgr or doing it manually by downloading, unzipping, and running
> Setup as long as the file is not a locked file. There appears to be a
> real problem, however, whenever a locked file is involved.
> Any help you can give me at this point would be appreciated.