Hi All,
I'm making progress, and now have a skeletal version of my driver, called
"drvtest.dll".
The problem is that it isn't being executed. I've placed it in the
C:\Windows\system32 directory, and also added the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 -
midi2, SZ, drvtest.dll
If however I rename my driver to be the same as an already existing dll,
then it does get executed.
What have I missed?
Kind Regards,
Chris Hubbard,
CH Sound Design.
www.chsounddesign.com
Sent from my abacus.
-----Original Message-----
From: Mike Audet
Sent: Friday, May 25, 2018 4:56 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Developing a "simple" user mode installable MIDI
driver.
It's exactly the same install as the 32 bit version. On a 64 bit
Windows, the registry entry gets redirected. Just do the exact same
thing in the non-redirected key, and it works in 64 bit applications.
I used it to connect the Ensoniq PARIS C16 mixing controller to a host
application using the ASIO driver and either HUI or Mackie Control
emulation. I needed to keep everything in the same process, and it
worked perfectly. I just ported it to 64 bits, and it's all exactly the
same. The DWORDS in the function signatures that hold handles and
pointers need to be updated to DWORD_PTRs (if I remember right), but
everything just worked. I found the updated signatures via a Google
search that took me to the React OS project.
All the best,
Mike
On 5/24/2018 2:39 PM, Tim Roberts wrote:
Mike Audet wrote:
I just finished writing an installable 64 bit MIDI driver. It works fine.You mean a midMessage / modMessage driver? I didn't think there was a
way to install those in the 64-bit world. I had a client who could have
used a waveIn/waveOut thing, and I couldn't make it work.
