Install ActiveState Perl on the Windows2000 server.

If you intend on having the users simply download the program, you should simply place it online, and allow users to download from there.

Perl Compilers aren't a good option. Perl is a part-compiled, part-interpretted language. Unless your target market is the 13-year-old AOL user demographic, I suggest having your users install Perl. It's a quick download, unintrusive, and opens a door for a world of programs not offered with Windows.

Hope this helps, if not, please post a reply (or sign up for an account :) ).

John J Reiser
newrisedesigns.com

I disagree, I find PerlApp invaluable. I have many Win32 machines that are regularly re-imaged, and trying to keep modules and perl versions up to date and in sync on those machines is more work than it is worth, having .exe's lets me just copy a tools directory over, put it in the path and use them. That is a much easier script to write than trying to sync all my version #'s.

And, if your going to allow users to play with these, in the .exe all of your scripts are always being run with the same version of perl, the same version of each module, etc...makes debuging user issues easier, and avoids many user support issues in the first place.

If you are going to put the tools up for download (for a legitimate reason :) making them .exe's makes support much easier.

"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!

Another compiler option is PerlApp, part of the PDK available from ActiveState

I agree with newrisedesigns, but if you still want to go the compiled way you can use perl2exe.