I can only suggect trashing MS Personal Web Server in place of Apache for
a Windoze platform then, follow the inline documentation within the httpd.conf file 
# 
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the sym
+bols
# pound (#) and exclamation (!) followed by the path of the program th
+at 
# can execute this specific script.  For a perl script, with perl.exe 
+in
# the C:\Program Files\Perl directory, the shebang line should be:

   #!c:/program files/perl/perl
# Note you _must_not_ indent the actual shebang line, and it must be t
+he
# first line of the file.  Of course, CGI processing must be enabled b
+y 
# the appropriate ScriptAlias or Options ExecCGI directives for the fi
+les 
# or directory in question.
#
# However, Apache on Windows allows either the Unix behavior above, or
+ can
# use the Registry to match files by extention.  The command to execut
+e 
# a file of this type is retrieved from the registry by the same metho
+d as 
# the Windows Explorer would use to handle double-clicking on a file.
# These script actions can be configured from the Windows Explorer Vie
+w menu, 
# 'Folder Options', and reviewing the 'File Types' tab.  Clicking the 
+Edit
# button allows you to modify the Actions, of which Apache 1.3 attempt
+s to
# perform the 'Open' Action, and failing that it will try the shebang 
+line.
# This behavior is subject to change in Apache release 2.0.
#
# Each mechanism has it's own specific security weaknesses, from the m
+eans
# to run a program you didn't intend the website owner to invoke, and 
+the
# best method is a matter of great debate.
#
# To enable the this Windows specific behavior (and therefore -disable
+- the
# equivilant Unix behavior), uncomment the following directive:
#
#ScriptInterpreterSource registry
#

[download]
Hope this helps

In reply to Re: what instead of #!/usr/bin/perl by ColtsFoot
in thread what instead of #!/usr/bin/perl by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.