Hardware lock and licenses
1. Dinkey Dongle error
If you are getting “dinkey dongle” error messages after installing shipweight 10.0 you should do the following steps:
1. Go to the dongle server and terminate the DDNET service (or stop program by running “DDNET /T” if it runs as a program).
2. Uninstall completely by running “DDNET /UFULL”.
3. Download “Lock files” from our download section at www.masstrakcom.wpengine.com
4. Copy the new DDNET.exe file from the downloaded “Lock Files” and replace the old ddnet.exe on the server.
5. Run DDNET.EXE (or “DDNET.EXE /S” to run as service). When asked for the DDNET file path, point to same folder as the SW.INI file is pointing to (only use local reference). Worst case a restart of the server is necessary, but I think not.
2. Dongle – cannot detect / error accessing
If you get the message: “Cannot detect dongle or error accessing dongles. Parallel port error: 128 USB error: 0 Extended error: 00 00 00 00 00 00”, this could mean that you need to install drivers again. Do the following:
1. You find the dongle driver (setupdrv.exe) on your computer if you have ShipWeight installed (In the folder C:> Programfiles >ShipWeight9).
2. Remove any dongles
3. Run setupdrv /ufull
4. Reboot the machine
5. Run setupdrv /usb
6. Insert the dongle into the machine – window should now install the drivers.
7. Reboot the machine
This will just reinstall your drivers. If your problem still exist you could check
3. Install a Client Hardware Lock
If ShipWeight is delivered with client hardware lock it is sufficient to plug in the hardware lock in an empty USB port on the client machine. This is all that should be needed for setup of a client lock.
To check that the lock is working properly, ensure that the end of the lock is lit.
If the lock is not lit this may indicate that the installation program was not able to install the drivers automatically. In this case, run the drivers manually after the installation. To do this, select the shortcut on the Start menu by clicking
Start=>All Programs=>ShipWeight Enterprise=>Hardware lock=>Setupdrv
This will run the program Setupdrv.exe which is installed in the ShipWeight program folder. A successful run of this program should give a messagebox stating that the drivers are installed.
4. Install a Network Hardware Lock
Install ShipWeight on all appropriate client machines.
The hardware net lock should be attached to a USB port on a server or other machine accessible from all client machines.
The files found in the Lock Driver folder on the ShipWeight installation CD-ROM or downloaded from www.ShipWeight.com should be copied to a new empty folder on the server/machine containing the lock. This new folder will be the Lock System Folder.
All client machines will need full access permissions (read/write/create/delete) to the Lock System Folder.
Run SETUPDRV.EXE from the Lock System Folder (once).
DDNET.EXE should be run from the Lock System Folder each time the server is started.
The first time DDNET.EXE runs it will ask for a path. Give the path to the lock system folder.
Put DDNET.EXE in the Windows Startup group to ensure execution at startup. (…or run “DDNET /S” to run DDNET.EXE as service instead of as a program)
On all client machines, edit the SW.INI to be found in the Windows folder (Win 2000: Winnt folder) and make sure that the string DinkeyNetPath in SW.INI points to the Lock System Folder. You can use long filenames in the path if the machine is Windows 9x/Me/2000/XP, but for Windows NT you must use short filenames.
Examples of the SW.INI file:
If the server containing the Lock System Folder is mapped up on the client machine, the SW.INI could look like this:
If the server is not mapped, the SW.INI could look like this:
The SERVERNAME represents the name of the server and the LockSystemFolder represent the name of the Lock System Folder.
5. Troubleshooting the Hardware Lock
In case you suspect the drivers to not work properly, try the following procedure:
1) Remove any dongles.
2) Run setupdrv /ufull
3) Reboot the machine.
4) Run setupdrv
5) Insert the dongle into the machine (for USB dongles, Windows should now install the drivers)
6) Reboot the machine.
Check that the dongle end is lit
Run the ddlook.exe file in the Lock System Folder and verify that the program finds the dongle and that SW is specified as the product code and that dd32.dll is listed as the protected program.
On the server, open DDNET.INI file in the windows folder to check the registered path to the system folder (keyword fserver holds this path) and verify that the SW.INI file on the client machines points to the same folder.
Make sure that the client machine got FULL access permission on the Lock System Folder.
Make sure that the DDNET program is actually running, check Windows Task Manager.
If the program returns an error code; try the support website of the dongle manufacturer http://www.microcosm.co.uk/kb/ (select “Dinkey Dongle” and “Continue”).