[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Perl Problems

At 16:20 02-12-97 -0500, you wrote:
>At 02:49 PM 12/2/97 CDT, Will Vervair wrote:
>>This worked GREAT! Thanks!!!!
>> ----------
>>From: pi3-users-request
>>To: 2524
>>Cc: pi3-users
>>Subject: Re: Perl Problems
>>Date: Tuesday, December 02, 1997 1:34PM
>>> Thanks John,
>>> I did not know this list was so new. Anyway here is the question.
>>> I am trying to get some perl scripts from Matt's Script Archive
>>> <http://worldwidemart.com/scripts/> to work. The script that I am working
>>> is the web message board. I had modified it to work on a win95 webserver
>>> (fnord) and it worked fine. I am getting this error when I try to test it.
>>> CGI: error DoExecCGIChild() failed. Error code is 2. Start of command
>>> is 'perl c:\cgi-bin\acboard.pl'
>>2 means 'file not found' at some point I'll use FormaMessage() to
>>get the text for windows errors. In this case it means the perl
>>interpreter was not found. You have three options to fix this:
>>        1) make sure the path to Perl.exe is in the PATH environment
>>        variable. A good way to test this is to invoke the bundled
>>        viewenv.exe program. If you bring up a dos box and type
>>        'perl c:\cgi-bin\acboard.pl' this emulates what the server does
>>        (note this is different from 'c:\cgi-bin\acboard.pl' which makes
>>        windows use the .pl to find the appropriate program).
>>        2) Open the file Conf\Config.pi3 and go down to the section
>>        ...
>>        <Object>
>>                Name StandardCGI
>>        ...
>>        Theres a bunch of options there to customize exactly how CGI's
>>        are started. Find the line
>>                CommandLineByExt .pl="perl %p%q"
>>        Remove this line, save the file, stop and start the server to cause
>>        Pi3 to start CGI's with .pl extensions like all others allowing
>>        windows to figure out how to exec file script using its 
>>        lots of web servers do this.
>>        3) Explicity point to your perl interpreter, same as above but
>>        change
>>                CommandLineByExt .pl="perl %p%q"
>>        to
>>                CommandLineByExt .pl="c:\\perl\\bin\\perl.exe %p%q"
>>        Where 'c:\perl\bin\perl.exe' is the full path to your perl 
>>Hope this helps,
>John, you are truly amazing.  From one simple error line, you can identify
>the problem, as well as various avenues of solution.

Can you give us a list of these error-codes and their possible solutions ???

BTW: Did any of you test some perl programs (win32) and is convinced that
it is working properly ??? (when it works, mail the url or the program to
me, ill add them to a list)


Maurits Bloos

[ maurits.bloos@visions.demon.nl ]
          [ ICQ: 3226444 ]
         To err is human......
    ...to really fool up things 
      requires a computer