Originally Posted by Droidriven
If using an emulator, it shouldn't require recording Windows, at least, not much, if any, should it? Isn't the point of using an emulator is to make it run on a system the software wasn't built for?
One of us has missed the point.
An emulator allows you to run software meant for the emulating OS. For example running excel on the Emulator.
I don't get where you mention "recording"? I can only guess you meant "re-coding"
As a software developer, an OS provides a standard guaranteed API that apps can use. eg In its simplest form, there is "draw a window" or "tell me when someone clicks on it and not somewhere else" etc etc etc etc etc. Now, these API's are expected by programs that run on the OS or they crash (ie calling a non-existent API, which I have done many times simply with a misspelling but is normally caught by the compiler). An OS like Windows, has countless
API's, and each of these would need to be duplicated or software just wont run.
The closest I can think of is WINE on Linux, to run .Net windows applications. But, .Net is only used by some applications, the OS itself and apps that are not .Net, would require the base API's (.Net is a simplified layer into the base API's, of whatever OS your running on just like JAVA). ie. you would need to re-code all the standard and expected API's; its a contract with app developers as to what they can expect on that OS. And think for a second, do you not think the ReactOS developers are smarter than both me and you? obviously they are nowhere near finished, because of the need to duplicate each and every API. And its not just the API interface. Because its closed source, there will be some API interfaces that do more than can be garnered from their name or documentation. If it were easy, there would be many many more than ReactOS but there is not. People hate being tied to M$ but are stuck
And don't forget, we are talking OS, not apps.