From: Kbwms AT aol DOT com
Message-ID: <499ba32b.2444ea97@aol.com>
Date: Tue, 13 Apr 1999 14:44:39 EDT
Subject: Re: LBInstDJ
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
CC: salvador AT inti DOT gov DOT ar, djgpp-workers AT delorie DOT com, lauras AT softhome DOT net
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-13-99 at 04:05:23 EST you wrote:
>
>
>   - for each configuration name, go to the end of the autoexec.bat and
>     add something like this:
>
>       if "%config%"=="CONFIG-NAME" PATH C:\DJGPP\BIN;%PATH%
>       if "%config%"=="CONFIG-NAME" set DJGPP=C:\DJGPP\DJGPP.ENV
>

I assume you mean that user's %djgpp% definition should be used?
For example, in my autoexec.bat I have:

     set djdir=c:\djgpp.v2
     set djgpp=%djdir%\djgpp.env

> You will still need to find out if there are any lines that invoke
> other batch files not through CALL (in which case the end of
> autoexec.bat is never reached), but you need to deal with this
> anyway.
>
> The above still has some cases not covered, but those would be rare
> (in my experience).

If you know of these rare cases, please reveal them.

> > BTW, about user's interface: how about porting it to turbo vision?
>
> I think the installer should be as non-demanding on system hardware
> and software as it can.  A simple ASCII interface would be the best
> approach for the first approximation.  Once you have the basics
> working, you can add bells and whistles.  There's nothing as
> frustrating as a runaway installer with a cute display...

DOS, DOS, DOS.  Remember?  The simple ASCII interface suggested is
preferred.


K.B. Williams