Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: "Laurynas Biveinis" , "DJGPP Workers" Date: Mon, 12 Apr 1999 15:11:45 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: LBInstDJ In-reply-to: <001201be8507$aa8bb360$75003bd4@default> X-mailer: Pegasus Mail for Windows (v2.54) Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk "Laurynas Biveinis" wrote: > >> I will do this too, but for other purpose - I will insert %PATH% in any > >> path setting lines where it is missing. > > > >Why?! it will change the path it could even break the system, why if the > user > >have a path that overwrites other you want to break it? > > It's a really bad thing to have such autoexec.bat where next path=... > overwrites previous. My installer will not create a new problem, it will reveal an old > one. That's silly, your attitude is really bad, "break it worst" instead of fixing. Why if what I say is really simple? > There is a lot of installation utilities (especially Borland's) which just > update first autoexec.bat line and that's all. If user user doesn't want old path, > he has to REM it. And he will be told so in LBInstDJ's warning. If it doesn't > matter for him - well, it's up to him. I'd like to hear your opinion. So as the rest does it wrong you'll do it in the same way. > OK, now about multiconfiguration... > > >And your solution doesn't work in multiconfiguration cases, while the thing > >I'm propposing looks like will work at least in most of these cases. See > this > >example: > > > (...) > > 1) If user knows how to setup multiconfigurations, he will be able to > install DJGPP by himself. Then remove the installer from v2 directory because even people that really knows how to install djgpp will blindly use install. Why? because they don't know how easy is to install djgpp and the first thing people does is running install. If no install is provided people reads the readme because is looking for the installer. > 2) There are a lot of issues about autoexec.bat and I even didn't document > well registry issues yet (Altough code is complete). So, at first, I will target > one-configuration autoexec.bat, for which my way works. > 3) For multi-confs my idea is: > * Read from config.sys all configuration names and their descriptions > * List all names and descriptions and ask user, which to update, with > possible case to update all users' settings (adding my stuff before > goto %config%) > * Use the same rule as for updating whole autoexec.bat, just stay in > the bounds of one conf. > > >That's why an installer *must* be complemented by djverify. > > It *will* be, but later. Now I will mention it in my doc and recommend to > use it after installation. But there is a lot of useful code for my prg. > > > BTW, about user's interface: how about porting it to turbo vision? Is possible but (and I'm the maintainer of this port) I think is too huge for an installer. Of course is a posible to use Turbo Vision and using EasyDiag (one of my libraries) the task of doing the dialogs becomes easy. But before it the installing mechanism should be very good and working OK, because doing TVision interface is harder than doing simple console interface. And 2 versions is the best in case one fails to run. For this your methodes you'll be as a library, then the 2 versions only differ in the user interface and shares the installing stuff. SET ------------------------------------ 0 -------------------------------- Visit my home page: http://welcome.to/SetSoft or http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(5411) 4759 0013