Suggestion for a fourth alternative, do the release, but split off the 3rd
party apps with regressions out of rosapps to roswork or some such, possibly as
a separate repository, so the kernel and core apps can be focused on. Someone
fixes the regressions and that app can be moved back into the
I agree with Alex's reasoning, plus in a multiprocessor environment such page
zeroing may be done asynchronously to other cores or processors attempting to
acquire use of that page while its state is inconsistent. Removing it counts as
a security hole, in other words, except for single core
] sumatraPDF
my point is, to allow them to still support XP/2003 systems (and, of
course,ReactOS :) )
On Fri, May 1, 2020 at 4:16 PM M. Ziggyesque
mailto:ziggyes...@hotmail.com>> wrote:
They have to commit to build/sln configurations based on VS2010-17 in parallel
with current VS2019
They have to commit to build/sln configurations based on VS2010-17 in parallel
with current VS2019 config, it appears, before it is a candidate for ROS to
support as part of the rosapp collection. While some support for mingw builds
is present, it is considered unsuitable for doing release
I'm not saying it isn't possible to support the hardware, just I have not seen
any pre-boot environment that the installer might need to communicate with
attempt to provide this support, so it is also available to whatever gets
installed, after reboot. The installer may be fine using only 6-dot
The console itself is still a graphical user mode app; it or a DOS box simply
uses a DefConsoleProc (sic) instead of DefWindowProc behind the scenes to
manage the GUI aspects and system menu, and may use an OEM code page instead of
an ANSI one in full screen mode. Windows may eventually be able
That would be more suitable for a new WidenPathObj or FlattenPathObj in an
add-on library, imo, not changing the declaration of those from the XP versions.
-- Original message--
From: katahiromz
Date: Sat, Sep 29, 2018 2:30 AM
To: ReactOS Development List;
Cc:
Subject:[ros-dev] WidenPath
warrants, but it
isn’t paranoia.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Pierre Schweitzer
Sent: Tuesday, June 5, 2018 1:46:55 PM
To: ReactOS Development List; M. Ziggyesque; David Quintana (gigaherz)
Subject: Re
No, I don't see it as pointless to have a plan B. It's more a question of when,
not if, it's desirable, given past practices.
Even with no immediate changes, github can no longer be considered
vendor-neutral. Down the road, as example, M$ may well try to require every
project adopt their
While this has application in protecting a system from rogue or trojan apps,
supposedly a shutdown privilege would be something granted manually by a SYSTEM
level process that is trusted, so that if the system is not recoverable a
graceful shutdown can be attempted with minimal process
My 2 cents,
I'd think it better specfies the hex values are BugCheck codes, not another
error number set's values. That it's being output to the debug console is
indication enough to most it's a System Error. :-) I'd keep "Fatal " before it
to keep the emphasis it isn't considered recoverable,
11 matches
Mail list logo
