I am trying to get a NetChip USB driver to work on an XP
sp1 Dell laptop. The error I receive says something
about the INF file missing a necessary entry. Would
someone be willing to look at the INF and tell me what is
missing?

Thanks, also, no NetChip is not giving support on this
like I was hoping.

Uhmm...INF file sections are fully documented in the DDK help. In addition
the DDK has numerous correct INFs that you can compare against, even for USB
devices. You can use the setupapi logger to help you narrow down exactly
what the system doesn't like about your INF as well. All of this has been
discussed here before, so I suggest you search google for more information.

--
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashu...es/utility.htm



"Sean Whitesell" <seanw@vigoris.net> wrote in message
news:08a001c35517$d8963fc0$a601280a@phx.gbl...

Excellent advice, Bill,

Sean, you should also run your INF through CHKINF in the DDK, it will
likely identify the missing section and possibly other errors.

You might also increase the level of diagnostic output from setupapi by
setting
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Setup\LogLevel
(DWORD) to 0x00006060 and reviewing \windows\setupapi.log.

Bryan S. Burgin
bburgin@microsoft.com

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

I wish this was as easy as saying RTFM. I only have the
2000 DDK. I ordered the XP sp1 DDK but it is back-
ordered. I tried ChkInf but first off, it doesn't work on
those made for/from Win98. Secondly, it gave two errors
referring to problems in the chkinf.pm file. I have
printed many papers regarding inf sections and have read
many details. But, only a few actually say what is
required. I have been comparing this inf file to others
and have not found difference that would lead to an
answer. Also, I didn't write the driver so I dont know
about setupapi. I was hoping for a lot more support out
of the chip manufacturer. I will try changing the error
level as mentioned, but I'm really stuck and need a quick
fix asap.

Thanks.

Instead of porting your Windows 98-based INF to 2K/XP, you may start with
an existing 2K INF that is close to your device's purpose as a template and
go forward from there. Also, if you're asking for the community's review,
you might want to post the text of your INF.

BTW, I didn't hold a lot of hope on my Setupapi.log suggestion, but I threw
it out because you never know

Bryan S. Burgin
bburgin@microsoft.com

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

Now that is kind of funny


Sean, I understand your frustration. Jumping into this stuff is not for the
timid.

But, as I suggested you aren't the first to run into INF problems and this
has been discussed many times here. Bryan's suggestion of posting your INF
is not a bad one at all. It is REALLY hard to guess what might be wrong
with an INF.

CHKINF, (I can't believe I forgot to mention that) can be really really
useful. I suggest you pull out the 98 specific portions of your INF and try
it again.

SetupApi logging is discussed in the DDK help, I believe even in the
2000DDK, but not absolutely sure there.

One other thing, how are you trying to install this device? Are you
plugging in the USB device and letting the "Found new hardware" pop-up
prompt you for an INF, or are you trying to do something else?

--
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/SRBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashu...es/utility.htm


""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:AKqSTaUVDHA.2080@cpmsftngxa06.phx.gbl...

To avoid INF-related problems, take the similar MS's INF from the OS itself and
use it as a template/sample. Looks like this advice was already given here.

Max

For some reason my last post did not go out. I'll try
again.

I tried many things. I compared it against others, I
tried chkinf, but it gaves its own errors about
chkinf.pm. And yes I do have the perl intpreter. The
driver is the I82930 will 4 lines changed. They changed
the pipe name in two places and two array element numbers
in two other places. Then compiled and sent out. It
works on my XP box but not on the latitude D600 with XP.

I'm posting the inf here. Can someone please check it and
see what I'm missing, if anything?

thanks,


[Version]
Signature="$WINDOWS NT$"
Class=USB
ClassGUID={36FC9E60-C465-11CF-8056-444553540000}
provider=%NetChip%
LayoutFile=layout.inf
DriverVer=03/27/2001

[ControlFlags]
ExcludeFromSelect = *

[DestinationDirs]
;DefaultDestDir = 11
NcUSB.CopyList = 11
NcUSB.CopyListSYS.NT = 10, system32\drivers

[Manufacturer]
%NetChip%=NetChip

[NetChip]
%NetChipUsb.Loopback%=NcUSB, USB\VID_0525&PID_2888
%NetChipUsb.Iso%=NcUSB, USB\VID_0525&PID_100D
%NetChipUsb.Transfer%=NcUSB, USB\VID_0525&PID_1000

[NcUSB]
AddReg=NcUSB.AddReg
CopyFiles=NcUSB.CopyList

[NcUSB.NT]
AddReg=NcUSB.AddReg.NT
CopyFiles=NcUSB.CopyListSYS.NT

[NcUSB.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,NcUsb.SYS

[NcUSB.AddReg.NT]
; HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,NcUsb.SYS

[NcUSB.CopyList]
NcUsb.sys

[NcUSB.CopyListSYS.NT]
NcUsb.sys

[NcUSB.NT.Services]
AddService = netchip,0x00000002, NcUSB.AddService

[NcUSB.AddService]
DisplayName = %NetChipUsb.SvcDesc%
ServiceType = 1
StartType = 2
ErrorControl = 1
ServiceBinary = %12%\ncusb.sys
LoadOrderGroup = Base


;---------------------------------------------------------
------;

[Strings]
NetChip = "NetChip"
NetChipUsb.Loopback = "NetChip USB Evaluation Board -
Loopback mode"
NetChipUsb.Iso = "NetChip USB Evaluation Board -
ISO mode"
NetChipUsb.Transfer = "NetChip USB Evaluation Board -
Transfer mode"
NetChipUsb.SvcDesc = "Netchip Service"

I have 0% experience with the setupapi. Where would I
begin to learn how to use the logger? Thanks.

search for "setupapi.log" in the ddk help

jolyon

"Sean Whitesell" <seanw@vigoris.net> wrote in message
news:092a01c355d1$ea7e2fd0$a601280a@phx.gbl...

Ok, I think I'm getting somewhere. Thanks for the
setupapi log help. I found that the last line entered
before the BSOD said it was restarting the device. Is
there a way to tell it not to do this?

Thanks