Date: Sun, 13 Oct 1996 12:40:18 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Cc: "John M. Aldrich" <fighteer AT cs DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: Install thingy
In-Reply-To: <Pine.NEB.3.95.961011141720.29964B-100000@ananke.amu.edu.pl>
Message-Id: <Pine.SUN.3.91.961013123627.15719F-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 11 Oct 1996, Mark Habersack wrote:

> I decided, following advices, to make the installed a real mode program. It
> assures it will run everytime on any system.  So the idea with stubify falls

I urge you to reconsider.  Hard as it might be, writing it in DJGPP 
ensures that any problem can always be fixed, since we have source to 
everything.  If it isn't written with free tools, you might have problems 
for which there is no solution and no work-around.

> I'm not sure, however, whether TC 2.0 will allow me to modify argv[0].  AFAIK,
> TC uses DOS calls to invoke external programs and this means that they are
> ALWAYS passed path\myname.exe as argv[0].  If this is true, install might use
> another approach to notify djverify it is run as its child.  I could hook INT
> 2Fh and install a callback known to djverify.  The latter would check if
> installer is in memory and behave according to the result.

I rest my case.  Is the above trouble less serious then potential 
problems with DJGPP code?  I don't think so.