If either of those vars is set, try clearing them and then re-run perl Makefile.PL etc. Also make sure that the perl.exe that gets run is the one you want to install the module with.

If this doesn't help, you might have the wrong library path built into the perl interpreter - you need to reconfigure and compile perl if that is the case.

When you run perl the old Perl interpreter is executing. If you specify the full path to the new interpreter you've just installed then it should work. Try it, with the -V option to display the version.

So now the problem isn't a Perl problem at all; it's that your computer is picking the wrong version of an app to run. That's probably down to your PATH setting. Tweak that so that the directory containing your new version of Perl comes before the one containing the older version (or remove the older one entirely.

The other thing is that I cannot use PPM, not that it is going to help me here, as the requests out are blocked by the firewall.

In similar situations I have been able to download PPM files from a repository using a web-browser, then unzip them and use PPM to install them locally. That way your firewall will never know, but you don't have to resort to make.

Howdy!

Nope nope nope...

I just ran into that myself the other day. I had upgraded from 5.8.0 to 5.8.4 and installed in the same place. "which perl" didn't change.

The module in question had been installed under the 5.8.0 subdirectory, and I ended up manually nuking the files. Once I had done that, make install put the new version in the right place and didn't complain about the version of perl.

I had been getting exactly the same message (module version numbers) that the original poster had gotten.

yours,
Michael

Smyler's advise is excellent. You may also profit by going to your file manager, select tools |folder options and click on the filetypes tab. Then hunt up the entry(ies) for perl and see what you find.

You say you've "downloaded and installed" but don't specify whether you're referring to a binary (Active State, for ex) or whether you compiled source.

If the former, consider whether you allowed the install to associate the binary with files of type ".pl" in which case there surely should be an entry in the filetypes tab, as least for action "open" (and if so, you may wish to add an action "edit" pointing to your favorite text editor).

Now some scattershooting:

• I'm not enuf of a sysadmin to rule out your "devious scripts" but somewhat suspicious thereof. Do you have install (admin) rights on your box/C: drive? (I suspect yes from what you wrote, but ??).
• And have you cd'ed (in a DOS window) to C:\Perl\bin and checked execution from there?
• And -- Smyler's comment re PPM is right on though you may have to add the local repository to your list of available sources.
</ul HTH...