If you've set up 4NT to replace your shell, you shouldn't see this. If you're seeing it, and you think you've set 4NT up as a replacement, then something's wrong and you need to check the registry.
If you're just running 4NT as an independent app, you can try JPSoft's tech support website. They have a bunch of registry hacks that make 4DOS/NT the default app for certain alternative batchfile types. You can modify perl2bat to create one of those types of files instead of .bat, so your script will run under 4NT by default. Don't forget--if 4NT isn't your default shell and your scripts CAN run under cmd.exe, they probably ought to do so, to avoid really-hard-to-debug behaviors. More generally, you should try asking this question on the jpsoft elist or of their tech support staff--plenty of perl hackers there.... --Chris -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ivano Di Domenico Sent: Tuesday, December 11, 2001 10: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 _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
