Can't find CMD only Powershell...

[benga]

It's so annoying, I shift right click on folders and stuff and the only option I get is for Powershell. I'll hit File on the top left of the window and it'll give me the Powershell option instead of CMD prompt. I can't figure out how to switch paths from C: drive to D: drive either. Can someone explain to me how I can switch all this powershell back to cmd prompt? and also how I switch paths to my D: drive

[AlTech]

1 minute ago, benga said:

It's so annoying, I shift right click on folders and stuff and the only option I get is for Powershell. I'll hit File on the top left of the window and it'll give me the Powershell option instead of CMD prompt. I can't figure out how to switch paths from C: drive to D: drive either. Can someone explain to me how I can switch all this powershell back to cmd prompt? and also how I switch paths to my D: drive

powershell is better than CMD imho.

 

also for switching drives use cd /d [Your Directory]

[Theguywhobea]

You can switch to your D drive by typing "D:" and hitting enter.

[2FA]

EDIT: nvm realized it's Windows 7

[samcool55]

You can use CMD commands in powershell so it shouldn't matter...

[benga]

6 minutes ago, AluminiumTech said:

powershell is better than CMD imho.

 

also for switching drives use cd /d [Your Directory]

It may well be but for some reason the task im trying to execute won't work in powershell

6 minutes ago, Theguywhobea said:

You can switch to your D drive by typing "D:" and hitting enter.

I got nothing to hide buddy, call me retarded lol

5 minutes ago, 2FA said:

This only replaces it when you press Win + X
But knowing how to redirect helped so that's good

3 minutes ago, samcool55 said:

You can use CMD commands in powershell so it shouldn't matter...

for some reason the task im trying to execute won't work in powershell

[AlTech]

13 minutes ago, benga said:

It may well be but for some reason the task im trying to execute won't work in powershell

I got nothing to hide buddy, call me retarded lol

This only replaces it when you press Win + X
But knowing how to redirect helped so that's good

for some reason the task im trying to execute won't work in powershell

have you tried opening cmd as usual and then cd to that directory?

[benga]

26 minutes ago, AluminiumTech said:

have you tried opening cmd as usual and then cd to that directory?

Yea that worked

[erniuss]

15 hours ago, samcool55 said:

You can use CMD commands in powershell so it shouldn't matter...

This is plain and simply wrong. PowerShell and CMD can and does vastly different things when fed the same commands.

You can however open CMD from PowerShell by typing "cmd" and hitting enter to use CMD within PowerShell within the same directory as PowerShell has loaded, else "start cmd" to start a command prompt.

[samcool55]

21 minutes ago, erniuss said:

This is plain and simply wrong. PowerShell and CMD can and does vastly different things when fed the same commands.

You can however open CMD from PowerShell by typing "cmd" and hitting enter to use CMD within PowerShell within the same directory as PowerShell has loaded, else "start cmd" to start a command prompt.

Well i don't know many CMD commands but they do exactly the same in  powershell so i dunno...

Which commands act differently then? 

[erniuss]

11 minutes ago, samcool55 said:

Well i don't know many CMD commands but they do exactly the same in  powershell so i dunno...

Which commands act differently then? 

How can you be so sure if you don't know many CMD commands?
I can't come up with an example off the top of my head but I have definitively ran into that issue myself so I can personally attest to it.

[samcool55]

37 minutes ago, erniuss said:

How can you be so sure if you don't know many CMD commands?
I can't come up with an example off the top of my head but I have definitively ran into that issue myself so I can personally attest to it.

Because my teacher told me everything from CMD works in powershell because the powershell commands that were also in CMD get an alias that matches, so if you call a CMD command it basically calls the powershell equivalent that functionally does exactly the same but just has a powershell equivalent.

 

ipconfig for example basically calls get-network whatever stuff because ipconfig is an alias of that cmdlet.

[erniuss]

1 minute ago, samcool55 said:

Because my teacher told me everything from CMD works in powershell because the powershell commands that were also in CMD get an alias that matches, so if you call a CMD command it basically calls the powershell equivalent that functionally does exactly the same but just has a powershell equivalent.

 

ipconfig for example basically calls get-network whatever stuff because ipconfig is an alias of that cmdlet.

Here's an example. Make two text files on your desktop, a.txt and b.txt, in a.txt type "a", in b.txt type "b" and save the changes. Now, in CMD type "copy *.txt out.txt", now your out.txt will look like "a\r\nb" (\r\n = linebreak), but if you do the same with PowerShell it will just output "b" and not "a".