Date:	Tue, 20 Jul 93 09:31:03 EDT
From:	DJ Delorie <dj AT ctron DOT com>
To:	vincent AT physique DOT ens DOT fr
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re:

> 	* there is a pb when using GRX with the event queue and trying to read
> or write from a drive t(hat is not ready : you get the error message Retry,
> Abort or Comit sucide and there is no way to answer since the keyboard is
> trappep ? is there a way to redirect the stupid dos message or to restore
> normal keyboard while performing dos function ?

That sounds like a Bad Thing.

> 	* I am planning to buy a new video acquisition board, some have the
> video memory mapped in 1 Mb mapped in the first 16Mb of the PC. Is there a way
> to acces in reading and writing this chunk of memory with GO32 ? How should I
> do that ? 

Linear memory can be accessed through 0xe0000000+addr in VCPI mode.
You should use dosmemget/dosmemput for compatibility with DPMI, but I
can't say for sure if those calls can access above 1M yet.  If not, I
can fix them to do so.

> 	* since the "fatal disk full" is going to be solved, is it possible to
> do something for "segmentation violation" and "numerical erros". I anderstand
> that those errors are serious but if there was an optinal way to avoid exiting
> that could be nice.  I am proposing that if an option is set when such an error
> occurs, then GO32 restart the 32 bits application which can easy check that it
> is lauch for the second times and open an error windows telling what is going
> wrong.

Hopefully, I'll get enough of signals working to implement SIGSEGV and
SIGFPE.  The disk full message will be solved by having malloc()
return NULL.

- Raw text -