SystemTags() creates a fully functional shell-handler process.
CreateNewProc() just creates a basic generic new DOS process.
SystemTags() actually calls CreateNewProc() internally to start
the shell process up. (FYI).
Since you want the shell-handler to execute a shell script,
a shell-handler process would be my first choice.
Ok, so I applied SystemTags() successfully, meaning the called file gets executed. But now I want to modify the called file in order to make it do something more usefull (Just waiting 5 secs makes not much sense, does it?).
However, upon saving that file I get a message that "the object is in use somewhere and can therefore not be saved". Normally this means that it is opened in MultiView, but that is not the case here.
Is there a Lock() on that file remaining?
EDIT: Yes, there was a Lock still in place, as a left-over from a check-for-excistence.
And there were even a few more Locks in place...
EDIT: Hm, UnLock()-ing these Locks does not change much...
SystemTags() creates a fully functional shell-handler process.
CreateNewProc() just creates a basic generic new DOS process.
SystemTags() actually calls CreateNewProc() internally to start
the shell process up. (FYI).
Since you want the shell-handler to execute a shell script,
a shell-handler process would be my first choice.
Ok, so I applied SystemTags() successfully, meaning the called file gets executed. But now I want to modify the called file in order to make it do something more usefull (Just waiting 5 secs makes not much sense, does it?).
However, upon saving that file I get a message that "the object is in use somewhere and can therefore not be saved". Normally this means that it is opened in MultiView, but that is not the case here.
Is there a Lock() on that file remaining?
EDIT: Yes, there was a Lock still in place, as a left-over from a check-for-excistence.
And there were even a few more Locks in place...
EDIT: Hm, UnLock()-ing these Locks does not change much...
OldFart