Installation guide
ScriptWorks® Technical Note – Hqn028 – HQMulDev for 4.1 Page 9 Revision 1.4, 96.09.24
where
<dongle>
is the security number of the dongle with which this control file is to be
used (in decimal), and
<name>
is the device family name.
The program will strip the leading ‘hq’ from the second argument and create a file called
<name>
.ctl, which should be copied into the SW\Devices directory of the RIP with which
it is to be used. Note that the name of the control file must be exactly
<name>
.ctl,
otherwise the plugin will not be able to find it and the user will not have access to any device
types at all.
For example, the following is the hqPelBox.oem file as supplied by Harlequin:
/* replace this line with your customer ID in C hex notation , e.g. 0x45 */
"PelBox 108 : 1045", "PelBox 108 : 1045"
"PelBox 108 : 1245", "PelBox 108 : 1245"
"PelBox 108 : 1545", "PelBox 108 : 1545"
"PelBox 3000 : 2030", "PelBox 3000 : 2030"
"PelBox 3000 : 2430", "PelBox 3000 : 2430"
"PelBox 3000 : 3030", "PelBox 3000 : 3030"
"PelBox ID36", "PelBox ID36"
"PelBox VR30", "PelBox VR30"
"PelBox VR36", "PelBox VR36"
"PelBox VR45", "PelBox VR45"
If your OEM ID is 9, and you have a customer with a dongle security number of 1234 to whom
you wish to grant access to all of the PelBox 3000 range and you want those machines to appear
named as ‘HighSetter’, you would edit the file to read:
0x09
"PelBox 3000 : 2030", "HighSetter (2030 dpi)"
"PelBox 3000 : 2430", "HighSetter (2430 dpi)"
"PelBox 3000 : 3030", "HighSetter (3030 dpi)"
and then type the following at the command prompt:
cryptctl 1234 hqPelBox.ctl < hqPelBox.oem
This would create a control file called PelBox.ctl.
Windows NT Registry entries
You should not need to edit the NT registry entries for the HQMulDev plugins directly, except to
remove drivers. If you do so you should exercise extreme care when using regedt32 as entering
incorrect values can damage your NT installation.
The registry changes which will be made are defined in two places:
• Some entries are specific to each plugin, and are defined in the [RegNT] section of the .PST
file used by the ScriptWorks installer when installing the plugin. For details of the .PST file
format please see tech note Hqn010N version 1.4 or later.
• Some entries will be applied for all plugins installed through the ScriptWorks installer. These
are described here.
In the descriptions below:
<
driverfile>
is the name of the .DRV file in lower case, i.e.
hwi
<tag>
.drv for HighWater ISA cards
hwe
<tag>
.drv for HighWater EISA cards
pci
<tag>
.drv for PCI interface cards
<
drivername>
is the name of the driver, i.e.
Hwi
<tag>
for HighWater ISA cards