WMI and GUIDs

Hi,

I am looking into adding WMI to a KMDF PCIexpress driver. Before I get started
(particularily before I get started in the wrong direction), I have a question
regarding GUIDs. I don’t see the answer really spelt out in Oney’s book, for example.

Do I need a separate GUID for the Dynamic Provider or can I use the same GUID I
use to identify the driver interface to application software (i.e. does Windows
have different namespaces for interfaces and WMI)?

If I can use the same GUID, is it a good idea, a bad idea or does it really matter?

Background is, I don’t want to unnecessarily contribute to filling up people’s
registries. I find them big enough as they are.

Thanks,
Charles

Better to use a diff value than the device interface guid. Don’t worry about the size of the change to the registry.

d

debt from my phone

-----Original Message-----
From: Charles
Sent: Sunday, June 19, 2011 12:17 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] WMI and GUIDs

Hi,

I am looking into adding WMI to a KMDF PCIexpress driver. Before I get started
(particularily before I get started in the wrong direction), I have a question
regarding GUIDs. I don’t see the answer really spelt out in Oney’s book, for example.

Do I need a separate GUID for the Dynamic Provider or can I use the same GUID I
use to identify the driver interface to application software (i.e. does Windows
have different namespaces for interfaces and WMI)?

If I can use the same GUID, is it a good idea, a bad idea or does it really matter?

Background is, I don’t want to unnecessarily contribute to filling up people’s
registries. I find them big enough as they are.

Thanks,
Charles


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

One of the common design failures is “I don’t want to make X too big” for
some kind of X. The correct answer is, X should be as big as it needs to
be, but no bigger (paraphrasing Einstein, here), but coming up with some
weird shortcut that saves nearly-unmeasurably-small amounts of whatever your
metric is, while compromising correctness, is not the right solution, ever.
And while part of the art-and-craft of programming is creating ideal
representations that solve the problem that needs to be solved without
excessive resource consumption (be it time, code space, memory space, page
faults, Registry size, or whatever), the solution must still be *correct*.
Trying to use the same GUID as is used for another purpose is not a good
solution, because it can lead to unfortunate consequences later. Maybe not
in this release, but perhaps in the next OS release. Better to ignore
trivia and build a robust solution.

You might check out my essay, “Optimization, your worst enemy”, at
http://www.flounder.com/optimization.htm
joe

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: Sunday, June 19, 2011 5:25 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] WMI and GUIDs

Better to use a diff value than the device interface guid. Don’t worry about
the size of the change to the registry.

d

debt from my phone

-----Original Message-----
From: Charles
Sent: Sunday, June 19, 2011 12:17 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] WMI and GUIDs

Hi,

I am looking into adding WMI to a KMDF PCIexpress driver. Before I get
started
(particularily before I get started in the wrong direction), I have a
question
regarding GUIDs. I don’t see the answer really spelt out in Oney’s book, for
example.

Do I need a separate GUID for the Dynamic Provider or can I use the same
GUID I
use to identify the driver interface to application software (i.e. does
Windows
have different namespaces for interfaces and WMI)?

If I can use the same GUID, is it a good idea, a bad idea or does it really
matter?

Background is, I don’t want to unnecessarily contribute to filling up
people’s
registries. I find them big enough as they are.

Thanks,
Charles


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


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.