WDK v. 7 for USB
in [Device Drivers]
|
Prev: Link Data User-Mode <--> Kernel-Mode. Please Help !
Next: hybird display adapter can't run DWM in Server 2008 R2 if one of adapter does't support 3D
From: Doron Holan [MSFT] on 21 Oct 2009 14:02 note that if your device is dedicated to a particular custom application, winusb by itself is probably going to be just fine and you do not need to write a UMDF driver. if the device is going to be shared across applications, UMDF is the route to go d -- This posting is provided "AS IS" with no warranties, and confers no rights. "Don Burn" <burn(a)stopspam.windrvr.com> wrote in message news:ODX0FAnUKHA.3720(a)TK2MSFTNGP04.phx.gbl... > Basic C/C++ is enough. UMDF is based on COM but is limited enough that > most people have no problem picking up the basics. > > > -- > Don Burn (MVP, Windows DKD) > Windows Filesystem and Driver Consulting > Website: http://www.windrvr.com > Blog: http://msmvps.com/blogs/WinDrvr > Remove StopSpam to reply > > > > "alistair cordon" <alistaircordon(a)discussions.microsoft.com> wrote in > message news:030B6F9D-22C0-415F-8756-D492E4946C84(a)microsoft.com... >> Okay then, >> I will proceed with treating WDK like DDK. >> I have the WDF book already and will read it. >> >> Does writing a driver for USB need an understanding of certain >> programming >> language or is basic C/C++ enough? >> >> >> >> >> "Don Burn" wrote: >> >>> Yes you can use the same. But as I stated you should look at WDF. The >>> book >>> covers KMDF the kernel stuff and UMDF the user stuff. >>> >>> >>> -- >>> Don Burn (MVP, Windows DKD) >>> Windows Filesystem and Driver Consulting >>> Website: http://www.windrvr.com >>> Blog: http://msmvps.com/blogs/WinDrvr >>> Remove StopSpam to reply >>> >>> >>> "alistair cordon" <alistaircordon(a)discussions.microsoft.com> wrote in >>> message news:40C5F060-6D8C-4D85-BFEC-33147C11EFF2(a)microsoft.com... >>> > So WDK can be used like DDK right? I can still use those books and >>> > develop >>> > the driver with WDK? >>> > >>> > I'm very-very new to this and XP DDK books are all I have. >>> > I'll check your WDF book. But does it also have explanations on UMDF & >>> > other >>> > stuff? (winUSB or something like that?) >>> > >>> > Thanks >>> > >>> > "Don Burn" wrote: >>> > >>> >> There are big differences, but they are things you want. First you >>> >> can >>> >> develop drivers the same way as was done with the XP DDK so you >>> >> should >>> >> not >>> >> worry about this. What the WDK does provide you are better ways of >>> >> doing >>> >> drivers in particular WDF which has a lot of applicability to USB. >>> >> Depending on your devices characteristics you can develop the driver >>> >> as a >>> >> UMDF driver, even if you need a kernel mode driver KMDF is a much >>> >> better >>> >> platform than WDM which was all that was available with the XP DDK. >>> >> >>> >> Get "Developing Drivers with the Windows Driver Foundation" >>> >> http://www.amazon.com/Developing-Drivers-Windows-Foundation-Developer/dp/0735623740/ref=sr_1_2?ie=UTF8&s=books&qid=1256067398&sr=1-2 >>> >> and start from there. >>> >> >>> >> >>> >> -- >>> >> Don Burn (MVP, Windows DKD) >>> >> Windows Filesystem and Driver Consulting >>> >> Website: http://www.windrvr.com >>> >> Blog: http://msmvps.com/blogs/WinDrvr >>> >> >>> >> >>> >> "alistair cordon" <alistair cordon(a)discussions.microsoft.com> wrote >>> >> in >>> >> message news:17EE0D01-6BB7-4D27-ACF0-EAE0C70BDE33(a)microsoft.com... >>> >> > Dear all, >>> >> > >>> >> > I hope this is the right forum to post this question. >>> >> > >>> >> > I'm doing a uni project to connect a device to PC through USB. >>> >> > I understand that I need a WDK since I use WinXP (& DDK has been >>> >> > superseded >>> >> > by WDK) >>> >> > >>> >> > This is my first time doing this. >>> >> > All the books I read still refer to DDK. >>> >> > >>> >> > My question is: >>> >> > is there a big difference between WDK & DDK for WinXP? >>> >> > >>> >> > if YES then >>> >> > where can I download WinXP DDK? >>> >> > >>> >> > Thank you. >>> >> > >>> >> > >>> >> > __________ Information from ESET NOD32 Antivirus, version of virus >>> >> > signature database 4527 (20091020) __________ >>> >> > >>> >> > The message was checked by ESET NOD32 Antivirus. >>> >> > >>> >> > http://www.eset.com >>> >> > >>> >> > >>> >> > >>> >> >>> >> >>> >> >>> >> __________ Information from ESET NOD32 Antivirus, version of virus >>> >> signature database 4527 (20091020) __________ >>> >> >>> >> The message was checked by ESET NOD32 Antivirus. >>> >> >>> >> http://www.eset.com >>> >> >>> >> >>> >> >>> >> >>> >> . >>> >> >>> > >>> > __________ Information from ESET NOD32 Antivirus, version of virus >>> > signature database 4528 (20091021) __________ >>> > >>> > The message was checked by ESET NOD32 Antivirus. >>> > >>> > http://www.eset.com >>> > >>> > >>> > >>> >>> >>> >>> __________ Information from ESET NOD32 Antivirus, version of virus >>> signature database 4529 (20091021) __________ >>> >>> The message was checked by ESET NOD32 Antivirus. >>> >>> http://www.eset.com >>> >>> >>> >>> >>> . >>> >> >> __________ Information from ESET NOD32 Antivirus, version of virus >> signature database 4530 (20091021) __________ >> >> The message was checked by ESET NOD32 Antivirus. >> >> http://www.eset.com >> >> >> > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4530 (20091021) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > >
From: Maxim S. Shatskih on 21 Oct 2009 14:23 > Could you suggest some books? Penny Orwick Guy Smith "Developing Drivers with the Windows Driver Foundation" ISBN-13 978-0-7356-2374-3 ISBN-10 0-7356-2374-0 -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
From: __ay on 22 Oct 2009 00:28 The NDIS IM Driver on win2k3. the driver complied by DDK 2k3 works well but the same code compiled by wdk was failed. Even though the code is successfully compiled , the driver does not works . "Don Burn" wrote: > > "__ay" <ay(a)discussions.microsoft.com> wrote in message > news:0027121B-59D1-4324-9453-B5AF4280C5AF(a)microsoft.com... > > Compared to the DDK , I personally think there are some changes in WDK . > > and the code i uesd to compile by the DDK 2k3 before was not successfully > > compiled by the wdk. Even though the compilation is done , the driver > > cannot > > hardly work as I expexct > > > > What type of driver and what were you doing? I have migrated over 40 > drivers to WDK as part of beta testing with no problems. Were you testing > these on the same system as the "working version" had been tested on? > > > -- > Don Burn (MVP, Windows DKD) > Windows Filesystem and Driver Consulting > Website: http://www.windrvr.com > Blog: http://msmvps.com/blogs/WinDrvr > Remove StopSpam to reply > > > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 4529 (20091021) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > > > . >
From: Tim Roberts on 24 Oct 2009 00:18
__ay <ay(a)discussions.microsoft.com> wrote: > >The NDIS IM Driver on win2k3. >the driver complied by DDK 2k3 works well but the same code compiled by wdk >was failed. Even though the code is successfully compiled , the driver does >not works . Are you compiling in the Windows 2003 Build Environment in the WDK? -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc. |