Within an organization, you can probably just pack up the script with pl2bat but change the two calls to perl to be calls to \\chorg-w2k\perl\bin\perl (assuming your desktop is called chorg-w2k and you make a read-only share of the directory where you installed perl and call that share "perl").

The way most WinNT/Win2K shops are set up, that will work just fine for most people you work with. As you produce more neat scripts in Perl, more people will install it on their machine or you can get a standard shared directory for Perl on one of the central file servers.

Around here, just about everyone has perl installed (all of the developers do because our development tools require it). But the standard Perl doesn't include Tk so my Tk utilities run the local copy of Perl and then check if the needed modules are installed. If not, they switch to my shared copy of Perl.

The cmd.exe of WinNT/Win2K is finally powerful enough that you can even detect whether they have Perl installed before you try to run your shared copy.

        - tye (but my friends call me "Tye")