From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<9609131418.AA13253@clio.rice.edu>
Subject:	Re: DJGPP Installation Diagnostic Program
To:	grendel AT ananke DOT amu DOT edu DOT pl
Date:	Fri, 13 Sep 1996 09:18:19 -0600 (CDT)
Cc:	fighteer AT cs DOT com, djgpp-workers AT delorie DOT com
In-Reply-To:	<Pine.NEB.3.95.960913114923.7351B-100000@ananke.amu.edu.pl> from "Mark Habersack" at Sep 13, 96 12:09:19 pm

No assumptions on video - needs to work on a monochrome system.
Needs to be either all 16-bit non-DJGPP code, or needs to be multiple
  images, so that really badly configured boxes can be identified.
PMODE binding will make the single image more portable, but PMODE is
  less stable and capable in some environments (low memory and/or 
  raw memory).  So if someone has memory misconfigured, a PMODE image
  won't run at all, while a CWSDPMI image can with as little as 100K
  total (ie DOS memory only) available.  So if you bind with PMODE, 
  you MUST have the 16-bit memory diagnostic program.
  
> 1.> - DJGPP files present
> 4.> - DJGPP files installed in the correct directory structure
> 3.> - Environment variables set
> 2.> - DJGPP version
> 6.> - Available memory

If 6) isn't set properly, 1,4,3,2 will need to be done with 16-bit image.

I don't have time to do any development, but I do have boxes of example
code sitting around (written in TC) for diagnosing memory.

- Raw text -