Open or not open Shell window?

[mritter]

I was poking around the code used the installer WshShell.Run() in a different way. I realized that if I/we want, no shell window could be opened when launching an installer or DOS command. For an installer no window would be good. For a script or DOS command, you may have some output you want to see. For DOS commands (copy, rename, etc) it can get annoying seeing the window flash open/close quickly.

So.....in your experiences do you see a Shell window flash open/close quickly (or stay open) during a regular program installer? Or do you see nothing, like a silent installer should be?

When doing DOS commands or scripts (.cmd), same thing: window flash, or stay open, or nothing at all?

When doing DOS or scripts, do you want a window to be opened for output?

I ask this because I don't like the flashing window. I would rather have no window opened ever. I can make it do that.

I need your input, though. Keep it the way it is because it is needed, or never open a window?

Edited October 11, 2008 by mritter

[Kelsenellenelvian]

NO FLASHING DOS WINDOWS...!!!

God I hate those also.

[mritter]

I answered my own question: the output window is necessary. No change can be made..............yet.

I still have ideas up my sleeves for DOS commands....... ;-)

[AlBundy33]

Why not use cmdow?

Currently I add the following line to all of my batchfiles:

CMDOW.EXE @ /HID

Which hides the current shell (the window is only for some ms to see).

But with

cmdow.exe /RUN /HID path_to_your_script

you can start the script in background.

Greetings

Al

Edited October 19, 2008 by AlBundy33