Earlier versions of IDRISI are not fully supported under Windows 7 and Vista. However, we have been successful in solving most cases. If you have already installed IDRISI Andes or Kilimanjaro and are receiving error messages, you may need to reinstall according to the following instructions.
Windows 7 and Vista Information
Windows 7 and Vista implement the best-practice of "least privileges" through a system called User Account Control. "Least privileges" refers to running processes as a user with the least privileges possible, while still being able to do what you are trying to do (work, etc.). This is generally advisable for security reasons since if you run as administrator, and the system is compromised, the damage caused is not limited to your account but may involve the entire machine and/or network. User Account Control can be turned off, but since it affects all processes and all users, it is unadvisable for us to suggest this to customers. UAC works as follows:
In Windows 7 and Vista, no matter what level of user you login as, you always run processes as a "limited user." Windows XP differs in that when you log in as a particular user, you run processes with the privileges of that user.
This means that in Windows 7 and Vista, if you or a process you initiate needs to do a task which requires higher level privileges, you must explicitly “request” these privileges. The Run As... context menu command (right-mouse)can be used for most cases where this is necessary. There is also a Run As command line equivalent.
1. When launching the IDRISI installer, be sure to “Run as administrator.” Right-click on the Setup.exe file from the CD or the download file and select Run as Administrator. You will need to do this even if you are currently logged in as administrator.
2. Near the end of the IDRISI installation, a Windows warning message will display, regarding the install of Client Activator. Choose the "Recommended" option. See Note below for Vista Home Edition users.
3. After installing, start IDRISI the first time with the “Run as administrator” option. Once you have done this, regular users may run IDRISI normally.
Vista Home Edition
For users running Windows Vista Home Edition, this option may not appear at the end of the installation process. Additionally Vista Home Edition does not allow general users to run IDRISI. In this case, users have two options:
1. Set IDRISI to always run as an administrator. To do this, right-click on the Idrisi32.exe icon or shortcut, go to 'Properties' > 'Compatibility', and check the box listed 'Run as administrator' or
2. Turn the User Accounts Control off under 'Control panel' > 'User accounts.' (This is not recommended.)
Beginning with Windows Vista, Microsoft terminated its support for 32-bit .hlp files, no longer distributing the WINHLP32.EXE file required to view .hlp files. Since the older versions of the IDRISI Help System are in this format, you will need to download and install this legacy executable. Visit Microsoft to review the legacy issue with .hlp files and download and install this help viewer on your Windows 7 or Vista machine.
IDRISI Andes and Kilimanjaro use the software licensing program Sentinel LM to manage the installation of stand-alone and multi-seat installations. Some common issues are listed below.
When launching IDRISI, you receive the error “SentinalLm: Error: Probably no servers running on this subnet?”
IDRISI returns this error when it cannot find a valid license file. It is an indication that your license file has either been improperly installed or that is it is not valid. The license file we send you will only work on the computer from which the locking code you sent was generated. If you encounter this error, please send by email (firstname.lastname@example.org) a screenshot of your locking code and a copy of the file ‘LSERVRC’ from your IDRISI Andes folder.
You can generate a screenshot of your locking code by attempting to activate IDRISI. First, launch IDRISI. Since it is not properly activated, the Activation Wizard will display and you will be presented with the option to activate your license. Choose this option and select “enter a license code.” This will display your locking code. Send by email (email@example.com) a screenshot of your locking code and a copy of the file 'LSERVRC' from your IDRISI Andes or Kilimanjaro folder. These two items will allow our technical support team to diagnose the problem you are encountering.
You installed IDRISI and it worked for a short period of time. Now it is asking to “Activate.”
IDRISI will run for a 15 day trial period without the installation of a license file. If you receive the Activate message, it is likely you are operating the license in Trial Mode and that the license file was not properly installed.
IDRISI requires the installation of a license file which is unique to the computer it is running on. This license file is generated at Clark Labs. If we have already sent you a license file, please go through the activation process and install the one we sent.
If not, you will need to provide us with some information about your license. Please send by email (firstname.lastname@example.org) a screenshot of your locking code and a copy of the file ‘LSERVRC’ from your IDRISI Andes or Kilimanjaro folder. You can generate a screenshot of your locking code by attempting to activate IDRISI. First, launch IDRISI. Since it is not properly activated the Activation Wizard will display and you will be presented with the option to activate. Choose this option and select “enter a license code.” This will display your locking code. These two items will allow our technical support team to diagnose the problem you are encountering.
Time tampering by changing the system clock and date on your computer.
If the date on your computer was changed after you installed IDRISI, you may experience problems running the program. If this occurs, document the series of error messages you received and email them to Clark Labs Technical Support. Steps will need to be undertaken to successfully reactivate IDRISI after time tampering occurs.
The following is a list of common problems that can cause errors activating your IDRISI Andes or Kilimanjaro. Please make sure the following settings are correct on your server and clients.
1. Check the date on the server. If the date is incorrect, IDRISI may not operate properly. Also, if the date was changed on the server after the IDRISI license was activated, it may not launch. If the latter occurs, please inform Clark Labs with details of this occurrence. Steps will need to be undertaken to successfully reactivate IDRISI after time tampering occurs.
2. Please ensure that there are no system environment variables set on the server named LSHOST and LSFORCEHOST. If either of these two variables is set, please remove them temporarily and try relaunching IDRISI. If IDRISI successfully launches, please contact Clark Labs with the details on the other programs needing either or both of these variables. On most operating systems, you can access environment variables through the Control Panel/System Properties. Select the Advanced tab and then ‘Environment variables.’ You must have full administrative privileges when adding or removing environment variables. Only the system variables need to be altered.
3. NetBios must be installed and enabled on the server.
4. The server must have a static IP after boot up.
5. The server can only have one network card installed. If there is more then one network card installed, you will need to remove the extra cards or use IDRISI on another server.
6. Make sure that the locking code is not being generated through remote access. It must be generated from the actual machine that IDRISI is installed on.
7. Make sure that IDRISI is installed on the boot drive. If IDRISI is installed on a secondary drive, it may cause confusion in the generation of the locking code and subsequently the license file.
8. In rare cases, a server may “lose” its license. Simply running the program LOADLS.EXE twice from the installed IDRISI folder (run it once to remove and again to add) can restore the license. A reboot of the computer may also restore the license.
9. Please ensure that the server has only one host name.
10. The Sentinel License Manager requires that UDP Port 5093 be open. If your firewall closes all ports, you will need to manually open this port for the Sentinel License Manager to communicate out.
If you check all of these items and IDRISI still will not run on the server, please send the following information to email@example.com
1. Your customer ID number or the name of the person that IDRISI is registered under.
2. A copy of the file ‘LSERVRC’ from the IDRISI Andes or Kilimanjaro folder.
3. Run the SET command from the command prompt to dump system settings. Run: SET > SET.TXT. This will create a text file called SET.TXT. Save it to the folder specified in the command prompt. After you run this command, attach this file to your email.
4. Run the LSWHERE.EXE program found in the IDRISI Andes or Kilimanjaro folder. It will display the results to the screen. Please send us a screenshot of the result as an attachment in your email.
5. Run the ECHOID.EXE program found in the IDRISI Andes or Kilimanjaro folder. It will return a locking code to your screen. Please send us a screenshot of this code as an attachment to your email.
6. Run the command IPCONFIG /ALL > IPCONFIG.TXT from the command prompt. This will create a text file called IPCONFIG.TXT. Please send us a screenshot of the result as an attachment in your email
There are two types of client installations; a ‘full install,’ which installs all components of IDRISI on the hard drive of the client, and a ‘thin client,’ which installs only the system files needed to run a client. If the network you are operating IDRISI on is frequently overloaded (slow data transfers), then we recommend a full install. If you are having problems running clients, first ensure that IDRISI runs properly on the server. If the client can still not get a license, refer to the notes below.
1. From the installed IDRISI folder on the server, copy the program LSWHERE.EXE to the client. Run this program and verify that it can find the License Manager on the server. If it is not able to find the server, proceed to step 2 below.
2. If the client cannot find a license, set the environment variables LSHOST and/or LSFORCEHOST to the IP address or the name of the server. Go to Control Panel/System Properties, select the Advanced tab and then ‘Environment variables.’ Make sure that you set the variables under ‘System variables’. This will tell the client where to find the license.
3. If you are attempting to run clients from a server on a different subnet, all the routers must be set to re-broadcast all UDP packets on port 5093, and UDP packets must be able to go to and from different subnets. All firewalls must have port 5093 open since it is the port the License Manager uses to communicate.