Hi Will,
There was no semi-colon at the end of the line - but I don't think one is
required there. However, I did notice that there was one white space
occurring before 'PATH'. Could that be it ? Are you telling me that the
'PATH' specification should be sufficient and that I should not need the
'SET PATH' setting ?
DOS 3.3 ? I've got 4.something. ( I believe they are both fully documented
in the 'Dead Sea Scrolls'. )
Cheers,
Rob
Visit our website at http://www.kalinabears.com.au
- Original Message -
From: Will W [EMAIL PROTECTED]
To: Sisyphus [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2001 12:59 AM
Subject: Re: Path in autoexec.bat
This seems more OSish than Perlish, but there is certainly a tie to
perl...
Back in a younger day, when DOS v3.3 ruled, we all found that appending
to PATH was dicey since whether it worked depended on whether the last
guy to do so put a terminating ";" in place. Otherwise, silent failures.
It was easier to prepend with an assured ";" at the tail of our own
addition than to use the batch file tools to determine whether a
trailing ";" was present (nobody wanted to waste precious bytes with
unnecessary ";"s-- we only had 127 chars for the entire path statement,
which was tight on those early networks).
Did you check whether the PATH causing the failure has semicolons in all
the right places? You may yet have other problems in your configuration.
- Original Message -
From: Sisyphus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 13, 2001 4:36 AM
Subject: Path in autoexec.bat
Hi,
When I first installed perl on my PC I was unable to run perl scripts
by
entering at the prompt:
perl somefile.pl
Instead I had to specify the path to the perl interpreter. So, to run
somefile.pl I would enter:
\perl\bin\perl somefile.pl
This was the case, even though the 'PATH' variable contained the
setting
'C:\PERL\BIN;'
It wasn't until I added 'SET PATH=C:\PERL\BIN;%PATH%' to the
autoexec.bat
file that I was able to run scripts by entering:
perl somefile.pl
Can someone explain this to me - why was the 'PATH' setting, by
itself,
unable to provide the functionality I was after ? What functionality
does it
provide ?
And does that 'PATH' setting (in regards to perl) currently serve any
useful
purpose now that 'SET PATH' is specified ?
Things are now working fine - but these questions still bug me.
I should add that the scripts I was running were not being run from
the root
directory (ie. I'd first 'cd' to the directory in which the scripts
were
saved, and run them from that directory). I mention that in case it's
relevant.
Cheers,
Rob
Visit our website at http://www.kalinabears.com.au
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
___
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
