dxd - dynax driver framework 2.1.0d48
cross platform open source driver development framework
No Matches
Build Environment

All Platforms

IOKit Kernel Extension Framework

WDK - Windows Driver Framework

  • Windows 10
  • WDK10 + VS2019
  • Wix3.11 Windows XML Installer framework
    Additional information about the log file created during Windows SetupAPI installation http://download.microsoft.com/download/e/b/a/eba1050f-a31d-436b-9281-92cdfeae4b45/SetupAPILog.doc
  • signing certificate
    • get a code signing certificate
    • deprecated: install MS cross signed certificate in [WDK root]\CrossCertificates:
      • http://msdn.microsoft.com/en-us/library/windows/hardware/hh967734(v=vs.85).aspx
      • signtool.exe does not seem to be able to find the cross signing certificates by itself from the Windows cert stores. Instead the WDK comes with a pre-selected choice of the obove certifcates "installed" @
        Program Files (x86)/Windows Kits/10/CrossCertificates
        Instead of explicitly selecting your cross certifiacte by filename as a command line option to signtool.exe you may consider adding your specific cross signing certificate to this path and therefor preparing the machine to find the correct certifacte for kernel code signing.
    • deprecated: allow cross signed drivers @ Windows 10
    • display your installed signing certificate(s)
      certutil -store -user My
    • install your signing certificate .pfx (.p12) with double click or
      certutil -user -p CertificatePassword -importPFX .pfx/.p12
    • install your signing certificate under the ssh user (login via ssh)
      certutil -p CertificatePassword -importPFX .pfx/.p12
      ... reboot(!)
      certutil -repairstore "My" *
      ... doesn't seem to help here anymore - so reboot
  • latest VS2019
  • disable UAC
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA = 0

  • Debug View is helpful http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
  • further hints: http://www.osronline.com/article.cfm?article=496 and http://windbg.info/download/doc/pdf/WinDbg_A_to_Z_bw2.pdf
  • enable driver installation over a network mapping: open command prompt as administrator
    net use drive: \\server\path

  • to be able to remove driver entries add
  • fine list of devcon scripts to cleanup installation mess http://www.robvanderwoude.com/devcon.php

Two machine kernel debug setup

Build server

  • use an ssh service to connect to your windows build server http://www.freesshd.com
  • install your signing certs under the service "user" - Windows has no strict user concept


CoreAudio server plugin driver interface

CoreAudio server plugin driver

  • Installation
  • stop CoreAudio server
    sudo launchctl stop com.apple.audio.coreaudiod
  • start CoreAudio server
    sudo launchctl load com.apple.audio.coreaudiod
  • debug CoreAudio Daemon by attaching to /usr/sbin/coreaudiod as root and wait for executable to be launched
  • restart CoreAudio server
    sudo launchctl stop com.apple.audio.coreaudiod && launchctl start com.apple.audio.coreaudiod

CoreMIDI server plugin

  • Installation
    ~/Library/Audio/MIDI Drivers
    /Library/Audio/MIDI Drivers

(c) copyright 2009 dynamic acoustics e.U. generated on Fri Feb 23 2024

a closed source license may be obtained by requesting a written permission from dynamic acoustics e.U.
however - governmental use generally and military use especially is strictly prohibited though.