Hi,
I’ve got a protocol driver and an NDIS intermediate driver that I’m trying
to install. I’ve successfully used the snetcfg.exe sample in the Windows XP
DDK (it’s in \src\network\config\netcfg) to install and uninstall
drivers from a command prompt. I then went ahead and used this from an
InstallShield setup program (along with other components) and it seems to
work for the most part. But, on some machines (and I can’t really discern
any common symptoms/configurations of the systems with the problem)
everything is installed, but after install is done, the NDIS Intermediate
driver doesn’t seem to be properly bound. Running the Snetcfg program after
that and looking at the XP Network Connections UI, it seems all is well, but
the driver isn’t getting into the packet loop. The only way to “fix” it is
to uninstall and install “manually” from the XP Network Connections UI.
Has anyone any suggestions? BTW, longer term, I do plan to integrate this
functionality into a program (DLL) instead of shelling out to snetcfg (from
InstallShield) but I’m just trying to get a reliable install in order to
ship a functional product.
Thanks,
Paul
----------------------------
Paul Benware
KoolSpan Incorporated
xxxxx@koolspan.com
On Wed, 2004-02-18 at 12:23, Paul Benware wrote:
I?ve got a protocol driver and an NDIS intermediate driver that I?m
trying to install. I?ve successfully used the snetcfg.exe sample in
the Windows XP DDK (it?s in \src\network\config\netcfg) to
> install and uninstall drivers from a command prompt. I then went
> ahead and used this from an InstallShield setup program (along with
> other components) and it seems to work for the most part. But, on
> some machines (and I can?t really discern any common
> symptoms/configurations of the systems with the problem) everything is
> installed, but after install is done, the NDIS Intermediate driver
> doesn?t seem to be properly bound. Running the Snetcfg program after
> that and looking at the XP Network Connections UI, it seems all is
> well, but the driver isn?t getting into the packet loop. The only way
> to ?fix? it is to uninstall and install ?manually? from the XP Network
> Connections UI.
I’ve run into this before, too. For some reason, some boxes just don’t
want to do the IM binding right on the first shot. In rare cases, the
computers wind up pretty hosed and in need of personal attention from
support –> not good.
There are some gotchas on installing the IM driver correctly - you have
to make sure you’re the only driver in your particular FilterClass, for
one thing. Search the archive for an old post of mine that describes
this.
Aside from confirming your observations, I can’t suggest much - if you
base your integrated installer code on the netcfg sample, you’ll run a
pretty good chance of having the same problems. If you figure anything
out, I’d like to know.
-sd