[sword-devel] BibleCS 1.6.2rc1 (a.k.a. The SWORD Project for Windows)

[scribe777@gmail.com]

Thanks David!

Could you try something for me? With the program closed, could you run InstallManager.exe and choose from the menu something like "Migrate Library Systemwide." I can't remember the wording right now, but basically there are 2 options for migration. One is a local copy of your modules and the other is a systemwide copy.

Remember, this is experimental software. I hope this doesn't screw up your other modules. But you can report to everyone else if it does. :)

After the migrate command, close InstallManager, run BibleCS, and let us know is some of the bolw problems are fixed.

The installer for this release will probably executed that menu choice behind the scenes during install.

Troy


David Troidl <DavidTroidl at aol.com> wrote:

>Further note: I did a search by Strong number.  It did fine with 
>unindexed search, but hung in the middle of creating an index for KJV.
>
>Peace,
>
>David
>
>On 7/18/2011 4:38 PM, Troy A. Griffitts wrote:
>> OK guys, I've been sitting on this for quite some time, mostly not
>> looking forward to remembering where I left off...
>>
>> But here the culmination of 3 years of:
>>
>> o	fiddling - probably fixed or created all sorts of bugs
>> o	migrating to av11n
>> o	migrating to play nice in the new world of windows security
>> o	updating Windows InstallMgr to:
>> 	o	have the ability to autodiscover repositories
>> 	o	install modules in a location which plays nice with
>> 		other SWORD frontends on Windows
>> 	o	and still preserve the ability to create a
>> 		self-contained movable installation-- there are
>> 		options in the InstallManager menus to migrate back
>> 		and forth between the two setups.
>>
>>
>> Instructions:
>>
>> You must have a working BibleCS installation already on your system
>to
>> try this beta.
>>
>> http://www.crosswire.org/sword/software/biblecs/
>>
>> **** YOU MUST DELETE YOUR locales.d/ folder within your working
>> installation (or rename it if you might return to the 1.5.11
>release).
>> The SWORD 1.5.x and 1.6.x engine locale formats are NOT COMPATIBLE.
>>
>> **** PLEASE FOLLOW THE ABOVE INSTRUCTIONS OR YOU WILL BE MOCKED IF
>YOU
>> REPORT CRASH BUGS AND WE DISCOVER YOU HAVE OLD LOCALES PRESENT!!! :)
>>
>> Download and unzip these files ON TOP of your existing installation
>> location.
>>
>>
>http://www.crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/alpha/BibleCS-1.6.2rc1.zip
>>
>> To try out av11n, you'll need to manually add the a11n repository to
>> InstallManager.exe
>>
>> name: CrossWire av11n Repo
>> host: ftp.crosswire.org
>> path: /pub/sword/avraw
>>
>> Save, go to the tab, hit [Refresh from Remote Repository], and
>install
>> av11n modules.
>>
>> I'm calling this a release candidate, but really, I'm just looking
>for
>> feedback from anyone whose interested/using BibleCS.  We need to
>release
>> an av11n version, and we now have multiple frontend choices on
>Windows
>> so we need to play nice with others.  These 2 factors are the major
>> driving force behind this release candidate.
>>
>> If we can get some feedback that this release is at least as stable
>as
>> the current 1.5.11 release, I'd love to release this soon.
>>
>>
>> Troy
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>_______________________________________________
>sword-devel mailing list: sword-devel at crosswire.org
>http://www.crosswire.org/mailman/listinfo/sword-devel
>Instructions to unsubscribe/change your settings at above page

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.