[uniqueuser]

Greetings,

Thanks to MS latest patch (it seems to have changed the way IIS handles URL's) I have had to change from IIS to Apache on a windows paltform. So I downloaded Apache for win and configured httpd.conf.

I now have Active Perl running under Apache (mod_cgi) on my Win XP box and also on an Apache *nix remote server.

...1 day down and so far so good.

But now I realize that every time I upload a perl file to my remote server I need to chage the path to perl (shebang) line at the top of every single file....yikes!

I tried adding this as the last line in httpd.conf:

ScriptInterpreterSource Registry

Which is meant to override the *nix shebang using the win registry reference for Perl executable...but it had no effect?

So my question is: how do I avoid changing the path to perl every time. How does everyone else handle this situtaion?

Any feedback and help on this would be appreciated as after an entire day of googling web and groups (2 days down now) I have not found an answer...or "suspiciously" even a question, so I am hoping I am doinmg something really dumb :-/

TIA.

[Chas]

So my question is: how do I avoid changing the path to perl every time. How does everyone else handle this situtaion?

I installed ActiveState Perl to \usr instead of the default \Perl. That lets me use #!/usr/bin/perl for a shebang instead of #!/Perl/bin/perl. If you installed AS Perl on a drive other than C: then this won't help you much. If you do come up with another solution please post back here. That would be good info to have.

~Charlie

[Chas]

Check this page from ActiveState: http://aspn.activestate.com/ASPN/doc...for_Win32_unde

I think if you associate the proper extensions with the Perl interpreter and add the correct handler to Apache you should be OK. I just don't know if have a shebang line in the script will override this.

~Charlie