delorie.com/archives/browse.cgi | search |
From: | "Mark Usher" <marku AT magnet DOT at> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | a complication with real mode function callback. |
Date: | Thu, 15 Apr 1999 22:14:46 +0200 |
Organization: | magnet Gesellschaft für digitale Kommunikation m.b.H |
Lines: | 22 |
Message-ID: | <7f5hap$k75$1@orudios.magnet.at> |
NNTP-Posting-Host: | 195.3.75.210 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Newsreader: | Microsoft Outlook Express 5.00.2013.600 |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.00.2013.600 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
I'm wondering if anyone can help me clear this up. I have a driver that needs a to call a real mode function as an event handler. That is easy enough after reading the FAQ - many thanks to all concerned there. The definition I have for the event handler is this. On entry DS:DX points to the start of an event handler. The first 8 bytes are reserved and will be filled in by the driver. 0-3 Pointer to next handler code part (offset 8) 4-7 Pointer to previous handler (offset 0) 8+ Executable code The question is... How can I be sure of reserving exactly 8 bytes at the start of my event handler that I pass with go32_dpmi_allocate_real_mode_callback_retf ? Due to the stub, wrapper etc I thought I'd better post the question for some more informed suggestons. Mark marku AT magnet DOT at
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |