in reply to How do I install perl on win2000 so that I can use perl file offline?

Try going here and downloading the Windows MSI item.

This provides an MSI file that you can install from Explorer. Simply double-click the file and let it work its magic. You should restart your computer once it's finished.

Once you've done that, you're set. For more information, go here.

Update: Ah, now we get to the heart of the matter. The following added to cover the Splinter's reply:

You haven't said whether you're trying to run utility scripts or CGI scripts. If the former, then check out ActiveState's FAQ on the subject.

If the latter, you'll need to install a web server of some form, such as Microsoft's Personal Web Server (bleah) or Apache. If you're not already using PWS, there's a bundle including Perl and Apache called IndigoPerl. I have hear this spoken of favorably, though I have no direct experience with it myself.

If you've checked these out, then please post a message outlining some more specific details such as the script you're running, how you're running it, and what it's doing/not doing right.

--f
  • Comment on Re: How do I install perl on win2000 so that I can use perl file offline?

Replies are listed 'Best First'.
Re: How do I install perl on win2000 so that I can use perl file offline?
by Splinter (Initiate) on Feb 12, 2001 at 01:54 UTC
    but whenever I access a .pl file using Internet Explorer It brings up a download thing. Or a perl dos window appears and then goes away. Not html output or anything. I did the right content type statement but no success.

      Your webserver returns the wrong content-type header or your Perl scripts don't return content-type:text/html headers, most likely because you are not using the CGI.pm module.

      That a DOS window (in fact, it's just a console window, but the term DOS window is more common) opens, is natural, as Windows starts Perl.exe to open/execute the file that was downloaded as .pl file, and Perl is connected to the .pl file extension. So check that your MIME types in your webserver are correct and that your scripts are also generating the right content-type headers.

      And use CGI !

      Silly question: are you accessing Perl scripts through a webserver (that is, <samp>http://localhost/myscript.pl</samp>) or are you accessing them through Windows Explorer (<samp>C:\InetPub\wwwroot\myscript.pl</samp>)? It sounds like the latter.

      It makes a world of difference. Windows explorer runs the Perl scripts as if they were run from a command shell. Your webserver runs them with the appropriate environment values set and querie parameters sent, filters the output, and sends it to the web browser.