On Dec 19, 2008, at 1:43 AM, Greg Hellings wrote:
On Fri, Dec 19, 2008 at 12:37 AM, Matthew Talbert <ransom1...@gmail.com
> wrote:
Having spent a good part of the day trouble-shooting issues all
related to this, I can say with certainty that SWORD does not play
well on Windows at the present.
SWORD plays fine on Windows if you point SWORD_PATH to where the
modules are installed.
The BibleCS installer sets this variable for the current user. We
tried to make the installer be one that would allow an administrative
install, but it was problematic.
Handling whether they are writable by the user
is a system administration issue, and should be left that way. The
only time when a user won't have write access to the Program Files
folder is when they are on a recent NT version of Windows, in which
case, ~/.sword notation works perfectly well to place the files in
C:\Users\<User name>\.sword
--Greg
_______________________________________________
sword-devel mailing list: sword-devel@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@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
