From:	Hannes Birnbacher <Hannes DOT Birnbacher AT T-online DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP Setup Utility in the making.
Date:	Mon, 07 Feb 2000 08:16:55 +0100
Organization:	T-Online
Lines:	32
Message-ID:	<87lre0$9ub$1@news05.btx.dtag.de>
References:	<87jegs02e44 AT enews2 DOT newsguy DOT com> <87kpuu$hu9$2 AT news01 DOT btx DOT dtag DOT de> <389DEF38 DOT F9D7606 AT tudor21 DOT net>
Mime-Version:	1.0
X-Trace:	news05.btx.dtag.de 949907712 10187 340097353547-0001 000207 07:15:12
X-Complaints-To:	abuse AT t-online DOT de
X-Sender:	340097353547-0001 AT t-dialin DOT net
X-Newsreader:	Forte Agent 1.7/32.534
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Am Sun, 06 Feb 2000 22:01:28 +0000 schrieb Richard Dawe
<rich AT tudor21 DOT net> :


>> I did not understand the need for reboot in the first place .Why
>> not run autoexec.bat after the addition of the necessary path and
>> environment variable. It worked perfectly with my system.
>
>Surely that depends entirely on what autoexec.bat does! What if you have a
>line to run a program that you only want to run at start-up? 

Yep, you are correct. I do have the habit to just try it. In
Linux this attitude is lethal, in MS-DOS it makes life easier;-)

>call c:\djgpp\djgpp.bat

>and then in djgpp.bat:

>SET PATH=%PATH%;c:\djgpp
>SET DJGPP=c:\djgpp\djgpp.env

>change paths as appropriate.

Why not modify autoexec.bat and additionally set the new path and
the DJGPP environment variable during the installation procedure.
Then the user (or even the installation script) can test if he
entered the correct path without re-booting, and the installation
procedure may give him a second chance,-).

-- 
Borland Turbo-C legal + kostenlos (1MB Download):
http://www.c-for-dummies.com/compilers/

- Raw text -