If you can't find an answer to your question here why then get in touch via the mailing list and we'll get cracking on it. You can also send as a private message if you would like. See the contacts page for details.
This is a known issue of the first release of Securix-NSM (v1.0). Due to our attempt to use the most up to date software, we slightly overlooked a data flushing issue with sancp-1.6.2-release.C which caused resulted in a "sguild.sancp doesn't exist" error. The data would not flush unless the process was actually terminated. Not very useful, still we're sure it will be fixed shortly of which we'll upgrade when appropriate.
Until then, in Securix-NSM (v1.0.1) we have regressed sancp to the stable 1.6.1 which has been confirmed working under all conditions.
Q.
How do I use this USB-HDD .img file?
A.
The img file is in fact an image of a HDD, including partition information. That is unlike some other distributions you will need to write this img file to the root node of the device your aiming for. For example if your USB-HDD is recognised by the kernel as /dev/sdb, you will write to /dev/sdb. Of course this will modify the parition table of the device and thus should be only performed on a device you're happy to play with ;)
Writing the img file is as simple as (assuming /dev/sdb is the root node of our device):
$ sudo dd if=securix-nsm.img of=/dev/sdb
Chances are that the device will be much smaller than your USB-HDD device. If you wish to use the remainder of the device then simply running cfdisk/fdisk over it will allow you to add a second parition. Alternatively you can use the remainder of the device as persistent data store for your live sessions with the following script.
File: auto-format
#/bin/bash
# Automatically add a second partition which fills the rest of the Securix-NSM
# USB-HDD and configures it for persistent storage for the live sessions.
#
# usage: auto-format device
# e.g. auto-format /dev/sdb
