Hi All,
I developed an NDIS Protocol Driver.
I Installed it on pre vista OSs and this worked fine (NOTE: THE DRIVER IS NOT SIGNED YET)
i am trying to install it on a Windows 7 32bit machine for testing reasons but when i go to to install it (right click on connection –> properties –> install —> protocol —> select inf file—> select .sys file)
I get the following error:
"Could Not add the requested feature: The error is: the system cannot find the specified file "
any ideas??
Thanks !!!
My guess is that your INF file has problems.
Run it through the chkinf tool provided in the WDK.
Compare your INF file with INF files provided with WDK NDISPROT sample.
Thomas F. Divine
http://www.pcausa.com
From:
Sent: Wednesday, February 09, 2011 9:40 AM
To: “Windows System Software Devs Interest List”
Subject: [ntdev] Windows 7 32 bit - NDIS Protocol Driver
> Hi All,
>
> I developed an NDIS Protocol Driver.
>
> I Installed it on pre vista OSs and this worked fine (NOTE: THE DRIVER
> IS NOT SIGNED YET)
>
> i am trying to install it on a Windows 7 32bit machine for testing reasons
> but when i go to to install it (right click on connection –>
> properties –> install —> protocol —> select inf file—> select .sys
> file)
>
> I get the following error:
>
> "Could Not add the requested feature: The error is: the system cannot
> find the specified file "
>
> any ideas??
>
> Thanks !!!
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
I did and infact it does have an error but it shouldnt prevent it from installing since it installed perfactly fine on pre-vista os with this error.
Here is the log…
NTLOG REPORT--------------
Total Lines: 88 |
Total Errors: 1 |
| Total Warnings: 2 |
|---|
| Line 4: ERROR: (E22.1.1081) Directive: CatalogFile required (and must not be blank) in section [Version] for WHQL digital signature. |
| Line 0: WARNING: (W22.1.2212) No Copyright information found. |
| Line 55: WARNING: (W22.1.2083) Section [INSTALL.REMOVE.SERVICES] not referenced |
Actually, chkinf was giving you the answer to your problem.
If you have a CatalogFile entry in your INF, then you must have a signed
.CAT file to go with it. Absolute must for Vista and later. Might get away
without it on XP.
You have two choices:
1.) Comment out the CatalogFile entry in your INF
2.) Sign your install files.
Good luck!
Thomas F. Divine
http://www.pcausa.com
From:
Sent: Wednesday, February 09, 2011 10:19 AM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] Windows 7 32 bit - NDIS Protocol Driver
> I did and infact it does have an error but it shouldnt prevent it from
> installing since it installed perfactly fine on pre-vista os with this
> error.
>
> Here is the log…
>
> NTLOG REPORT--------------
> Total Lines: 88 |
> Total Errors: 1 |
> Total Warnings: 2 |
> --------------------------
> Line 4: ERROR: (E22.1.1081) Directive: CatalogFile required (and must not
> be blank) in section [Version] for WHQL digital signature.
> Line 0: WARNING: (W22.1.2212) No Copyright information found.
> Line 55: WARNING: (W22.1.2083) Section [INSTALL.REMOVE.SERVICES] not
> referenced
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
Assuming that any error or warning from ChkInf will not stop an install,
is in general a really bad idea. And yes you can install on one system
even though you can on another. The error you posted in the original
question I’ve seen a lot (on Win7, but not earlier systems) if you don’t
have your driver in an i386 directory under the location of the INF.
To really debug this, turn on SetupApi logging and give us the log.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“xxxxx@hotmail.com” wrote in
message news:xxxxx@ntdev:
> I did and infact it does have an error but it shouldnt prevent it from installing since it installed perfactly fine on pre-vista os with this error.
>
> Here is the log…
>
> NTLOG REPORT--------------
> Total Lines: 88 |
> Total Errors: 1 |
> Total Warnings: 2 |
> --------------------------
> Line 4: ERROR: (E22.1.1081) Directive: CatalogFile required (and must not be blank) in section [Version] for WHQL digital signature.
> Line 0: WARNING: (W22.1.2212) No Copyright information found.
> Line 55: WARNING: (W22.1.2083) Section [INSTALL.REMOVE.SERVICES] not referenced
I placed the INF file inside the i386 directory and it worked
is this one of those strange windows thingies?? or is there a valid technical reason for this?
No you should not have had to place the INF inside of i386, in fact it
will mess you up later. What was needed is that the driver and any
other install files be under i386.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“xxxxx@hotmail.com” wrote in
message news:xxxxx@ntdev:
> I placed the INF file inside the i386 directory and it worked
>
> is this one of those strange windows thingies?? or is there a valid technical reason for this?
Nope. It’s not one of those strange Windows thingies.
It’s something wrong with your INF file or an unsigned .CAT file.
I have been installing NDIS protocol drivers for years on platforms from DOS
through server 2008.
I have never had to copy the INF to the i386 folder to install. Sorry.
That’s not the solution.
It is something else entirely for sure!
Take Don’s suggestion and examine the SetupApi log.
Good luck!
Thomas F. Divine
From:
Sent: Wednesday, February 09, 2011 10:44 AM
To: “Windows System Software Devs Interest List”
Subject: RE:[ntdev] Windows 7 32 bit - NDIS Protocol Driver
> I placed the INF file inside the i386 directory and it worked
>
> is this one of those strange windows thingies?? or is there a valid
> technical reason for this?
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer