[squidboy]

Howdy,

I invariably need to quickly get to a command prompt/dos box and this is a neat trick we use at work and at home. I use it all the time as it's really handy.

http://www.petri.co.il/add_command_p...s_explorer.htm

[ChuckE]

Why not just make a shortcut key to the Command Prompt?

Just select Start>All Programs>Accessories>Command Prompt
and right click the Command Prompt, and select "Properties"

Then, in the "Shortcut key" field just press the "D" key.
That will display "Ctrl + Alt + D" in the box and then [OK] the window.

Then, anytime you need a DOS window just press Ctrl+Alt+D.

Works great, it is simple, and the same tip can be used for (in WinXP) any selection you have in the Start>All Programs menu. (There were some limitations with earlier versions of Windows, but it can work in those other as well for many menu items).

I do this for all my computers, at home and work. I also do similar shortcut keys for the Notepad, Calculator, Word, Excel, PowerPoint, and any other program that I frequently used.

Notice, I also changed the "Start in" field to be just "C:\" since I prefer that to other, buried, directories.

[squidboy]

Why not just make a shortcut key to the Command Prompt?

Becuase you can't shortcut what you can't see, and there are other security concerns which I can't discuss here.

I agree that's an alternate way to use it for home but in a distributed large network making shortcuts is a "bad idea" which restricts mobility and replication.

[ChuckE]

Please explain. What do you mean you can't shortcut what you can't see?
Anything in the Start path can be seen. What security concerns are there?
If a person can see a program in their Start menu then they can SEE a program in their Start menu.

In WinXP, if the program does not exist in their personal "Start Menu\Programs" directory structure, and they only have limited access rights, then the only thing that will happen when trying to change the Properties of a program is an error message stating:
"Unable to save chanes to 'whateverprogram.link'.
Access is denied."
So, no harm, no foul. The access rights protect the user from changing things they don't have rights for.

