Message-ID:	<001901be8509$249384c0$75003bd4@default>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
To:	<djgpp-workers AT delorie DOT com>
Subject:	Re: LBInstDJ
Date:	Mon, 12 Apr 1999 19:21:41 +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

>
>> I will do this too, but for other purpose - I will insert %PATH% in any
>> path setting lines where it is missing. This will help to ensure that
djdir
>> on the 1st path line will not be skipped and will repair broken
autoexec.bat
>> where first paths are not included by laters.
>
>This may add other directories to the user's path that weren't there
>before.  I wouldn't do this.

If he lets new path= settings to overwrite old ones, he doesn't know what
he is doing. He would not be able to install BC++, Delphi etc because they
all update 1st path line and do nothing more. He should REM out old
'path=' lines. I will warn him about it.

>
>I think the right way (also the hard way) is to read autoexec into
>memory, and find the *last* path statement (last in each section for
>menu-driven ones) and modify that.  If there is no path statement, add
>one at the beginning of the file.  Probably want to special case "win"
>and edit the last path before that.


If only "win" would be the only one special case... There is Norton
Commander,
Volkov Commander, Dos Navigator, even Dosshell and PCTools...

Laurynas Biveinis (yeah, updating autoexec.bat is not a piece of cake...)

- Raw text -