I've run the install.bat file as follows:
"C:\CalendarScript\install.bat" www.compasschurch.info USERNAME PASSWORD wwwroot/cgi-bin/calendar
Everything looks like it installs correctly. I've checked the directory via FTP and I see the following files in the folder:
[calendarscript]
calendar.pl
calendar_admin.pl
debug.pl
history.txt
readme.txt
And the [calendarscript] folder has a series of subdirectories -- cache, calendar, lib, plugins, etc. -- each with their own files.
So far, so good...
But when I try to load the calendar.pl file in my browser for the first time (http://www.compasschurch.info/cgi-bin/calendar/calendar.pl), I receive a page listing the following information:
------------------------------
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers. The headers it did return are:
Can't locate asp.inc in @INC (@INC contains: D:\webppliance\conf\domains\compass\Inetpub\wwwroot\cgi-bin\calendar\/calendarscript/lib C:/Perl/lib C:/Perl/site/lib .) at D:\webppliance\conf\domains\compass\Inetpub\wwwroot\cgi-bin\calendar\calendar.pl line 29.
BEGIN failed--compilation aborted at D:\webppliance\conf\domains\compass\Inetpub\wwwroot\cgi-bin\calendar\calendar.pl line 41.
------------------------------
I'm really not sure how to proceed at this point. Any help?
Here is other pertinent information, in case this helps you know how to help me from here:
I'm running Windows XP and Internet Explorer, and have checked the directories manually using SmartFTP.
I've successfully installed other scripts to this site, but I admit that I'm a real beginner when it comes to all this stuff. Be gentle... *grin*
Our host is Applied Innovations (www.appliedi.net). Some information they've provided:
* "Your entire virtual server is scriptable and is in essence a cgi-bin folder. If you wish to create a specific folder for your scripts feel free to create a folder and copy your cgi-bin applications into it. You can name this folder anything you like and some common choices are: cgi-bin, cgi, scripts, and so forth."
* "Applied Innovations does support CGI scripts and has already linked PERL to the .cgi and .pl extensions. If you wish to run a PERL script simply end the name of the file with a .cgi or .pl extension and call it."
* "The entire virtual server is enabled for scripting so you can actually name the folder anything you like. Also, if you plan to use perl scripts you'll want to end them with a .cgi or .pl. PHP scripts are ended with a .php and ASP scripts with a .asp."
* "We currently support ActiveState Perl 5.6.X"
* "Under Windows NT/2000 there is no physical Perl path, simply end the file with a .pl or .cgi and the Perl interpreter will be initiated."
[This message has been edited by Scott Heine (edited April 13, 2004).]