From: "Christian Langanke" Received: from mxout2.mailhop.org ([63.208.196.166] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 312983 for os2-wireless_users@2rosenthals.com; Fri, 25 Aug 2006 14:05:01 -0400 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout2.mailhop.org with esmtp (Exim 4.51) id 1GGg38-00069W-9N for os2-wireless_users@2rosenthals.com; Fri, 25 Aug 2006 14:05:01 -0400 Received: from server01.proxy.hosteurope.de ([80.237.136.2]) by mxin2.mailhop.org with esmtp (Exim 4.51) id 1GGg37-000JFF-Ny for os2-wireless_users@2rosenthals.com; Fri, 25 Aug 2006 14:04:57 -0400 Received: from server03.webmailer.hosteurope.de ([10.9.0.182]) by server01.proxy.hosteurope.de with esmtp (Exim 4.50) id 1GGg35-0006Ja-2u for os2-wireless_users@2rosenthals.com; Fri, 25 Aug 2006 20:04:55 +0200 Received: from nobody by server03.webmailer.hosteurope.de with local (Exim 3.35 #1 (Debian)) id 1GGg35-00049d-00 for ; Fri, 25 Aug 2006 20:04:55 +0200 X-submitted-by: 145.254.87.114 using webmailer.hosteurope.de/HTTP at Fri, 25 Aug 2006 20:04:54 +0200 (CEST) Received: from 145.254.87.114 (SquirrelMail authenticated user wp43877-cla) by webmailer.hosteurope.de with HTTP; Fri, 25 Aug 2006 20:04:54 +0200 (CEST) Message-ID: <43877.59374.145.254.87.114.1156529094.squirrel@webmailer.hosteurope.de> In-Reply-To: References: Date: Fri, 25 Aug 2006 20:04:54 +0200 (CEST) Subject: Re: [OS2Wireless]Re: Genmac problems To: "OS/2 Wireless Users Mailing List" Reply-To: cla@clanganke.de User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -1.1 (-) Hi andy, >> > 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