https://forge.codesys.com/forge/talk/Engineering/thread/ced8df3f5e/2020-02-27T14:21:40.815000ZRecent posts to [WINDOWS] Calling external programs: SysProcessCreate2 or _ ?2020-02-27T14:21:40.815000Z2020-02-27T14:21:40.815000Zi-campbellhttps://forge.codesys.com/u/i-campbell/https://forge.codesys.com0105755a79c06ed15eb03290f475b7bf22899501

<div class="markdown_content"><p>It is as you have said.</p> <p>And yes, it is a known bug with _ when used in the forum.</p> <p>As such the entire forum will be moved to a new platform, forge.codesys.com, should be this weekend. I have tested, and you can say _ on the newer platform. In fact, the new platform gives other improvements too.</p></div>

2020-02-27T14:21:39.663000Z2020-02-27T14:21:39.663000Zandre-tepromhttps://forge.codesys.com/u/andre-teprom/https://forge.codesys.comd670262f489545815be02ed4778c867832f11617

<div class="markdown_content"><p>Hi there,</p> <p>I have seen both above functions being called to instantiate programs from Codesys, but I could not get what is the main advantages and drawbacks for each case. Do the <strong>SysProcessCreate2</strong> instantiate a program which stay resident at the OS whereas the SysProcess ExecuteCommand2 just make a callback to the command at its argument?</p> <p>Once I'm out of office, for while I'm unable to taste the differences among both functions.</p> <p>Thanks in advance,<br/> Andre.</p></div>