ActiveState Community

windows

How to prevent freeze-ups on dual-core Windows machines

OS: Windows | Product: Komodo | tags: core debugging dual dual-core freeze windows
Question: 

I run Komodo on a dual-core Windows machine. Occasionally after running a Perl program, either inside the debugger or outside, Komodo will freeze up. This seems to happen whether the CPU is Athlon or Pentium, it doesn't seem to matter.

Answer: 

The key is to open the task manager, select the komodo.exe process, right-click
it using the "set affinity" function.

Remove the checkmark from all but one CPU and komodo will work fine.

Thanks to community contributor JTa for working this out.

You can track this bug at
http://bugs.activestate.com/show_bug.cgi?id=53927

PHP configuration fails on Windows Vista x64

OS: All / Any | Product: Komodo | tags: amd64 komodo vista windows x64
Question: 

I am using a Windows Vista x64 system, and get an error when trying to configure PHP for debugging. Is there are fix for this?

Answer: 

This problem is because Komodo is installed to the path

C:\Program Files (x86)\

on Windows Vista x64, and php.ini will not allow paths with parnthese characters in it. There are two possible workarounds:

1. Run the debugger configuration wizard and specify that Komodo's php.ini and php_xdebug.dll should both be placed on a safe path, preferably something like:

C:\php5.2\xdebug\

2. optionally reinstall Komodo to C:\Program Files\ instead.

Perl IO redirection problems on Windows

OS: Windows | Product: ActivePerl | tags: activeperl io Perl pipe redirect windows
Question: 

On Unix I can run commands like "foo.pl | bar.pl" and have the output of foo.pl be the input of bar.pl. This doesn't seem to work on Windows. How can I make this work?

Answer: 

The Windows command interpreter cmd.exe does not support IO redirection for programs started via shell associations, like those created for .pl files during the ActivePerl installation. It only works for .bat, .com, .cmd, and .exe files.

You need to write:

perl foo.pl | perl bar.pl

Or if the files are not in your current directory but are on the PATH:

perl -S foo.pl | perl -S bar.pl

Alternatively, you can wrap your .pl files into .bat scripts using pl2bat:

pl2bat foo.pl
pl2bat bar.pl

Then run them as:

a | b

This is also the case for > and <.

What is the best version of ActivePerl to use with Windows Vista?

OS: Windows Vista | Product: ActivePerl | tags: compatibility Perl vista windows
Question: 

What is the best version of ActivePerl to use with Windows Vista?

Answer: 

The best version of ActivePerl to use on Windows Vista is always the most recent build of ActivePerl 5.8.8 or 5.10.0.

ActivePerl 5.8.8.819 and later versions pass the same suite of tests on Windows Vista as they do on Windows XP and other supported versions of Windows.

ActivePerl's known issues on Windows Vista include:

  • PerlIS and PerlEx are installed but not automatically configured due to differences in the script extension mapping process for IIS
  • the OLE browser will not function with Internet Explorer 7

If you run into other issues, please report them at:

http://bugs.activestate.com

What version of Komodo should I use with Windows Vista?

OS: Windows Vista | Product: Komodo | tags: compatibility komodo vista windows
Question: 

What version of Komodo should I use with Windows Vista?

Answer: 

The best version of Komodo to use with Windows Vista is Komodo 4.1.1. Komodo 3.5 and earlier will not work with Vista.

Should you run into any issues, please file a bug report at:

http://bugs.activestate.com/

What is the best version of ActivePython to use with Windows Vista?

Question: 

What is the best version of ActivePython to use with Windows Vista?

Answer: 

The best version of ActivePython to use with Windows Vista is ActivePython 2.5.0.0.

ActivePython versions 2.4.3.12 and above pass all of the same tests on Vista that they do on Windows XP and other supported versions of Windows.

Note that you will need to right-click on the installation file and select "Run as Administrator" for the installation to be successful. This issue will be resolved in a future version of ActivePython.

What version of ActiveTcl should I use with Windows Vista?

OS: Windows Vista | Product: ActiveTcl | tags: compatibility tcl vista windows
Question: 

What version of ActiveTcl should I use with Windows Vista?

Answer: 

The best version of Tcl to use with Windows Vista is ActiveTcl 8.4.14 or later.

There are currently minor issues with installing and uninstalling, but these are not serious and are being worked on. The demo applications distributed with ActiveTcl all function as expected, including the graphical libraries and Expect.

Note that you will need to right-click the installation file and select "Run as Administrator" for the installation to be successful. This will be fixed in a future release of ActiveTcl.

New to Perl. New to programming.

OS: Windows | Product: ActivePerl | tags: newbie windows
Question: 

I've installed ActivePerl. What now?

Answer: 

Go to Start | Run. Enter 'CMD' in the Open field and press Enter. This will open up a DOS command prompt. At the prompt, type:

  C:\>perl -v

You should see version information for ActivePerl.

To evaluate perl code on the command line, you can do this:

  C:\>perl -e "print \"hello world\";"

Note: you must escape double quotes in the code when using -e.

To run a script:

  C:\>perl scriptname.pl

Here are some great online resources targeted at new Perl developers:

http://learn.perl.org/library/beginning_perl/

http://www.steve.gb.com/perl/tutorial.html

If you are looking for an editor / development environment for Perl, you should try ActiveState's Komodo:

http://activestate.com/Products/Komodo/

Adding a User Environment Variable in Windows

OS: Windows 2000 Pro / Server | Product: Main | tags: path windows
Question: 

How do I add a 'user' environment variable under Windows?

Answer: 
  1. Right-click 'My Computer' and select 'Properties'
  2. Click the 'Advanced' tab, then 'Environment Variables'. This opens
    the Environment Variables dialog.
  3. In the top 'User variables for ' pane, select 'PATH' and
    click 'Edit'. If there is no 'PATH' variable, click on 'New' to create
    it.
  4. Add this to the beginning of the 'Variable value' field:
  5.   C:\perl\bin;
    
  6. Click 'Ok' to close each open dialog

You may want to open a new command prompt to check if perl is now in the
path. The following command should work (and return perl's version
information) if the above steps were successful:

  C\>perl -v