Message-ID:	<004801be8426$764f8860$a4003bd4@default>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
To:	"DJGPP Workers" <djgpp-workers AT delorie DOT com>
Cc:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Subject:	Re: LBInstDJ
Date:	Sun, 11 Apr 1999 16:17:51 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3612.1700
Reply-To:	djgpp-workers AT delorie DOT com

(BTW, I posted EILSEQ patches to wrong mailing list by accident. Sorry.)

>Let me serve as a Devil's advocate here, and alert you to some
>potential problems.

It's a Good Thing to be Devil's advocate if problems are revealed earlier
than very angry users respond about them.


>> 1) insert @SET DJGPP=... as first line in autoexec.bat
>
>Problem no.1: how do you know which autoexec.bat to edit?  (Some
>systems, like Windows 98 and NT, has them in special places under
>special names.)

I have access only to Win95. Can anyone who has access to 98/NT, help me ?

>Problem no.2: you might get "Out of environment space" if you simply
>add a variable; you need to find a way to detect such problems and
>deal with them.

OK, I can update config.sys. But I will have more think about it.

>> 2) look for first line with "path=" but not "rem"
>
>Problem no.3: don't forget the colon `:' that can also mark a comment
>line (rarely used, but you can be sure somebody out there does it).

Oops, I didn't know about it. But it is easy to fix.

>
>Problem no.4: what about those autoexec.bat files which define
>multiple configurations?  In these cases there's more than a single
>PATH= line that needs to be changed.  How do you know which ones?  And
>some of the configurations might not be appropriate for running DJGPP;
>only the user will know which ones.

It's a hard issue. Hey, but if user knows how to use multiple
configurations,
he will be able to setup DJGPP by himself. I'll put it in my TODO, but in
low priority.

>Problem no.5: some systems set PATH like this:
>
> PATH c:\foo\bar;d:\baz
>
>i.e., no leading SET and no equals sign.

No leading SET isn't problem for me now. No '=' case should
not be hard to fix.

>Problem no.7: some malformed autoexec.bat files can override PATH=
>settings in a later line (I saw too many of these!), so the first line
>is probably not a fool-proof solution.

Completely fool-proof solution isn't any line, because e.g. last line may be
after win, nc, dosshell... How about updating first line, as is now, and
then
inserting "%PATH%;" in any next path lines if there isn't any? This sounds
better for me.

>
>> And I create new autoexec.bat if there isn't one :)
>> (Who will need this feature?
>
>Lots of people, IMHO.  The default in Windows 9X is not to have
>autoexec.bat at all.
>

Thanks for your valuable response,

Laurynas Biveinis

- Raw text -