Date: Fri, 13 Sep 1996 21:51:51 -0400
From: dj (DJ Delorie)
Message-Id: <199609140151.VAA27677@delorie.com>
To: fighteer AT cs DOT com
CC: djgpp-workers AT delorie DOT com
In-reply-to: <323A1C3F.3728@cs.com> (fighteer@cs.com)
Subject: Re: "djverify" - DJGPP Installation Diagnostic Program


>    Question:  Am I safe in assuming that every computer the program
>    runs on will be capable of displaying the extended ASCII character
>    set (127-255)?  If not, is there any way to test for this?

I think it's safe to assume a minimum 80x25 color or bw text screen
(adapt to larger screens, of course) and that the BIOS functions and
direct memory access (0xb8000 or 0xb0000) are available.  Just don't
try to *change* the screen setting.

> However, how do I convince symify to use the modified stub that I
> have made instead of the standard one?  I don't want to get rid of
> the standard stub, for obvious reasons.  Ideally, the new stub would
> be in the same directory as the program itself.

You build a new version of symify.

> Lastly, is this stub likely to exist solely for the purposes of my
> program, or is there a possibility of it being made the standard
> for the next version?  Mostly, I need to know how careful I have
> to be in limiting the extent of my changes.

I'm thinking of expanding the "No DPMI" message to "No DPMI - get
csdpmi*.zip" (if it fits) but I have no other changes planned.