Re: Problem with Windows Mobile 2003 Second Edition
- From: "Win CE developer" <rc7219@xxxxxxxxxxx>
- Date: Tue, 28 Jun 2005 13:22:46 -0700
I have been able to solve this problem. It was caused by some serial port
code in the applications. Since the MC50 device supports only USB (no serial
port) the application couldn't find the serial port and would just exit.
This was causing problems in other parts of the application as well. After
removing these lines of code everything works perfectly now.
Thank you Robert for taking the time to provide assistance in this matter.
"Win CE developer" <rc7219@xxxxxxxxxxx> wrote in message
news:%23X30Yr1eFHA.3048@xxxxxxxxxxxxxxxxxxxxxxx
> As I initially thought this problem doesn't seem to be related to the
> Second Edition of Windows Mobile 2003. I have tested the same applications
> on another Second Edition device like Dell Axim X50 but the applications
> run flawlessly.
>
> I still haven't been able to find anything that might solve this problem.
> The applications should run fine by installing the eVB runtime on the
> Symbol MC50 device as well. Any other pointers from anyone will be
> appreciated, Thanks.
>
> <r_z_aret@xxxxxxxxxxxx> wrote in message
> news:lafea1ltl0mp1knr70rsra8rmc1o6oq89j@xxxxxxxxxx
>> C/C++ programmers experience this somewhat often. Almost always
>> because of a bad pointer or array reference. So code in one part of
>> the program writes where it shouldn't, and that affects code in
>> another part of the program. They symptoms commonly show far away (in
>> code lines) from the actual bug. So finding the bug(s) can be painful.
>> I've never used eVB, and used VB only briefly and several years ago,
>> so I'm not sure how much eVB might insulate you (for good and bad)
>> from such details.
>>
>> The bug in SetWindowText might actually cause such symptoms. If your
>> application uses any edit boxes, you can at least check to make sure
>> you never pass a NULL string when you try to set edit box text.
>>
>>
>>
>> On Wed, 8 Jun 2005 11:06:22 -0700, "Win CE developer"
>> <rc7219@xxxxxxxxxxx> wrote:
>>
>>>Thank you Robert for your reply.
>>>
>>>Since I am using eVB it seems that some part of the code there is not
>>>working correctly for this device. The problem I have is that this occurs
>>>randomnly in any part of the application (though limited only to the
>>>options
>>>in the Menu bar) and hence it's difficult to locate.
>>>
>>>At some times I can go into the Menu bar options, click on them, open
>>>other
>>>forms and then hit ok and return to the main menu. At other times when I
>>>go
>>>in the menu bar option into another form and then hit the ok button on
>>>the
>>>top to return to the main menu, the app just exits. Has anyone had a
>>>similar
>>>situation?
>>>
>>><r_z_aret@xxxxxxxxxxxx> wrote in message
>>>news:tquba1lt13b316v7cdlmndo13ov3mth8dt@xxxxxxxxxx
>>>> On Mon, 6 Jun 2005 15:56:39 -0700, "Win CE developer"
>>>> <rc7219@xxxxxxxxxxx> wrote:
>>>>
>>>>>I installed our application that ran fine on Pocket PC 2000, 2002 and
>>>>>2003(with eVB runtime) on Pocket PC Mobile 2003 Second edition on
>>>>>Symbol
>>>>>MC50 device. At some points in the application when I hit on certain
>>>>>buttons
>>>>>the application just exits. At other times when I hit on the same
>>>>>buttons
>>>>>the application doesn't exit.
>>>>>
>>>>>I have no clue as to what is happening, as these applications are
>>>>>running
>>>>>fine on other devices. Does anyone have any similar experiences? I
>>>>>believe
>>>>>it has something to do with the second edition. The screen orientation
>>>>>is
>>>>>set to Portrait.
>>>>
>>>> I know of two "problems" with Pocket PC 2003 SE:
>>>>
>>>> 1) Menu "emulation" mode doesn't work. More specifically, if an
>>>> application uses CommandBar_Create rather than SHCreateMenuBar the
>>>> menu will be invisible. I don't think this is relevant here.
>>>>
>>>> 2) The SetWindowText function for edit boxes can cause nasty problems
>>>> if passed a NULL argument. For a bit more info, see a 18-22 Apr 2005
>>>> thread called "eVC++ 3 for PocketPC2003?" in this newsgroup
>>>>
>>>>
>>>>>
>>>>>Thanks.
>>>>>
>>>>
>>>> -----------------------------------------
>>>> 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
>
>
.
- References:
- Problem with Windows Mobile 2003 Second edition
- From: Win CE developer
- Re: Problem with Windows Mobile 2003 Second edition
- From: r_z_aret
- Re: Problem with Windows Mobile 2003 Second edition
- From: Win CE developer
- Re: Problem with Windows Mobile 2003 Second edition
- From: r_z_aret
- Re: Problem with Windows Mobile 2003 Second Edition
- From: Win CE developer
- Problem with Windows Mobile 2003 Second edition
- Prev by Date: Re: Need simple custom application for HHP by using VB.NET
- Next by Date: Re: Problem: I can't open the serial COM1
- Previous by thread: Re: Problem with Windows Mobile 2003 Second Edition
- Next by thread: Pocket IE ignores Content-Disposition in Secure HTTP Mode
- Index(es):