Date:	Thu, 20 Jan 1994 09:45:01 +0100
From:	terra AT diku DOT dk
To:	turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: GO32 1.11.maint2 and QDPMI 1.04 access violations

>     I'm running DESQview/X 2.0beta, QEMM 7.04beta, and QDPMI 1.04.
> When I run any GO32 program in a DOS window with protection level set
> to 3, I get two successive protection violations with the program
> attempting to write to location B000:0000, which is outside of its
> memory space.  This does not occur when GO32 is run with no program.
> It occurs before the main program as far as I can tell when GO32 is
> used to execute a program.  In particular it occurs after the
> 8024+4096+4096 = 16216 message , but before the prompt indicating the
> start of execution of the program, when the ed32-dpmi external
> debugger is used.
>     Since QDPMI itself gives similar violations (at B000:00B5 and
> B000:0054) when invoked from the command line (to turn DPMI off), I
> suppose that this has to do with the mechanics of using DPMI.  I would
> like confirmation of this guess from someone who knows why GO32 tries
> to write to B000:0000.

B000:0000 is the location of the screen memory (mono screen), so it
makes sense for the debugger to access that memory, because it wants
to use it for the status line.

Morten Welinder
terra AT diku DOT dk

- Raw text -