|
|
|
|
|
Install USB Key Drivers
All the files required for the driver installation have been extracted during the installation of the PMOD software and stored in the PMOD hksetup sub-directory. For Linux, it includes four installation files, the 32-Bit and 64-Bit installers for RedHat/Fedora as well as Ubuntu/Debian systems. The driver installation should be preformed as root user.
On Ubuntu/Debian Linux systems double-click WkRt-Lin32_6.0.501_i386.deb (32-Bit) or WkRt-Lin64_6.0.501_amd64.deb (64-Bit) depending on the architecture of your host system, and then install the package.
Similarly, on RedHat/Fedora Linux systems use WkRt-Lin32-6.0.501_i386.rpm (32-Bit) or WkRt-Lin64-6.0.501_amd64.rpm (64-Bit). If the installation per double-clicking does not work open a terminal and enter the command
cd /opt/Pmod3.4/hksetup/Linux
rpm -i WkRt-Lin64-6.0.501_amd64.rpm
(or rpm -i WkRt-Lin32-6.0.501_i386.rpm)
If a message usbutils conflicts with WkRt-Lin-5.20.500-1 occurs on the console, please cancel the installation of WkRt-Lin-5.20.500-1.i386.rpm and enter the command:
rpm -e --nodeps usbutils
to uninstall conflicting USB support.
If messages occur in the console window indicating a conflict with an older version of the driver please uninstall that prior version (eg. WkRt-Lin-5.10.501-1.i386) by entering the command:
rpm -e WkRt-Lin-5.10.501-1.i386
After these cleaning procedures try the installation again.
Note: If you experience problems during driver installation, you are recommended downloading the most recent drivers for the WIBU-KEY (Runtime Kit) from http://wibu.com/download_user.php and try the installation again. Also, in some cases, a reboot may be required after driver installation.
License File
In the delivery note you have received with the PMOD CD you find account information for logging into the support area of www.pmod.com. There you will find a license report, and a button for downloading the license file for your purchased configuration. Please download pstarter.lcs and copy it to the directory Pmod3.4/properties/system/lcs.
Important Note: Please do not change pstarter.lcs in any way - a modified license file will not be accepted. Do not open pstarter.lcs in any program, do not rename it, and if you transfer it per FTP, use binary transfer.
Start PMOD
PMOD can now be started with command script RunPmod in Pmod3.4/Start. Example:
!/bin/sh
cd /opt/Pmod3.4
.\java\jre\bin\java -version
.\java\jre\bin\java -Xmx1800M -jar pmod.jar
Notes:
The script has been tailored to the installation directory. Therefore, if the Pmod3.4 directory is moved to a different location, the path needs to be adjusted.
The -Xmx4000M option specifies the maximum heap memory (4000 MB) that PMOD can allocate. To process large data sets this number should be increased. However, please note that currently there is an operating-system dependent limitation on 32-Bit operating systems: only a maximum of 1800M can be allocated, even if the physical RAM size is larger. Increasing -Xmx beyond 1800M might result in an error Could not reserve enough space for object heap. Caution: The P3D tool may crash, when the reserved space approaches the physical RAM size.
Change Permission Settings of Directories for writing
To allow other users than root the full usage of PMOD it is important to open some PMOD directories for writing:
chmod -R ugo+w /opt/Pmod3.4/properties
chmod -R ugo+w /opt/Pmod3.4/data/
There may be other directories you have to open for writing later on, if several users are working with the same PMOD installation.