Install error - "ActivePerl is not supported by my processor type"


When I try to install ActivePerl on Windows, it says it is not supported by my processor type. My system meets the ActiveState requirements. Why is it not recognized?


This message isn't an ActiveState error message. It comes from within the Microsoft Installation tool, and it's rather misleading. The processor isn't in fact the problem.

What the message really indicates is that you are attempting to install a 64-bit binary on a 32-bit version of Windows. This won't work. A 64-bit processor will run either 32-bit or 64-bit Windows, but MSI installers for 64-bit software will only install on 64-bit Windows.

Most users solve this by using the 32-bit x86 ActivePerl installer with a 32-bit Windows, however in cases where a full 64-bit x86_64 ActivePerl is necessary there is no alternative except to first upgrade to a 64-bit version of Windows.

Komodo file locations


Where can I find the Komodo files?


Where is Komodo installed?

The default location varies by platform, and the name of the directory corresponds to the version of Komodo you are running ("IDE" or "Edit" plus the version number - e.g. "Komodo IDE 8"):

  • Windows
    C:\Program Files\ActiveState Komodo [IDE|Edit] <version>\
  • Linux
  • OS X

Where does Komodo keep settings data?

Komodo stores preferences, macros, templates, keybinding schemes and other settings in a user-specific directory called the user data directory. The name and location of this directory varies depending on the operating system and Komodo version:

  • Windows Vista, Windows 7, Windows 8 or newer
  • Windows XP or older
    C:\Documents and Settings\<username>\Local Settings\Application Data\ActiveState\Komodo[IDE|Edit]\<version>
  • Linux
  • Mac OS X
    /Users/<user>/Library/Application Support/Komodo[IDE|Edit]/<version>

You can find more details about the contents of the profile directory here:

The location of this directory can be overridden using the KOMODO_USERDATADIR environment variable, see:

Where does Komodo log output and errors?

Note: In Komodo 6, you can use the "Help->Trouble Shooting->View log file" menu command to quickly examine Komodo's main log file ("pystderr.log").

There are two files named "pystderr.log" and "pystdout.log" within your Komodo user data directory. These files are extremely useful for troubleshooting problems with Komodo and are often requested when logging bug reports.

  • Windows Vista, Windows 7, Windows 8 or newer
  • Windows XP or older
    C:\Documents and Settings\<username>\Local Settings\Application Data\ActiveState\Komodo[IDE|Edit]\<version>\pystd[err|out].log
  • Linux
  • Mac OS X
    /Users/<user>/Library/Application Support/Komodo[IDE|Edit]/<version>/pystd[err|out].log

How do I reset Komodo's preferences to the default settings?

Warning: This will reset a lot of preference information, including opened files, recent files, projects and toolbox, additional installed extensions, customized Komodo preferences, etc... So make sure you backup the folder instead of simply deleting it, this way you can easily restore your settings.

Your preferences should be reset.

Note 1: If you have older Komodo preferences from before Komodo 4.0, these will be applied on-top of the default preferences as part of a Komodo upgrade process, so for a total default/fresh set of preferences you will need to rename the older komodo directory as well.

Note 2: You can also use a completely different Komodo user data directory, see below.

How can I change Komodo's profile storage location

You can use a completely custom Komodo user data (profile) directory by setting the KOMODO_USERDATADIR variable in your environment settings before starting Komodo.

export KOMODO_USERDATADIR=/tmp/komodoide

Komodo Port Usage


My [insert security company here] software Firewall is reporting that Komodo is engaging in 'suspicious activity' or is a Trojan. What is going on here?


We've always used socket connections, and have occasionally had problems with Security software returning a false positive. Komodo uses ports for the following reasons:

- the debugger ( typically port 9000, but user-configurable )
- the start page has an iFrame that displays a page on our site.
- ssh / sftp / ftp editing
- the html perview, if you open a url

It is almost always the debugger that is the problem because the other features all use 'standard' ports for relatively well-known protocols. Komodo does not have any kind of spyware in it, so my best suggestion is to configure your software to allow Komodo to make these connections.