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:48:07 -0800

Just an add-on to my previous post - sorry it maybe was
not clear. Here is what you could do

...
OEMIoControl(...,dwIoControlCode,...)
...
where dwIoControlCode is from the list

Processor IOCTLsSee Also
Supported OAL APIs

The following is a list of processor IOCTLs:
...
IOCTL_PROCESSOR_INFORMATION
...

If that is not implemented by OEM, then you could try
SystemParametersInfo() with
SPI_GETPLATFORMTYPE or
SPI_GETPLATFORMINFO

which probably calls inside to the same OEM code as the
first method above.

Best 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. ... >> Have an opinion on the effectiveness of Microsoft ...
    (microsoft.public.windowsce.platbuilder)
  • Re: RUNDLL32.EXE
    ... 0x66800000 0x155000 Windows Shell Common Dll ... 0x75FA0000 0xA000 BSD Socket API for Windows ... 0x794D0000 0x15000 Microsoft WinSock Extension APIs ...
    (comp.security.firewalls)
  • Re: Explorer keep launching at start up
    ... aka "Nutcase" - Microsoft MVP ... > "Load at next startup only"=dword:00000010 ... > Filters\Export\JPEG\Filter API] ... >> Associate Expert - WindowsXP Expert Zone ...
    (microsoft.public.windowsxp.general)
  • Re: strncpy_s()
    ... API, it's to make it convenient to modify existing code to use the new API ... Valid in the sense that they don't yield undefined behaviour, ... empty string, ... sponsor, Microsoft**, who has affirmatively stated they do not intend to ...
    (comp.std.c)
  • Re: Returning structs
    ... It's pretty good at Win32 API but pretty dreadful at RAD, which is why a lot of people do reach for Borland, and it's at this point that OMF vs COFF actually matters. ... In theory you *could* use a DLL linked by borland using a Microsoft ... jacob at jacob point remcomp point fr ...
    (comp.lang.c)