Shishir Saxena wrote: > I just installed perl and I don't know what settings I fiddled with,
I trust that YOU did not fiddle with any settings. Fiddling with nsettings is agood recipe for making a Perl installation fail--especially if you do not know which ones you changed. If you are working on Windows, you should let the installer do its work. > but now > on Windows Command Prompt I am unable to execute perl scripts with > somthing like, "perl test.pl" rather I have to do "perl.exe test.pl" > ....same for any application ... everything has to be suffixed with a .EXE > ... > Please advise ... http://support.microsoft.com/ This is really a Windows question, not a Perl issue. The ActiveState installer does its work just fine [albeit with an irritating tendency to try to re-install to any prior installation location]. You should let it do its job. Also, in a proper Win32 installation of Perl, you should not even have to call perl explicitly. I run scripts like: Greetings! E:\d_drive\perlStuff>testbush.pl and they run just fine, because the Perl executable is registered as the default application for the .pl extension. Joseph -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
