When system boots up, the order of drivers being loaded is determined by the
"Order" in registry setting (platform.reg).

But which factor/component determines the order of driver being unloaded
when system suspends?

Any documents describes this ? Thanks !

Re: Driver unload order when system suspends by Jeff

Jeff
Sat Oct 18 13:31:30 CDT 2003

Drivers do not get unloaded when the system suspends. Some drivers will get
unloaded and reloaded when the system wakes up after having been suspended.
Those cases should only be for devices on hot-plug busses and the unload
order will depend on the bus. In any case, hot-plug busses don't usually use
the Order value even for driver loading. Order is used in the regenum driver
because keys in the registry cannot be enumerated in any guaranteed order.

The deal is that fixed drivers may have dependency relations among them and
the Order value is used to avoid breaking those relations. Drivers on
hot-plug busses cannot have fixed dependency relations because they can be
installed in any order physically permitted by the bus. Hence, the bus's
physical restrictions apply and there is no need (and sometimes no meaning)
for a static Order setting.

- Jeff.

"Lee Guo-hua" <ghlee@csie.nctu.edu.tw> wrote in message
news:bmqudk$23vr$1@netnews2.csie.nctu.edu.tw...
>
> When system boots up, the order of drivers being loaded is determined by
the
> "Order" in registry setting (platform.reg).
>
> But which factor/component determines the order of driver being unloaded
> when system suspends?
>
> Any documents describes this ? Thanks !
>
>
>
>
>
>
>
>
>



Re: Driver unload order when system suspends by Lee

Lee
Sat Oct 18 20:34:13 CDT 2003



My original problem should be corrected as:

When system boots up, the order of built-in drivers being loaded is
determined by the "Order" in registry setting (platform.reg).

But which factor/component determines the order of driver power handler
being called when system suspends/resumes?

Any documents describes this ? Thanks !


Jeff Rosenfeld <spamophobe@comcast.net> wrote:
> Drivers do not get unloaded when the system suspends. Some drivers will get
> unloaded and reloaded when the system wakes up after having been suspended.
> Those cases should only be for devices on hot-plug busses and the unload
> order will depend on the bus. In any case, hot-plug busses don't usually use
> the Order value even for driver loading. Order is used in the regenum driver
> because keys in the registry cannot be enumerated in any guaranteed order.
> The deal is that fixed drivers may have dependency relations among them and
> the Order value is used to avoid breaking those relations. Drivers on
> hot-plug busses cannot have fixed dependency relations because they can be
> installed in any order physically permitted by the bus. Hence, the bus's
> physical restrictions apply and there is no need (and sometimes no meaning)
> for a static Order setting.
> - Jeff.
> "Lee Guo-hua" <ghlee@csie.nctu.edu.tw> wrote in message
> news:bmqudk$23vr$1@netnews2.csie.nctu.edu.tw...
> > When system boots up, the order of drivers being loaded is determined by
> the
> > "Order" in registry setting (platform.reg).
> > But which factor/component determines the order of driver being unloaded
> > when system suspends?
> > Any documents describes this ? Thanks !

Re: Driver unload order when system suspends by Jeff

Jeff
Tue Oct 21 01:56:19 CDT 2003

Not sure if it's in the docs, but PowerOn handlers are invoked in load order
(actual load order; registry is not directly relevant for this) and PowerOff
handlers in reverse load order.

- Jeff.

"Lee Guo-hua" <ghlee@csie.nctu.edu.tw> wrote in message
news:bmspml$dmb$1@netnews2.csie.nctu.edu.tw...
>
>
> My original problem should be corrected as:
>
> When system boots up, the order of built-in drivers being loaded is
> determined by the "Order" in registry setting (platform.reg).
>
> But which factor/component determines the order of driver power handler
> being called when system suspends/resumes?
>
> Any documents describes this ? Thanks !
>
>
> Jeff Rosenfeld <spamophobe@comcast.net> wrote:
> > Drivers do not get unloaded when the system suspends. Some drivers will
get
> > unloaded and reloaded when the system wakes up after having been
suspended.
> > Those cases should only be for devices on hot-plug busses and the unload
> > order will depend on the bus. In any case, hot-plug busses don't usually
use
> > the Order value even for driver loading. Order is used in the regenum
driver
> > because keys in the registry cannot be enumerated in any guaranteed
order.
> > The deal is that fixed drivers may have dependency relations among them
and
> > the Order value is used to avoid breaking those relations. Drivers on
> > hot-plug busses cannot have fixed dependency relations because they can
be
> > installed in any order physically permitted by the bus. Hence, the bus's
> > physical restrictions apply and there is no need (and sometimes no
meaning)
> > for a static Order setting.
> > - Jeff.
> > "Lee Guo-hua" <ghlee@csie.nctu.edu.tw> wrote in message
> > news:bmqudk$23vr$1@netnews2.csie.nctu.edu.tw...
> > > When system boots up, the order of drivers being loaded is determined
by
> > the
> > > "Order" in registry setting (platform.reg).
> > > But which factor/component determines the order of driver being
unloaded
> > > when system suspends?
> > > Any documents describes this ? Thanks !