In <list-309591@2rosenthals.com>, on 08/24/06
at 11:06 AM, "Christian Langanke" <os2-wireless_users@2rosenthals.com>
said:
>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.
That's unfortunate.
Given this, I guess the best solution is to provide a delay after helperw
is started, as in
RUN=helperw.exe
CALL=CMD.EXE /C \DELAYFOR.CMD 2
or if it is too soon to run a REXX script the delay will need to be
implemented by an executable as in
RUN=helperw.exe
CALL=\DELAYFOR.EXE 2
If helperw has a public interface, the delay app could determine if
helperw is loaded and ready.