Date: Sat, 2 Dec 2000 21:33:37 -0700 From: Bill Currie To: djgpp AT delorie DOT com Subject: Re: Real Mode Callbacks: The Return Message-ID: <20001202213337.E8387@taniwha.org> Mail-Followup-To: djgpp AT delorie DOT com References: <3a293995$0$30011$6d6c75b AT news DOT execpc DOT com> <20001202190931 DOT B8387 AT taniwha DOT org> <3a29c279$0$29999$6d6c75b AT news DOT execpc DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3a29c279$0$29999$6d6c75b@news.execpc.com>; from sauls@nospam.subdimension.com on Sat, Dec 02, 2000 at 12:19:42PM -0600 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, Dec 02, 2000 at 12:19:42PM -0600, sauls wrote: > > Did you remember to lock all code and data touched by the callback? This > is a > > very important step. > > Errr... no. Would you mind explaining how I go about doing that? heh, it's been three years :/ _go32_dpmi_lock_code and _go32_dpmi_lock_data They're in the (lib)c info (see, been so long I can't remember the name of the info files:) There's example code in mouse.c within drivers.zip within http://taniwha.org/ed.tar Bill -- Leave others their otherness. -- Aratak