I don't know of a PS internal solution for this problem, but you may try
these workarounds:
1) The PSCX (http://www.codeplex.com/PowerShellCX) contain a CmdLet
"start-process" which can do the job
2) Utilize the Scripting Host:
$shell = new-object -com wscript.shell
$shell.run('calc', $null, $true)
3) Use the System.Diagnostics.Process class
I personally ended up with #2.
Gerd
http://blogs.technet.com/industry_insiders/pages/executing-a-command-line-utility-from-powershell-and-waiting-for-it-to-finish.aspx
--
Richard Siddaway
Please note that all scripts are supplied "as is" and with no warranty
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk
The .NET System.Diagnostics class approach is very informative.
This is important stuff to know to get the power out of PowerShell.
- Doug
"RichS" <Ri...@discussions.microsoft.com> wrote in message
news:0DB496B8-E801-444D...@microsoft.com...