Eugene Muzychenko wrote:
Hello Tom,Could someone from Microsoft please confirm if the same is true for a 64-bit install of Vista? Or are the shut down altogether?64-bit MME drivers are not fully supported even in 64-bit XP and 2003 Server. In these systems, 64-bit user-mode MME drivers are not loaded for 32-bit applications (WOW64). In Vista, winmm.dll does not look for "waveN" entry, only for the single "wave" entry. If you replace "wdmaud.drv" with your driver file name, your driver will be invoked but other drivers, including WDM ones, will not be invoked. Regards, Eugene
Eugene,Thanks for the reply. Have you successfully loaded a user mode MME driver in x64 Vista? I tried putting a 64 bit version in Drivers32 and a 32 bit version in SysWOW64 (with the same filename) and changed the wave entry in SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 and SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 but I still only see wdmaud exposed devices in 32 or 64 bit apps with waveOutGetNumDevs() waveOutGetDevCaps().
If I delete these registry entries entirely the wdmaud devices still show up.
Is there some background process "fixing" the edited registry entries?Hakon Strande at MS suggested that I needed to sign the user-mode driver but according to the white paper "Code Signing for Protected Media Components in Windows Vista": "Note: If your component processes only unprotected content---for example, WAV decoding---and the processing is done outside the PE, a PMP-PE certificate is not required." Do these modules need to be signed even if I don't need a PMP-PE cert? Even if I'm running with the kernel mode debugger attached via 1394?
Thanks, Tom
