x64 bit driver loading

NTDEV
1

Can anyone tell what are the changes/sections that has to be added in inf file for loading the driver for 64 bit Windows system.I have a inf file that loads the driver for 32 bit machine.
For 64 bit systems i have added the following in inf file

[Micro.NTamd64]
XXXXXX

Is this section enough or i have to add some more sections?

2

Same, you just need to sign the driver.

wrote in message news:xxxxx@ntdev…
> Can anyone tell what are the changes/sections that has to be added in inf file for loading the driver for 64 bit Windows system.I have a inf file that loads the driver for 32 bit machine.
> For 64 bit systems i have added the following in inf file
>
> [Micro.NTamd64]
> XXXXXX
>
>
> Is this section enough or i have to add some more sections?
>

3

Please modify below section for all x86, x64, and IA64.

[Manufacturer]
Provider=MSFT,NTx86,NTia64,NTamd64

[MSFT.NTx86]
%Desc%=Install, BP_BAMP

[MSFT.NTia64]
%Desc%=Install, BP_BAMP

[MSFT.NTamd64]
%Desc%=Install, BP_BAMP

Regards,
Devender

4

Hi Thanks for your reply
I want to convert my 32bit driver to 64 bit driver.What are the things that has to be done to convert?
Can i just build the 32bit driver in 64bit build environment and use it if there are no errors reported in building the driver ?

5

Mostly it’s simply a rebuild, given you handled pointers correctly in the 32 bit version. The biggest change will be having to sign the driver for loading and installing. For debug you can disable signing in the boot menu, or set testSignng on. For release you will need a certificate from a CA such as Verisign, Thawte or Globalsign.

Gary Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

On Mar 16, 2012, at 7:53 AM, xxxxx@gmail.com wrote:

Hi Thanks for your reply
I want to convert my 32bit driver to 64 bit driver.What are the things that has to be done to convert?
Can i just build the 32bit driver in 64bit build environment and use it if there are no errors reported in building the driver ?

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

>For debug you can disable signing in the boot menu, or set
testSignng on. For release you will need a certificate from a CA such as
Verisign, Thawte or Globalsign

Can you explain on this , ie disabling signing in boot menu (how to do it)
Certificate from a CA ? .We dont need to get certificate from microsoft?

And one more question is how to get catalog file for my driver??

7

Enter the menu provided by F8 and select Disable Driver Signature Enforcement. You have to do that on every boot. If you want to avoid having to do that on every boot then follow this:

I’m assuming your are on at least Vista, if so run bcdedit and enable test signing. then create a test certificate per the KMCS documentation in the WDK and sign the driver using your test certificate.

Gary Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

On Mar 16, 2012, at 8:05 AM, xxxxx@gmail.com wrote:

> For debug you can disable signing in the boot menu, or set
testSignng on. For release you will need a certificate from a CA such as
Verisign, Thawte or Globalsign

Can you explain on this , ie disabling signing in boot menu (how to do it)
Certificate from a CA ? .We dont need to get certificate from microsoft?

And one more question is how to get catalog file for my driver??

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

8

On 3/16/2012 10:57 AM, xxxxx@igatepatni.com wrote:

[MSFT.NTia64]
%Desc%=Install, BP_BAMP

Note: “ia64” is not x64, but “Itanium Architecture”

Windows support for this is officially discontinued.

9

xxxxx@gmail.com wrote:

> For debug you can disable signing in the boot menu, or set
> testSignng on. For release you will need a certificate from a CA such as
> Verisign, Thawte or Globalsign
>
Can you explain on this , ie disabling signing in boot menu (how to do it)
Certificate from a CA ? .We dont need to get certificate from microsoft?

And one more question is how to get catalog file for my driver??

Again, you seem to be allergic to looking for and reading the
documentation. I tend to be helpful to a fault, but you are really
starting to try my patience. We are doing your work for you, piece by
piece.

For your first question, Google “disable signing boot menu”. It’s the
first hit.

For your second question, Google “inf2cat”.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

10

It critically depends on how you have handled pointers. If you never cast
a pointer to a ULONG, or anywhere else have an expectation that
sizeof(anything*) == 4, the code should port easily. That has certainly
been my experience in user space. That said, the number of times I see
what are now 64-bit values (pointers and handles) cast to 4-byte values is
downright scary. Fortunately, the compiler flags most of the occurrences.
I never see these in my code, because I’ve been writing code that is
64-bit aware for quite a few years, but customer code varies in quality,
from the occasional glitch to pervasive failure.
joe

Hi Thanks for your reply
I want to convert my 32bit driver to 64 bit driver.What are the things
that has to be done to convert?
Can i just build the 32bit driver in 64bit build environment and use it if
there are no errors reported in building the driver ?

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