Re^4: WindowsRegistry{ServiceName} V.S. wmic{ServiceName}

Sorry - that is a bit deeper into the network stack and Registry interaction than I have dived.

In fact, I am not comfortable with the code I posted, because I do not understand the interaction between "wmic nic" information and the registry location (which was pointed out by ikagami, I believe. To me, the code is a hack, and there ought to be a better way (but I do not have the time or motivation to research it).

I'm not sure it is meaningful to invent and attach GUIDs to devices that Windows does not care enough about to assign GUIDs.

"As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom

Comment on Re^4: WindowsRegistry{ServiceName} V.S. wmic{ServiceName}

Replies are listed 'Best First'.
Re^5: WindowsRegistry{ServiceName} V.S. wmic{ServiceName} by ddn123456 (Pilgrim) on Sep 21, 2007 at 07:06 UTC
Hi, At the locations below you can find the doc behind the device driver related registry relationships. The DevCon command-line utility functions as an alternative to Device Manager Device Identification Strings Device Driver Tools and Settings (including the win32 registry locations) With kind regards. ddn123456	[reply]