So your Perl version is different, for one thing. And you're installing it using a combination of PPM and cpan... seems odd. And you've modified the source code of the module, possibly without fully understanding what the modification is for. Those are at least three opportunities for trouble to creep in, without even considering the potential for bugs within the module itself.

Speaking of which, I found this: RT#77800, which deals specifically with a problem that turns up under Perl 5.16.x and newer, relating to deprecation warnings... not the same type of warning you're getting, but definitely within the same code segment.

I don't know the answer to the question I'm about to ask, because I do my best to avoid working with PDF's: Is it possible that there is a newer, better maintained module on CPAN that can be of use to you, that doesn't have bugs in its queue that are --in some cases-- several years old?

Anyway, try rolling your Perl version back to an earlier version -- preferably the same version you're using on the old Windows machine -- and see if it works then. If so, you've found another bug to report, though I don't think anyone is monitoring the reports at this point.

It sounds like you're using ActiveState. It appears that Perl-5.10.x is available from ActiveState for a fee. You might, instead, download the Strawberry Perl Perl v5.10.1 in a sandboxed dev environment and see if the module works under that Perl. If so, and if you still are required to use ActivePerl in production, you'll at least know whether or not its worthwhile investigating what ActiveState charges for 5.10.