## [Release] cmdhide.exe (cmdow replacement)

Here are some other small tools that have been created by Siginet that are in someway helpful.

### [Release] cmdhide.exe (cmdow replacement)

cmdhide[/CENTER]

This small tool is useful for hiding ugly cmd windows.

It might not be quite as effective as cmdow.exe but cmdow.exe is now triggered by antivirus programs as a virus. cmdow.exe is not a virus... but since the AV makers decided to destroy cmdow.exe I came up with this alternative.

It works a little diffrently than cmdow. Here is how you use it:

Most people will want to place the cmdhide.exe file in the system32 directory so they don't have to specify the path to cmdhide.exe in their batch files.

There are 2 ways to use it.

1. Hide one Batch File
Let's say you want to hide only one batch file. The batch file you want to hide is the batch you are going to start. In this case you would want to call cmdhide.exe with the title of the batch window. So somewhere in your batch you need to make a Title for the batch window like this:
Code: Select all
Title MyBatchWindow

So now your Window Title is "MyBatchWindow"

Now in your batch you will want to call cmdhide.exe with the window title like this:
Code: Select all
Title MyBatchWindow
Code: Select all
[size=84]cmdhide /name:MyBatchWindow[/size]

*Make sure you put your window title between quotes if it has spaces in it.

Now when the batch starts you will see the cmd window for a second then it will dissapear.

2. Hide batches called from other scripts
This is my favorite and will probably be the most used because it never flashes the batch window at all. It is hidden from the get go. Also it is very simple to do.

From within your main script if you are gonna call any batch windows you want to hide all you have to do is call cmdhide.exe with the path to the batch you want to hide.
Example:
Code: Select all
cmdhide "X:\path\to\mybatch.bat"

v1.3
1. Bug fixed when run without path.
v1.2
1. Fixed bug where Environment Variables were not parsed.
2. Fixed bug where if path was not given the batch was not run.
v1.1
1. Fixed bug where if the path is not given an error would occur.
2. If file does not exist an error would occur... now there will be no indication at all.

Siginet
Senior Member

Posts: 1445

pemdas
Junior Member

Posts: 1

Ah!!! funny I was looking for it as well. I only get a damaged 48.4kb zip file :???: doh.
Tasslehoff
Junior Member

Posts: 4

Windows XP PowerPacker Reviewed in PC-Quest & PC Utilities magazines!
RVM Integrator Reviewed in CPU magazine and Maximum PC!
--Siginet--

Siginet
Senior Member

Posts: 1445

### thank you

thank you ......................................
komsboy_more
Junior Member

Posts: 3

Great tool
Smile
Junior Member

Posts: 1

i tried cmdhide "X:\path\to\mybatch.bat"
from my current location
cmdhide "mybatch.bat"
no Go
and does this have start /wait in it ?
cmdhide "*.bat"
or will that complicate things
i wanted it the to work with a "FOR" LooP
ENU_user

Posts: 485

ENU_user wrote:i tried cmdhide "X:\path\to\mybatch.bat"
from my current location
cmdhide "mybatch.bat"
no Go
and does this have start /wait in it ?
cmdhide "*.bat"
or will that complicate things
i wanted it the to work with a "FOR" LooP

I haven't used cmdhide in a long time... and I wrote it a long time ago. So bare with me.

Where is your cmdhide.exe file located?
cmdhide "X:\path\to\mybatch.bat" should definatly work if you throw cmdhide.exe in the system32 directory or are running your batch in the same folder as cmdhide.exe.

If it doesn't then maybe I'll have a look into it and see if I can reproduce the error.

As for cmdhide "*.bat" ... It should work in theory... but I would have to look at my source code because I don't remember what I wrote. lol!

I actually thought cmdhide.exe wasn't popular at all so I stopped developing it. Allthough I have noticed latley that people are still using it all over the internet. So any ways I can improve on it I will.

As for the Start/ Wait... Again I need to look at my source to find out. I think it does wait until the app is finished before it stops... but I am not sure. If I need to I can allways add some switches to allow the user to choose wether cmdhide waits or not.

Edit: Now that I am thinking... I doubt if * represents a wild character in this case... but it might. If not I can work on something.

Windows XP PowerPacker Reviewed in PC-Quest & PC Utilities magazines!
RVM Integrator Reviewed in CPU magazine and Maximum PC!
--Siginet--

Siginet
Senior Member

Posts: 1445

greets jobs sir.keep it up
hasl
Junior Member

Posts: 1

you've gotta be fucking kidding me. this is autoit bullshit. lol
rootw0rm
Junior Member

Posts: 3

Next