--- Mike Hearn <[EMAIL PROTECTED]> wrote:
> Maybe. I'm not really convinced, they do totally different things. In
> ReactOS it has to be a kernel, in Wine it just has to be a usermode DLL
> that exports enough to please SafeDisc. I'd be amazed if much code sharing
> is possible (or even necessary,
Maybe. I'm not really convinced, they do totally different things. In
ReactOS it has to be a kernel, in Wine it just has to be a usermode DLL
that exports enough to please SafeDisc. I'd be amazed if much code sharing
is possible (or even necessary, how much code does SafeDisc need?)
I've just sent
Because if we design things properly from the start we can share more
code Wine <-> ReactOS. I am planning on making it a discussion topic
at WineConf.
Well, the reactos code just has hardcoded values for PsGetVersion.
I'll send another patch that adds PsGetVersion as a stub in case AJ agrees wit
On Wed, 22 Dec 2004 14:12:22 -0800, Steven Edwards wrote:
> Because if we design things properly from the start we can share more
> code Wine <-> ReactOS. I am planning on making it a discussion topic
> at WineConf.
Maybe. I'm not really convinced, they do totally different things. In
ReactOS it
--- Mike Hearn <[EMAIL PROTECTED]> wrote:
> Why not? This isn't ReactOS, ntoskrnl is just another DLL from the
> SafeDisc perspective. Its implementation details shouldn't matter.
Because if we design things properly from the start we can share more
code Wine <-> ReactOS. I am planning on making
On Wed, 22 Dec 2004 13:29:35 -0800, Steven Edwards wrote:
> kernel32 can't be a dependancy on ntoskrnl. We are going to need to redesign
> Wine if we are going
> to have a ntoskrnl implementation.
Why not? This isn't ReactOS, ntoskrnl is just another DLL from the
SafeDisc perspective. Its impleme
Hi,
--- Ivan Leo Puoti <[EMAIL PROTECTED]> wrote:
> Add ntoskrnl, only a few stub functions for now, so we have something to
> work on.
> All the functions needed by safedisc are in the spec, we can't implement
> them all
> as stubs ATM because for two of them we need defines from the ddk,
> I'l
