Need ideas about ntoskrnl

Peter Beutner p.beutner at
Tue Sep 6 04:29:29 CDT 2005

Vitaliy Margolen schrieb:
> We need ntoskrnl to run some subset of drivers on wine. Notably cd protection
> drivers. They are not a hardware drivers, but a means to access something that
> is not accessible from user space. So in a sense ntoskrnl is just a process to
> run those drivers in, and send/receive requests to/from those drivers.
> You need to keep in mind that this is a kernel level, so some things will not
> work, and some things have to work that normally do not in the user space. Also
> ntoskrnl for windows _is_ what wineserver for wine.
Why implement ntoskrnl as a seperate process plus inventing a new IPC 
protocol to talk to it? As you said: "ntoskrnl for windows _is_ what 
wineserver for wine.". So why not implement the needed ntoskrnl stuff 
into wineserver?


More information about the wine-devel mailing list