I have had this problem fairly infrequently using different modules on win32.
One of the things that will ALWAYS cause this is a binary that was compiled
against a different version of perl. If you can, grab the source of the module
and compile on your machine, see if that does the trick. If this is
not an option, try and find a more up to date version of the module.
Thanks for the idea, slycer, but I don't get it.
I just looked through all the modules I'm using
and they all seem to be source (text) only, no
binaries at all. I don't even know what perl module
binaries would look like. Am I missing something?