Unfortunately, CMD.EXE does use the shebang line in your perl script. The Win32 mechanism for knowing which executable to use to process a given file is quite different. Being ASSOC and FTYPE; On my system these are set as follows:

C:\test>assoc .pl
.pl=perl_script

C:\test>ftype perl_script
perl_script=e:\perl\bin\perl.exe -w %1 %*
[download]

Use HELP ASSOC|FTYPE for fulll definition of these commmands.

You will notice that I have modifes the ftype line and added the -w before any passed args. You could modify this on your system to have the -naF switches, but this would then be used for all Perl scripts run on that system which isn't very useful.

The second and probably best alternative is to use the ActiveSystems (assuming your using AS) supplied pl2bat command on your script, and the edit the top of it to have the switches you want.

Example: (additions in bold):

@rem = '--*-Perl-*--
@echo off
if "%OS%" == "Windows_NT" goto WinNT
[download]

goto endofperl
:WinNT
[download]

if NOT "%COMSPEC%" == "%SystemRoot%\system32\cmd.exe" goto endofperl
if %errorlevel% == 9009 echo You do not have Perl in your PATH.
if errorlevel 1 goto script_failed_so_exit_with_non_zero_val 2>nul
goto endofperl
@rem ';
#!perl
#line 15
[download]

For further information for ActiveState installations read the AS docs at: A/S docs

(The above link assumes AS perl istalled in the default directories on your C: drive. Adjust as necessary on the addressline of your browser.

Edited bits per authors req. - dvergin 2002-07-29