From:	sandmann AT clio DOT rice DOT edu (Charles W. Sandmann)
Subject:	Graphics problems
To:	djgpp AT sun DOT soe DOT clarkson DOT edu (djgpp)
Date:	Mon, 14 Jun 1993 16:17:14 -0600 (CDT)

> Date: Mon, 14 Jun 1993 16:02 EST
> From: "Wonkoo Kim, EE, U. of Pittsburgh" <WKIM AT vms DOT cis DOT pitt DOT edu>
> Subject: Use go32 1.10a to resolve graphics problem.
> To: djgpp AT sun DOT soe DOT clarkson DOT EDU
> 
> I saw too many messages reporting graphics problem on this list, but most
> graphics problem is due to not using go32 1.10a. Please use go32 1.10a which is
> bug-fixed by Charles Sandmann.
> Get djgpp/pub/csdpmit1.zip from omnigate, which includes go32 1.10a executable,
> then most graphics problems will be gone. (So far I don't have any problem.)
> 
> I guess it is better to have a better meaningful file name at omnigate for go32 
> 1.10a.  People might not know if the fixed version 1.10a is in csdpmit1.zip.
> Dear Charles Sandmann, could you create another file so that people easily 
> identify go32 1.10a file?  This could reduce user's time waste.

1.10a isn't a fix all.  As Jih-shin Ho pointed out, the new graphics.c also
destroys ESI, which can cause bugs, too.  There probably needs to be a 1.10b
which removes the VESA code until the new GRX stuff is finished.  If you have
your own TCC or BCC, put the graphics.c from 1.09 on top of the 1.10
distribution and build it.  Since graphics and DPMI are mutually exclusive
right now, use 1.09 GO32 for graphics and 1.10 only if you need DPMI or
specific 1.09 bug fixes.

Since the second most frequent bitch is DPMI memory problems, I still 
recommend getting the .ZIP which will gives a bit more information there also.

Before we get wide distribution on a potentially buggy 1.10a, I would like to
get a 1.11 out based on 1.10 bug fixes + new LIBGRX support.  If everyone 
insists on a short term fix, then it should be a 1.10b...

- Raw text -