Re: Install problem (previous version of windows mobile)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

r_z_aret_at_pen_fact.com
Date: 01/11/05 

Date: Tue, 11 Jan 2005 15:47:27 -0500

On Mon, 10 Jan 2005 15:45:04 -0800, "Benjamin"
<Benjamin@discussions.microsoft.com> wrote:

>Thanks for the tip. I did edit the .inf file and added the BuildMax Value
>file and made the cab files again. My application is still crashing though.
>At this point I am hesitant to say that it is because of the warning message
>on install, because that only has to do with screen rotation and my screen is
>always in the normal portrait mode. The program works fine on the 2003
>emulator, but crashes at certain spots on the 2003 Pocket PC. Is there any
>way I can figure out what is causing the problems on the device?

1) Are you sure your app can handle the screen resolution of the
Pocket PC 2003 you've been testing? The rationale for the warning
during installation is/was that most apps built for earlier
generations of Pocket PC could only handle 320x240.

2) Usual causes for intermittent crashes are bad pointers, bad array
indices, etc. Symptoms usually show far from the actual cause. I use
ASSERTs to check pointers and array indices whenever I set or use
them, so I catch such bugs much closer to the actual problem.

3) When I run programs under the Windows CE debuggers, passing
INVALID_HANDLE_VALUE (defined in windows.h) to ::IsWindow causes a
hang. I haven't noticed this under "big" Windows or when my programs
run on their on (on real devices without a debugger).

4) Two ways to narrow down the location of a bug:
a) message boxes (crude, but effective)
b) break points and the debugger
Scatter a few around your code. If a crash consistently occurs between
two markers, you can move the markers closer until you can get close
enough to step through the code reasonably.

5) I have an app that runs well on many versions of Windows CE and
"big" Windows. But it crashes on Pocket PC 2003. On both devices I've
managed to borrow. I've got many ASSERTs that have caught bugs before,
but aren't being triggered. I've run the app using BoundsChecker, and
eliminated the few new problems that cropped up in the last few
months. If I run the program under the debugger, when it crashes and I
try to break, I can't (all threads are in system calls).

>
>"r_z_aret@pen_fact.com" wrote:
>
>> On Mon, 10 Jan 2005 12:09:05 -0800, "Benjamin"
>> <Benjamin@discussions.microsoft.com> wrote:
>>
>> clip
>>
>> >I have developed a program in Microsoft Visual Studio .Net 2003 using VB.NET.
>> >sqlce.ppc3.arm.cab, and finally install my program. With the new 2003 pocket
>> >pc devices I am having problems during the installation process. I went to
>> >install netcf.core.ppc3.arm.cab (.Net Compact Framwork) and it installed but
>> >gave me a popup of: "the program you have installed may not display properly
>> >because it was designed for a previous version of windows mobile software."
>>
>> I just used google (http://groups.google.com/advanced_group_search)
>> to look up that error message (exact phrase) and got 28 hits. I took a
>> quick look, which confirmed that you will find your answer.
>>
>> clip
>> -----------------------------------------
>> To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).
>>
>> Robert E. Zaret, eMVP
>> PenFact, Inc.
>> 500 Harrison Ave., Suite 3R
>> Boston, MA 02118
>> www.penfact.com
>>

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
www.penfact.com

Relevant Pages

  • Re: Very bad crashes when debugging with Spy++
    ... with the NtUser code (the code that does `windowing` in the broader sense, ... you might past back the problem of a debugger needeing a message loop. ... >>>app, but there are no other symptons of it so it seems strange that it ... >> Microsoft MVP, Windows SDK ...
    (microsoft.public.vc.language)
  • Re: FTP file transfer gets DrWatson32 errors during server reset
    ... Have you tried to duplicate the crash in a debugger? ... Also note that enumeration of files on a remote server is not always ... automated app you'd better handle the failures in your app. ... with dr watson error windows. ...
    (microsoft.public.vc.mfc)
  • Debugging tips needed - application dies on WinXP SP2
    ... I'm currently working with modifying a large MFC app to handle Unicode ... This happens regardless of the debugger used ... without a debugger attached raises the error report dialog in Windows, ... updated to a new version in SP2. ...
    (microsoft.public.vc.mfc)
  • .Net Compact Framework - Pocket PC vs Windows CE???
    ... I am starting to develop a Smart Device application using the .Net Compact ... I can set it up as a Pocket PC app or a Windows CE ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Probably a Pocket PC shell bug: NavBar not restored after a fullscreen app exits or dies
    ... Neither "big" Windows nor other Windows CE platforms restore the Task ... So current behavior for Pocket ... >restore the navbar to a visible state before exiting. ... >does not forcibly restore the NavBar when a fullscreen app terminates ...
    (microsoft.public.pocketpc.developer)