Thanks for catching the documentation error -- we changed the name at some point and didn't update the docs. I'll forward that on. Re: key linkage, you need to #include <initguid.h> in exactly one file and it needs to be done ahead of the header that defines the keys. One strategy is to have one c or cpp file in your project (e.g. guids.cpp) that does nothing but include initguid.h and any headers that define guids and propertykeys, e.g. #include <initguid.h> #include <mmdeviceapi.h> #include <propkeys.h>, etc. Hopefully that helps... Regards, Mitch Rundle Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. ________________________________ From: wdmaudiodev-bounce@xxxxxxxxxxxxx On Behalf Of Alexandra Schoepel (Ally) Sent: Friday, September 15, 2006 3:56 PM To: wdmaudiodev@xxxxxxxxxxxxx Subject: [wdmaudiodev] PKEY_AudioEndpoint... Hi guys, FYI, the documentation shows PKEY_AudioEndpoint_PhysicalSpeakerConfig, but the actual header declares it as PKEY_AudioEndpoint_PhysicalSpeakers. (I am assuming that the meaning is synonymous?!) Also, there is no linkage to the definition of the PROPERTYKEY itself (again EXTERN_C) -- so I've had to define it locally based on the GUID information from the header for now. Thanks, Ally ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/