Writing Device Drivers? Perhaps playing with Cypress Semiconductor's USB Starter Kit? If so, the Device Driver Fiddler allows you to test DeviceIOCommand() Calls before you write your User Mode Application. . . . The Device Driver Fiddler saves the device name and your current IO Control Code into the registry, so your not forever entering in these details.
|
The Driver Install Utility for Windows NT 4 & Windows 2000 prevents making testing of your newly written drivers a chore. Simply fill in the driver name and it's location and your given the option of Installing, Starting, Stoping and Uninstalling your device driver. Once again, this utility remembers your previous driver details. After the success of the previous version, users commented the information boxes where annoying, and that it would be good to be able to reload the driver (stop, uninstall, reinstall, start) after a new version of your driver has been built. This new version has a status line, showing any successful or failed attempts with loading your driver.
|
Writing PNP device drivers under Windows 95 or 98? The Remove Driver Utility follows Microsoft's directions layed out in the Device Driver Kit, to remove all traces of your device driver. This allows Windows to ask for a new driver once the device is plugged in again. Great for USB WDM Device Driver Programming.
|