Hi Steve,
The information you enter when creating USB framework files with EasyHID is just for the embedded side with a very handy .dll that handles host to function communications.
EasyHID just gives you the USB framework. As far as I know, it does not create a Windows .inf file. That's up to you to create.
If you don't have your own .inf file or HID driver, then Windows will install its own HID drivers, and your new USB gadget is just going to show up with the default Windows name in Device Manager like 'USB Human Interface Device' and 'HID-Compliant Device'.
If you're running XP, look in the Windows input.inf file, and you'll see why. It tries to match the descriptors, VID, PID with existing "certified" manufacturers & hardware. If your new USB gadget isn't in the list, Windows uses the default HID compliant description with generic HID drivers.
Download the Microchip USB framework and take a look at how they setup the .inf & driver files. That will help you understand what's required.
If you plan on making a USB enabled "product", then you might also want to grab a copy of Jan Axelson's USB Complete 3rd edition. It's worth every penny, and gives you details on how to get your USB product/manufacturer name to show up in Windows Device Manager.
EasyHID will get you started, (and really quick I might add), but there's still a lot left to the end user to figure out.
Hats off to Dave at Mecanique for putting in the HUGE amount of time & study required just to give everyone that nifty "free" utility.
Bookmarks