Date: Sun, 23 Feb 1997 13:16:05 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: nikki <nikki AT gameboutique DOT co>
cc: djgpp AT delorie DOT com
Subject: Re: real mode calls pmode
In-Reply-To: <5emufu$e7u@flex.uunet.pipex.com>
Message-ID: <Pine.SUN.3.91.970223131544.1774D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 22 Feb 1997, nikki wrote:

> currently, i'm locking all the memory in the same way i would have done for
> interrupts, then i pass the entry point to my function as
> SEG=(((unsigned int)wibble)>>4) & 0xffff;
> OFF=wib & 0xf
> 
> but i get sigsegv problems everywhere :( it's not actually an
> interrupt that's calling me so i can't use the same routines i used
> to do those with can i? 
> i can't seem to find anything in the faq that helps

The FAQ explains in section 18.8 how to set up a real-mode callback,
which is what you need.  If I understand what you need to do
correctly, you should call the library function
`_go32_dpmi_allocate_real_mode_callback_retf', then pass the `segment'
and `offset' fields it returns to your 16-bit real-mode driver.