I suspect that by not contacting the maintainer and sending a "this seems wrong to me" message to p5p - I will get every opinion in the book as to how to solve the problem with no action, no response at all, or a "wrong place kid" response.

Since you are the only person replying to this thread - I just may do that. I don't really feel that strongly about it to fight for though. I just wanted to raise some awareness about how an error message could be more user friendly.

I think you misunderstand what Dave is saying. When Perl builds, it creates the Config.pm module. There is no maintainer; it's an autogenerated file.

If you read the first two lines of the module, they allude to this. Perhaps there's a better way to explain what's going on there, but I can't think of a situation where Config would break after a normal installation process.

chromatic,
I certainly was. So then this problem really should be address with ActiveState then. When you download their zip file (look ma - no installation), you get a Config.pm with entries in the hash containing:  C:\TEMP\perl-------------------------------------------please-run-the-install-script------------------------------------------\bin It isn't that I should expect something that hasn't been installed to be psychic to know where you have installed it, but it could do a better job of explaining the problem. FWIW - I looked for an install script or some documentation on what to do to fix this and came up with nothing.

I suppose I have to educate myself on the Config process now just so I won't make such an obvious oversight again. Cheers and thanks for clarifying.

Cheers - L~R