I presume what you mean is that the functions such as system, exec, and backticks invoke CMD.EXE instead of 4NT.EXE.
The documentation for the system function (see perldoc -f system) implies that the shell invoked by system is hardcoded.
Here's a little script that demonstrates that CMD.EXE is hardcoded, and a workaround to the problem as well:
print $ENV{COMSPEC}, "\n";
system qq(if "%\@eval[1+2]%" == "3" echo Test 1: 4NT is loaded);
system qq($ENV{COMSPEC} /c if "%\@eval[1+2]%" == "3" echo Test 2: 4NT is loaded);
Gary
-----Original Message-----
From: Ivano Di Domenico [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 8:39 AM
To: [EMAIL PROTECTED]
Subject: alternative to cmd.exe
In our environment, we are using 4NT to get around some DOS issues that W2K
has problems with, or we haven't dealt with. What I found is that when a
PERL job is run in a 4NT environment, it runs using the CMD.EXE instead of
4NT.EXE. Is there a way in PERL to tell it to use a different command line
interpreter other than CMD.EXE ?
thx
Ivano
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
