There are many reasons for ROS now. They include: Freedom from Windows "bloat" that slows down the machine and adds security problems. Wanting something that gives you freedom and doesn't bind you to the wishes of a corporation. Compatibility with older hardware, even recently "older" hardware that ...

The only way I'd support this would be for there to be a separate Sponsors page. If you want ads, you go there.

1. It will likely continue to support the 2003 Server for a while. However, some newer APIs are already included. So they may change targets in the future. Nobody really knows. They may add some forward compatibility. 2. The intended users are whoever wants to use it. It would be good for gamers sin...

I believe this could use a wiki page.

The overall answer is yes and no, just use at own risk and make sure you back up any important data.

From what I understand, Windows parses it out and runs its own, at least on the newer ones.

Yeah, I think I misread the first part of your sentence. Right now, we just have the downloads. That's why I suggested my older idea. If you had a program to examine the ISOs and pull out what changed and then register the necessary files, that would work for now. But yeah, it would be interesting i...

Yes, but if there is a server for update of ReactOS, it would be very good. So you mean like remote updates across an entire local network? Yes, that would be great in an enterprise environment. And my earlier comment about BITS was concerning 3rd-party software that uses it. I am pretty sure that ...

I agree. You don't really want to look like you have your hand out. Maybe something like a "premiere licensing" option. There needs to be some sort of incentive to make the corporate types want to give. So offering things like tech support, features they find important, or prestige might work. Of co...

And it is not even an option at this point. Even if the updaters were compatible, and even if ROS could accept their upgrades, XP and 2003 support are long gone.

Taking the above further, if you fix the one used to replace the "official" one to where it works, then you might end up with breakage elsewhere. Or you can do it the other way by putting the official file in place of the ROS file if you are looking for associated breakages when things are done corr...

Make it a purple alien girl with a bunch of scalp tentacles and eyestalks. Few can figure her out, much like the few here who have figured out a Windows kernel.

Yeah, I had to look closer to see the USB "trident" logo.

Why is the girl cutting herself? Oh, never heard of "sawing" USB. So a Russian pun. But the more I think of it, the more it makes sense since, in the US, we do have a tool that is called a hacksaw. And yes, our USB code is still a bit "hacky."

That's the whole point. NOT all core components are THEIRS to "open source", and they cannot cleanly separate them without having to re-develop parts. I just gave an example, but the issue is general. It has to do with the problem that licenses can be given for specific usage manners... but not for...