23 Apr
2010
23 Apr
'10
8:02 a.m.
You had enough time to try and fix this. If it's not fixed, then it's
going to be temporarily commented out until this new (correct) code
works.
I know how hard it was for the kernel, but if our OS turns out into a
perfect modern and cool OS architecture-wise which can't render text
correctly.. Who needs that? One or two developers?
Some real usage would be beneficial, not only self-ertaintaining. At
the very last, after so many years.
I don't really understand the logic of enabling the code (correct
piece of one) which does NOT work. Either make it work or don't
enable it until it works. That's the principe for everyone who wants
to develop ReactOS. Otherwise it's gonna rot in http://
web.archive.org instead of becoming a mainstream OS.
WBR,
Aleksey.
On Apr 23, 2010, at 5:47 AM, James Tabor wrote:
Not surprised!
I guess ReactOS new polices are for hiding the real issues and not
fixing them and revert all the correct code. Since the kernel rewrites
and the new order of coding, these oddities have now surfaced. The
TEB, is inaccessible from kernel mode as in bug 5265 and 5314, and the
strange processes access issues in bug 5310. This revert silliness
will result in moving the project back to post windows 95 architecture
(arwinss). ReactOS is about moving forward and taking chances with
innovations from learned information then moving away to make it work
even better. Personally, I hope someone will take up where this left
off and move on.
Good luck!
Reference:
http://www.reactos.org/bugzilla/show_bug.cgi?id=5265
http://www.reactos.org/bugzilla/show_bug.cgi?id=5310
http://www.reactos.org/bugzilla/show_bug.cgi?id=5314