How to determine if driver is x32 or x64

Hi,

Is there a easy way to tell if a driver is for x32 or x64 by just having the
..sys binary?

TIA!!

Yes. Open it in dependency viewer (depends.exe) and it will show this.

--pa


"David F." <> wrote in message
news:517B2DDF-4F7A-48DE-923F-...
> Hi,
>
> Is there a easy way to tell if a driver is for x32 or x64 by just having
> the .sys binary?
>
> TIA!!
>

link -dump -headers myfile.sys

FILE HEADER VALUES
14C machine (x86)

or

FILE HEADER VALUES
8664 machine (x64)

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com

"David F." <> wrote in message news:517B2DDF-4F7A-48DE-923F-...
> Hi,
>
> Is there a easy way to tell if a driver is for x32 or x64 by just having the
> .sys binary?
>
> TIA!!
>

>options for microsoft linker such as -dump -header? It seems that the
>output is same as dumpbin.

"link -dump" is the same as "dumpbin", and I cannot make "dumpbin" working in more-or less modern WDK, while "link -dump" works.

--
Maxim S. Shatskih
Windows DDK MVP

http://www.storagecraft.com

Chequer <> wrote:
>
>Would you like to tell me, where to find the undocumented argument
>options for microsoft linker such as -dump -header? It seems that the
>output is same as dumpbin.

Look at the directory that contains "link.exe". Note that "lib.exe",
"dumpbin.exe", and "editbit.exe" are each only 18k bytes. That's not big
enough to do anything useful. All three of those utilities do nothing
other than invoke link.

lib => link /lib
dumpbin => link /dump
editbin => link /edit
--
Tim Roberts,
Providenza & Boekelheide, Inc.