boemmels at physik.uni-kl dot de wrote: > Pete Lomax writes: > > > I've only just installed perl. Running Configure.pl on a > > windows box, I got 'bad command or file name' because line > > 12 of config\init\hints.pl is: > > my $hints = "config/init/hints/" . lc($^O) . ".pl"; > > I had to change it to: > > my $hints = "perl config/init/hints/" . lc($^O) . ".pl"; > > [...] > > Normaly this "bad command or file name" come form failing > system calls.
Could it be something as simple as not having established an file association for *.pl files? If you compiled and installed perl yourself, there's a good chance it isn't there. The following instructions walk you through how to create it. Apologies in advance if I'm completely off-base... Execute explorer, select 'view', 'options' from the menu, 'file types' tab... and look for a registered file type for perl scripts. If there isn't one, select 'new type', and enter the following: Description of type: Perl Associated extension: .pl Content Type (MIME): application/perl Select the 'new' button to create a new action, and enter the following: Action: open Application used to perform action: [path to perl.exe] %1 "%*" -- Garrett Goebel IS Development Specialist ScriptPro Direct: 913.403.5261 5828 Reeds Road Main: 913.384.1008 Mission, KS 66202 Fax: 913.384.2180 www.scriptpro.com garrett at scriptpro dot com
