Can't run external app from command line

I can run this command successfully from the DOS command:

flashfxp.exe -download POWDB -remotepath="test.ps1"

However, when I try to run this from the Powershell prompt,
../flashfxp.exe -download POWDB -remotepath="test.ps1"

I get the continuation prompt on the next line. If I remove the double-quotes
from the last parm, the app sees the 2nd and 3rd parms as a single parm and
fails. If I substitute the double with single quotes, I still get the
continuation line.

What am I missing here? Thanks Flomo
--

Have you tried ./flashfxp.exe "-download POWDB -remotepath='test.ps1'"

"Flomo Togba Kwele" <Flomo@community.nospam> wrote in message
news:Tu6dnfP7GNG11afbnZ2dnUVZ_rGinZ2d@giganews.com...
>I can run this command successfully from the DOS command:
>
> flashfxp.exe -download POWDB -remotepath="test.ps1"
>
> However, when I try to run this from the Powershell prompt,
> ./flashfxp.exe -download POWDB -remotepath="test.ps1"
>
> I get the continuation prompt on the next line. If I remove the
> double-quotes
> from the last parm, the app sees the 2nd and 3rd parms as a single parm
> and
> fails. If I substitute the double with single quotes, I still get the
> continuation line.
>
> What am I missing here? Thanks Flomo
> --
>

Really funny. I have a version that should work

flashfxp.exe -download POWDB '-remotepath="test.ps1"'

but I can't tell why your version fails. I've played around a little bit
with your commandline and found out that the misbehavior is bound to both the
- in front of remotepath and the . within the quotes.

This type of commandline always fails
any.exe -x="."
but I'm not aware of any syntactical rules that may cause this behavior. As
long as nobody can explain that, I would rate it as a bug.

Gerd


"Flomo Togba Kwele" wrote:

> I can run this command successfully from the DOS command:
>
> flashfxp.exe -download POWDB -remotepath="test.ps1"
>
> However, when I try to run this from the Powershell prompt,
> ../flashfxp.exe -download POWDB -remotepath="test.ps1"
>
> I get the continuation prompt on the next line. If I remove the double-quotes
> from the last parm, the app sees the 2nd and 3rd parms as a single parm and
> fails. If I substitute the double with single quotes, I still get the
> continuation line.
>
> What am I missing here? Thanks Flomo
> --
>
>

Thanks to you both for your ideas. Brandon, when I try to embed all the
arguments in double-quotes and the last argument in single-quotes, the app sees
it as a single parameter and fails.

Gerd, when I tried your suggestion, the app said it "Cannot open file".

It sure would be nice to see what data Powershell is supplying to the app. I
can't get this information from FlashFxp.

Flomo

"Flomo Togba Kwele" <Flomo@community.nospam> wrote in message
news:Tu6dnfP7GNG11afbnZ2dnUVZ_rGinZ2d@giganews.com...
>I can run this command successfully from the DOS command:
>
> flashfxp.exe -download POWDB -remotepath="test.ps1"
>
> However, when I try to run this from the Powershell prompt,
> ./flashfxp.exe -download POWDB -remotepath="test.ps1"
>
> I get the continuation prompt on the next line. If I remove the
> double-quotes
> from the last parm, the app sees the 2nd and 3rd parms as a single parm
> and
> fails. If I substitute the double with single quotes, I still get the
> continuation line.
>
> What am I missing here? Thanks Flomo

I think this might work (subsitute flasfxp for echoargs):

280# echoargs.exe -download POWDB '-remotepath=\"test.ps1\"'
Arg 0 is "-download"
Arg 1 is "POWDB"
Arg 2 is "-remotepath="test.ps1""

Note that echoargs.exe comes with PSCX 1.1:

http://www.codeplex.com/powershellcx

--
Keith

Keith,

Thanks for the tip about pscx and echoargs - exactly what I asked for.

I ran per you suggestion, and it got further than before. But now it needs an
output spec. Here is my attempt:

32# echoargs.exe -download POWDB '-remotepath=\"test.ps1\"'
'-localpath=\"c:\temp\test.ps1\"'
Arg 0 is "-download"
Arg 1 is "POWDB"
Arg 2 is "-remotepath="test.ps1""
Arg 3 is "-localpath="c:\temp\test.ps1""

When I do the transfer through the GUI app, it splits the transfer into Source
and Target.
Source-Name = test.ps1
Source-Path = g:/Backup/
Target-Name = test.ps1
Target-Path = C:\TEMP\
The transfer works just fine.

When I do it with the commmandline as the echoargs above:
Source-Name = " #(That's a double-quote)
Source-Path = \"test.ps1\
Target-Name = "
Target-Path = \"c:\temp\test.ps1\

What echoargs sees doesn't translate too well with what the app sees.

"Flomo Togba Kwele" <Flomo@community.nospam> wrote in message
news:i_Gdnck7PJmZFqfbnZ2dnUVZ_veinZ2d@giganews.com...
> What echoargs sees doesn't translate too well with what the app sees.
>

What happens if you try it without the \" around the paths?

--
Keith

Keith,

That did it! Thanks so much for all your help.

Flomo

37# echoargs.exe -download POWDB '-remotepath="test.ps1"'
'-localpath="c:temp\test.ps1"'
Arg 0 is "-download"
Arg 1 is "POWDB"
Arg 2 is "-remotepath=test.ps1"
Arg 3 is "-localpath=c:temp\test.ps1"