In WinXP or Win2K, the "Command Prompt" program selection (in the Start>All Programs>Accessories" path) is in each persons personal directory structure. It is theirs to alter. If person A decided to make Ctrl+Alt+D their shortcut key to the DOS window, and Person B decides to make Ctrl+Alt+C their shortcut key to DOS and Ctrl+Alt+D to some other program, it does NOT conflict.

As for doing such shortcut keys in a "large distributed network;" I work at probably the largest distributed network in the world, and if not the largest then it is one of the top 3. The company I work for was instrumental in making the internet, we were the originators and developers of Ethernet, and we are worldwide. There has never been any kind of mobility or replication problems with any of these shortcuts to what already exists in a person's Start menu. Basically because what exists in a person's personal Start menu is theirs to deal with. All the items in the Start menu are basically shortcuts to actual programs, they are all .lnk files. All I was informing people, through this board, is that they can also make shortcut keys easily through the tools that MS has given us, not to install PowerToys, not to make batch files, not to make registry edits (where a person could easily screw up Windows operation completely).

So, please explain.

[squidboy]

So, please explain.

I did as best I could. If you don't want to use it that's fine. If you don't want folks sharing tips on this board then perhaps you could suggest another board for me? I certainly don't want to suggest anything that wouldn't be useful to most folks who read here.

[ChuckE]

Now what are you talking about?
You haven't explained anything, and is that the best you could?
I never took anything away from the tips you mentioned.
I only said that what I suggested (the shortcut key to an existing shortcut in the person's Start menu) was easy, simple, and quick.

You alluded to a point that what I suggested was, in some way, a security concern, that it was a bad idea in a distributed large network. Now that I have asked you to explain your points you want to act wounded and hide behind some amplified sense of "if you don't like my ideas I'll just take my ball and go home" (wimper wimper). Geeze! grow up squidboy.

All I asked you was to explain your points of how modifying the properties of a shortcut, in any way, restricts mobility, or replication, or a security concern. I really would like to know.

I am not suggesting you go anywhere else. Come on, let's talk this out. I am sure others would like to learn as well, and if somehow you were mistaken then there is nothing wrong with that either. If you show me I am wrong then I will learn something as well. That is what we are all here for, to learn from each other. Don't get hurt, but, at least, hold up to simple questions to your own statements.

[squidboy]

All I asked you was to explain your points of how modifying the properties of a shortcut, in any way, restricts mobility, or replication, or a security concern. I really would like to know.

Sure. First tip, try not to break into a pissing contest about "my network is bigger than yours". This tends to discourage open discussion. If you can get beyond that, then sure, I'd like to learn more too.

I'm currently contracted with JPMorganChase doing network support and the like. I've done similar work with other large scale networks. That said I cannot reveal certain features they use. My suggestion was to assist folks that might be deploying to desktops on a large scale to foment better security and reduce costs through the end of life-cycle. It's openly available via my link above, and not intended for individual user use in a general sense, which is why I suggested it.

As for the shortcuts, if you shortcut or create a link to a locally stored executable and that executable changes name or location, that link becomes useless. Multiply that by 100, 000 and you've got a bigger problem. In addition, that link only runs the app...it doesn't check the server for the 'latest and greatest'. This doesn't account for remote users but they are usually a smaller number and can be accomodated differently, depending on your setup.

All that aside, from a user perspective, asking them to remember numerous shortcuts to run apps is counter-productive and costly if considered from a life-cycle view, especially on a large scale. This is especially crucial if the key security counter-measure for Windows is the ctrl-alt-del function which is a de facto standard to thwart intercepts, loggers, and the like. Anything similar to that, as in your example, is probably ill-advised and confusing.

So, assuming your setup were to remove the command prompt and the run command from the start menu as part of its applied policy to every workstation, you'd wan't a similar, although less known but convenient way of accessing the command prompt. Your policies would still restrict user intervention, yet provide a way for local support to quickly gain that lovely C:>. It works well from my experience but every network is different.

[ChuckE]

Ah geeze, now you are offended. I wasn't trying to say "my network is bigger than yours" I only stated that the network I work at is large, only to support the fact that I do indeed have large network experience, like for the last 36 years (oh, I'm sorry was that pissing on you again?) Some people will read large network and think 5, 10, maybe 100 computers. No, that is not what I am considering large. Large to me is in the 10's or 100's of thousands of computers. And the bit about my years of experience is only to dissuade someone thinking of only a few years. These are numbers, or relative terms, only to give credence, not pissing, and certainly not to discourage open discussion, and if you can't see the difference then perhaps you ought to find a more kid gloves environment.

Now to the matter at hand.
At no time did I ever give directions to modifying any executable. If you go back and read my tip, it is just a property change to an existing shortcut in a person's Start Menu>Programs>Accessories folder. My way DOES NOT "restrict user intervention" to access the command prompt. Nothing is removed, nothing is relocated, and I'm not taking away anything on any persons PC. Everything remains exactly as before, only a shortcut key is added to an existing shortcut.lnk file. Get your points straight.

In trying to get anyone to remember another shortcut [key sequence] is no different than trying to get them to remember a new right-click item to get to a new addition, where most people seldom even realize the function of many of the right-click menus. Since a person adds the shortcut key sequence (suggested: Ctrl-At-D) to their own repertoire they probably will remember it. It doesn't force that sequence on anybody else. It doesn't conflict with anybody else’s desire to use that same sequence for any other function. What a person adds to their own personal Start menu is theirs to personalize.

And just how much of a security issue is it when you point others to tips of modifying their registry? That is what your tip pointed to.

So my guess is that your initial concern was based on the bad assumption that I suggested modifying, or relocating, or removing, the "cmd.exe" file. I wasn't.

[TOF]

I like the one where I can edit the registry. Thanks!

[jesvingeorge]

press window key + R , type "cmd"

enter

nxt time jst press Winw + R
ent