Sethuraman R wrote:
Thanks for all your replies.
What do you expect the system to do in that case? Leave the device
unrecognized?I could really understand the basic behavior of widnows’ default
design.
However, as i am trying to install a new driver, in a need not to roll
back to my old driver. I have written few other utilites, which will
be corrupted if my old driver loaded back.
But you need to think about genuine user scenarios here. Are your
driver and your application installed together? If so, then running the
uninstaller should remove both of them, so the application can no longer
run. If a stubborn user deletes your driver by hand without deleting
the application, then it is his own fault if the application doesn’t
work. He gets the result he deserves.
Can’t your application tell whether it is talking to the old driver or
the new driver?
Now,I am able to retreive around 5 INF paths matched with my h/w id
following the steps 1 & 2.One INF contains driver for other device?.
However the registry maps with H/W id.
Does windows reallocate the OEM.inf to other device?
Yes. When you add a new INF, Windows looks for the lowest number that
is not in use. So, if you delete oem4.inf, the next device to be loaded
will go to oem4.inf.
Am I doing anything wrong here?Please advice…
I think you are worrying about situations that you do not need to worry
about.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.