The proxy is authenticated, but the authentication is a "secret." IE: The name of the proxy server, the UID used, and the password are all unknown, and corporate policy is, they won't let us know any of them. So "direct" HTTP is impossible.
By "hacked install," I mean that the ActivePerl MSI is installed just fine, but the Tk, DBI, and DBD::ODBC drivers were simply "copied in", e.g. from ".../blib/lib/*.pm" to ".../perl/lib/*.pm", directory tree intact.
The access violation seems to say to me that one of (DBI.DLL?, PERL.EXE, PERLCRT.DLL) is mismatching the versions of the others; but the DBI.tar.gz was just pulled today from ActiveState.Com/packages/x86, so I don't know how that's possible...
In reply to Re: Re: ActivePerl Problems
by Anonymous Monk
in thread ActivePerl Problems
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |