From: "Andy Willis" Received: from mxout3.mailhop.org ([63.208.196.167] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 310430 for os2-wireless_users@2rosenthals.com; Thu, 24 Aug 2006 12:11:21 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout3.mailhop.org with esmtp (Exim 4.51) id 1GGHVV-000AwZ-Io for os2-wireless_users@2rosenthals.com; Thu, 24 Aug 2006 11:52:38 -0400 Received: from nf-out-0910.google.com ([64.233.182.188]) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1GGHVP-000CgS-Vo for os2-wireless_users@2rosenthals.com; Thu, 24 Aug 2006 11:52:32 -0400 Received: by nf-out-0910.google.com with SMTP id g2so680451nfe for ; Thu, 24 Aug 2006 08:52:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=IAOrbclGh5nGwJh8pKY2ZZHXO9GzZSPazkKBybUk3lwhfnsETcJfwl/x5DfsqvyzULmIyCilj0matFRJgbWO06kPyNz1lGeA0j/OgNhMmTJYklsh72iZRM7o1t2ginq/xJqHYpJ3FJXt7+NHWC1jvdxr51/uTMEPAT3CgZ3bwuc= Received: by 10.67.93.6 with SMTP id v6mr1099804ugl; Thu, 24 Aug 2006 08:52:22 -0700 (PDT) Received: from ?192.168.0.2? ( [71.208.172.119]) by mx.gmail.com with ESMTP id 11sm1370811hug.2006.08.24.08.52.21; Thu, 24 Aug 2006 08:52:22 -0700 (PDT) Message-ID: <44EDCB33.30800@gmail.com> Date: Thu, 24 Aug 2006 09:52:19 -0600 Reply-To: abwillis1@gmail.com User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a1) Gecko/20060823 SeaMonkey/1.5a MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]Re: Genmac problems References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.5 (--) Christian Langanke wrote: >> It doesn't have to necessarily be at the top.. it has to be in front of >> certain other lines so top makes sure that is the case. I don't recall >> which lines but it is documented. >> Andy > > Tru. the helper has to be available when netbind is called. Unfortutantely > it is not sufficient to place the helperw run command exactly before > netbind, as then it does not have enough time to get ready before the next > command. So there needs at least one or two run or start commands in > beetween them. If tha is not the case, netbind will just hang (usually not > trap BWT). > > To play safe, helperw.exe is placed at the top of config.sys. > Theoretically even this may not suffice, depending on the system > configuration. Unfortunatley the author was not willing to code the helper > and the driver a way that at least something more meaningful than just a > hang happens, even though the problem was pretty clear. I'd say an error > message or at least a beep would be great, and then the boot should a > least continue. > > BTW, for the current problem it should be checked for if the trap occurrs > during netbind, so ALT-F2 should be pressed and watched out for the last > successful command before the trap (if possible). Is it really netbind > being executed while the trap happens ? > > bye, Christian > From a user perspective... it may be possible to CALL instead of RUN helperw. It would still have to be in place prior to netbind but the difference is that it could be right before netbind. CALL waits for a completion message, whereas RUN continues without it. If you make changes via mpts then mptstart.cmd line becomes a CALL line. At Warpstock 2002 it was suggested (though stated not supported) that for better boot performance to change that to a RUN. I have't tried changing helperw to CALL yet, I suppose it could just hang there waiting for something that won't occur. Guess I'll try that here and see. Andy