FAQs - General/All Products
General / All Products
- There seems to be a problem with the dongle. I receive the error message "Cannot access hardware key" or "missing or invalid hardware key. Driver not installed. 12(0x000c)."
- During installation, the following error message is displayed: "The location pointed to by qtc_execs is corrupted."
- Can QTC programs support multiple databases?
- I modified the settings in the <product>.ini / <product>.cfg/ qtc_licence file and my changes did not have any effect.
A1. Quester Tangent's software protection module uses a Sentinel hardware key (dongle) made by Safenet. Their website references problems with Windows 2000 and XP. Use the Control Panel "Add/Remove Programs" to uninstall all Sentinel System Drivers. Download the latest drivers from their web site http://www.safenet-inc.com/support/tech/sentinel.asp . If you have a USB dongle, click on Sentinel SuperPro . For 64-bit computers, select the driver for Windows XP-Pro 64-bit, version v7.2.2. If you have a parallel dongle, click on Other Hardware Keys . The Quester Tangent software does not have to be reinstalled.
Restart the computer after reinstalling the drivers.
A 2 . The last uninstall did not remove the product initialization (*.ini) file from the Windows directory. Manually remove the old product ini file (e.g.C:\Windows\impact.ini), and then repeat the install.
A 3 . Yes. Ideally each survey area/ vessel/ set of work activities should be constrained to onedatabase. In QTC IMPACT 3.40 , QTC MULTIVIEW 3.00 and QTC SIDEVIEW 1.30, go to File |Preferences and choose the Database tab. Type in the location of the database and restart the program.
If you have an older version of the software, there is a different procedure. To create a new database, choose the disk location, edit the
.ini file and modify the setting for qtc_data to point to the new disk location.
A 4. Before modifying anysettings in the these files, be sure the program is not running. Shut down the program, edit the file and then restart. Another possibility is that the file editor may have saved previous changes as a text file, i.e. changes the file to product.ini.txt