Powershell

[praecorloth]

Powershell's errors are incredibly verbose. Unfortunately they're also content-free, making them completely useless.

Comments

[maekern]

Example?

[praecorloth]

mount z: "\\server\share\"

New-PSDrive : Cannot find a provider with the name '\\server\share'. The name is not in the proper format
. A provider name may only be alpha-numeric characters or a Windows PowerShell snap-in name followed by a single '\' followed by alpha-numeric characters.
At line:1 char:6
+ mount <<<< z: "\\server\share"
+ CategoryInfo : ObjectNotFound: (\\server\share:String) [New-PSDrive], ProviderNotFoundException
+ FullyQualifiedErrorId : ProviderNotFoundBadFormat,Microsoft.PowerShell.Commands.NewPSDriveCommand

Sorry if the paste is fail. Y'know, Windows command shells 'n all that.

[chardin]

Did you remove the double quotes from the "\\server\share\" thing?

[praecorloth]

Y'know, I didn't do that. But it wouldn't make sense for me to try that since neither PowerShell nor cmd recognize paths with spaces in them if you don't have them in quotes.

[maekern]

Kind of like how if you mistype or improperly construct the arguments for "net" it just gives you the help instead of saying what was wrong?

[praecorloth]

Different from this, though this is pretty faily.