🚀 go-pugleaf

In <1992Dec23.190904.14515@proto.com> joe@proto.com (Joe Huffman) writes:

>rwallace@unix1.tcd.ie (russell wallace) writes:

>>Could someone mail me the fix for the problem with Zortech C++ v3.0,
>>compiling for 386 (extended memory model), when you try to access screen
>>memory (memory protection error)? 

>Can you give me an example?  It might be something you are doing wrong...
>We (FlashTek) supplied the extender to Zortech/Symantec and probably can 
>answer your questions as well as anybody...

Basically the method of accessing screen memory I'm using is with a far
pointer with segment = B800h and offset = row*160 + column*2, to give a
pointer to the character+attribute at (row,column). This works fine in
tiny, small, large etc. memory models, but does not work in extended
(option mx) memory model - as soon as I try to write a value into the
selected address, the program drops out to DOS with a 386 general
protection error. Presumably what's happening is that the 386 DOS
extender assumes that since I don't have permission to write to that
area of memory, a memory protection violation has occurred. I've heard
that a fix can be downloaded from Zortech's bulletin board, but I can't
access that.

--
"To summarize the summary of the summary: people are a problem"
Russell Wallace, Trinity College, Dublin
rwallace@unix1.tcd.ie