This registry key sets what shell starts upon boot: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell
Normally, it's set to explorer.exe, but you can set it to cmd.exe to make it command prompt only.
I've also had occasion to make a custom shell to do HMI startup tasks and keep the operator from clicking about (sometimes quite disruptively).
Sorry, I should retract that somewhat. If memory serves, the background still appears and you get the cmd.exe window. On the other hand, you don't get explorer, which, IMO, is 85-90% of whatever goes wrong with Windows anyway.
Services still work, so installing OpenSSH or CopSSH (or even RDP) still works as normal.
I did up an XP vm with the modified registry entry, installed CopSSH (OpenSSH will work, but the service needs to be run as a user and not SYSTEM-- CopSSH creates its own use account, so it was quicker for me to demonstate), and connected to it via Putty:
EDIT: Added a few more details to my explanation...
Comments
Sorry, I should retract that somewhat. If memory serves, the background still appears and you get the cmd.exe window. On the other hand, you don't get explorer, which, IMO, is 85-90% of whatever goes wrong with Windows anyway.
Interesting.
To make it actually useful how do we start XP, or any Windows, such that the shell can be reached from a serial port or over the net, via ssh say?
Of course what I'm asking for is totally pointless because that can all be done by Free and Open Source operating systems anyway.
Interesting as a curio none the less.
I did up an XP vm with the modified registry entry, installed CopSSH (OpenSSH will work, but the service needs to be run as a user and not SYSTEM-- CopSSH creates its own use account, so it was quicker for me to demonstate), and connected to it via Putty:
EDIT: Added a few more details to my explanation...