A. - Did you make your script executable?
to make a file executable:
as root (or sudo)
# chmod +x your-file.pl
B. - Check in
make sure lines 41-46 are not commented out.
C. - Just a BTW, use an editor to look at test-cgi - its a shell script, printenv uses a shebang that points to perl, so neither is a really good test of mod_perl. The fact that they run only indicates that the server is set up for CGI correctly. My forum software doesn't use mod_perl, so I can't test that aspect, they run correctly with a shebang line. (at least right now)
Upon some reflection, I think LAMPP will fail standard mod_perl tests, as LAMPP is NOT a stack, but a self-contained bash script, and I don't think that mod_perl will be found in the %ENV server environment variables. You can definitely run your Perl scripts via a standard shebang line... (I have several LAMPP servers with Perl driven forums and blogs.)
Last update - you can easily check if mod_perl is running by forcing an error 404 (go to a page that deosn't exist)- and examining the Server Signature
Mon 09 Jul 2012 05:07:22 PM EDT
Apache/2.2.21 (Unix) DAV/2 mod_ssl/2.2.21 OpenSSL/1.0.0c PHP/5.3.8 mod_apreq2-20090110/2.7.1 mod_perl/2.0.5 Perl/v5.10.1
The best page I could find to explain things:http://perl.apache.org/docs/2.0/user/in ... _fast.html