From: Kbwms AT aol DOT com
Message-ID: <6f47ea06.244765f9@aol.com>
Date: Thu, 15 Apr 1999 11:55:37 EDT
Subject: Re: LBInstDJ
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
CC: djgpp-workers AT delorie DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 38
Reply-To: djgpp-workers AT delorie DOT com

Dear Eli Zaretskii,

On 04-15-99 at 06:32:58 EST you wrote:
>
>
> These cases can be handled.  First, there are some known names of
> programs that are invoked from AUTOEXEC.BAT, like nc etc.  For the
> rest of them, where you don't know if that's a batch file or a
> program, you can either bypass them or ask the user whether to bypass
> them or invoke them.
>

Please explain:

    1) nc
    2) etc

>
> Another approach would be to build a COMMAND.COM simulator.  Shouldn't
> be too hard.

I wouldn't bet the farm on that last statement, if I were you.

> You still will need to detect and bypass all calls to
> batch files and external programs, though.
>

And heaven only knows what other dangers lurk out there.


K.B. Williams