So what current Windows version does REACTOS most closely resemble?
And is there any plans to develop a ReactOS Server, which would be very cool?
Thanks,
Ray
ReactOS Windows Equivalent?
Moderator: Moderator Team
Re: ReactOS Windows Equivalent?
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
Re: ReactOS Windows Equivalent?
So it looks like Windows 2000? What about future versions, like server? Is that in the cards?
Re: ReactOS Windows Equivalent?
It does not matter what it looks like. It is based upon server 2003.
Skillset: VMS,DOS,Windows Sysadmin from 1985, fault-tolerance, VaxCluster, Alpha,Sparc. DCL,QB,VBDOS- VB6,.NET, PHP,NODE.JS, Graphic Design, Project Manager, CMS, Quad Electronics. classic cars & m'bikes. Artist in water & oils. Historian.
Re: ReactOS Windows Equivalent?
The tl;dr version:
OS editions are nothing but marketing crap of MS. Aside some missing applications between both "server" and "client" editions, the difference between them is a single registry switch. That's all. It doesn't matter a thing to consumer if the OS is either "client" or "server" edition, both are equally capable of everything.
Note: NT 5.2 is a core shared between Windows 2003, Windows XP x64 and Windows XP Embedded. NT 5.1 is the older and slightly inferior 32-bit Windows XP SP3.
What ReactOS currently is - it's a re-implementation of NT 5.2-compatible core with NT 5.2-alike WinAPI equivalent, except for the small yet important detail - it has NT 6.0 WinAPI implemented as shim compatibility layer that redirects "modern" function calls into additional wrapper libraries that contain the NT 6.0-compatible code derived from Wine. In fact, almost the entire WinAPI stack is taken from Wine and the code syncs are done regularly.
OS editions are nothing but marketing crap of MS. Aside some missing applications between both "server" and "client" editions, the difference between them is a single registry switch. That's all. It doesn't matter a thing to consumer if the OS is either "client" or "server" edition, both are equally capable of everything.
Note: NT 5.2 is a core shared between Windows 2003, Windows XP x64 and Windows XP Embedded. NT 5.1 is the older and slightly inferior 32-bit Windows XP SP3.
What ReactOS currently is - it's a re-implementation of NT 5.2-compatible core with NT 5.2-alike WinAPI equivalent, except for the small yet important detail - it has NT 6.0 WinAPI implemented as shim compatibility layer that redirects "modern" function calls into additional wrapper libraries that contain the NT 6.0-compatible code derived from Wine. In fact, almost the entire WinAPI stack is taken from Wine and the code syncs are done regularly.
Re: ReactOS Windows Equivalent?
Also, to add on; NT 6.0 shim isn't perfect yet, a lot of applications fail to run regardless.dsp8195 wrote:The tl;dr version:
OS editions are nothing but marketing crap of MS. Aside some missing applications between both "server" and "client" editions, the difference between them is a single registry switch. That's all. It doesn't matter a thing to consumer if the OS is either "client" or "server" edition, both are equally capable of everything.
Note: NT 5.2 is a core shared between Windows 2003, Windows XP x64 and Windows XP Embedded. NT 5.1 is the older and slightly inferior 32-bit Windows XP SP3.
What ReactOS currently is - it's a re-implementation of NT 5.2-compatible core with NT 5.2-alike WinAPI equivalent, except for the small yet important detail - it has NT 6.0 WinAPI implemented as shim compatibility layer that redirects "modern" function calls into additional wrapper libraries that contain the NT 6.0-compatible code derived from Wine. In fact, almost the entire WinAPI stack is taken from Wine and the code syncs are done regularly.
My working rigs:
Dell Latitude E5430 on 0.4.9-vgal - i5-3340M, USB boot.
Partially working rigs:
Ryzen 7 3700X on B450 board - 0.4.14 boot via preinstall. USB broken.
[ external image ]
Dell Latitude E5430 on 0.4.9-vgal - i5-3340M, USB boot.
Partially working rigs:
Ryzen 7 3700X on B450 board - 0.4.14 boot via preinstall. USB broken.
[ external image ]
-
- Developer
- Posts: 246
- Joined: Fri Dec 19, 2014 10:00 pm
Re: ReactOS Windows Equivalent?
because it doesnt redirect api's to NT 6.0 compatible variants at all.cernodile wrote:Also, to add on; NT 6.0 shim isn't perfect yet, a lot of applications fail to run regardless.dsp8195 wrote:The tl;dr version:
OS editions are nothing but marketing crap of MS. Aside some missing applications between both "server" and "client" editions, the difference between them is a single registry switch. That's all. It doesn't matter a thing to consumer if the OS is either "client" or "server" edition, both are equally capable of everything.
Note: NT 5.2 is a core shared between Windows 2003, Windows XP x64 and Windows XP Embedded. NT 5.1 is the older and slightly inferior 32-bit Windows XP SP3.
What ReactOS currently is - it's a re-implementation of NT 5.2-compatible core with NT 5.2-alike WinAPI equivalent, except for the small yet important detail - it has NT 6.0 WinAPI implemented as shim compatibility layer that redirects "modern" function calls into additional wrapper libraries that contain the NT 6.0-compatible code derived from Wine. In fact, almost the entire WinAPI stack is taken from Wine and the code syncs are done regularly.
What dsp8195 claims is simply not true.
-
- Posts: 441
- Joined: Sat Nov 15, 2008 4:13 pm
Re: ReactOS Windows Equivalent?
dsp8195 wrote:What ReactOS currently is - it's a re-implementation of NT 5.2-compatible core with NT 5.2-alike WinAPI equivalent, except for the small yet important detail - it has NT 6.0 WinAPI implemented as shim compatibility layer that redirects "modern" function calls into additional wrapper libraries that contain the NT 6.0-compatible code derived from Wine. In fact, almost the entire WinAPI stack is taken from Wine and the code syncs are done regularly.
cernodile wrote:Also, to add on; NT 6.0 shim isn't perfect yet, a lot of applications fail to run regardless.
Now I'm wondering, is it possible/feasible to implement NT6+ function calls into ReactOS' application compatibility system(s) in a way similar to what dsp8195 described?learn_more wrote:because it doesnt redirect api's to NT 6.0 compatible variants at all.
What dsp8195 claims is simply not true.
It may not be what's happening now, but it sounds like a good idea. Can we get some thoughts about it from people who know more than I do about the inner working of Windows & ReactOS?
I reserve the right to ignore any portion of any post if I deem it not constructive or likely to cause the discussion to degenerate.
Who is online
Users browsing this forum: DotBot [Crawler], Google [Bot] and 46 guests