# [sword-devel] Hello, I need help with the Sword Utilities

Sat Jan 26 08:13:57 MST 2013

```As a fellow Windows user (Win 7 x64) I found it useful to make (in my Sword
to where the Sword utilities are stored.

Symbolic links may be unfamiliar to many Windows users, but old-hat to Linux
folk.

They are created using the Windows command called *mklink*
You can use Windows Help to find out more.

Then for any of the individual tasks (especially those that need repeating),
I create a custom Windows CMD file to launch the utility,
such that I can just double-click it to start that from within Windows
Explorer.

You can use any decent text editor (even Notepad will do) to make a CMD
file.

Here's an example:

I've been working on the Norsk module yesterday, so my CMD file called
*MakeNorsk.cmd* contains:

..\utils2\imp2vs ..\Import\Norsk.raw.imp.edited.txt -z -o
..\modules\texts\ztext\norsk  1>..\log\imp2vs.log 2>..\log\error.log

You see that I also capture the stdout and stderr streams to a pair of log
files in a separate subfolder.

It's also useful to append a pause command within the CMD file, so that you
can watch what happens before the CMD window closes, and then close it
manually.

Also, to avoid clutter, all my CMD files are in a sub-directory I created
under Sword (called Make).
Likewise, source text files being used to make a module, these are in a
folder I created (called Import).

Once you've mastered these techniques, you'll wonder why you ever thought it
difficult.

Finally, for all utility commands relating to modules, the module name is
Case Sensitive.
It must be exactly as in the first line of the conf file, less the square
brackets.
This requirement appertains to all commands that do something with an
existing module.

David

--
View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651826.html
Sent from the SWORD Dev mailing list archive at Nabble.com.

```