The following tools will enable you to update your K-Rea v3 and/or Foxta v3 hardlock by email. Download the relevant tool depending on your hardlock type and follow the instructions:
USB local hardlock
USB network hardlock
USB evaluation hardlock
FAQ
Updating my K-Rea v3 and/or Foxta v3 hardlock
64bit compatibilty of TERRASOL software
Talren4 v2.0.4, K-Rea v2.4.1 and Straticad V.1.22 are compatible with 64bit systems (Windows® Vista/7).
Note: Talren4 v2.0.4 update should be operated with a new Talren 4 local dongle (whereas the previous network dongles are still working). Contact us if you need your dongle to be exchanged for a new one.
But we still cannot guarantee that Foxta v2, Tunren and Cazenove/Espora will work with 64bit systems.
(you may try " compatibility mode " of Windows®., or 32bit emulations).
Network installation
Yes, it is possible. Refer to the above items in case of a problem
There should be no problem provided:
- both networks can "talk" to each other (ping is possible),
- port 475 is opened (please refer to the above items),
- NAT is activated or VPN exists between both locations.
If all these conditions are fulfilled, edit file nethasp.ini (unzip the file) and define the IP address of the firewall if NAT is activated or the IP address of the server if VPN exists.
The installation of the network hardlock may require additional setup according to your operating system or network setup.
- Check to see if the HASP key is visible by downloading the Diagnostic tool from the Aladdin website.
- Install this on the server.
- Open port 475 and if necessary download the nethasp.ini file (unzip this file).
- In the DOS command window, type the following instruction: "telnet IPServer 475" with the IP address of the server instead of the word "IPServer".
Is an error message displayed or not? (the port 475 should be opened so that the network hardlock can work properly).
If an error message is displayed, contact your IT department and ask them to open port 475. - It is sometimes necessary to setup the nethasp.ini file (unzip the file):
- NH_SERVER_ADDR = 1.1.1.1 (1.1.1.1 should be replaced with the IP address of the server).
This file NetHASP.ini should be placed in the installation directory of Talren 4 for instance (it can also be placed in the C:\Windows\System32 directory, which enables sharing with all other Terrasol programs). - in some cases, NH_TCPIP_METHOD = UDP should be changed to NH_TCPIP_METHOD = TCP
- in some cases, "broadcast" should be "disabled".
- NH_SERVER_ADDR = 1.1.1.1 (1.1.1.1 should be replaced with the IP address of the server).
The hardlock key works from a broadcast sent by the 'server', which has to be recognised by all 'client' computers:
- the server (see below for detailed installation)
You must install both the hardlock driver and the license manager on the computer to which the network hardlock will be connected (it can be the network server but it's not compulsory). This can be any computer on the network that is "visible" to all other users. The server should be on all the time and permanently connected to the hardlock.
- the clients
You must install Talren 4 and the local hardlock driver on all client computers. When running Talren 4, select "Network" instead of "Local" on the first menu screen.
Network installation is more complex than single user and it is essential to use the latest drivers to keep up with the latest Windows updates.
If you encounter problems, the latest license manager and hardlock driver can be downloaded from the following links:
- license manager (v4.99, November 2005);
- hardlock driver (both for the server and the users computers, v8.31, September 2005).
Alternatively, if you still encounter problems, please visit the Aladdin website: www.aladdin.com ("Support & downloads", hardlock type is HASP 4, NetHasp).
Detailed installation procedure for the 'server'
(please follow the order of operations indicated below)
- Disconnect network hardlocks from the server if any.
If this is your first Aladdin installation, go to step 4. - From the Control panel (Add/Remove programs), uninstall all previous hardlock drivers and license managers on the server.
- Reboot the server.
- Install the hardlock driver from the link above.
- Install the license manager from the link above.
Important : do not install the hardlock driver when prompted at the end of the license manager installation (versions are incompatible). - Switch the server off, connect the network hardlock and start the server again.
- Wait for installation to complete and then run Talren 4 on a 'client' with the program/drivers previously installed (see 'Clients' above), selecting network mode.
HASP hardlock driver
If you connected several Terrasol hardlocks (for example one for Talren and one for K-Rea), only one of them will be found by the computer. Disconnect the hardlocks that you are not using right now (only one hardlock should remain connected). The last dongle will then be found by the computer. If you need to use several programs at the same time, contact-us for a hardlock exchange: we will provide you with a single hardlock including all the software you bought. You will then be able to use all these programs at the same time on the same computer.
The hardlock driver provided by Terrasol also works for Plaxis software, but it's not the same with Plaxis hardlock driver (it doesn't work with Terrasol software). You need to reinstall the hardlock driver provided by Terrasol: download this file. Then unzip it and execute the extracted file drivers.bat (agree to overwrite the existing hardlock if requested so). If the problem still occurs, contact us or your local agent.
You probably need a more recent version of the hardlock driver than the one proposed on the installation CD-ROM: download this file. Then unzip it and execute the extracted file drivers.bat (agree to overwrite the existing hardlock if requested so). If the problem still occurs, contact us or your local agent.
If you use a very recent computer, this problem sometimes occurs. You probably need a more recent version of the hardlock driver than the one provided on your CD: download this file. Then unzip it and execute the extracted file drivers.bat (agree to overwrite the existing hardlock if requested so). If the problem still occurs, contact us or your local agent.
TALREN 4
Talren 4 is compatible with Java 6.
But Talren 4 is not yet compatible with Java 7.
If you are not logged in as an administrator of your computer, the problem is probably that you don't have full control of the Talren 4 installation directory (by defaultC:\Program Files\Talren 4\). Please contact your IT deparment and request full control of the directory.
If you are not logged in as an administrator of your computer, the problem is probably that you don't have full control of the Talren 4 installation directory (by defaultC:\Program Files\Talren 4\). Please contact your IT deparment and request full control of the directory.
Please check that you are using Java 6 or a more recent version, and that you haven't upgraded to v2 directly from v1.1. We advise that you uninstall all Talren versions from your computer, and start a complete installation and update process again.
This problem is very rare. Send us your prj files so that we can try to fix it.
Install the latest hardlock driver: download this file. Then unzip it and execute the extracted file drivers.bat (agree to overwrite the existing hardlock if requested so). If the problem still occurs, contact us or your local agent.
The slope boundary calculation is not automatic when reading a .tal file. You have to check this option is the geometry dialogue box.
This problem occurs when using a non-typical screen resolution. Use a typical resolution such as 1024x768 or 1280x1024.
If you are using soil patterns (instead of colours), the problem may also be related to the Java version on your computer: printing with patterns works fine until Java 1.6.13, but an incompatibility occured with upper Java versions.
The problem may be due tu blanks or tabs at the beginning of the strings input for project description. Delete these blanks in the project general settings, and also try not to use new lines in the project comments. You may also try to install the latest update of the problem still occurs after that.
Files sols.bd and/or renforcements.bd are missing in the Talren 4 installation directory. Contact us so that we can send you the missing files (which will be provided as with the initial installation).
This problem relates to the safety factors dialogue box and the soil properties dialogue box. It is usually caused by the graphical device driver which results in these dialogue boxes not being displayed. Install the driver for the graphical device of your computer (CD-ROM provided with the computer or download from the Internet, depending on the trademark).
Alternatively if this doesn't solve the problem, please download this JRE update.
Test if the error occurs with all files, or if it is related to a single file or group of files. To do this, run Talren 4 and open one of the example files provided with Talren 4 in the installation directory.
- If you don't encounter your problem with the example file, it may be related to data input. In this case, please send us your prj file (with a full description of the problem), so that we can help you model a solution.
- If you also encounter your problem with the example file, it most probably relates to the version of the Java Runtime Environment installed. Please download the latest Talren 4 update and download this JRE update
The dll files used by the program are not the right ones. They may have been overwritten. Re-install the latest Talren update.
This usually happens relates to a Windows 2000 operating system. The following procedure normally resolves the problem: copy the files DFORRT.DLL and DFORRTD.DLL from directory C:\Program Files\Talren 4 into directory C:\Windows\System32 and start the Talren 4 calculation again. It should work properly now.
Talren 4 uses a program called Java Runtime Environment (JRE). Since compiling the program, Java Runtime Environment has been updated several times and we endeavour to ensure that Talren 4 is fully compatible with the latest version.
Please use this link to download JRE 1.6.0_03, then execute the downloaded file and follow the default installation instructions.
The hardlock driver may not be properly installed or the hardlock driver version is not up-to-date). You can install the hardlock driver from the Talren 4 CD-ROM by inserting the CD-ROM, and selecting "install hardlock driver" from the first menu. This installation solves most of the problems, but make sure you uninstall any previous version beforehand. If this is not the case, contact us or your agent, and please provide the following information:
- is another hardlock (USB or parallel) connected to the computer ? If so, please try to run Talren 4 after disconnecting all other hardlocks.
- is a printer connected after the Talren hardlock (parallel). If so, check whether the printer is on and run Talren again. If Talren still doesn't work, please try to run Talren after disconnecting the printer from the computer.
- is the port (parallel or USB) working fine (to check, please test it by connecting other equipement to the same port: printer, other hardlock, etc).
- can you try to install Talren 4 on another computer, and run it with the same hardlock ? Is it working fine or not ?
- did you try to install the latest hardlock driver ?
Nota Bene : the above answer relates to local hardlock problems. See TALREN 4 NETWORK INSTALLATION for network hardlock issues.
You need Java 1.6 at least. You may download this version from here: JRE 1.6.0_03 (14 Mo, update for Java Runtime Environment).
It depends on the version you are using now:
- if you use version v1.14a or more recent versions, all you need to do is download and install the latest update, and any other relevant file advised on the update webpage (you don't need to install intermediate versions/updates in this case).
- if you are using a version older than v1.14a : download and install the latest update first v1.14a, and then the latest update, and any other relevant file advised on the update webpage.
K-REA v3
When installation an anchor with no prestress force, the anchor will start working only from the next phase, because only the prestress force is taken into account in the installation phase of the anchor (the anchor stiffness is activated in the next phase).
No, some actions need to be combined with others. For example, the actions "Sheeting installation", "Berm" and "Hydraulic gradient" need to be preceded by an action "Excavation-Water". A warning will be displayed if this is not the case, and this is also highlighted in the technical manual (description of each action).
In K-REA, the action "strut installation" generates no modification of the wall equilibrium. K-REA then displays a non-convergence which only means that the results for this phase are exactly the same as the results for the previous phase (this is valid only if the strut installation is the only action in the phase).
Maximize the DOS window (from the task bar), and close it (top right button). Then ask for calculation again. Results should be displayed correctly this time.
You need to change the screen resolution (probably 800x600 at the moment) to a minimum of 1024x768. To do that, right click on the desktop. Select Properties, then Settings and move the cursor to 1024x768 pixels minimum. Apply and validate this change.
You need to change the decimal symbol: it should be a point and not a komma. To do that, open the control panel, select Regional settings, and click on "Personnalise". Finally, change the decimal symbol to a point (.). Apply and validate this change.