1) Win32k.sys is buggy, but TaskMgr is buggy too - performance card. We
repaired it and it displays correctly on ReactOS.
2) You can use our code. It will be published on GPL.
3) Yeah, explorer is Windows shell. But you musn't clone it. You can do
somethink else, somethink better, somethink, what will can reply Explorer.
4) We'll not help you by commiting patches to your SVN or submiting to
you diffs. If you want, you can use our code. It will be published on
SVN server on GNU General Public License.
Alex Ionescu wrote:
Rafal Kupiec wrote:
We're going to follow Windows arch, becouse
Windows isn't really bad OS,
It only often hangs up. Making HostiliX we want to do new OS that will
be able to run Windows Applications and drivers.
That's what ReactOS is.
Why? There's a lot of
great programs and I think the most drivers for this OS (eg. there's no
drovers for Canon i560 pronter for Linux). All hardware manufacturers do
drivers for Windows, so we want to HostiliX be able to support them.
That's what ReactOS is.
Why we don't help ReactOS to make it better?
We hate your policy. You want to do Windows NT clone, so must you do
for. example explorer? Cannot you do any other application?
You don't want us to use explorer? I don't understand. Explorer is the
shell on Windows, so we must clone it so that users can feel at home.
A few days
ago I asked on ReactOS forum why your Task Manager looks buggy? e7
answered me: "Because ReactOS is still a alpha version (0.3svn), and the
developers have other things todo (extend API, let applications and
drivers work...)"
Actually it's because of some bugs in Win32K that aren't our priority
right now. If you copy our code your taskmgr will have the same bug. Run
it in windows, and you'll see it runs excellent.
It's your policy, that I don't
understand. Why are you
doing new think incompletelly?
Taskmgr is 100% complete. Try it in windows. Win32K took Microsoft years
to finish, and still has bugs. So does ours. We are in alpha version,
it's normal.
You want to do all at the same time!
The design of Windows requires a minimal amount of things to be ready
simulatanously. We can't say "ok guys, let's work 100% on the kernel for
the next 2 years". Window's design doesn't allow that, which is why we
needed to work 50% on everything and then improve bit by bit.
But
we want to do less than you but better. We'll not help you, becouse we
don't want to repair your bugs(eg. taskmgr).
If you take our GPL Code and "not help us" (ie: not re-release your
modified sources) then you are committing copyright infringement and
violating the GPL license. I thought you want to make an OS, not go to
jail...
Why taskmgr is buggy?
I just told you.
Becouse someone who developed it stoped working
on it and I think start
working on somethink else.
No, taskmgr is not buggy. The developer stopped working on it because it
works. If you don't understand that this is because of win32k, you
shouldn't be coding a Windows OS.
I personally don't do all system
ingredients.
I do only one thing.
Good luck. Works for monolithic kernels. Won't work for a micro-kernel
subsystem architecture like NT.
Best regards,
Alex Ionescu
Kernel Developer, ReactOS