Re: Determining EXE/DLL processor type

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: sergeir (anonymous_at_discussions.microsoft.com)
Date: 03/19/04 

Date: Fri, 19 Mar 2004 04:39:20 -0800

Maybe you could try some assembly instructions or get the
hardware platform description, like the one returned by a
call to IOCTL function - it returns a string, if
implemented by OEM, naming the platform hardware in their
convention. This way you would not end up executing SH4
code on ARM processor - first get what's we are on, then
decide if it is close enough.

E.g for VIA C3 processor it returns "Centaur Hauls" with
some numbers. Not quite obvious, but still useful.

Regards
Sergei

>-----Original Message-----
>We have CE units with SH and ARM builds. Didn't do a
perfect job separating
>out some of the conditions that can be present with files
on removable
>media, so customers can get confused and put an SH-based
media into an ARM
>unit in rare cases. Trying to easily code to prevent
problems.
>
>Nothing desktop related, I just feel that sometimes the
desktop's drive the
>API more than CE.
>
>"Michael J. Salamone [eMVP]" <mikesa#at#entrek#dot#com>
wrote in message
>news:O0fNxaWDEHA.3348@TK2MSFTNGP11.phx.gbl...
>> Nothing that I'm aware of. All documentation I know of
tells you the
>> format - no mention of APIs.
>>
>> Are you trying to determine information about a file on
the desktop?
>> Presumably an ARM-built module would never end up on a
SH3 or X86 or
>> anything other than an ARM-based platform. So I'm
assuming you want to
>> examine a file on a desktop machine, perhaps where it
was built? You can
>> use the dumpbin tool for that.
>>
>> For anything on a CE target device, or anything beyond
what dumpbin does,
>I
>> think you're on your own.
>>
>> --
>> Have an opinion on the effectiveness of Microsoft
Embedded newsgroups?
>Tell
>> Microsoft!
>> https://www.windowsembeddedeval.com/community/newsgroups
>>
>>
>> Michael Salamone [eMVP]
>> Entrek Software, Inc.
>> www.entrek.com
>>
>>
>>
>> "bill" <poddw@yahoo.com> wrote in message
>> news:u8FnVJVDEHA.3852@TK2MSFTNGP10.phx.gbl...
>> > I know the PE header has the processor type in it and
all of the PE
>> > structures are defined in winnt.h. My question is, is
there an API call
>> that
>> > returns the PE information ?
>> >
>> > I'd like to be able to determine that a file is an SH
file versus an ARM
>> > build (or a CE 3.0 versus a 4.x file). I know I can
open the file and
>> parse
>> > the PE header myself, but it would seem like
something the API would
>> > provide. Especially since nt had the x86/alpha
versions. I just can't
>seem
>> > to find anything.
>> >
>> >
>>
>>
>
>
>.
>

Relevant Pages

  • Re: Determining EXE/DLL processor type
    ... >We have CE units with SH and ARM builds. ... >API more than CE. ... >> use the dumpbin tool for that. ... >> Have an opinion on the effectiveness of Microsoft ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Determining EXE/DLL processor type
    ... We have CE units with SH and ARM builds. ... API more than CE. ... > Have an opinion on the effectiveness of Microsoft Embedded newsgroups? ... >> I know the PE header has the processor type in it and all of the PE ...
    (microsoft.public.windowsce.platbuilder)