Navigation
RSS Feeds
PDK
Problem installing PerlDevKit 7.2.0
Case #1 - The PerlNET component is disabled in the installer. PDK installs but I don't get PerlNET.
Case #2 - The PerlDevKit gets past creating shortcuts, but not much further, then it fails silently and starts rolling back.
Case #3 - I keep receiving an error message that says "Error writing to file: Perl510RT.dll. Verify that you have access to that directory." (can be one of several Perl510xx.dll files)
PerlNET in PerlDevKit 7.2.0 requires .NET 1.1 and .NET 2.0, with SP1 for both being strongly recommended.
In Case #1 there is no .NET installed. PDK detects this and automatically disables PerlNET.
In Case #2 only .NET 1.0 is installed.
In Case #3 only .NET 1.1 is installed.
You have two options. You can either install .NET 1.1 and .NET 2.0, then proceed with a full installation of PerlDevKit, or you can disable the PerlNET component of PerlDevKit during the PDK installation process (as is done automatically in Case #1). Either should allow you to complete the install.
Extending PDK trial
How do I extend my PDK trial license?
To extend your PDK trial license:
1. go to this link in your browser:
http://www.activestate.com/products/perl_dev_kit/trial_options.plex
2. sign in to your ActiveState.com account (you may need to register if you have not previously)
3. download and install the new Trial license
- Login to post comments
PDK 7.0 - Error 2908/problems installing PerlRT.dll during Perl Dev Kit installation
I get an "Internal error 2908" and then "An error occurred during the installation of assembly 'PerlRT69.dll'..." (or 'PerlRT70.dll,... depending on the version of PDK) during the installation of the Perl Dev Kit. What causes this? How can I proceed with the installation?
The errors above are caused by the machine in question not having a Microsoft .NET runtime installed. There are two ways to handle the situation:
- install a .NET runtime from Microsoft (.NET 3.0 is not yet supported)
- restart the PDK installation and deselect the PerlNET component -- it isn't useful without an installed .NET runtime
Either case will allow the installation to proceed.
"No perl found at C:\perl\bin\perl.exe" when using PerlApp
When I try to use PerlApp I get the following error: "No perl found at C:\perl\bin\perl.exe" -- but that file is really there. What's going on, and how can I fix it?
This message is usually caused by the directory containing cmd.exe not being found in your PATH environment variable. The usual directory to ensure is there is C:\Windows\System32. If it's missing, simply add it and PerlApp will work as expected.
- Login to post comments
Where can I get past versions of the PDK?
Where can I get past versions of the PDK? Is there an ftp site for the PDK?
You can get past versions of ActiveState products from our ftp server:
You can also access the ftp repository via the web at:
This can be useful if you are behind a firewall that does not allow ftp.
- Login to post comments
What is the ECCN for the PDK?
What is the Export Classification Control Number for the Perl Developers Kit?
The Export Control Classification Number for the PDK is EAR99 (self-classified). For a brief description of EAR99 and information on the difference between EAR99 and NLR (No License Required), see:
- Login to post comments
Manually Install PDK Extension
Why are my PDK tools unavailable?
It's possible that the PDK integration module wasn't installed
automatically when you installed Komodo. You can do this manually:
- Go to File | Open
- Browse to and open the extension here:
C:\Program Files\ActiveState Komodo3.5\lib\support\modules\perldevkit.xpi
Komodo will install the extension; you will need to re-start Komodo for
the extension to take effect.
- Login to post comments