I'm sure this is the case for him. In his other thread he mentioned that it runs ok within Padre, but not when he runs it from the command line. This is a classic example of Padre using Padre's perl, and the command line using some other Perl (on Windows, I guess this means some registry configuration).

Also, in this thread he discussed running ppm, which is Active State, but also mentioned that he's using Strawberry Perl. So there you have it; Padre is configured with the Active State Perl as its environment, and from the command line he's using Strawberry. They won't be (and shouldn't be) sharing libraries. They are probably not even binary compatible since Active Perl is usually built with MSVC, and Strawberry with gcc.