I think should split my patch into many little commits. Should also add some tests or make some changes?
Yes, add conformance tests for the new ntoskrnl functions and usbd.sys, and break the patch up a lot...
Looks like people have been hoping for something like this for a couple years now, e.g. http://www.winehq.org/pipermail/wine-devel/2005-November/042357.html
Yes, add conformance tests for the new ntoskrnl functions and usbd.sys, and break the patch up a lot...
Conformance tests should consist of a driver and a program to load it. I do not know other method to call functions from ntoskrnl.exe and usbd.sys on Windows. But I have a problem with building drivers with MinGW. I was able to create a driver which is loading on Wine with manual editing of PE header but it does not work on Windows and I do not understand what should change to fix this. Did somebody build NT drivers with MinGW?
On Tue, Jul 8, 2008 at 10:05 AM, Alexander Morozov amorozov@etersoft.ru wrote:
Conformance tests should consist of a driver and a program to load it. I do not know other method to call functions from ntoskrnl.exe and usbd.sys on Windows. But I have a problem with building drivers with MinGW. I was able to create a driver which is loading on Wine with manual editing of PE header but it does not work on Windows and I do not understand what should change to fix this. Did somebody build NT drivers with MinGW?
Look at how the ReactOS guys are doing it. I know for a fact that some of their developers build certain drivers like the ReactOS VBE driver and test it under NT4 and others so Mingw can do it.