I have now recompiled my .dll with this information but still don't know
how to install it on 64-bit xp.
There is a message box poping up during installation:
Driver Error
! Cannot load the driver. The driver file may be missing. Try installing
the driver again, or contact your system administrator. Ok
I have verified that the driver file is copied to the system32 directory
during the installation.
I'm using equal .inf entries for 32-bit and 64-bit in this part of the
installation:
...
[mydriver_64.AddReg]
HKR,,AssociatedFilters,,"wdmaud,swmidi,redbook"
HKR,Drivers,SubClasses,,"wave,midi,mixer"
HKR,Drivers\wave\mydriver_mme.dll,Driver,,mydriver_mme.dll
HKR,Drivers\wave\mydriver_mme.dll,Description,,%mydriver.DeviceDesc%
...
Does anyone know what's going wrong here?
Another open question is if it is possible to install the 32-Bit Version
of the .dll on 64-bit xp.
Uwe
Ron Kuper wrote:
If you look in the latest Platform SDK headers, parameters like this are
declared a DWORD_PTR instead of DWORD. DWORD_PTR is a typedef that
compiles differently depending on whether you have chosen a 32-bit or a
64-bit OS.
-----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Waldemar Haszlakiewicz Sent: Tuesday, January 11, 2005 9:08 AM To: uwe kirst Subject: [wdmaudiodev] Re: WIDM, WODM definition for 64-bit XP?
Well shouldn't there be a 64bit SDK/DDK?
uk> Hello, uk> How is the WIDM and WODM for 64-bit windows defined? uk> Here is a qote form the msdn library online doc (32-bit version). uk> It's about the WIDM_OPEN message:
uk> "dwParam1
uk> Specifies a pointer to a WAVEOPENDESC structure containing the uk> client's device handle, notification target, and instance
identifier."
uk> So how can a DWORD contain a pointer on 64-bit windows? uk> Uwe
uk> ******************
uk> WDMAUDIODEV addresses: uk> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx uk> Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe uk> Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe uk> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
uk> URL to WDMAUDIODEV page: uk> http://www.wdmaudiodev.de/
******************
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.de/
******************
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.de/
******************
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.de/
