DIFxApp and Ndis IM driver install miniport problem

I download DIFX and check DpInst.exe with Samples\Network.Intermediate (I simply put this exe file to driver root directory).

DpInst incomplete install this driver - protocol part only

The similar problem is observed with use DIFxApp in msi package.

jeffm
Wed Jun 02 09:40:01 CDT 2004

------=_NextPart_0001_762517A7
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

First, I would take a look at the dpinst.log file that was created in the
%WINDIR% folder. If that doesn't provide any helpful information, then I
would look at a verbose setupapi log of the install. To enable verbose
logging, set this environment variable:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]
"LogLevel"=dword:0000ffff

Then delete or rename %WINDIR%\setupapi.log, and repeat the installation.
A new setupapi log will be created. That should contain some information
about why the setup failed.

Thanks,
[MS] Jeff McCashland
jeffm@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_762517A7
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 First, I would take a look at the dpinst.log file that was created in the %WINDIR% folder. If that doesn't provide any helpful information, then I would look at a verbose setupapi log of the install. To enable verbose logging, set this environment variable:
\par
\par [HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Setup]
\par "LogLevel"=dword:0000ffff
\par
\par Then delete or rename %WINDIR%\\setupapi.log, and repeat the installation. A new setupapi log will be created. That should contain some information about why the setup failed.
\par
\par Thanks,
\par [MS] Jeff McCashland
\par jeffm@online.microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_762517A7--

alex_mtk
Wed Jun 02 11:41:03 CDT 2004

This log too large, I think that it part will be was interestingly -

[2004/06/02 19:55:30 2580.68 Driver Install
#-019 Searching for hardware ID(s): ms_passthrum
#-198 Command line processed: "C:\DIFX\Samples\Network.Intermediate\DpInst.exe"
@ 19:55:30.169 #V017 Enumerating files "C:\winnt\inf"
@ 19:55:30.189 #V392 Using INF cache "C:\winnt\inf\INFCACHE.1"
................................
@ 19:55:34.906 #T075 Enumerating files: Directory pass completed
@ 19:55:34.945 #T076 Enumerating files: Cache pass completed
@ 19:55:34.965 #W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device
[2004/06/02 19:55:35 2580.69
#-198 Command line processed: "C:\DIFX\Samples\Network.Intermediate\DpInst.exe"
@ 19:55:35.102 #V039 Opened INF "C:\DIFX\Samples\Network.Intermediate\netsf.inf", PNF not created (Language = 0419)
[2004/06/02 19:55:35 2580.70
#-198 Command line processed: "C:\DIFX\Samples\Network.Intermediate\DpInst.exe"
@ 19:55:35.141 #V039 Opened INF "C:\DIFX\Samples\Network.Intermediate\netsf.inf", PNF not created (Language = 0419)

Send me your real EMail address to alex_mtk@hotmail.com and I send full log file in EMail message

Before run this setup I manual remove *.inf in OEM store directory, clear registry and reboot system

anonymous
Wed Jun 02 12:01:12 CDT 2004

I manual add netsf_m.inf to Winnt/inf directory and setup process work success

I have understood, that the installation program not execute this instruction -

CopyInf = miniport\netsf_m.in

Jason
Fri Jun 04 11:51:11 CDT 2004

You have to tell DPInstn and DIFxApp to install all the packages, it doesn't
automatically process the CopyInf directive. This might seem like a pain,
but we figured it would give vendors more control.

For DPInst, view the document on dpinst.xml that shows you how to get
DPInst.exe to search subdirectories for driver packages.

For DIFxApp, you will need to add an entry for all driver packages (i.e. INF
files) that you want to install.

...and it is never a good idea to manually copy an INF into the INF
directory as it could replace an existing INF from another vendor...

--
This posting is provided "AS IS" with no warranty, and confers no rights.

Jason Cobb
Developer

"Alex" <anonymous@discussions.microsoft.com> wrote in message
news:4A08C449-189E-4D6B-BFA9-A35C97755F43@microsoft.com...
>I manual add netsf_m.inf to Winnt/inf directory and setup process work
>success.
>
> I have understood, that the installation program not execute this
> instruction -
>
> CopyInf = miniport\netsf_m.inf
>
>