![]() ![]() Microsoft didn't give permission for it to be out there so no one has a license that permits them to have it. Simply having a copy of the leaked code is very much illegal. Of course I shouldn't be discussing but it's just what I felt. This won't be copying and I don't see why it should be illegal. Probably they have lessons to learn and have similar things to implement. They won't last a week with their product if they use. You will be blocked/banned from their social media and forums if you so much as suggest the idea or try to discuss it.Īs for gaming, it's making great progress in that area, but it's currently intended more for the 98/XP Direct3D games than the 3.1/95 ones that people here would play.ĭevs don't have to use their code either. If you have looked at the leaked code or have a copy of it or have had any ties to Microsoft or their contract developers, you are asked not to contribute anything to the project and anyone found to have been using the leaked code or anything from Microsoft to inform their work on the project will be permanently banned and their work stricken from the codebase. The ReactOS Devs said "NO! NO! NO!" to using the leaked Microsoft source, specifically the XP code that was part of the leak. But it is not reasonable to expect such a mixture because they never considered it as possible, since most PC users blindly install Windows.RetroGamer4Ever wrote on, 13:21: The ReactOS Devs said "NO! NO! NO!" to using the leaked Microsoft source, specifically the XP code that was part of the leak. If they did that, then we wouldn't be having this discussion. They don't check each newer API for existence and decide which version of code to use at each point and fall back if only the older exists. But the industry wrote bad drivers or bad firmware and put the devices in addresses that conflict with installed memory.Īs for confusion, the problem is supporting the libraries in a piecemeal fashion, I mean, if it finds NT 6.x, it tends to expect it ALL to be there. With PAE, up to 64 GB of RAM could be addressed on 32-bit machines. ![]() Windows have been forced to make choices based on the industry mucking up. Not all developers know the correct procedures for checking for functions or versions. In fact, if they barely know what they are doing, they would be more likely to run into version conflicts. It is not about what developers care about. I am myself from the artistic and gaming side of the development world, so I can confirm from the firsthand experience it is indeed the truth. They compile against VS2015 or later, so all they care about is if their piece of software works at all. The latter part is extremely important, because, let's face it, no matter what you say about idealized applications "getting confused about the version of Windows" once they find the NT 6.x libraries on NT 5.x system, the actual real life software developers don't give a damn about Windows version. * Allowing dwmapi and other runtime libraries from Wine that were originally introduced in Vista to co-exist with NT 5.2-alike core - fixes Shantae Half-Genie Hero and Child of Light being unable to run on Windows XP/2k3 * Applying patch that allows bigger number of software shader slots - fixes games like The Sims 2 and Jinko Shoujo 3 So ReactOS has a hard time advertising itself.ĮDIT: Here is the topic where we talked about direct x rendering: viewtopic.php?f=2&t=16366ĭsp8195 wrote:Seamless ReactOS gaming is impossible without the following things: There's also the issue that ReactOS kernel is NT, so OS statistics like Steam charts, market share, etc, all detect ReactOS as XP/2003, so everyone thinks we are all just XP/2003 users. But we won't be able to get another file system working until the cache manager is finished, which I have been trying to push and sending money to the bounty here. So if you think of games like quantum Break or GTA V or other really large games, they probably won't work well, even if we had dx11 working. Currently ReactOS uses Fat32, which doesn't handle large file sizes well. There is also other issues other then rendering, like a proper filesystem. Even Vulkan doesn't have XP drivers that would work with ReactOS, though I heard Vulkan can run on XP if someone made a driver for it. I even suggest the developers should focus the whole. Obviously, gaming is a big reason why people use Windows. We recently had a topic (of which I can not find atm) about rendering in ReactOS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |