Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We need more information about the device to point you in the right direction, but here are a few steps to get you started:</p> <ul> <li>register with Microsoft Connect so you can download the Windows Driver Kit</li> <li>register with <a href="http://www.osronline.com/" rel="noreferrer">osr-online</a> as you'll find great articles, plenty of information, and a newsgroup dediciated just to Windows drivers -- this place is a goldmine</li> <li>buy <a href="http://rads.stackoverflow.com/amzn/click/0735623740" rel="noreferrer">Developing Drivers with WDF</a>, which will help you make sense of driver development on Windows and give you a good foundation to read articles from OSR and Microsoft</li> <li>Hope that you can use UMDF (user-mode drivers) as you can use C++ and just write COM code. If you're doing anything with USB that requires kernel-space....you've got a lot of reading and learning to do for the next year!</li> </ul> <p>To answer your question on versions, the Driver Kit has tools that will help you manage creating different drivers. If you write a good driver, it should run on all three OS with no problems, and the differences will just be in the config area (not the binary)</p> <p>Basically, it depends on how complex your device is. What type of driver are you trying to write? File system? MP3 player? Camera? Modem?</p> <p>If you end up having to write a kernel mode driver, let me know and I can point you to some good articles and what not. </p> <p>I should also add that for around US $5,000, you can buy a license for <a href="http://www.jungo.com/st/windriver_usb_pci_driver_development_software.html" rel="noreferrer">WinDriver</a>, a tool that takes all of the hard stuff out of driver development. You can use C++ or C# user-mode code to communicate with their driver that is custom generated for your device. This is the way to go if you have a tight deadline.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload