Problem installing drivers on Vista

I am currently trying to debug my driver installation on Vista Beta2. I
compiled a working Windows XP 32 bit driver set using the Vista Beta2 WDK. I
am trying to install it and I am not sucessfull. I get the following lines
in the setupapi.dev.log file

!!! ndv: Driver Package import failed for new device...intalling NULL driver.
!!! ndv: Error 122: The data area passed to a system call is too small.

I don't have a clue what this means. Can anyone help?

I tried to install my package with devcon utility. It copies my package,
creates a oem0.inf. If I do a scan for hardware changes after, it is not
better that poiting to my original INF. I bassically get the same error.

Eliyas
Thu Sep 14 09:30:51 CDT 2006

Did you run chkinf on your INF?

On Vista there is an inbox utility that you can use to preinstall driver
packages. It's called pnputil.exe. When I'm writing an INF, I use this
utility to make sure whether my INF is correct or not by installing the
package. It's lot easier to install and delete packages this way.
Especially, if you miss out any files in your package, this utility will
fail to install the package and you can find the issue right away.

-Eliyas

"RAZ" <RAZ@discussions.microsoft.com> wrote in message
news:DAA851A2-9ACD-4AA0-8A7A-B73A3DE28A21@microsoft.com...
>I am currently trying to debug my driver installation on Vista Beta2. I
> compiled a working Windows XP 32 bit driver set using the Vista Beta2 WDK.
> I
> am trying to install it and I am not sucessfull. I get the following
> lines
> in the setupapi.dev.log file
>
> !!! ndv: Driver Package import failed for new device...intalling NULL
> driver.
> !!! ndv: Error 122: The data area passed to a system call is too small.
>
> I don't have a clue what this means. Can anyone help?
>
> I tried to install my package with devcon utility. It copies my package,
> creates a oem0.inf. If I do a scan for hardware changes after, it is not
> better that poiting to my original INF. I bassically get the same error.
>
>
>

Eliyas
Thu Sep 14 10:48:04 CDT 2006

I had a discussion with the setup folks. It seems that on beta2, there has
been some reports of this failures due to certain classinstallers. Theses
issues have been fixed since then. So I suggest you upgrade your system to
RC1 and try again. If you run into this error on RC1 build, please post the
setupapi.dev.log and the INF.

-Eliyas

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:%23ZsrgpA2GHA.4300@TK2MSFTNGP03.phx.gbl...
> Did you run chkinf on your INF?
>
> On Vista there is an inbox utility that you can use to preinstall driver
> packages. It's called pnputil.exe. When I'm writing an INF, I use this
> utility to make sure whether my INF is correct or not by installing the
> package. It's lot easier to install and delete packages this way.
> Especially, if you miss out any files in your package, this utility will
> fail to install the package and you can find the issue right away.
>
> -Eliyas
>
> "RAZ" <RAZ@discussions.microsoft.com> wrote in message
> news:DAA851A2-9ACD-4AA0-8A7A-B73A3DE28A21@microsoft.com...
>>I am currently trying to debug my driver installation on Vista Beta2. I
>> compiled a working Windows XP 32 bit driver set using the Vista Beta2
>> WDK. I
>> am trying to install it and I am not sucessfull. I get the following
>> lines
>> in the setupapi.dev.log file
>>
>> !!! ndv: Driver Package import failed for new device...intalling NULL
>> driver.
>> !!! ndv: Error 122: The data area passed to a system call is too small.
>>
>> I don't have a clue what this means. Can anyone help?
>>
>> I tried to install my package with devcon utility. It copies my package,
>> creates a oem0.inf. If I do a scan for hardware changes after, it is not
>> better that poiting to my original INF. I bassically get the same error.
>>
>>
>>
>
>

RAZ
Thu Sep 14 14:19:02 CDT 2006

Thanks. While waiting for any reply, I tried many others things without
success. So my next step will be to install RC1. This will take me some
time. I will reply once I get results.

"Eliyas Yakub [MSFT]" wrote:

