Thank you all for your replies!

@VinsWorldcom
-I recursively copied C:\Perl on the old system to C:\ on the new systems. As a result, I have a C:\Perl directory on each of the new systems.
-I did not always put them in the order you mentioned, but I played with that later and found no difference in outcome.
-Having executed the line of code your provided, I obtained the following output:

C:/Perl/site/lib/MSWin32-x86-multi-thread
C:/Perl/site/lib
C:/Perl/lib
.
[download]

All of these directories exist.

@Jenda
-It turns out that there are many vpp.pm's, but never in a directory named "version".
-The code you provided gives the following error: "Can't load 'C:\Perl\site\lib\auto\version\vxs\vxs.dll' for module version::vxs: load_file:%1 is not a valid Win32 application at C:\Perl\DynaLoader.pm line 201."
-I'm sure that Perl was never installed on the XP virtual machine, at the very least.

So the message I was after was in fact a bit misleading. The DLL could not be loaded as I expected, but not because it would be invalid, but rather because it depended on some missing libraries. One tool that's great for such things is the Dependency Walker. It'd tell you whether the DLL is corrupted or missing dependencies. It doesn't know where to get the missing DLLs, but at least it tells you the dependencies are the problem and the names of the DLLs.

P.S.: If you reply to my post, I get notified.

Jenda
Enoch was right!
Enjoy the last years of Rome.

Hello,

I will definitely look into that tool for the future. It seems like it might be useful.

I will also keep my replies in line with their respective posts. I didn't realise that this feature existed.

Thanks for all of your help.
Perldough