Using Walter Oneys Driver Wizard bug? or no bug?
Peter Kelly
I have installed the disk that comes with Walter Oney's "Programming
the Microsoft Windows Driver Model 2nd Ed". And i have downloaded and
applied the latest SP from Walters site.
Now, I use Walters wizard to create a Generic Filter driver. Apply the
'fix driver' by right mouse context option over the .dsp. Next,
compile with no changes to the wizard produced code against the latest
WinXP DDK. All is well so far.
Next I use the AddFilter.exe that comes with the DDK to add my new
filter driver as an upper filter driver to my cdrom device using the
following cmd
addfilter /device \Ide\IdeDeviceP1T0L0-c /add MyFilt
here are my results.
On Windows 2000 - the output from addfilter asks to restart the
computer (more or less). But now the machine has completely hung and
the mouse is reluctant to move. Remedy is to hard reboot. On reboot
everything is still extremely slow. Requires another hard reboot to
Recovery console where i delete cdrom.sys so that the CDROM fails to
start thus preventing the previous hangs. Boots fine now. Uninstall
erroroneous cdrom device from device manager and reinstall. All is
well and as expected MyFilt is not in reg as upper filter driver. Why
does it hang? Anyone experienced this?
On XP - the device restarts as per code in AddFilter.exe but has an
error. In device manager the cdrom device in question has error code
41. Apparently, this means that the driver was loaded but the device
could not be found. Any ideas?
I have tried this on many different machines with many different
wizard built drivers.
If anyone could help me with this it would be greatly appreciated.
I've been pulling my hair out for days.
TIA,
Pete.