[sword-devel] ANOTHER newbie problem making a module
Troy A. Griffitts
Tue, 25 Jun 2002 11:46:34 -0700
The SWORD engine looks in a number of places for its modules (Bibles,
commentaries, etc.). You can see a detailed description of the route it
takes by looking at the docs distributed with the source code.
The easiest way to make a sword program work is to put to modules in the
same directory as the .exe. Just download a Raw Zip module and unzip it
to the same directory as the .exe. Or, alternatively, if you have the
windows frontend installed and working, move the .exe to that directory.
To confirm, you should have a directory which contains the .exe AND also
contains a directory called mods.d
Hope this helps.
Charles Carey wrote:
> All I wanted to do was avoid paying another (would make fourth) $20 royalty
> to zondervan so I could use the NIV in Sword!
> I have the NIV in OLB (v5 & v6 for DOS) and Quickverse and have exported it
> to a simple text file but for the life of me I can't get vpl2mod to work!
> I would happily use mod2vpl to see what it's supposed to look like but
> that won't work either!
> Can anyone tell me why mod2vpl tells me it can't find mods.d or mods.conf?
> I've set the path in autoexec.bat:
> set SWORD_PATH=C:\Program Files\ etc.
> I'm using a PentiumII 400mhz/Win98 system and trying to run the utils in a
> dos box.
> I'm not new to computers or programming. I started in 1984 on an XT Clone
> and DOS v3.1 and I've programmed in Pascal, Basic, Visual Basic v1-v6,
> Assembler and C(embeded systems and CGI on a Unix server) along with Perl
> and HTML and ASP. BTW I have an in the box never used copy of MASM6.1 if
> anyone is interested.
> Sorry for the whinnnnnnny tone of my e-mail. I don't mean it to sound that
> way. I know the guys who wrote these utilitys did it to make a
> contribution and I appreciate their efforts. On the other hand, I have to
> ask myself, "Do I really want to do this?" when a utility returns a cryptic
> error message, or fails and says, "Look at the readme file for
> configuration..." and the readme file is nowhere to be found! OR just
> fails and says nothing! Sorry, there I go again. :-)