LoadOrderGroup for PnP driver

NTDEV
1

I’m just trying to resolve some warnings which new HCK generated on our long time used driver INFs. Among others it complains about LoadOrderGroup used for PnP driver ServiceInstall section:

Driver package C:\Windows\Inf\oem5.inf specifies LoadOrderGroup for registration of service WUDFRd display name “Windows Driver Foundation - User-mode Driver Framework Reflector”. This is not recommended.

I guess it is right and it doesn’t make any sense there. But I’m not quite sure, I’ve used it the last time at NT4. Can somebody confirm that removing it doesn’t break anything. The funny this is it was copied from WDK UMDF drivers samples with no change:

[WUDFRD_ServiceInstall]
DisplayName = %WudfRdDisplayName%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WUDFRd.sys
LoadOrderGroup = Base

I just checked and found it is used in 51 of 82 WDK8 samples I have installed…

Michal

NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately.
Thank You!
AuthenTec, Inc. http://www.authentec.com/

2

Vodicka, Michal wrote:

I’m just trying to resolve some warnings which new HCK generated on our long time used driver INFs. Among others it complains about LoadOrderGroup used for PnP driver ServiceInstall section:

Driver package C:\Windows\Inf\oem5.inf specifies LoadOrderGroup for registration of service WUDFRd display name “Windows Driver Foundation - User-mode Driver Framework Reflector”. This is not recommended.

I guess it is right and it doesn’t make any sense there. But I’m not quite sure, I’ve used it the last time at NT4. Can somebody confirm that removing it doesn’t break anything.

Think about this logically. LoadOrderGroup is used to control driver
load order at boot time. That only applies to drivers that are
SERVICE_BOOT_START (that is, StartType=0). For all other values of
StartType, LoadOrderGroup is entirely decorative and always has been.
No one looks at (or for) that value.

The funny this is it was copied from WDK UMDF drivers samples with no change:

Old habits die hard, even when they are pointless. Many INF files still
ship with these lines:
HKR,DevLoader,*ntkern
HKR_NTMPDriver,xxxxx.sys

even though they were only used in the 16-bit systems (Windows 95/98/ME).

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

> -----Original Message-----

From: xxxxx@lists.osr.com [mailto:bounce-502139-
xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Monday, May 07, 2012 7:12 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] LoadOrderGroup for PnP driver

> I guess it is right and it doesn’t make any sense there. But I’m not quite
sure, I’ve used it the last time at NT4. Can somebody confirm that removing it
doesn’t break anything.

Think about this logically. LoadOrderGroup is used to control driver
load order at boot time. That only applies to drivers that are
SERVICE_BOOT_START (that is, StartType=0). For all other values of
StartType, LoadOrderGroup is entirely decorative and always has been.
No one looks at (or for) that value.

Yes, I was thinking the same way but I wasn’t quite sure if something didn’t change and if there isn’t some new meaning. The number of WDK samples using it made me a bit unsure.

Old habits die hard, even when they are pointless. Many INF files still
ship with these lines:
HKR,DevLoader,*ntkern
HKR_NTMPDriver,xxxxx.sys

even though they were only used in the 16-bit systems (Windows
95/98/ME).

I guess you’re right and it is probably pointless remains of the past. I guess WDK team should make their sample at least HCK warning free…

Michal

NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately.
Thank You!
AuthenTec, Inc. http://www.authentec.com/

4

The check is relatively new, we are going through the samples and cleaning them up

d

debt from my phone

From: Vodicka, Michal
Sent: 5/9/2012 9:59 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] LoadOrderGroup for PnP driver

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-502139-
xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Monday, May 07, 2012 7:12 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] LoadOrderGroup for PnP driver

> I guess it is right and it doesn’t make any sense there. But I’m not quite
sure, I’ve used it the last time at NT4. Can somebody confirm that removing it
doesn’t break anything.

Think about this logically. LoadOrderGroup is used to control driver
load order at boot time. That only applies to drivers that are
SERVICE_BOOT_START (that is, StartType=0). For all other values of
StartType, LoadOrderGroup is entirely decorative and always has been.
No one looks at (or for) that value.

Yes, I was thinking the same way but I wasn’t quite sure if something didn’t change and if there isn’t some new meaning. The number of WDK samples using it made me a bit unsure.

Old habits die hard, even when they are pointless. Many INF files still
ship with these lines:
HKR,DevLoader,*ntkern
HKR_NTMPDriver,xxxxx.sys

even though they were only used in the 16-bit systems (Windows
95/98/ME).

I guess you’re right and it is probably pointless remains of the past. I guess WDK team should make their sample at least HCK warning free…

Michal

NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately.
Thank You!
AuthenTec, Inc. http://www.authentec.com/

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

5

OK, thanks. To be fair, we’re speaking about beta software and if it is cleaned till release, it is perfect.

Michal

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Wednesday, May 09, 2012 9:55 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] LoadOrderGroup for PnP driver

The check is relatively new, we are going through the samples and cleaning them up

d

debt from my phone

From: Vodicka, Michal
Sent: 5/9/2012 9:59 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] LoadOrderGroup for PnP driver

-----Original Message-----
From: xxxxx@lists.osr.commailto:xxxxx [mailto:bounce-502139-
> xxxxx@lists.osr.commailto:xxxxx] On Behalf Of Tim Roberts
> Sent: Monday, May 07, 2012 7:12 PM
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] LoadOrderGroup for PnP driver
>
> > I guess it is right and it doesn’t make any sense there. But I’m not quite
> sure, I’ve used it the last time at NT4. Can somebody confirm that removing it
> doesn’t break anything.
>
> Think about this logically. LoadOrderGroup is used to control driver
> load order at boot time. That only applies to drivers that are
> SERVICE_BOOT_START (that is, StartType=0). For all other values of
> StartType, LoadOrderGroup is entirely decorative and always has been.
> No one looks at (or for) that value.

Yes, I was thinking the same way but I wasn’t quite sure if something didn’t change and if there isn’t some new meaning. The number of WDK samples using it made me a bit unsure.

> Old habits die hard, even when they are pointless. Many INF files still
> ship with these lines:
> HKR,DevLoader,*ntkern
> HKR_NTMPDriver,xxxxx.sys
>
> even though they were only used in the 16-bit systems (Windows
> 95/98/ME).

I guess you’re right and it is probably pointless remains of the past. I guess WDK team should make their sample at least HCK warning free…

Michal

NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately.
Thank You!
AuthenTec, Inc. http://www.authentec.com/

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

NOTE: The information in this message is intended for the personal and confidential use of the designated recipient(s) named above. To the extent the recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an obligation of confidentiality, with AuthenTec, then this message and/or any attachments shall be considered confidential information and subject to the confidentiality terms of that agreement. If the reader of this message is not the intended recipient named above, you are notified that you have received this document in error, and any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this document in error, please delete the original message and notify the sender immediately.
Thank You!
AuthenTec, Inc. http://www.authentec.com/</mailto:xxxxx></mailto:xxxxx>