Re: "Not a valid pocket pc application" -- not just trying to ins

From: Nicky (Nicky_at_discussions.microsoft.com)
Date: 11/18/04 

Date: Thu, 18 Nov 2004 11:19:07 -0800

Mostly, when you build a program for PDA, the processor should not be x86. I
am using HP and dell's pad with ARMV4.
And also, mostly, the "... is not a valid......" just means the process is
wrong.
So, you can create an empty project and compile with different process
option to see which one works. I know this is not a smart method, but
sometimes, it really helps!
Good luck.

"Alex" wrote:

> I'm sorry, I realize i didn't include nearly enough details in the
> description of my problem. It is a ppc2003, i made the mistake of
> using evc3.0 with ppc2002 sdk and it wouldn't even sync to transfer
> the executable over, but that problem was fixed by updating to evc4.0.
> I do think the problem has to do with the processor. In the pull down
> menu on the main window of evc4.0 there are the options to compile for
> Win32(WCE ARMV4) release and debug and Win32(WCE emulator) release and
> debug. When I compile using the ARVV4 option i get the following
> error:
>
> corelibc.lib(pegwmain.obj) : error LNK2019: unresolved external symbol
> WinMain referenced in function WinMainCRTStartup
> ARMV4Rel/PDABot1.exe : fatal error LNK1120: 1 unresolved externals
>
> When I build using the WCE emulator option it compiles and links fine
> but i get that "not a valid pocket pc application" error when i try to
> run it from the pocket pc. The pocket pc's processor is an Intel
> pxa255. I read that that means i should use x86 selection because
> that is the general option for all intel processors. Although x86
> isn't explicit in the evc4.0 options (where it was in evc3.0), the WCE
> option does link where the ARM selection fails.
>
> Thanks again in advance.
>
> Alex Steingart
> Trinity '06
> Duke University
> Department of Mechanical Engineering
>

Relevant Pages

  • Re: Compact SQL - Any CPU Build
    ... but compile our application to x86 and x64 version respectively. ... We welcome your comments and suggestions about how we can improve the support we provide to you. ...
    (microsoft.public.dotnet.general)
  • Re: Obfuscation and Salamander
    ... > exposed in its assemblies/builds? ... the compiler that a function should be compiled as x86 rather than IL, ... able to work out your algorithm. ... by compilers when they compile a class that use them. ...
    (microsoft.public.dotnet.faqs)
  • Re: VC++6 LNK1112 Error
    ... Itanium into a piece of code destined for an x86. ... correctly select your target to be an Itanium. ... Note also that you can't really compile IA64 code unless you have a compiler that targets ...
    (microsoft.public.vc.mfc)
  • Re: [Git pull] x86 bugfixes
    ... please pull x86 bugfixes from ... Some more voyager fixes and other compile warning fixups than in the ... x86: ... movl $,%eax ...
    (Linux-Kernel)
  • Re: Multicast Socket for Win CE 4.2 / Pocket PC 2003
    ... API and multicast works, in general, on a variety of devices that I've built ... I can't speak directly for Pocket PC, ... The Unicode thing has *nothing* to do with incompatibility and Microsoft ... it does not even compile. ...
    (microsoft.public.windowsce.embedded.vc)