>>
> From a user perspective... it may be possible to CALL instead of RUN
> helperw.
sorry, this won't work because helperw will no and _may_ not return.
But this gives me the idea to have another executable in between, being
started with CALL, launching helperw asynchronously and then wait for it.
So you gave a good hint anyway :-)
I am not sure how this executable would wait for helperw though. Just
checking the pocess status list and additionally wait one or two secs may
be good enough. Better would be if an API of the helperw could be called
to make sur it is up _and running_.
bye, Christian
-------------------------------------------------
Christian Langanke
COS2E & CWSE
Team OS/2 Ruhr e.V.
cla@clanganke.de