driver loading sequence

I have driver A,B and C. A depends on B and B depends on C. So
obviously I will load C first and then B and then A. When C is ready,
it will set an event using SetEvent function to tell B, so does B. B
will wait C's event in init to finish its initialization. So does A.

But I found that waiting an event calling WaitforSingleOject isn't a
good idea in the init function. this will slow down the whole system's
booting up.

any good approach to this issue?

thanks,

Mike

.

Relevant Pages

  • Re: Device Driver for WatchDog using WIN CE 4.2
    ... Why are you "unable to use activatedeviceEx"? ... Does your driver's init function ... Do you have entries in the registry for the driver? ... beitman AT applieddata DOT net ...
    (microsoft.public.windowsce.embedded)
  • Re: driver loading sequence
    ... good idea in the init function. ... booting up. ... them and call the init functions in the correct sequence and you can know ... layered driver model like that would be an exceptionally rare thing. ...
    (microsoft.public.windowsce.platbuilder)
  • RE: RegisterDevice failed !!!
    ... And in my source code declare the init function as ... PVOID Context ... >> when the CE platform load the driver, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: DLL initialization help
    ... > But I got error mesg from tcl interpreter as: ... The _Init function is called automatically when you load the dll. ...
    (comp.lang.tcl)