I am currently porting a 32-bit driver to run on 64-bit windows. My
problem though at the moment is that the driver simply won’t load
(DriverEntry is not invoked). I am a bit inexperienced in debugging
windows drivers, so I was curious how I should go about debugging this
issue? I am guessing that maybe it is a dependency issue or something
along those lines. Is there a tool I can run on my 64-bit driver that
tells me whether all the dependencies are met? and possibly provide me
an error message on why it cannot load the driver?
> Hello, > > I am currently porting a 32-bit driver to run on 64-bit windows. My > problem though at the moment is that the driver simply won’t load > (DriverEntry is not invoked). I am a bit inexperienced in debugging > windows drivers, so I was curious how I should go about debugging this > issue? I am guessing that maybe it is a dependency issue or something > along those lines. Is there a tool I can run on my 64-bit driver that > tells me whether all the dependencies are met? and possibly provide me > an error message on why it cannot load the driver? > > Thanks, > J
I am currently porting a 32-bit driver to run on 64-bit windows. My
problem though at the moment is that the driver simply won’t load
(DriverEntry is not invoked). I am a bit inexperienced in debugging
windows drivers, so I was curious how I should go about debugging this
issue? I am guessing that maybe it is a dependency issue or something
along those lines. Is there a tool I can run on my 64-bit driver that
tells me whether all the dependencies are met? and possibly provide me
an error message on why it cannot load the driver?
The most likely problem is that you have not signed your driver. The
64-bit operating systems will not load a driver that is not signed by a
Class 3 code-signing certificate from either Verisign or GlobalSign.
Start here:
Thanks guys for the quick reply. I’ve actually manually disabled the
driver signing by pushing F8 at the boot screen and then selecting
“Disable Driver Signing Verification”. This should allow my driver to
load properly correct?
On Wed, Nov 24, 2010 at 10:15 AM, Tim Roberts wrote: > Jonathon wrote: >> I am currently porting a 32-bit driver to run on 64-bit windows. My >> problem though at the moment is that the driver simply won’t load >> (DriverEntry is not invoked). ?I am a bit inexperienced in debugging >> windows drivers, so I was curious how I should go about debugging this >> issue? ?I am guessing that maybe it is a dependency issue or something >> along those lines. ?Is there a tool I can run on my 64-bit driver that >> tells me whether all the dependencies are met? and possibly provide me >> an error message on why it cannot load the driver? > > The most likely problem is that you have not signed your driver. ?The > 64-bit operating systems will not load a driver that is not signed by a > Class 3 code-signing certificate from either Verisign or GlobalSign. > Start here: > > http://www.microsoft.com/whdc/driver/install/drvsign/default.mspx > http://www.microsoft.com/whdc/driver/install/drvsign/kmcs-walkthrough.mspx > > – > Tim Roberts, xxxxx@probo.com > Providenza & Boekelheide, Inc. > > > — > 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 >
Yes
On Nov 24, 2010 1:21 PM, “Jonathon” wrote: > Thanks guys for the quick reply. I’ve actually manually disabled the > driver signing by pushing F8 at the boot screen and then selecting > “Disable Driver Signing Verification”. This should allow my driver to > load properly correct? > > On Wed, Nov 24, 2010 at 10:15 AM, Tim Roberts wrote: >> Jonathon wrote: >>> I am currently porting a 32-bit driver to run on 64-bit windows. My >>> problem though at the moment is that the driver simply won’t load >>> (DriverEntry is not invoked). I am a bit inexperienced in debugging >>> windows drivers, so I was curious how I should go about debugging this >>> issue? I am guessing that maybe it is a dependency issue or something >>> along those lines. Is there a tool I can run on my 64-bit driver that >>> tells me whether all the dependencies are met? and possibly provide me >>> an error message on why it cannot load the driver? >> >> The most likely problem is that you have not signed your driver. The >> 64-bit operating systems will not load a driver that is not signed by a >> Class 3 code-signing certificate from either Verisign or GlobalSign. >> Start here: >> >> http://www.microsoft.com/whdc/driver/install/drvsign/default.mspx >> http://www.microsoft.com/whdc/driver/install/drvsign/kmcs-walkthrough.mspx >> >> – >> Tim Roberts, xxxxx@probo.com >> Providenza & Boekelheide, Inc. >> >> >> — >> 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
Thanks guys for the quick reply. I’ve actually manually disabled the
driver signing by pushing F8 at the boot screen and then selecting
“Disable Driver Signing Verification”. This should allow my driver to
load properly correct?
Well, that’s one step.
Have you changed your INF at all? (Note that changes are not always
required.) How are you installing your driver (meaning what tool are
you using)? What kind of driver is it?
What is the error code in Device Manager? Which operating system?
c:\windows\inf\setupapi.dev.log probably has more good information on
the problem as well. You might post the last thousand lines or so from
that log.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Thanks guys for the help. After some investigation, I determined that
the cause is not due to my driver, but due to the installer. For some
reason, when I install my driver on windows 7 - 32-bit, it sets the
startup to 2 (which is correct). When I install the driver on a
64-bit windows, the startup is automatically set to 4 (disabled which
is incorrect). Can someone suggest a reason why after the install
Windows would automatically set it to disabled? If I manually set it
to 2 after the install, things work great on the 64-bit windows.
Thanks
On Wed, Nov 24, 2010 at 10:40 AM, Tim Roberts wrote: > Jonathon wrote: >> Thanks guys for the quick reply. ?I’ve actually manually disabled the >> driver signing by pushing F8 at the boot screen and then selecting >> “Disable Driver Signing Verification”. ?This should allow my driver to >> load properly correct? > > Well, that’s one step. ? > > Have you changed your INF at all? ?(Note that changes are not always > required.) ?How are you installing your driver (meaning what tool are > you using)? ?What kind of driver is it? > > What is the error code in Device Manager? ?Which operating system? > c:\windows\inf\setupapi.dev.log probably has more good information on > the problem as well. ?You might post the last thousand lines or so from > that log. > > – > Tim Roberts, xxxxx@probo.com > Providenza & Boekelheide, Inc. > > > — > 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 >
Thanks guys for the help. After some investigation, I determined that
the cause is not due to my driver, but due to the installer. For some
reason, when I install my driver on windows 7 - 32-bit, it sets the
startup to 2 (which is correct). When I install the driver on a
64-bit windows, the startup is automatically set to 4 (disabled which
is incorrect). Can someone suggest a reason why after the install
Windows would automatically set it to disabled? If I manually set it
to 2 after the install, things work great on the 64-bit windows.
Well, not if you’re going to make us guess HOW you did the install.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
