Couple of additions to my posting: > 1. A Virtual Directory called cgi-bin within your web site. It doesn't have to be called cgi-bin - though that is the normal name for the script directory. The Virtual Directory has to have the name that you are going to access via, as in: http://your_web_site/virtual_directory_name/your_script.pl As access to the Virtual Directory is resolved by IIS. > 4. Check that the Perl association in the Virtual Directory is set to: > C:\Perl\bin\perl.exe %s %s (the s in both should be lower case) The association should be .pl if you are using the .pl extension for your scripts, and the path to perl should reflect where Perl is installed on your box. Right click on the cgi-bin directory in the IIS MMC, click on the configuration button and scroll down to see if you have a .pl Extension. If not the click on the Add button and the Executable is C:\Perl\bin\Perl.exe and the Extension is .pl, you can also restrict the Verbs the script is allowed i.e. GET and POST or leave it at the default ALL. > 5. Check the Perl association in the Registry: > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Paramet > ers\Script Map is: > C:\Perl\bin\Perl.exe %s %s (the s in both should be lower case) Again the association is with the Name .pl and the path to perl of your box.
Hth. Shaun --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.314 / Virus Database: 175 - Release Date: 11/01/2002 -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
