We have had similar problems with Windows 7 and Windows Server 2008R2. I thought it was a new security "feature". Starting the app from a command shell works fine. Setting compatibility options and "run as administrator" doesn't help.
Gab, It crashes (freezes) with the console open. currently, it really requires /show if using the R2 CALL func.
otherwise pre-pending "CMD /C" to the command while using cheyenne's win-call also works, but has the advantage of not showing a dos prompt at each execution.
this works from 220.127.116.11.1 get-env "%userprofile%" but in my SdK I get none. Ideas
ah.. works without the %
so small difference between the sdk and core
Here is working example on Win7: stdout: make string! 255 call/wait/output rejoin [to-local-file system/options/path %\extract.exe " mypassword"] stdout
I remember that CALL supports rebol style file names, but it sometimes fail to run the app. So to put TO-LOCAL-FILE is good. But in this example extract.exe is a Win32 application that outputs to stdout, not a real DOS app. This might be a difference.
anything, so I guess the parameters being used by win-call when the launch process is being done are different.
Did Carl release the CALL source at one point, to get input and help on it?
Only talked about that, I think
Anybody ever tried signing an encapped REBOL binary (R2) for the Mac? With Gatekeeper coming distribution of REBOL application will be dead in the water. OTOH: if we can get it working, I see a productivity boon for a whole suite of Desktop "Apps".