is anyone able to use the /output  refinement of CALL within an encapped app?  
I've tried using different encappers and it just doesn't work for me.  the exact same call string on my rebol console works fine.
and if I remove the /output refinement it also works in the encapp.
but when encapped and using /output,  it runs the call, and then it just hangs. (forever).
I'm running windows 7
Maxim, I had an app that did:
call/output/error join {md5 -d} [{"} p  {"}] myout  error
I'm afraid I haven't run the app since March 2011. It did work though. I was using encmdview.exe version 2.7.6.
Not sure I tested it on Win 7 either.
I've been testing for a while now, and the same script runs when I launch it from within ultra-edit, and it fails when I try to launch it from the explorer... this is really strange.
Hope you can figure it out. Also glad to hear you're an Ultra-edit guy. I've been using this ancient version :-)
Before you beat your head on it too much, it might be useful to try it (if you can) on Windows XP.  If it works there but not on Windows 7, then you have a clearer idea of what you are up against.  I still am struggling to have a REBOL program call a Powershell script on Windows 7.  It works fine on XP.
another detail, it works if launched from within a command prompt...
This seems more and more related to the defective piping in windows graphical environments.
btw, sometimes specifying an /input   with a value of "^/^/^^/" solves a few command line apps which start asking for returns when they generate an error... I had this problem with a version of ssh I was using a while ago.
I used CALL with /output on XP soon. It works fine.
And my customers OS is Win7, and it works there too, after try a bit more.

Last message posted 49 weeks ago.