Jump to content
|Topic||Stats||Last action by|
|ESXi 5.5 - My Experience (and some questions)||
|Who is running DNSSEC domains, using validation for thier dns?||
|Download flash video||
|Study on penises reveals the average size ... and it's smaller than you think||
|LAPD Officers Shoot Man Five Times in Broad Daylight||
Posted 31 October 2011 - 00:56
Posted 31 October 2011 - 05:44
You invoke cmd to ping? I just do Windows+R and then ping from the run prompt.
Posted 31 October 2011 - 05:50
Posted 31 October 2011 - 09:44
It seems many people here don't understand what CMD is.
Short explanation: CMD is a console window that provides basic functionality for changing the current directory (cd), showing the files and folders (dir) and a few other things (copy, auto-completion, command history...). The most important thing it does is to enable you to open files, give arguments to executables, and provide input and output for console applications.
What you're doing by calling "robocopy C:\SomeFolder C:\SomeOtherFolder" is launching robocopy.exe using "C:\SomeFolder" and "C:\SomeOtherFolder" as parameters. "tree C:\" just calls tree.com with "C:\" as a parameter. "ping google.com" calls ping.exe with "google.com" as parameter. And so on.
These programs (not commands - check your C:\Windows\System32 folder) can be used exactly the same way in PowerShell, and their output will look exactly the same.
In fact, if Microsoft set the default background color to black in PowerShell and removed the "PS" at the beginning of each line, most people wouldn't notice the difference. You would still be able to use the programs you use now.
cmd of course but Powershell.........Powershell and bash can compete pretty good with each other
cmd and Powershell are like kids toys by comparison
Another good post.
Cmd maybe, but don't think you've actually tried PowerShell or you wouldn't be saying that. It's quite powerful. Bash is good yes,but looking over what Bash has built in, nothing really jumps out as being something that others can't do or just doesn't apply.. most of it's goodies come from external programs or scripting languages, most of which are available to other shells.
I already posted this: http://en.wikipedia....dows_PowerShell
wtf is powershell?
As Aethec said, from CMD you are actually calling other programs. (stated in %PATH) so in a sense you can use all the commands in CMD in Powershell as well. There might be some conflicts with Powershell commands but thats why I stated that if a program calls cmd then executes a command, Powershell should start up in a cmd compatibility mode.
Powershell is NOT a replacement for CMD and ALL commands do not work in the same manner or using the same syntax in the 2 environments. Many of the most commonly used ones do however.
I already commented on this If a program calls cmd then executes a command, Powershell should start up in a cmd compatibility mode. This way it is backwards compatible.
cmd can't be removed as it would break existing scripts and applications that call cmd.
Though PowerShell has aliases for many cmd built-in commands, the cmdlets for which the aliases are mapped do not support the switches of the cmd commands (e.g., you can't do "dir /w" in PowerShell). Variable syntax is also different (e.g., %windir% in cmd vs $env:windir in PowerShell).
That would be the only thing neccesary
PowerShell is getting ever increasing usage as the underpinning for Windows administration and troubleshooting functionality. While it should see greater exposure, such as adding it to the Ribbon and the context menu ("Open PowerShell here"), cmd should not be removed to elevate PowerShell unless the use cases for cmd are covered by PowerShell. It's not like cmd is the only shell besides PowerShell that currently ships with Windows. Its presence doesn't diminish PowerShell.
Obviously since you have no argument, you simply state it is your opinion. While I do find your opinion valid, there is no base to it therfore I can not agree with it.
Let me ask you a question. You made a poll here, right? Then you ask everyone's opinion, when someone gives it you just come with all your love for Powershell. I know the differences between CMD and Powershell and that's why I posted my goddamn opinion.
Posted 31 October 2011 - 09:55
Posted 31 October 2011 - 12:35
1. It will get better
I'd use powershell by default if it:
1. Started up as quickly as cmd
2. Had a convenient and reliable phrase in the start menu. PowerPoint gets in the way!
Posted 03 November 2011 - 23:03
I don't think really think people understand what powershell is. In some ways its more powerful then bash and other ways its more awkward. But I do think it really is getting better/ more powerful with each version. In Windows 8 server powershell knowledge looks like it almost most know.
Posted 05 November 2011 - 19:51
if you do it that way, the cmd window disappears as soon as the pings finish.
Posted 05 November 2011 - 23:29
You ping, you see the response on the screen, and then the screen goes away. I can see special case scenarios where you may want the command window to persist, but for just finding out if a resource is reachable, what is the issue?
Posted 05 November 2011 - 23:42
The issue on all systems I've ever done that on is that the cmd window disappears too quickly to read the results. Is that not the case in your situation??
Posted 05 November 2011 - 23:58
ping address -t
Posted 07 November 2011 - 17:02
You can run any command from the search bar using either CMD or PS:
Ha! Well, you didn't specify that ;-) And the person who posted that method as a suggestion didn't either.
cmd /k ping google.com powershell -noexit -command ping google.comIt opens a new CMD window and executes the command, but doesn't close afterwards.
Posted 08 November 2011 - 10:53
I can see in PATH being stored a variable that if you call CMD or command it executes powershell -noexit -command %s in Windows 8/
You can run any command from the search bar using either CMD or PS:cmd /k ping google.com powershell -noexit -command ping google.comIt opens a new CMD window and executes the command, but doesn't close afterwards.
What he posted or calling cmd from Powershell and Powershell from cmd?
^ nice! Didn't know you could do that.
Posted 08 November 2011 - 10:56