[bt-devel] BT doesn't start on WinXP
Matthew Talbert
ransom1982 at gmail.com
Thu Oct 22 08:07:34 MST 2009
Sorry for not replying in context. BibleCS *does* use the registry,
most notably for setting SWORD_PATH during installation (ironically,
it ignores the variable itself unless you completely remove any
modules from its installation directory). I personally feel that this
is not a good thing, as it can cause (and has caused, in the case of
another program that isn't quite compatible) problems with other
programs.
The only real need for using the registry is to allow uninstalling the
program from within the Control Panel. If you use NSIS, it makes it
easy to do this.
We personally do not override SWORD_PATH if it is already set, just to
maintain compatibility with BibleCS. What you do is up to you, but you
may not even have that option, considering how you use your own
sword.conf (probably the best thing you could do is add the contents
of SWORD_PATH to your sword.conf as an augmented path).
Gary, I think you have a good concept of what Xiphos is doing, and
your proposal is pretty much what we are doing.
Finally, we do use 'Sword' rather than '.sword', and JSword does the
same. I believe Gary is already aware of this.
Matthew
PS I appreciate the attitude here to make things compatible with
Xiphos as well as to fit in with how Windows does things.
More information about the bt-devel
mailing list