View previous topic :: View next topic |
Author |
Message |
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Fri Apr 07, 2017 1:30 pm Post subject: |
|
|
I have done now further investigations on the problem with START_PROCESS@ and Error 740.
The app which should be started by START_PROCESS@ has an UAC symbol in its icon and the "Properties" of the app have no "Compability" tab. So I can't remove this administrator privilege.
Even if I delete the app and rebuild it, I get the same behaviour.
This appears only for the 32-bit release of my project.
The 64-bit release is working without problems. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7927 Location: Salford, UK
|
Posted: Fri Apr 07, 2017 2:03 pm Post subject: |
|
|
I am willing to do some testing if you can provide some code that illustrates the failure. I am assuming that you are using Windows 10. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sat Apr 08, 2017 3:09 pm Post subject: |
|
|
Paul,
I have sent an example to your e-mail address. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Sun Apr 23, 2017 12:46 pm Post subject: |
|
|
Paul,
I have solved the problem by using ShellExecuteEx. I have build a small function START_MY_PROCESS which works like START_PROCESS@ and has no problem with my examples.
If you are interested in the solution, I can send the source code to you. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7927 Location: Salford, UK
|
Posted: Mon Apr 24, 2017 6:44 am Post subject: |
|
|
Thank you. That would be useful. |
|
Back to top |
|
|
dpannhorst
Joined: 29 Aug 2005 Posts: 165 Location: Berlin, Germany
|
Posted: Mon Apr 24, 2017 8:19 am Post subject: |
|
|
I have sent the example to your e-mail address. |
|
Back to top |
|
|
silicondale
Joined: 15 Mar 2007 Posts: 248 Location: Matlock, Derbyshire, UK
|
Posted: Mon May 01, 2017 1:35 pm Post subject: |
|
|
I am using START_PROCESS@ in FTN95 v8.0 with no problems. 32-bit calling 32-bit, on Windows 10.
Never heard of START_PROCESS_AND_WAIT@ - how does that differ, if at all, from START_PROCESS@ where the calling program waits for the called process to finish? |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7927 Location: Salford, UK
|
Posted: Mon May 01, 2017 1:49 pm Post subject: |
|
|
They serve the same purpose and are coded in much the same way but START_PROCESS_AND_WAIT@ is for Windows (e.g. ClearWin+) applications where an internal "temporary yield" is required in order to process the Windows message loop. |
|
Back to top |
|
|
silicondale
Joined: 15 Mar 2007 Posts: 248 Location: Matlock, Derbyshire, UK
|
Posted: Mon May 01, 2017 1:56 pm Post subject: |
|
|
Thanks, Paul. My 'parent' application is Windows/Clearwin+ and START_PROCESS@ works just fine (The 'child' process is a command-window program). But maybe I should really be using START_PROCESS_AND_WAIT@ -- will try it and see if it runs any differently! |
|
Back to top |
|
|
|