AutoStart of CMD Shell

  • Thread starter Thread starter JoP
  • Start date Start date
J

JoP

Hi there. I have a working and tested xpe run-time image. In my
configuration, I use the Minlogon and the Windows Command Processor
components.
- CMD - Windows Command Processor 5.1.2600
- Minlogon 5.1.2600.1106

At startup in xpe, the cmd shell automatically loads. I want to remove
this auto-loading feature. I look in almost every Run, RunOnce,
RunOnceEx keys in the registry, and in startup folder, but I can find
where the cmd.exe is loaded. Someone knows which value in registry I
have to change to stop the auto-loading of cmd.exe ? I don't want to
remove cmd.exe from my configuration.
 
JoP said:
Hi there. I have a working and tested xpe run-time image. In my
configuration, I use the Minlogon and the Windows Command Processor
components.
- CMD - Windows Command Processor 5.1.2600
- Minlogon 5.1.2600.1106

At startup in xpe, the cmd shell automatically loads. I want to remove
this auto-loading feature. I look in almost every Run, RunOnce,
RunOnceEx keys in the registry, and in startup folder, but I can find
where the cmd.exe is loaded. Someone knows which value in registry I
have to change to stop the auto-loading of cmd.exe ? I don't want to
remove cmd.exe from my configuration.
Click to expand...

The command processor and the command shell are independent. You can set
another shell but still have the cmd.exe available.
 
Minlogon has dependency upon Command Shell.
Command Shell has dependency upon CMD - Windows Command Processor.
In my configuration they are not independant.

CMD - Windows command processor is the component containing cmd.exe and
registry data to set the cmd.exe properties.
I found the AutoRun string value under HKLM\Software\Microsoft\Command
Processor\. I removed it but cmd.exe still autostart at startup.
 
JoP said:
Minlogon has dependency upon Command Shell.
Command Shell has dependency upon CMD - Windows Command Processor.
In my configuration they are not independant.

CMD - Windows command processor is the component containing cmd.exe and
registry data to set the cmd.exe properties.
I found the AutoRun string value under HKLM\Software\Microsoft\Command
Processor\. I removed it but cmd.exe still autostart at startup.
Click to expand...
You *should* be able to change the shell, even with Minlogon.
 
There is no dependency between CMD-Windows Command Processor and Minlogon
component. There is a dependency in the Minlogon Sample Macro Component. Are
you using the Minlogon Sample Mcro Component? If you are you can go to the
settings, and uncheck the Command Shell and then add a shell component to
the configuration.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.
 
I kept Minlogon & CMD - Windows Command Processor & Dos Windows on
Windows Support (to support my maintenance script)
I removed Command Shell and its dependencies.
When I said "Minlogon has dependency upon Command Shell", I clarify,
this wasnt a real dependency, just Target Designer complaining that I
need to choose a shell because I inserted Minlogon in the
configuration. I didnt select any shell. The component Dos Windows on
Windows Support has a dependency upon Command Shell, then I build my
target image without doing a check dependencies.
After fba, my run-time image booted without shell, win xpe blue
backgound appeared... and my .Bat maintenance script runned at startup
using cmd.exe.

Thx for the help Adora!
 
Sean
I agree there is no dependency. I clarified what I said in my last
post.
I dont use Minlogon Sample Macro Component.
I just need cmd.exe to be able to launch my maintenance script (.bat)
at startup.
After tested, I think the Dos Windows on Windows Support component can
be added to a configuration and ignore the dependency with Command
Shell.
Maybe I can do a smaller version of the Dos Windows on Windows Support
component. There is probably lots of utilities in this component that
my script dont need.
Thx for your help.
 
Hi,

if you want to resolve all dependencies automatically, you can try to
add a REG_SZ value "Shell" to the key "HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon" with a value like "%%SystemRoot%%\my.bat".
At least it worked for me.

Regards,
Susanne
 
Ok I readded Command Shell, I modified the key you mentionned to point
to my script.bat. No dependencies remained. It worked! Before, I
ignored this key because im using minlogon. Strange that minlogon use
winlogon key. Thx Susanne!
 
Back
Top