12 May
2016
12 May
'16
4:39 p.m.
Quite a few 'userland' features of NT6 requires kernel support to
function properly. If we go in, it would be, do NT6 kernel and slowly
bring the userland up to NT6. But we don't have a fully working NT5
kernel yet, so....
On Thu, May 12, 2016 at 8:34 AM, David Quintana (gigaherz)
<gigaherz(a)gmail.com> wrote:
If we do NT6, we may want to have latest NT6 instead
of trying to stick to
an older one and having the same deprecation issue in a couple years?
Also, what about the "idea" of keeping the majority of the kernel and large
part of the usermode NT5, but having compatibility profiles that
implement/emulate NT6 API functions using the existing NT5 feature set? Is
that unrealistic?
On 12 May 2016 at 14:39, Aleksey Bragin <aleksey(a)reactos.org> wrote:
Which again brings in the topic of updating the version we are targeting.
Windows 7 would be a minimum target these days, IMO.
Regards,
Aleksey Bragin
On 12.05.2016 14:04, Ged Murphy wrote:
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
Yeah it's nonsense. No one drops support for ReactOS, they drop support
for
older versions of Windows which likely includes reactos too.
If they were adding in ReactOS specific code, they were doing it wrong.
The bigger issue here is that a lot of apps are starting to drop support
for
XP and recommend a minimum of Win7. If we don't do something about our
insistence on sticking with 2k3, we'll soon be in a position where no
browsers will run on ros, as well as a whole other list of apps.
Ged.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev