Linked by Thom Holwerda on Mon 18th Jan 2010 16:06 UTC, submitted by fireball
ReactOS The ReactOS project aims to be an open source Windows NT-compatible operating system which can run Windows applications and utilise Windows drivers. Obviously, this is quite a daunting task, and as such, progress has been relatively slow. As a result, project coordinator and kernel developer Aleksey Bragin has proposed a rather drastic solution.
Thread beginning with comment 404641
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Wine basically converts Win32 into Linux system calls, but I didn't see Linux in the architectural diagram. I am guessing though there has to be a Linux kernel underneath it all.

So what this amounts to is that emulating the internals of the modern Win32 OS is a lost cause. Whereas emulating the Win 32 API on top of another OS (Linux) is a proven approach that supports something like 13k windows apps.

I think you're getting a little confused there.

ReactOS is a complete OS from the ground up. The problem Aleksey Bragin mentioned was specifically with ReactOS's implementation of it's Win32 calls.

So what Aleksey Bragin is suggesting is by using WINEs Win32 code (baring in mind that WINE has a larger and more complete development) in place of the existing ReactOS Win32 so you have WINEs app compatibility.

So it doesn't really matter what kernel is running as this is purely user space tools.
(case in point being the numerous non-Linux kernel systems that WINEs been ported to: from *BSD and Solaris ports to 'Crossover' for the Mac).

The only problem I can see is that you lose driver support. You can't just install your win32 drivers for your hardware in ReactOS and expect it to work.

AFAIK drivers wouldn't use Win32. Win32 isn't generally used that low-level. It's more a graphical toolkit with knobs on.
That said - it's been a while since I've used Win32 so I maybe forgetting some details.
However Aleksey Bragin seems to hint that drivers were a non-issue:

ARWINSS has many advantages, not in the least the fact that it would bring Wine's level of application support to ReactOS: 13495 applications from the Win database, as well as a theoretical number of applications Wine can't run due to hardware issues.

Reply Parent Score: 4

joshv Member since:

Ok, so this is a port of the Wine Win32 user land to run on top of the ReactOS kernel? Correct? If so, I have to admit I pretty much thought that's what ReactOS was already.

Reply Parent Score: 4

Bill Shooter of Bul Member since:

Yeah... Me too. My guess is that when they decided they weren't going to do this back in 99 or so, wine wasn't nearly as complete as it is now. So it wasn't obvious that they should focus on leveraging the wine source as heavily, instead of writing one more in tune with their development goals.

Reply Parent Score: 2

robojerk Member since:

Same here...

Reply Parent Score: 2

Laurence Member since:

Ok, so this is a port of the Wine Win32 user land to run on top of the ReactOS kernel? Correct? If so, I have to admit I pretty much thought that's what ReactOS was already.

WINE and ReactOS shared code and developers, but ReactOS was never really a port of WINE.

There's much much more to Windows than Win32 and NT kernel - just like there is more to ReactOS than it's Win32 calls and it's kernel.

However, up until today, I must admit I thought ReactOS had heavier influences from WINE too.

Edited 2010-01-18 22:27 UTC

Reply Parent Score: 2