- how to correctly install a NDIS IM from your app?
- Posted by Vitalie Vrabie on April 26th, 2008
hi.
currently i'm doing SetupCopyOEMInfW() for each inf file, then issue a
NetCfgClassSetup::Install() for the pnpid of my service (not miniport)
component.
it works fine on all systems in the test environment (2000, xp, vista
home) except for one Vista Business Edition installation at one of my
friends -- NetCfgClassSetup::Install() returns
SPAPI_E_NO_DRIVER_SELECTED.
am i missing something?
or is that vista business installation somehow corrupt?
- Posted by Vitalie Vrabie on April 26th, 2008
UPD: previous calls to SetupCompyOemInfW() succeed okay.
- Posted by Gianluca Varenni on April 28th, 2008
"Vitalie Vrabie" <vitalie.vrabie@gmail.com> wrote in message
news:b05cc695-3c56-4616-8d21-8b16152b5792@m44g2000hsc.googlegroups.com...
Does bindview install your driver correctly on your Vista Business machine?
Have a nice day
GV
--
Gianluca Varenni, Windows DDK MVP
CACE Technologies
http://www.cacetech.com
- Posted by Vitalie Vrabie on April 28th, 2008
haven't tried bindview. thanks for suggestion.
the built-in "install -> service" of the adapter properties seems to
install okay, but the driver doesn't seem to work there. i.e, it shows
the driver installed, shows the binding checkmark, but the data seems
to flow bypassing my driver. very strange.
- Posted by Vitalie Vrabie on April 30th, 2008
tried bindview today.
same symptoms as for the service installation throgh the adapter
properties.
shows it installed and bound, but driver doesn't actually get control
(none of my kdprints are shown in dbgview).
- Posted by Gianluca Varenni on May 2nd, 2008
Debugging IM installation problems is a pain, been through it.
What I do in these cases is start from the beginning: I take the passthru
sample from the DDK/WDK, and try to install it. If it works, there is
something weird in my INF (or in my driver).
Have you heavily modified the original INFs for the passthru (if you have
used it as a starting point).
Have a nice day
GV
--
Gianluca Varenni, Windows DDK MVP
CACE Technologies
http://www.cacetech.com
"Vitalie Vrabie" <vitalie.vrabie@gmail.com> wrote in message
news:6f13ec0b-ad69-47c7-8335-8f4159b25380@26g2000hsk.googlegroups.com...
- Posted by Vitalie Vrabie on May 4th, 2008
On May 2, 6:50 pm, "Gianluca Varenni"
<gianluca.vare...@community.nospam> wrote:
not quite heavily. just changed the IDs and that's all. the INFs were
from 1790.1830 DDK.
recently some good soul gave me the passthru INFs taken from the
latest (Vista) WDK and I've built my INFs again, based on fresh ones.
unfortunately, this didn't help on the problematic computers (two of
them, same model from same vendor).
next week we'll try a fresh Vista install on those computers, with
none of the vendor-specific software installed. we're really out of
other ideas.
- Posted by Gianluca Varenni on May 5th, 2008
"Vitalie Vrabie" <vitalie.vrabie@gmail.com> wrote in message
news:511de3c7-28d8-4a1b-bfda-6dd1ac97a337@x35g2000hsb.googlegroups.com...
Just a hint to debug these issues: install Vista on a VmWare virtual
machine, and use the snapshot feature to revert to a clean installation of
Vista. This is what I usually do to test software only driver installation.
Hope it helps
GV
--
Gianluca Varenni, Windows DDK MVP
CACE Technologies
http://www.cacetech.com
- Posted by Vitalie Vrabie on May 6th, 2008
we've already tried in vmware, including on those problematic
computers. works perfectly okay.
today we'll try on real comps with a clean vista.
- Posted by Vitalie Vrabie on May 6th, 2008
hm. tried. works okay on clean vista, and does not work if HP software
is installed.
remains to clarify which HP software item causes the problem.
anyone from HP here? hello!
- Posted by Gianluca Varenni on May 7th, 2008
Some IM driver from HP?
I would probably try two things:
1. go to the device manager, enable the hidden devices (view->Show hidden
devices), and then look within the network adapters. The miniport half of an
IM is shown there.
2. attach windbg to the machine and use the ndiskd extension to list all the
miniports and protocols.
In both cases, I would look for things that are suspicious/unknown (kinda
vague suggestion, I know).
Hope it helps
GV
--
Gianluca Varenni, Windows DDK MVP
CACE Technologies
http://www.cacetech.com
"Vitalie Vrabie" <vitalie.vrabie@gmail.com> wrote in message
news:5055cb92-6af1-4e27-a187-c3a5d6387944@m44g2000hsc.googlegroups.com...
- Posted by Vitalie Vrabie on May 8th, 2008
probably. who knows.
it also might be some piece of their software that hooks onto INetCfg
and its friends.
no, it doesn't.
to make things even worse, HP made the effort of their software not
installing on non-HP hardware.
thus, i cannot try their software in a VM piece by piece, and
precisely point to the guilty item.
and you know what? i don't care. i'll make an entry in the release
notes, leaving it all on HP's behalf. i have no plans to purchase any
of their hardware just because they guys don't know how to write
compatible software.
