How to create a duplicate cmd.exe under Win7 SP1?

msalton1 said:

I prefer the never combine setting. I also set the icons to 'small', the taskbar to autohide and resize it vertically to handle the pinned icons and two rows of running apps. It can be frustrating to arrange it all, but I find it works well.

Oh, me 2. Small and combine. I also have several utilities to send things to the system tray. I'm very hard at work trying to organize that taskbar but it fights you at every corner.

One thing, I forgot to mention, you can't have 2 different links to the same program in the quicklaunch area (which is where they must go, because the lining up becomes "same program @ same position always"

msalton1 said:

alacarre said:

msalton1 said:

Seems to work here:

Attachment 328345

What am I looking at?

That's the taskbar shortcuts on the bottom...an explorer window containing the shortcuts on top. My subsequent image should clear it up.

Remember it's not any two programs. It's cmd.exe, two links and not aligned. And all "admin" cmd's align with each other, non-admins with each other. That's why we need two programs.

You're probably missing Service Pack 1. You're talking old days, like last year.

Well, actually though you have a point. I could create something like a hard link say, so the paths are different. Otherwise the command line is the same and it should (checking...) ya, if it's the same program when you right click it you get a "Remove From Taskbar" option (not add).

msalton1 said:

alacarre said:

You're probably missing Service Pack 1. You're talking old days, like last year.

I'm running SP1, 64 bit. Have been since beta.

So you've added 2 links to the same program? Because I don't get that option. Although mine takes some parameters (startup batch file and a switch). When I change the parameters it still says "Remove"

They may open, but they won't work. Not after SP1 (although mine is x86).

[Edited to add]
You did see that output right? I typed "dir"

Another thing, the way things are these days with COM say, an experiment performed on one machine says very little about what will happen on another. If cmd.exe were just a regular old Win32 executable then it should work the same. No matter what I do with it. But it's not. It must be using COM for its text output or something, or has some special manifest embedded in it which makes no difference if you're living in the US but may break in Cambodia where I am.