Date: Sun, 13 Oct 1996 14:41:32 -0400
Message-Id: <199610131841.OAA00713@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: grendel AT ananke DOT amu DOT edu DOT pl
CC: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.NEB.3.95.961013203411.5686E-100000@ananke.amu.edu.pl>
	(message from Mark Habersack on Sun, 13 Oct 1996 20:38:56 +0200 (MET
	DST))
Subject: Re: Install thingy


I believe this is the same solution that djverify chose.  Feel free to
use a custom stub with lengthy descriptive error messages and extra
machine checks.

> Well... ok, so maybe I'll do it this way: I'll write the main install
> executable in DJGPP and add a small 'loader' utility that would run on every
> machine (it might be done in djasm).  I know that there's a stub loader for
> DJGPP programs, but it will report only that, say, it cannot find DPMI.  The
> RM loader would check for everything that's needed to start up the install:
> mainly processor type and free memory.  Such a solution would provide an
> elegant way to tell users who have incompatible machines what's wrong with
> their computers.  Loader would not be limited to few bytes for messages and
> would present users more explanative error messages.