Another thought - I remember from my Unix days that you can put "&" at the end
of a line command to make it run in the background and make it non-blocking. Of
course you have to redirect its output to a text file. Would that work here?
(Probably not on Windows though.)
Just throwing it against the wall to see if it sticks...
Phil Davis
On 10/14/10 2:56 AM, Monte Goulding wrote:
Write a tiny script that does something trivial in shell (e.g. "shell ls"), and
build that as a tiny executable.
Have your real script run that as a separate process and see if it never
returns.
That's not a bad plan.
Cheers
--
Monte Goulding
M E R Goulding Software Development
Bespoke application development for vertical markets
InstallGadget - How to create an installer in 10 seconds
revObjective - Making behavior scripts behave
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
