“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
…
> Driver package cannot be removed (only by manual procedure unsuitable for
> production use).
>
> You can only delete the devnode, or dissociate the package from it.
>
> So, the driver package is forever, and, if you re-connect the hardware,
> PnP will automatically associate the driver package with it.
pnputil /D [/F]
http://msdn.microsoft.com/en-us/library/ff550428(v=VS.85).aspx#deleting_a_driver_package_from_the_driver_store
Regards,
--pa
Pavel A. wrote:
“Tim Roberts” wrote in message news:xxxxx@ntdev…
> …
>> The worst part is the client’s sales staff thinks this is a great
>> general purpose tool, so they keep handing it out.
> Doesn’t the experience prove that customers are always right -
> so better give them what makes them happy?
I suppose you’re right. In my mind, I really do think of the tool as
setting off a small tactical nuclear device. Every time I run it, I
raise the radioactivity level in my computer just a bit, until
eventually it will be hopelessly poisoned. When I hear about them using
it in their “normal” uninstall process, it makes me cringe. I’m
contributing to the world-wide rise in ambient digital radioactivity.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Wow, lot’s of replies 
After consulting with the driver’s author I’ve been told that:
- It’s not PnP
- It may be a “legacy” driver
- It’s not a Virtual device like I said. It’s an Intermediate device based on the Passthru Ndis Intermediate Driver from the WDK.
There are 2 INFs. Classes are NetService and Net as in the Passthru Ndis Intermediate Sample Driver from the WDK.
Does this help?
Thanks,
James
Is the tool that installs the driver built with Visual Studio?
If so, then it depends on the companion VS runtime libraries.
Does your installer install the merge modules (used to distribute the VS
runtimes…) before running the install tool?
Thomas F. Divine
From:
Sent: Friday, February 04, 2011 8:07 AM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] Driver stopped installing (0x80070002)
> Wow, lot’s of replies
>
> After consulting with the driver’s author I’ve been told that:
> 1. It’s not PnP
> 2. It may be a “legacy” driver
> 3. It’s not a Virtual device like I said. It’s an Intermediate device
> based on the Passthru Ndis Intermediate Driver from the WDK.
>
> There are 2 INFs. Classes are NetService and Net as in the Passthru Ndis
> Intermediate Sample Driver from the WDK.
>
> Does this help?
>
>
> Thanks,
> James
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Indeed - if all else fails, run Depends on all involved.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Thomas F. Divine
Sent: Friday, February 04, 2011 8:55 AM
To: Windows System Software Devs Interest List
Subject: Re: RE:[ntdev] Driver stopped installing (0x80070002)
Is the tool that installs the driver built with Visual Studio?
If so, then it depends on the companion VS runtime libraries.
Does your installer install the merge modules (used to distribute the VS
runtimes…) before running the install tool?
Thomas F. Divine
From:
Sent: Friday, February 04, 2011 8:07 AM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] Driver stopped installing (0x80070002)
> Wow, lot’s of replies
>
> After consulting with the driver’s author I’ve been told that:
> 1. It’s not PnP
> 2. It may be a “legacy” driver
> 3. It’s not a Virtual device like I said. It’s an Intermediate device
> based on the Passthru Ndis Intermediate Driver from the WDK.
>
> There are 2 INFs. Classes are NetService and Net as in the Passthru Ndis
> Intermediate Sample Driver from the WDK.
>
> Does this help?
>
>
> Thanks,
> James
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
> Is the tool that installs the driver built with Visual Studio?
If so, then it depends on the companion VS runtime libraries.
Yet another cause to build all UI-less user mode binaries with WDK and not VS.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Yes, it’s build with VS.
Yes, the runtime libraries are installed.
Dependency Walker is very happy with this app, so that’s not that.
Regards,
James
Dependency walker on the machines that fail?
Or Dependency walker on your own machine?
From:
Sent: Friday, February 04, 2011 9:57 AM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] Driver stopped installing (0x80070002)
> Yes, it’s build with VS.
> Yes, the runtime libraries are installed.
> Dependency Walker is very happy with this app, so that’s not that.
>
>
> Regards,
> James
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
VS’s runtime libraries also can have SxS issues which are IIRC not checked by DEPENDS.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
wrote in message news:xxxxx@ntdev…
> Yes, it’s build with VS.
> Yes, the runtime libraries are installed.
> Dependency Walker is very happy with this app, so that’s not that.
>
>
> Regards,
> James
>
>
Like I said, dependencies are not an issue here. But if you must know I’ve run it on the problematic machine obviously. I have not run it on mine, but I’m quite certain it would also be pleased with the result.
No SxS issues reported in the Event Manager so I don’t think it’s that.
The rest of our product works fine BTW and the entire thing is compiled by the same, dedicated machine. So once again, not dependencies.
I’d like to get the topic back to drivers/installations. The info I posted about the driver/device - is that helpful? Maybe that’s just not the way of installing such drivers?
Thanks,
James
A small update. I’ve been away for 2 weeks. After I’ve returned I’ve been told it got worse. More and more computers seem to be developing the problem. Not only new ones, but also old (virtual) test machines.
I will explore the world of DIFx. Any new ideas/clues much welcome!
So is your driver actually a NDIS 5 IM? (the “filtering service” being the protocol part)
Then this thread can be useful:
INetCfg::FindComponent returns S_FALSE
Date: Wed, 22 Dec 2010 12:45:50 -0500
Regards,
– pa
and this:
Subject: NDIS IM Installation
Sent: Thursday, December 17, 2009 17:33
Yes, it’s an NDIS 5.0 miniport filter.
I will take a look, thanks!
Well, I’ve taken my look. Interesting but that’s the next step. For now it turns out we are getting more and more complains about this driver not installing which is a priority.
It came to our attention that the problems started when we incorporated the installer code into our main service (as in a user-mode Windows service). Before the installer was only called when we actually installed our software but later it turned out it needs to be a bit more dynamic.
Now each time our service starts (usually one+ times per session) it checks if the driver is there and if it’s not it tries to install it. Do not ask why. We probably will need to change this since it’s (obviously) problematic. The fact is that our service tries (and sometimes) failes to install the driver. After this fails we are unable to install it even manually (“mouse+GUI” way). Somehow this partial installation breaks everything.
In the previous version of the software the service did not do this and if it didn’t find the driver in the system it simply stopped & reported the problem which was usually solvable by manual driver installation (“mouse+GUI” way). Now it’s not that simple…
And a bit details on the driver package. It’s made of a SYS and 2 INFs. What’s peculiar is that ALL the problems look the same. The installation (whichever way) installs the first INF (one service is visible in the system) and fails to install the other (second service never created).
The ‘OK’ INF is for the “master” service and the ‘bad’ is for the miniport service.
Maybe this is the reason? Obviously we need to remove this from the service. But that’s simple. The interesting part is WHY it creates a problem.
Also the VERY important question is how to actually fix this so it can be installed by hand? It is quite possible that this service issue has nothing to do with the problems but still worth telling you. If it’s not the source of the problem it means that even before we install anything on a machine the manual installation would fail and that the problem lays elsewhere.
I hope I made that clear. It’s a bit complicated