Yes, at this phase, I am attempting to load up the minimum core ReactOS followed by just a single GUI application. The idea is to find out what is the minimum needed for the base plain OS and then what is needed to be added (ie GUI subsystem, etc..) for a particular application in 2 clearly separated groups.
The rational is that the ReactOS base always has to be load, but the GUI and other subsystems only may need to be loaded depending upon application. Typically the GUI and other subsystems will be load prior to the application in almost all cases.
The idea is to run a very lean ReactOS core system and just one single application of some type. When the application exits then the OS shuts down perhaps.
This is good learning for how ReactOS flows from boot to application instance as well as understanding the minimum core files (and size) needed to have the ReactOS base and some application in 2 separate groups of files.
If I am starting to understand ReactOS better then I suspect that (for testing purposes) I could load the ReactOS base files followed by the real Windows XP subsystems file and the OS should function cleanly and stable if there is complete compatibility across these 2 OS.
This would answer the question of compatibility and stability within ReactOS after which when each new ReactOS subsystem is developed, then the Windows XP subsystem can be removed from the process. Eventually, one should arrive at a completey compatible drop-in replacement ReactOS system.
Just some general thoughts though on what I have been thinking lately as well.
Thanks again and have a great day all,
Lonnie
On Wed, Jun 20, 2012 at 6:36 PM, Timo Kreuzer
<timo.kreuzer@web.de> wrote:
Am 20.06.2012 17:23, schrieb Alex Ionescu:
You don't need all of that.
Here's what TinyKRNL 2 used:
freeldr (ntldr)
ntoskrnl
hal
bootvid
kdcom
fastfat
ramdisk
kbdclass
i8042prt
ntdll
smss
And then a native app to launch (configured by registry)
Native app, yes, but he asked for notepad.
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev