V86
Pupsi
allocated memory page of 4 Ko, to make 1 Mo.
There is you API kernel runtime for developper a machine virtual 8086?
if not is necessary you it to act on the memory of the descriptors of task
(LSS) ?
Tim Robinson
> In kernel mode: For create a session V86, 256 should first of all be
> allocated memory page of 4 Ko, to make 1 Mo.
Yes, but the bottom 64KB is never accessible to Win32 apps. Unfortunately,
this bottom 64KB contains the interrupt vector table, which would be hard to
live without in V86 mode.
> There is you API kernel runtime for developper a machine virtual 8086?
Yes, but it's not documented. Look at the functions that NTVDM.EXE imports.
> if not is necessary you it to act on the memory of the descriptors of
> task (LSS) ?
Yes, in the sense that you'll need to worry about segmentation. But recall
that V86 mode uses real mode-style address formation, so the segment
registers contain segment addresses, not selectors, and any GDT and LDT
descriptors are ignored.
--
Tim Robinson (MVP, Windows SDK)
http://mobius.sourceforge.net/
Nicolas Bannerde
message de news:2kj3deF...@uni-berlin.de...
> Pupsi wrote:
> > In kernel mode: For create a session V86, 256 should first of all be
> > allocated memory page of 4 Ko, to make 1 Mo.
>
> Yes, but the bottom 64KB is never accessible to Win32 apps. Unfortunately,
> this bottom 64KB contains the interrupt vector table, which would be hard
to
> live without in V86 mode.
>
> > There is you API kernel runtime for developper a machine virtual 8086?
>
> Yes, but it's not documented. Look at the functions that NTVDM.EXE
imports.
Ah good VMWare however does not use NTVDM.EXE
Tim Robinson
>>> There is you API kernel runtime for developper a machine virtual
>>> 8086?
>>
>> Yes, but it's not documented. Look at the functions that NTVDM.EXE
>> imports.
>
> Ah good VMWare however does not use NTVDM.EXE
VMware doesn't use V86 mode, but emulates entirely in ring 3 protected mode.