Code 37

NTDEV
1

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

2

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

3

Does import error need a debugging session and a breakpoint to check? Is Depends.exe (shipped with VC6, 7, 8 and SDK) enough?

BR, Raymond

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: 2007??11??1?? 10:55
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

4

You can use depends.exe if you have it w/out the need to attempt to load the driver

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Zhang, Raymond
Sent: Wednesday, October 31, 2007 8:19 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Code 37

Does import error need a debugging session and a breakpoint to check? Is Depends.exe (shipped with VC6, 7, 8 and SDK) enough?

BR, Raymond

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: 2007$BG/(B11$B7n(B1$BF|(B 10:55
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

—
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

5

You can use depends.exe if you have it w/out the need to attempt to load the driver

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Zhang, Raymond
Sent: Wednesday, October 31, 2007 8:19 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Code 37

Does import error need a debugging session and a breakpoint to check? Is Depends.exe (shipped with VC6, 7, 8 and SDK) enough?

BR, Raymond

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Doron Holan
Sent: 2007$BG/(B11$B7n(B1$BF|(B 10:55
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

—
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

6

Hi, Doron,

This is the 6001 WDK on a Vista Target. I do not get the breakpoint I put in my DriverEntry, I’ll try FxDriverEntry and see what’s happening. Thanks!

Alberto.

----- Original Message -----
From: Doron Holan
To: Windows System Software Devs Interest List
Sent: Wednesday, October 31, 2007 10:55 PM
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

7

The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well.

d

Sent using my smartphone, apologies forany typos

-----Original Message-----
From: “Alberto Moreira”
To: “Windows System Software Devs Interest List”
Sent: 11/01/07 7:19 PM
Subject: Re: [ntdev] Code 37

Hi, Doron,

This is the 6001 WDK on a Vista Target. I do not get the breakpoint I put in my DriverEntry, I’ll try FxDriverEntry and see what’s happening. Thanks!

Alberto.

----- Original Message -----
From: Doron Holanmailto:xxxxx
To: Windows System Software Devs Interest Listmailto:xxxxx
Sent: Wednesday, October 31, 2007 10:55 PM
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

—
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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

8

Thanks, Doron! I took a closer look, and here’s what I found.

I get control at FxDriverEntry ok. However, after a while it calls WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a C0000024 status. That eventually leads IopLoadDriver to return a C0000365 status, which eventually is converted to code 37.

Also, I’m not sure I quite undertand what you said, what do you mean by “install down level” ?

And here’s a suggestion. Would it be too hard to percolate up these statuses (and other such) into some kind of “Expert Diagnostics” button in the Install Wizard ? They might save a lot of debugging time!

Alberto.

----- Original Message -----
From: Doron Holan
To: Windows System Software Devs Interest List
Sent: Thursday, November 01, 2007 11:07 PM
Subject: RE: [ntdev] Code 37

The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well.

d

Sent using my smartphone, apologies forany typos

-----Original Message-----
From: “Alberto Moreira”
To: “Windows System Software Devs Interest List”
Sent: 11/01/07 7:19 PM
Subject: Re: [ntdev] Code 37

Hi, Doron,

This is the 6001 WDK on a Vista Target. I do not get the breakpoint I put in my DriverEntry, I’ll try FxDriverEntry and see what’s happening. Thanks!

Alberto.

----- Original Message -----
From: Doron Holan
To: Windows System Software Devs Interest List
Sent: Wednesday, October 31, 2007 10:55 PM
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

—
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

—
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

9

The 6001 WDK ships with KMDF v1.7. vista contains v1.5. the required runtime version is embedded in your driver so when you try to load a v1.7 driver on a system with v1.5, it fails. The KMDF coinstaller fixes this by installing the required runtime for you during installation. Right now the v1.7 coinstaller that ships in the 6001 wdk does not install on vista or previous OS’s (which is what I meant by downlevel). By building in the 6000 wdk you get v1.5 and a coinstaller that does install on Vista and previous releases.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Saturday, November 03, 2007 6:25 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Code 37

Thanks, Doron! I took a closer look, and here’s what I found.

I get control at FxDriverEntry ok. However, after a while it calls WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a C0000024 status. That eventually leads IopLoadDriver to return a C0000365 status, which eventually is converted to code 37.

Also, I’m not sure I quite undertand what you said, what do you mean by “install down level” ?

And here’s a suggestion. Would it be too hard to percolate up these statuses (and other such) into some kind of “Expert Diagnostics” button in the Install Wizard ? They might save a lot of debugging time!

Alberto.

----- Original Message -----
From: Doron Holanmailto:xxxxx
To: Windows System Software Devs Interest Listmailto:xxxxx
Sent: Thursday, November 01, 2007 11:07 PM
Subject: RE: [ntdev] Code 37

The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well.

d

Sent using my smartphone, apologies forany typos

-----Original Message-----

From: “Alberto Moreira” mailto:xxxxx

Tomailto:xxxxx: “Windows System Software Devs Interest List” mailto:xxxxx

Sentmailto:xxxxx: 11/01/07 7:19 PM

Subject: Re: [ntdev] Code 37

Hi, Doron,

This is the 6001 WDK on a Vista Target. I do not get the breakpoint I put in my DriverEntry, I’ll try FxDriverEntry and see what’s happening. Thanks!

Alberto.

----- Original Message -----
From: Doron Holanmailto:xxxxx
To: Windows System Software Devs Interest Listmailto:xxxxx
Sent: Wednesday, October 31, 2007 10:55 PM
Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.commailto:xxxxx [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

—
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

—
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

—
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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

10

Thanks again, Doron. As soon as I get to the Office on Monday morning I’ll load v1.5. Much appreciated, specially your very quick answers!

Alberto.

----- Original Message -----
From: Doron Holan
To: Windows System Software Devs Interest List
Sent: Saturday, November 03, 2007 11:16 AM
Subject: RE: [ntdev] Code 37

The 6001 WDK ships with KMDF v1.7. vista contains v1.5. the required runtime version is embedded in your driver so when you try to load a v1.7 driver on a system with v1.5, it fails. The KMDF coinstaller fixes this by installing the required runtime for you during installation. Right now the v1.7 coinstaller that ships in the 6001 wdk does not install on vista or previous OS’s (which is what I meant by downlevel). By building in the 6000 wdk you get v1.5 and a coinstaller that does install on Vista and previous releases.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Saturday, November 03, 2007 6:25 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Code 37

Thanks, Doron! I took a closer look, and here’s what I found.

I get control at FxDriverEntry ok. However, after a while it calls WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a C0000024 status. That eventually leads IopLoadDriver to return a C0000365 status, which eventually is converted to code 37.

Also, I’m not sure I quite undertand what you said, what do you mean by “install down level” ?

And here’s a suggestion. Would it be too hard to percolate up these statuses (and other such) into some kind of “Expert Diagnostics” button in the Install Wizard ? They might save a lot of debugging time!

Alberto.

----- Original Message -----

From: Doron Holan

To: Windows System Software Devs Interest List

Sent: Thursday, November 01, 2007 11:07 PM

Subject: RE: [ntdev] Code 37

The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well. d Sent using my smartphone, apologies forany typos -----Original Message-----From: “Alberto Moreira” To: “Windows System Software Devs Interest List” Sent: 11/01/07 7:19 PMSubject: Re: [ntdev] Code 37 Hi, Doron,

This is the 6001 WDK on a Vista Target. I do not get the breakpoint I put in my DriverEntry, I’ll try FxDriverEntry and see what’s happening. Thanks!

Alberto.

----- Original Message -----

From: Doron Holan

To: Windows System Software Devs Interest List

Sent: Wednesday, October 31, 2007 10:55 PM

Subject: RE: [ntdev] Code 37

What WDK did you build your driver in? in the 6001 WDK or the Vista 6000 WDK? But a breakpoint on !FxDriverEntry and see if that is called. If it does, that would rule out unresolved exports. If the bp is not hit, I would guess an unresolved import is preventing your driver from loading.

d

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Alberto Moreira
Sent: Wednesday, October 31, 2007 6:02 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Code 37

Hello, Peoples,

I have an easy problem but somehow I’m not finding its origin. I have converted my driver to WDF, and I’m trying to install it on Vista, so that I can break at the DriverEntry routine and begin testing it. I took my old and tried .INF routine and just added the WDF lines (straight from the Toaster Function Drive example), and guess what, I’m being bounced by the Installer with a Code 37: the driver’s not installed, and my DriverEntry breakpoint never triggers. I got to a point where the service entries in the Registry are identical for the old and for the new driver (I’m using different names for them so that I can have both entries in the hive), and yet the old one installs fine, while the new one barfs.

I don’t have any experience with WDF, this is my first time. Do any of you have experience with that Code 37 ? Tks,

Alberto.

—
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

—
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

—
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

—
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

—
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

—
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

11

Alberto Moreira wrote:

Thanks, Doron! I took a closer look, and here’s what I found.

I get control at FxDriverEntry ok. However, after a while it calls
WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a
C0000024 status. That eventually leads IopLoadDriver to return a
C0000365 status, which eventually is converted to code 37.

Also, I’m not sure I quite undertand what you said, what do you mean by
“install down level” ?

And here’s a suggestion. Would it be too hard to percolate up these
statuses (and other such) into some kind of “Expert Diagnostics” button
in the Install Wizard ? They might save a lot of debugging time!

Alberto.

----- Original Message -----
*From:* Doron Holan mailto:xxxxx
> To: Windows System Software Devs Interest List
> mailto:xxxxx
> Sent: Thursday, November 01, 2007 11:07 PM
> Subject: RE: [ntdev] Code 37
>
> The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well.
>
> d
>
> Sent using my smartphone, apologies forany typos
>
> -----Original Message-----
> From: “Alberto Moreira”
> To mailto:xxxxxTo>: “Windows System Software Devs Interest List”
> Sent mailto:xxxxxSent>: 11/01/07 7:19 PM
> Subject: Re: [ntdev] Code 37
>
>
> Hi, Doron,
>
> This is the 6001 WDK on a Vista Target. I do not get the breakpoint
> I put in my DriverEntry, I’ll try FxDriverEntry and see what’s
> happening. Thanks!
>
> Alberto.
>
>
> ----- Original Message -----
> From: Doron Holan mailto:xxxxx
> To: Windows System Software Devs Interest List
> mailto:xxxxx
> Sent: Wednesday, October 31, 2007 10:55 PM
> Subject: RE: [ntdev] Code 37
>
> What WDK did you build your driver in? in the 6001 WDK or the
> Vista 6000 WDK? But a breakpoint on !FxDriverEntry
> and see if that is called. If it does, that would rule out
> unresolved exports. If the bp is not hit, I would guess an
> unresolved import is preventing your driver from loading.
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com
> mailto:xxxxx
> [mailto:xxxxx@lists.osr.com] *On Behalf Of
> *Alberto Moreira
> Sent: Wednesday, October 31, 2007 6:02 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Code 37
>
>
>
> Hello, Peoples,
>
>
>
> I have an easy problem but somehow I’m not finding its origin. I
> have converted my driver to WDF, and I’m trying to install it on
> Vista, so that I can break at the DriverEntry routine and begin
> testing it. I took my old and tried .INF routine and just added
> the WDF lines (straight from the Toaster Function Drive
> example), and guess what, I’m being bounced by the Installer
> with a Code 37: the driver’s not installed, and my DriverEntry
> breakpoint never triggers. I got to a point where the service
> entries in the Registry are identical for the old and for the
> new driver (I’m using different names for them so that I can
> have both entries in the hive), and yet the old one installs
> fine, while the new one barfs.
>
>
>
> I don’t have any experience with WDF, this is my first time. Do
> any of you have experience with that Code 37 ? Tks,
>
>
>
>
>
> Alberto.
>
>
>
>
>
>
> —
> 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
>
>
> —
> 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
>
>
> —
> 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
>
> —
> 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
This is really good idea - some form enhanced installation debugging.
Setupapi.log already does some of this, perhaps all, but it is a little
overwhelming, and installation problems are common enough that something
like this would be welcomed by many, I think.

mm</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

12

Other than those developing drivers, who would it be useful for? My mom or brother certainly would not have any idea with what to do with this info.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Sunday, November 04, 2007 5:55 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Code 37

Alberto Moreira wrote:

Thanks, Doron! I took a closer look, and here’s what I found.

I get control at FxDriverEntry ok. However, after a while it calls
WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a
C0000024 status. That eventually leads IopLoadDriver to return a
C0000365 status, which eventually is converted to code 37.

Also, I’m not sure I quite undertand what you said, what do you mean by
“install down level” ?

And here’s a suggestion. Would it be too hard to percolate up these
statuses (and other such) into some kind of “Expert Diagnostics” button
in the Install Wizard ? They might save a lot of debugging time!

Alberto.

----- Original Message -----
*From:* Doron Holan mailto:xxxxx
> To: Windows System Software Devs Interest List
> mailto:xxxxx
> Sent: Thursday, November 01, 2007 11:07 PM
> Subject: RE: [ntdev] Code 37
>
> The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well.
>
> d
>
> Sent using my smartphone, apologies forany typos
>
> -----Original Message-----
> From: “Alberto Moreira”
> To mailto:xxxxxTo>: “Windows System Software Devs Interest List”
> Sent mailto:xxxxxSent>: 11/01/07 7:19 PM
> Subject: Re: [ntdev] Code 37
>
>
> Hi, Doron,
>
> This is the 6001 WDK on a Vista Target. I do not get the breakpoint
> I put in my DriverEntry, I’ll try FxDriverEntry and see what’s
> happening. Thanks!
>
> Alberto.
>
>
> ----- Original Message -----
> From: Doron Holan mailto:xxxxx
> To: Windows System Software Devs Interest List
> mailto:xxxxx
> Sent: Wednesday, October 31, 2007 10:55 PM
> Subject: RE: [ntdev] Code 37
>
> What WDK did you build your driver in? in the 6001 WDK or the
> Vista 6000 WDK? But a breakpoint on !FxDriverEntry
> and see if that is called. If it does, that would rule out
> unresolved exports. If the bp is not hit, I would guess an
> unresolved import is preventing your driver from loading.
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com
> mailto:xxxxx
> [mailto:xxxxx@lists.osr.com] *On Behalf Of
> *Alberto Moreira
> Sent: Wednesday, October 31, 2007 6:02 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Code 37
>
>
>
> Hello, Peoples,
>
>
>
> I have an easy problem but somehow I’m not finding its origin. I
> have converted my driver to WDF, and I’m trying to install it on
> Vista, so that I can break at the DriverEntry routine and begin
> testing it. I took my old and tried .INF routine and just added
> the WDF lines (straight from the Toaster Function Drive
> example), and guess what, I’m being bounced by the Installer
> with a Code 37: the driver’s not installed, and my DriverEntry
> breakpoint never triggers. I got to a point where the service
> entries in the Registry are identical for the old and for the
> new driver (I’m using different names for them so that I can
> have both entries in the hive), and yet the old one installs
> fine, while the new one barfs.
>
>
>
> I don’t have any experience with WDF, this is my first time. Do
> any of you have experience with that Code 37 ? Tks,
>
>
>
>
>
> Alberto.
>
>
>
>
>
>
> —
> 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
>
>
> —
> 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
>
>
> —
> 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
>
> —
> 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
This is really good idea - some form enhanced installation debugging.
Setupapi.log already does some of this, perhaps all, but it is a little
overwhelming, and installation problems are common enough that something
like this would be welcomed by many, I think.

mm

—
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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

13

Of course not, nor do they know what to do with ‘37,’ and neither do we
for that matter, but driver installation issues are, at the moment,
really common, particularly with WDF, in my opinion, and as far as
diagnostics go ‘37’ isn’t very helpful. I think being able to get at
this information without WinDbg would be very useful, especially
remotely. It’s not like it’s going to solve most of your problems, but
it would be a place to start, and, in my experience, there is usually at
least one person at a client’s site who would be capable of collecting
and sending this sort of information were it easy to produce. I realize
that it is not exactly the sort of thing that would be considered a
feature, but neither is a driver that otherwise works failing
installation with no useful information. I realize that we are a very
small group, but look at this thread - this is a lot of work to figure
this out, and it involved very competent people. I would agree with you
that this not an ideal feature for a push button, but it seems like
other windows components have “advanced” diagnostic information, and
while this sort of thing seems like what the Event log is used for, it
is just a swamp of useless information at this point. Fundamentally, it
would be nice to have some idea of what the problem is before heading to
a site or down the hall or wherever, more than likely guaranteeing a
return visit.

It’s not an easy problem, and I would really like to see a “button”
either, but the problem, in my opinion, needs some attention.

mm

Doron Holan wrote:
Other than those developing drivers, who would it be useful for? My mom or brother certainly would not have any idea with what to do with this info.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Sunday, November 04, 2007 5:55 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Code 37

Alberto Moreira wrote:
> Thanks, Doron! I took a closer look, and here’s what I found.
>
> I get control at FxDriverEntry ok. However, after a while it calls
> WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a
> C0000024 status. That eventually leads IopLoadDriver to return a
> C0000365 status, which eventually is converted to code 37.
>
> Also, I’m not sure I quite undertand what you said, what do you mean by
> “install down level” ?
>
> And here’s a suggestion. Would it be too hard to percolate up these
> statuses (and other such) into some kind of “Expert Diagnostics” button
> in the Install Wizard ? They might save a lot of debugging time!
>
>
> Alberto.
>
>
>
> ----- Original Message -----
> *From:* Doron Holan mailto:xxxxx
>> To: Windows System Software Devs Interest List
>> mailto:xxxxx
>> Sent: Thursday, November 01, 2007 11:07 PM
>> Subject: RE: [ntdev] Code 37
>>
>> The 6001 wdk ships with kmdf 1.7, the co installer that it ships with does not install down level. Use the 6000 wdk and all will be well.
>>
>> d
>>
>> Sent using my smartphone, apologies forany typos
>>
>> -----Original Message-----
>> From: “Alberto Moreira”
>> To mailto:xxxxxTo>: “Windows System Software Devs Interest List”
>> Sent mailto:xxxxxSent>: 11/01/07 7:19 PM
>> Subject: Re: [ntdev] Code 37
>>
>>
>> Hi, Doron,
>>
>> This is the 6001 WDK on a Vista Target. I do not get the breakpoint
>> I put in my DriverEntry, I’ll try FxDriverEntry and see what’s
>> happening. Thanks!
>>
>> Alberto.
>>
>>
>> ----- Original Message -----
>> From: Doron Holan mailto:xxxxx
>> To: Windows System Software Devs Interest List
>> mailto:xxxxx
>> Sent: Wednesday, October 31, 2007 10:55 PM
>> Subject: RE: [ntdev] Code 37
>>
>> What WDK did you build your driver in? in the 6001 WDK or the
>> Vista 6000 WDK? But a breakpoint on !FxDriverEntry
>> and see if that is called. If it does, that would rule out
>> unresolved exports. If the bp is not hit, I would guess an
>> unresolved import is preventing your driver from loading.
>>
>>
>>
>> d
>>
>>
>>
>> From: xxxxx@lists.osr.com
>> mailto:xxxxx
>> [mailto:xxxxx@lists.osr.com] *On Behalf Of
>> *Alberto Moreira
>> Sent: Wednesday, October 31, 2007 6:02 PM
>> To: Windows System Software Devs Interest List
>> Subject: [ntdev] Code 37
>>
>>
>>
>> Hello, Peoples,
>>
>>
>>
>> I have an easy problem but somehow I’m not finding its origin. I
>> have converted my driver to WDF, and I’m trying to install it on
>> Vista, so that I can break at the DriverEntry routine and begin
>> testing it. I took my old and tried .INF routine and just added
>> the WDF lines (straight from the Toaster Function Drive
>> example), and guess what, I’m being bounced by the Installer
>> with a Code 37: the driver’s not installed, and my DriverEntry
>> breakpoint never triggers. I got to a point where the service
>> entries in the Registry are identical for the old and for the
>> new driver (I’m using different names for them so that I can
>> have both entries in the hive), and yet the old one installs
>> fine, while the new one barfs.
>>
>>
>>
>> I don’t have any experience with WDF, this is my first time. Do
>> any of you have experience with that Code 37 ? Tks,
>>
>>
>>
>>
>>
>> Alberto.
>>
>>
>>
>>
>>
>>
>> —
>> 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
>>
>>
>> —
>> 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
>>
>>
>> —
>> 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
>>
>> —
>> 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
> This is really good idea - some form enhanced installation debugging.
> Setupapi.log already does some of this, perhaps all, but it is a little
> overwhelming, and installation problems are common enough that something
> like this would be welcomed by many, I think.
>
> mm
>
> —
> 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
></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

14

That last sentence should read “wouldn’t really like to see.”

mm

Martin O’Brien wrote:

Of course not, nor do they know what to do with ‘37,’ and neither do we
for that matter, but driver installation issues are, at the moment,
really common, particularly with WDF, in my opinion, and as far as
diagnostics go ‘37’ isn’t very helpful. I think being able to get at
this information without WinDbg would be very useful, especially
remotely. It’s not like it’s going to solve most of your problems, but
it would be a place to start, and, in my experience, there is usually at
least one person at a client’s site who would be capable of collecting
and sending this sort of information were it easy to produce. I realize
that it is not exactly the sort of thing that would be considered a
feature, but neither is a driver that otherwise works failing
installation with no useful information. I realize that we are a very
small group, but look at this thread - this is a lot of work to figure
this out, and it involved very competent people. I would agree with you
that this not an ideal feature for a push button, but it seems like
other windows components have “advanced” diagnostic information, and
while this sort of thing seems like what the Event log is used for, it
is just a swamp of useless information at this point. Fundamentally, it
would be nice to have some idea of what the problem is before heading to
a site or down the hall or wherever, more than likely guaranteeing a
return visit.

It’s not an easy problem, and I would really like to see a “button”
either, but the problem, in my opinion, needs some attention.

mm

>Doron Holan wrote:
> Other than those developing drivers, who would it be useful for? My
> mom or brother certainly would not have any idea with what to do with
> this info.
>
> d
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
> Sent: Sunday, November 04, 2007 5:55 PM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Code 37
>
> Alberto Moreira wrote:
>> Thanks, Doron! I took a closer look, and here’s what I found.
>>
>> I get control at FxDriverEntry ok. However, after a while it calls
>> WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a
>> C0000024 status. That eventually leads IopLoadDriver to return a
>> C0000365 status, which eventually is converted to code 37.
>>
>> Also, I’m not sure I quite undertand what you said, what do you mean by
>> “install down level” ?
>>
>> And here’s a suggestion. Would it be too hard to percolate up these
>> statuses (and other such) into some kind of “Expert Diagnostics” button
>> in the Install Wizard ? They might save a lot of debugging time!
>>
>>
>> Alberto.
>>
>>
>>
>> ----- Original Message -----
>> *From:* Doron Holan mailto:xxxxx
>>> To: Windows System Software Devs Interest List
>>> mailto:xxxxx
>>> Sent: Thursday, November 01, 2007 11:07 PM
>>> Subject: RE: [ntdev] Code 37
>>>
>>> The 6001 wdk ships with kmdf 1.7, the co installer that it ships
>>> with does not install down level. Use the 6000 wdk and all will be
>>> well.
>>>
>>> d
>>>
>>> Sent using my smartphone, apologies forany typos
>>>
>>> -----Original Message-----
>>> From: “Alberto Moreira”
>>> To mailto:xxxxxTo>: “Windows System Software Devs
>>> Interest List”
>>> Sent mailto:xxxxxSent>: 11/01/07 7:19 PM
>>> Subject: Re: [ntdev] Code 37
>>>
>>>
>>> Hi, Doron,
>>>
>>> This is the 6001 WDK on a Vista Target. I do not get the breakpoint
>>> I put in my DriverEntry, I’ll try FxDriverEntry and see what’s
>>> happening. Thanks!
>>>
>>> Alberto.
>>>
>>>
>>> ----- Original Message -----
>>> From: Doron Holan mailto:xxxxx
>>> To: Windows System Software Devs Interest List
>>> mailto:xxxxx
>>> Sent: Wednesday, October 31, 2007 10:55 PM
>>> Subject: RE: [ntdev] Code 37
>>>
>>> What WDK did you build your driver in? in the 6001 WDK or the
>>> Vista 6000 WDK? But a breakpoint on !FxDriverEntry
>>> and see if that is called. If it does, that would rule out
>>> unresolved exports. If the bp is not hit, I would guess an
>>> unresolved import is preventing your driver from loading.
>>>
>>>
>>>
>>> d
>>>
>>>
>>>
>>> From: xxxxx@lists.osr.com
>>> mailto:xxxxx
>>> [mailto:xxxxx@lists.osr.com] *On Behalf Of
>>> *Alberto Moreira
>>> Sent: Wednesday, October 31, 2007 6:02 PM
>>> To: Windows System Software Devs Interest List
>>> Subject: [ntdev] Code 37
>>>
>>>
>>>
>>> Hello, Peoples,
>>>
>>>
>>>
>>> I have an easy problem but somehow I’m not finding its origin. I
>>> have converted my driver to WDF, and I’m trying to install it on
>>> Vista, so that I can break at the DriverEntry routine and begin
>>> testing it. I took my old and tried .INF routine and just added
>>> the WDF lines (straight from the Toaster Function Drive
>>> example), and guess what, I’m being bounced by the Installer
>>> with a Code 37: the driver’s not installed, and my DriverEntry
>>> breakpoint never triggers. I got to a point where the service
>>> entries in the Registry are identical for the old and for the
>>> new driver (I’m using different names for them so that I can
>>> have both entries in the hive), and yet the old one installs
>>> fine, while the new one barfs.
>>>
>>>
>>>
>>> I don’t have any experience with WDF, this is my first time. Do
>>> any of you have experience with that Code 37 ? Tks,
>>>
>>>
>>>
>>>
>>>
>>> Alberto.
>>>
>>>
>>>
>>>
>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>>
>>> —
>>> 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
>>>
>>> —
>>> 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
>> This is really good idea - some form enhanced installation debugging.
>> Setupapi.log already does some of this, perhaps all, but it is a little
>> overwhelming, and installation problems are common enough that something
>> like this would be welcomed by many, I think.
>>
>> mm
>>
>> —
>> 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
>>
></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>

15

I know many users wouldn’t be able to use that information, but once things
go bad it can be pretty hard to figure out why a driver installation didn’t
succeed. That’s why I said, maybe an “expert” button, for those of us who
need more info. And it doesn’t need to be individual users, sometimes
sysadmins or application developers get in the situation where some driver
doesn’t install, and their app depends on said driver, and they don’t have
enough information to figure out. There are many applications out there that
are vertically integrated with some sort of driver, and now that we can
write UDMF drivers to run on the user side, I bet there will be more such
apps around.

We are using a new source control called “Subversion”, and it has a great
feature. It’s the “Blame” button: hit it, and it frigs the author of every
change to a module. Maybe that’s what we need here. Press the blame button,
and the reason(s) for the driver not loading are exposed!

Alberto.

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Sunday, November 04, 2007 10:20 PM
Subject: RE: Re:[ntdev] Code 37

Other than those developing drivers, who would it be useful for? My mom or
brother certainly would not have any idea with what to do with this info.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Sunday, November 04, 2007 5:55 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Code 37

Alberto Moreira wrote:
> Thanks, Doron! I took a closer look, and here’s what I found.
>
> I get control at FxDriverEntry ok. However, after a while it calls
> WdfVersionBind in the WDFLDR.SYS driver. That entry point returns a
> C0000024 status. That eventually leads IopLoadDriver to return a
> C0000365 status, which eventually is converted to code 37.
>
> Also, I’m not sure I quite undertand what you said, what do you mean by
> “install down level” ?
>
> And here’s a suggestion. Would it be too hard to percolate up these
> statuses (and other such) into some kind of “Expert Diagnostics” button
> in the Install Wizard ? They might save a lot of debugging time!
>
>
> Alberto.
>
>
>
> ----- Original Message -----
> From: Doron Holan mailto:xxxxx
> To: Windows System Software Devs Interest List
> mailto:xxxxx
> Sent: Thursday, November 01, 2007 11:07 PM
> Subject: RE: [ntdev] Code 37
>
> The 6001 wdk ships with kmdf 1.7, the co installer that it ships with
> does not install down level. Use the 6000 wdk and all will be well.
>
> d
>
> Sent using my smartphone, apologies forany typos
>
> -----Original Message-----
> From: “Alberto Moreira”
> To mailto:xxxxxTo>: “Windows System Software Devs
> Interest List”
> Sent mailto:xxxxxSent>: 11/01/07 7:19 PM
> Subject: Re: [ntdev] Code 37
>
>
> Hi, Doron,
>
> This is the 6001 WDK on a Vista Target. I do not get the breakpoint
> I put in my DriverEntry, I’ll try FxDriverEntry and see what’s
> happening. Thanks!
>
> Alberto.
>
>
> ----- Original Message -----
> From: Doron Holan mailto:xxxxx
> To: Windows System Software Devs Interest List
> mailto:xxxxx
> Sent: Wednesday, October 31, 2007 10:55 PM
> Subject: RE: [ntdev] Code 37
>
> What WDK did you build your driver in? in the 6001 WDK or the
> Vista 6000 WDK? But a breakpoint on !FxDriverEntry
> and see if that is called. If it does, that would rule out
> unresolved exports. If the bp is not hit, I would guess an
> unresolved import is preventing your driver from loading.
>
>
>
> d
>
>
>
> From: xxxxx@lists.osr.com
> mailto:xxxxx
> [mailto:xxxxx@lists.osr.com] *On Behalf Of
> *Alberto Moreira
> Sent: Wednesday, October 31, 2007 6:02 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Code 37
>
>
>
> Hello, Peoples,
>
>
>
> I have an easy problem but somehow I’m not finding its origin. I
> have converted my driver to WDF, and I’m trying to install it on
> Vista, so that I can break at the DriverEntry routine and begin
> testing it. I took my old and tried .INF routine and just added
> the WDF lines (straight from the Toaster Function Drive
> example), and guess what, I’m being bounced by the Installer
> with a Code 37: the driver’s not installed, and my DriverEntry
> breakpoint never triggers. I got to a point where the service
> entries in the Registry are identical for the old and for the
> new driver (I’m using different names for them so that I can
> have both entries in the hive), and yet the old one installs
> fine, while the new one barfs.
>
>
>
> I don’t have any experience with WDF, this is my first time. Do
> any of you have experience with that Code 37 ? Tks,
>
>
>
>
>
> Alberto.
>
>
>
>
>
>
> —
> 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
>
>
> —
> 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
>
>
> —
> 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
>
> —
> 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
This is really good idea - some form enhanced installation debugging.
Setupapi.log already does some of this, perhaps all, but it is a little
overwhelming, and installation problems are common enough that something
like this would be welcomed by many, I think.

mm

—
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

—
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</mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx></mailto:xxxxx>