> I had a discussion with the setup folks. It seems that on beta2, there has
> been some reports of this failures due to certain classinstallers. Theses
> issues have been fixed since then. So I suggest you upgrade your system to
> RC1 and try again. If you run into this error on RC1 build, please post the
> setupapi.dev.log and the INF.
>
> -Eliyas
>
> "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> news:%23ZsrgpA2GHA.4300@TK2MSFTNGP03.phx.gbl...
> > Did you run chkinf on your INF?
> >
> > On Vista there is an inbox utility that you can use to preinstall driver
> > packages. It's called pnputil.exe. When I'm writing an INF, I use this
> > utility to make sure whether my INF is correct or not by installing the
> > package. It's lot easier to install and delete packages this way.
> > Especially, if you miss out any files in your package, this utility will
> > fail to install the package and you can find the issue right away.
> >
> > -Eliyas
> >
> > "RAZ" <RAZ@discussions.microsoft.com> wrote in message
> > news:DAA851A2-9ACD-4AA0-8A7A-B73A3DE28A21@microsoft.com...
> >>I am currently trying to debug my driver installation on Vista Beta2. I
> >> compiled a working Windows XP 32 bit driver set using the Vista Beta2
> >> WDK. I
> >> am trying to install it and I am not sucessfull. I get the following
> >> lines
> >> in the setupapi.dev.log file
> >>
> >> !!! ndv: Driver Package import failed for new device...intalling NULL
> >> driver.
> >> !!! ndv: Error 122: The data area passed to a system call is too small.
> >>
> >> I don't have a clue what this means. Can anyone help?
> >>
> >> I tried to install my package with devcon utility. It copies my package,
> >> creates a oem0.inf. If I do a scan for hardware changes after, it is not
> >> better that poiting to my original INF. I bassically get the same error.
> >>
> >>
> >>
> >
> >
>
>
>

RAZ
Mon Sep 18 09:06:02 CDT 2006

Well, even with RC1, I get the same problem. Any other ideas. Since the log
files and the inf are big, can I send this directly to someone? I am not
sure this list is the place to paste the content of multiple files.

"RAZ" wrote:

> Thanks. While waiting for any reply, I tried many others things without
> success. So my next step will be to install RC1. This will take me some
> time. I will reply once I get results.
>
> "Eliyas Yakub [MSFT]" wrote:
>
> > I had a discussion with the setup folks. It seems that on beta2, there has
> > been some reports of this failures due to certain classinstallers. Theses
> > issues have been fixed since then. So I suggest you upgrade your system to
> > RC1 and try again. If you run into this error on RC1 build, please post the
> > setupapi.dev.log and the INF.
> >
> > -Eliyas
> >
> > "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> > news:%23ZsrgpA2GHA.4300@TK2MSFTNGP03.phx.gbl...
> > > Did you run chkinf on your INF?
> > >
> > > On Vista there is an inbox utility that you can use to preinstall driver
> > > packages. It's called pnputil.exe. When I'm writing an INF, I use this
> > > utility to make sure whether my INF is correct or not by installing the
> > > package. It's lot easier to install and delete packages this way.
> > > Especially, if you miss out any files in your package, this utility will
> > > fail to install the package and you can find the issue right away.
> > >
> > > -Eliyas
> > >
> > > "RAZ" <RAZ@discussions.microsoft.com> wrote in message
> > > news:DAA851A2-9ACD-4AA0-8A7A-B73A3DE28A21@microsoft.com...
> > >>I am currently trying to debug my driver installation on Vista Beta2. I
> > >> compiled a working Windows XP 32 bit driver set using the Vista Beta2
> > >> WDK. I
> > >> am trying to install it and I am not sucessfull. I get the following
> > >> lines
> > >> in the setupapi.dev.log file
> > >>
> > >> !!! ndv: Driver Package import failed for new device...intalling NULL
> > >> driver.
> > >> !!! ndv: Error 122: The data area passed to a system call is too small.
> > >>
> > >> I don't have a clue what this means. Can anyone help?
> > >>
> > >> I tried to install my package with devcon utility. It copies my package,
> > >> creates a oem0.inf. If I do a scan for hardware changes after, it is not
> > >> better that poiting to my original INF. I bassically get the same error.
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> >

Khamsing
Tue Sep 19 12:12:03 CDT 2006

You must build a debug driver, hook up a debugger, then install your debug
driver, it will be successful. This is a feature of Vista to make sure that
driver is WHQL certified. For non-WHQL certified driver must be a debug
driver, a release driver will fail.

-Khamsing


"RAZ" <RAZ@discussions.microsoft.com> wrote in message
news:A4AE3A18-623F-42E7-A615-832180D37F78@microsoft.com...
> Well, even with RC1, I get the same problem. Any other ideas. Since the
> log
> files and the inf are big, can I send this directly to someone? I am not
> sure this list is the place to paste the content of multiple files.
>
> "RAZ" wrote:
>
>> Thanks. While waiting for any reply, I tried many others things without
>> success. So my next step will be to install RC1. This will take me some
>> time. I will reply once I get results.
>>
>> "Eliyas Yakub [MSFT]" wrote:
>>
>> > I had a discussion with the setup folks. It seems that on beta2, there
>> > has
>> > been some reports of this failures due to certain classinstallers.
>> > Theses
>> > issues have been fixed since then. So I suggest you upgrade your system
>> > to
>> > RC1 and try again. If you run into this error on RC1 build, please post
>> > the
>> > setupapi.dev.log and the INF.
>> >
>> > -Eliyas
>> >
>> > "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
>> > news:%23ZsrgpA2GHA.4300@TK2MSFTNGP03.phx.gbl...
>> > > Did you run chkinf on your INF?
>> > >
>> > > On Vista there is an inbox utility that you can use to preinstall
>> > > driver
>> > > packages. It's called pnputil.exe. When I'm writing an INF, I use
>> > > this
>> > > utility to make sure whether my INF is correct or not by installing
>> > > the
>> > > package. It's lot easier to install and delete packages this way.
>> > > Especially, if you miss out any files in your package, this utility
>> > > will
>> > > fail to install the package and you can find the issue right away.
>> > >
>> > > -Eliyas
>> > >
>> > > "RAZ" <RAZ@discussions.microsoft.com> wrote in message
>> > > news:DAA851A2-9ACD-4AA0-8A7A-B73A3DE28A21@microsoft.com...
>> > >>I am currently trying to debug my driver installation on Vista Beta2.
>> > >>I
>> > >> compiled a working Windows XP 32 bit driver set using the Vista
>> > >> Beta2
>> > >> WDK. I
>> > >> am trying to install it and I am not sucessfull. I get the
>> > >> following
>> > >> lines
>> > >> in the setupapi.dev.log file
>> > >>
>> > >> !!! ndv: Driver Package import failed for new device...intalling
>> > >> NULL
>> > >> driver.
>> > >> !!! ndv: Error 122: The data area passed to a system call is too
>> > >> small.
>> > >>
>> > >> I don't have a clue what this means. Can anyone help?
>> > >>
>> > >> I tried to install my package with devcon utility. It copies my
>> > >> package,
>> > >> creates a oem0.inf. If I do a scan for hardware changes after, it
>> > >> is not
>> > >> better that poiting to my original INF. I bassically get the same
>> > >> error.
>> > >>
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>> >

Maxim
Tue Sep 19 12:19:52 CDT 2006

Vista driver signing has nothing to do with WHQL, it is just to provide the
author's identity, not the quality assurance.
WHQL in some form will still survive, but will not prevent the driver from
loading.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Khamsing" <Vn@nooneknows.com> wrote in message
news:450ff2cd_2@newsfeed.slurp.net...
> You must build a debug driver, hook up a debugger, then install your debug
> driver, it will be successful. This is a feature of Vista to make sure that
> driver is WHQL certified. For non-WHQL certified driver must be a debug
> driver, a release driver will fail.
>
> -Khamsing
>
>
> "RAZ" <RAZ@discussions.microsoft.com> wrote in message
> news:A4AE3A18-623F-42E7-A615-832180D37F78@microsoft.com...
> > Well, even with RC1, I get the same problem. Any other ideas. Since the
> > log
> > files and the inf are big, can I send this directly to someone? I am not
> > sure this list is the place to paste the content of multiple files.
> >
> > "RAZ" wrote:
> >
> >> Thanks. While waiting for any reply, I tried many others things without
> >> success. So my next step will be to install RC1. This will take me some
> >> time. I will reply once I get results.
> >>
> >> "Eliyas Yakub [MSFT]" wrote:
> >>
> >> > I had a discussion with the setup folks. It seems that on beta2, there
> >> > has
> >> > been some reports of this failures due to certain classinstallers.
> >> > Theses
> >> > issues have been fixed since then. So I suggest you upgrade your system
> >> > to
> >> > RC1 and try again. If you run into this error on RC1 build, please post
> >> > the
> >> > setupapi.dev.log and the INF.
> >> >
> >> > -Eliyas
> >> >
> >> > "Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
> >> > news:%23ZsrgpA2GHA.4300@TK2MSFTNGP03.phx.gbl...
> >> > > Did you run chkinf on your INF?
> >> > >
> >> > > On Vista there is an inbox utility that you can use to preinstall
> >> > > driver
> >> > > packages. It's called pnputil.exe. When I'm writing an INF, I use
> >> > > this
> >> > > utility to make sure whether my INF is correct or not by installing
> >> > > the
> >> > > package. It's lot easier to install and delete packages this way.
> >> > > Especially, if you miss out any files in your package, this utility
> >> > > will
> >> > > fail to install the package and you can find the issue right away.
> >> > >
> >> > > -Eliyas
> >> > >
> >> > > "RAZ" <RAZ@discussions.microsoft.com> wrote in message
> >> > > news:DAA851A2-9ACD-4AA0-8A7A-B73A3DE28A21@microsoft.com...
> >> > >>I am currently trying to debug my driver installation on Vista Beta2.
> >> > >>I
> >> > >> compiled a working Windows XP 32 bit driver set using the Vista
> >> > >> Beta2
> >> > >> WDK. I
> >> > >> am trying to install it and I am not sucessfull. I get the
> >> > >> following
> >> > >> lines
> >> > >> in the setupapi.dev.log file
> >> > >>
> >> > >> !!! ndv: Driver Package import failed for new device...intalling
> >> > >> NULL
> >> > >> driver.
> >> > >> !!! ndv: Error 122: The data area passed to a system call is too
> >> > >> small.
> >> > >>
> >> > >> I don't have a clue what this means. Can anyone help?
> >> > >>
> >> > >> I tried to install my package with devcon utility. It copies my
> >> > >> package,
> >> > >> creates a oem0.inf. If I do a scan for hardware changes after, it
> >> > >> is not
> >> > >> better that poiting to my original INF. I bassically get the same
> >> > >> error.
> >> > >>
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> >
> >> >
> >> >
>
>

Don
Tue Sep 19 12:22:02 CDT 2006


"Khamsing" <Vn@nooneknows.com> wrote in message
> You must build a debug driver, hook up a debugger, then install your debug
> driver, it will be successful. This is a feature of Vista to make sure
> that driver is WHQL certified. For non-WHQL certified driver must be a
> debug driver, a release driver will fail.
>

Sorry but there are a number of things wrong with the above statement.
First the OP had a specific problem the error message from this type of
problem is not indicative of what you are stating. Second, it is not WHQL
certification of the driver, it is digital signing of the driver, this is a
different thing. Third it does not matter if the driver is debug or free it
matters that the debugger is connected if you want to install an unsigned
driver on Vista. Finally, you can still install an unsigned driver, you
need to choose the option under the F8 choices when you boot.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply

RAZ
Tue Sep 19 13:38:02 CDT 2006

I found the problem! it seems that there is a bug with Vista and the size of
a list of PCI IDs. a line too big in the INF produce the error I reported.
If I remove all the IDs and keep just one, the bug disappears. Here is how
my problematic INF line looks like. The formating is a little bit different
than this but the esssential is the size of the list. It looks like it is
too big and maybe gets truckated.

%MyDriver% = MyDriver.Install,
PCI\VEN_BBBB&DEV_8160&SUBSYS_9000BBBB,\
PCI\VEN_BBBB&DEV_8160&SUBSYS_9001BBBB,\
PCI\VEN_BBBB&DEV_8160&SUBSYS_9010BBBB,\
PCI\VEN_BBBB&DEV_8160&SUBSYS_9011BBBB,\
PCI\VEN_BB2B&DEV_8160&SUBSYS_9020BBBB,\
PCI\VEN_BBBB&DEV_8160&SUBSYS_9021BBBB,\
PCI\VEN_BBBB&DEV_8190&SUBSYS_9000BBBB,\
PCI\VEN_BBBB&DEV_81B0&SUBSYS_9000BBBB,\
PCI\VEN_BBBB&DEV_8240&SUBSYS_9000BBBB,\
PCI\VEN_BBBB&DEV_8210&SUBSYS_9000BBBB,\
PCI\VEN_BBBB&DEV_81C0&SUBSYS_9000BBBB,\
PCI\VEN_BBBB&DEV_81D0&SUBSYS_9000BBBB

ChkInf do not see any problems with my INF file. I have not tested how many
IDs I can put. I will in the next days.




"Don Burn" wrote:

>
> "Khamsing" <Vn@nooneknows.com> wrote in message
> > You must build a debug driver, hook up a debugger, then install your debug
> > driver, it will be successful. This is a feature of Vista to make sure
> > that driver is WHQL certified. For non-WHQL certified driver must be a
> > debug driver, a release driver will fail.
> >
>
> Sorry but there are a number of things wrong with the above statement.
> First the OP had a specific problem the error message from this type of
> problem is not indicative of what you are stating. Second, it is not WHQL
> certification of the driver, it is digital signing of the driver, this is a
> different thing. Third it does not matter if the driver is debug or free it
> matters that the debugger is connected if you want to install an unsigned
> driver on Vista. Finally, you can still install an unsigned driver, you
> need to choose the option under the F8 choices when you boot.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>
>
>
>

Khamsing
Wed Sep 20 02:43:05 CDT 2006


"Don Burn" <burn@stopspam.acm.org> wrote in message
news:e%235gpAB3GHA.2176@TK2MSFTNGP04.phx.gbl...
>
> "Khamsing" <Vn@nooneknows.com> wrote in message
>> You must build a debug driver, hook up a debugger, then install your
>> debug driver, it will be successful. This is a feature of Vista to make
>> sure that driver is WHQL certified. For non-WHQL certified driver must
>> be a debug driver, a release driver will fail.
>>
>
> Sorry but there are a number of things wrong with the above statement.
> First the OP had a specific problem the error message from this type of
> problem is not indicative of what you are stating. Second, it is not WHQL
> certification of the driver, it is digital signing of the driver, this is
> a different thing. Third it does not matter if the driver is debug or
> free it matters that the debugger is connected if you want to install an
> unsigned driver on Vista. Finally, you can still install an unsigned
> driver, you need to choose the option under the F8 choices when you boot.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> http://www.windrvr.com
> Remove StopSpam from the email to reply
>


You are right Don, yes there is a difference. I remember it now "digital
signing of the driver", that's what I meant to say. Thanks for your
correction.

-Khamsing

Khamsing
Wed Sep 20 02:55:22 CDT 2006

Hi Don,
Have you worked for Microsoft before in 1996 under Premier DDK support
dept.? If the answer is Yes, I think I have met you and may have worked
with you before briefly, you probably do not know me by name.

It's good to see you here.

-Khamsing.

Don
Wed Sep 20 06:10:40 CDT 2006

Nope, I never worked for Microsoft and still do not. In 1996 I was the
software architect for a small fault tolerant firm known as Sequoia Systems
Inc. Since 1998 I have been an independant consultant in the Windows driver
space.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply




"Khamsing" <Vn@nooneknows.com> wrote in message
news:4510c1d3_2@newsfeed.slurp.net...
> Hi Don,
> Have you worked for Microsoft before in 1996 under Premier DDK support
> dept.? If the answer is Yes, I think I have met you and may have worked
> with you before briefly, you probably do not know me by name.
>
> It's good to see you here.
>
> -Khamsing.
>
>