Hi Marc,
ReactOS already had a CMD-only interface, but it regressed.
You can try out the "reactos0.3.0-REL-cmd.zip" package from
http://sourceforge.net/project/showfiles.php?group_id=6553
<http://sourceforge.net/project/showfiles.php?group_id=6553&package_id=6629>
&package_id=6629.
IIRC, that package was broken a bit, but when the correct settings are used,
it should work.
These are:
*
/NOGUIBOOT in "freeldr.ini"
*
Setting the "Shell" registry value to load "cmd.exe" instead of
"explorer.exe"
Would be cool if anyone could unregress the CMD-only interface in trunk :-)
Best regards,
Colin
_____
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of Marc Piulachs
Sent: Monday, March 17, 2008 2:45 AM
To: ros-dev(a)reactos.org
Subject: [ros-dev] Reactos booting to CLI
As we know Windows (at least till Windows 7) was designed to be a GUI based
operating system. All applications can safely assume that the windowing
subsystem is running.
Windows/Reactos can run native applications without starting the windowing
subsystem like usetup during 1st stage setup but of course without having
access to Win32 apis as Win32k is not loaded. AFAIK win32k is designed to be
the main subsystem and is the responsible of starting the windowing
subsystem so my question is . Would be technically possible to have a
striped win32k version without the GUI code? + command line enabled
winlogon, syssetup etc.. so you can boot and run cli based applications like
cmd.exe ? what other parts of the boot process relay on having the GUI
running?
It's more of a design curiosity question rather than a real request
Regards,
Marc