hethx gmail
Subject: Re: [Freedos-devel] About my driver, HIMEM/EMM386 and interrupts
To: freedos-devel@lists.sourceforge.net
Received: Tuesday, 27 October, 2009, 4:56 PM
>> However, I understood that HIMEM did something like establishing a
>> routine that was run whenever you tried
>> However, I understood that HIMEM did something like establishing a
>> routine that was run whenever you tried to use an offset greater than
>> 0h together with a "real-mode-made" segment. This routine would
>> "trap" the event and handle the switch to protected mode and back,
>> keep
>When you say a program would still need to set up flat real mode, I
> suppose you mean that they still need a jump to protected mode and back
> to initially setup the segment registers.
Yes.
> However, I understood that HIMEM did something like establishing a
> routine that was run whe
rom: Christian Masloch
Subject: Re: [Freedos-devel] About my driver, HIMEM/EMM386 and interrupts
To: freedos-devel@lists.sourceforge.net
Received: Monday, 26 October, 2009, 3:28 PM
> I'm building a driver (for DOS) that's supposed to have several
> functions hooked at an in
>I'm building a driver (for DOS) that's supposed to have several
> functions hooked at an interrupt. When applications call these
> functions, the driver should load and unload some tables or
> activate/deactivate them somehow. Because these tables are big, I don't
> want to keep them i
Guys,
I'm building a driver (for DOS) that's supposed to have several functions
hooked at an interrupt. When applications call these functions, the driver
should load and unload some tables or activate/deactivate them somehow. Because
these tables are big, I don't want to keep them in conven
