Message 4 of 5
14 Feb 18 06:43
Join Date: 23 Feb 2011
Posts To This List: 1406
Driver Prototyping Hardware
The deployment stuff in the WDK has never worked reliably. Most experienced
driver developers would never use it, instead install the first time and use
.kdfiles in Windbg to update the driver.
Windows Driver Consulting
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of
Sent: Wednesday, February 14, 2018 1:56 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Driver Prototyping Hardware
On Tue, Feb 13, 2018 at 11:15 PM, firstname.lastname@example.org
> On 2/13/2018 6:22 PM, email@example.com wrote:
>> Alternatively, if anyone has tips for using VMs that would help, but
>> my issue was I could never deploy properly - my host is Linux, and
>> nested KVM is broken on my hardware so I can not run VirtualBox
>> inside my development machine. I tried to deploy over network to the
>> VM, but was never able to get it working.
> What sort of driver are you developing? If it's for a PCIe device, you
<...excess quoted lines suppressed...>
Currently a different keyboard transport protocol over USB (prototyped with
libusb and userspace calls). PCIe is pretty far down on the list at the moment.
I've gotten PCIe passthrough working, the problem is my hardware does not
support nested KVM, so I am not able to follow the guides that use VirtualBox
My question could also be interpreted as "does anyone have a known working test
configuration?" Despite all my attempts, I can't get automated deployment with
the WDK working, and have been doing things by hand. This is less than ideal.
NTDEV is sponsored by OSR
Visit the list online at:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
To unsubscribe, visit the List Server section of OSR Online at