It sounds like you've really got your hands tied behind your back on this
one. Maybe you might try running a batch file that sets the PATH variable
and then executes the script passed to it as an argument. That way you can
use your environment variables without altering the system's environment
variables, since they will only be valid as long as the script is running.
-----Original Message-----
From: Declan Mullen [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 5:13 PM
To: [EMAIL PROTECTED]
Subject: RE: A perl interpreter that doesn't require registry or PATH
settings ?
Thanks for the many suggestions that are based around using a network share.
I most cases it would seem to be the best solution, however in my case the
Perl interpreter needs to be available even when the LAN goes down, so Perl
needs to be available locally.
Thanks,
Declan
-----Original Message-----
From: Declan Mullen [mailto:[EMAIL PROTECTED]]
Sent: 22 June 2001 11:39
To: [EMAIL PROTECTED]
Subject: A perl interpreter that doesn't require registry or PATH settings ?
Hi,
I need to deploy a windows Perl interpreter to a large number of
NT4/Win2k systems that are owned by other departments within my company.
In order to reduce the objections to this deployment, I need a version
of Perl that does not require the registry or the PATH environment
variable to modified, (explicitly calling the Perl .exe to run scripts
is very acceptable). In addition the interpreter needs to be augmentable
with additional Perl modules. However, I don't need any ActiveX or web
server support.
Many thanks for any recommendations.
BTW I'm a newbie to Perl.
Regards,
Declan
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
