If you have console access to the server then maybe you could try cding to the relevant dirctory and then running "perl script.pl" and seeing what happens.

If that prints out your HTML try just "myscript.pl" from the commnd line to see if perl is correctly associated with the .pl extension - take a look at the activeperl specific help (mirrored here if you need it and especially the how to associate .pl with perl FAQ answer).

If it all works from the CLI and you followed the related links to the one above for how to enable perl support in IIS then the obvious thing to do is look in the log file and see what it is that IIS is saying it did.

Alternatively you bin IIS and run a real web server (Apache, thttpd, Xitami or any one of a million others) and get the added benefit of a lack of Microsoft security holes after all even Microsoft'spaid for IDC study said that opensource is better for running webservers

Dingus

---

Enter any 47-digit prime number to continue.