From:	kunst AT prl DOT philips DOT nl
Subject:	Re: LIBGRX <=> go32.exe compatibility
To:	ahelm AT email DOT tuwien DOT ac DOT at (Dipl.-Ing. Anton Helm)
Date:	Thu, 5 Aug 1993 15:20:50 +0100 (METDST)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu (DJGPP users list)

> 
> 
> >Hello Tony,
> >
> >First a remark about version numbers:
> >GCC 2.4.1 is bundled with DJGPP 1.10.
> >GCC 2.2.2 was bundled with DJGPP 1.09 and earlier versions.
> >
> >DJGPP 1.10 has a bug in the graphics routines.
> >You can recompile GO32 yourself with Turbo C 3.0 (and tasm)
> >and then the graphics bug will disappear.
> >If this is too much work for you, I have included the 'patched'
> >GO32 at the end of this message.
> >Remove everything above the dotted line below, and use 'uudecode'.
> >Then replace the file 'C:\DJGPP\BIN\GO32.EXE' by the uudecoded one.
> 
> Hi Pieter,
> Thanks for go32exe v10u. Unfortunatly it doesn't work properly. There
> is no problem with the graphic output. That part works well. But this 
> go32.exe disables the keybord when using LIBGRX graphic modes. (?????)
> That means, I get a nice dialog screen but cannot enter any command.
> So I have to reboot again. I tried some tricks for more then 2 hours, but
> could not fix it. The go32 of 1.0.9 version works correct.
> Sorry...
> 
> Regards, 
> 
> 
> 
> Tony
> 
> P.S.: I hope you have better weather in the Netherlands. We have about 
> 36o C by now and there are some thunderstorms approaching. 
> 
> 

Hello Tony,

Sorry the patched GO32.EXE didn't solve your problems.
I'll report your bug to the DJGPP mailing list. Perhaps one of
the other DJGPP users has had the same problem, and has found a
cure for it...

I would like to advise you to join this mailing list too, and
post your problems directly to the DJGPP forum instead of the
general 'gnu.gcc.help' internet list.

Some info on how to do this follows below (from README.1ST):

The chances your problem will be solved are much higher if you
send a *SMALL* sample source program to the DJGPP mailing list
which shows the buggy behaviour.

Kind regards, Pieter Kunst.

P.S. The weather is lousy here, too...

----------------------------------------------------------------------------
  From: README.1ST
----------------------------------------------------------------------------

    ====================  Reporting bugs  ====================

ALL changes to the source code should be submitted in "diff -c2" format.
If you just send replacement files, I'll reject them, since I don't know
which parts you've changed and my sources keep changing anyway.  Diffs
will also be rejected for use of bcc features in go32 sources (like //
comments), or more than one feature or bugfix per diff.  Please use the
same programming style as the existing style when making changes to my
sources.

Note that new features are not bugs.  If you would like to work on
adding features to djgpp, please send me e-mail at dj AT ctron DOT com
beforehand, in case it's being worked on already and to coordinate it's
integration.  If you want to request a new feature but not work on it,
send to the mailing list.

If the problem is in one of the FSF utilities, please don't expect me to
fix it.  Problems with FSF code should be reported to the FSF; I only
compile the code and distribute it.  My best suggestion is to post to
the appropriate newsgroup or mailing list, but if you can't find one,
ask gnu AT prep DOT ai DOT mit DOT edu.

If the problem is in anything else, and you have e-mail access, I strongly
recommend joining the djgpp mailing list.  To do so, send mail to
listserv AT sun DOT soe DOT clarkson DOT edu:

        $ mail listserv AT sun DOT soe DOT clarkson DOT edu
        Subject:
        help
        add <e-mail address> djgpp
        ^D

Any mail sent to djgpp AT sun DOT soe DOT clarkson DOT edu will get automatically
forwarded to all the subscribers on the list, and someone may have an
answer to your query.  Note that I (DJ) am of course a subscriber, so I
will get it also.

- Raw text -