0x80000002 crashes in .net PC2002 but ok in .net PC2003

  • Thread starter Thread starter John Bell
  • Start date Start date
J

John Bell

Hello All

First, must say how impressed I am with the level of support and help
on this group...


Perhaps I am mis-informed, but I assumed if one writes an application
in .vb.net for the compact framework. I expected it to run on PC2002
with the .net runtime the same way it runs in .net for the PC2003
runtime.

I have an application which uses create process to fire up an email
message ..
this duly loads and the email message is fine, but the sip is raised
in the email message and back in the main application the sip enabled
change event seems to fire several times and after 2 or three shots
causes an exception ie 0x80000002.

The same code runs fine on PC2003, but causes the above on PC2002.

I am using two Ipaqs a 5550 for 2003 and a ipaq 3870 for the PC2002
code both using the correct runtime and at srv pk 2 (I have tried svpk
1 and the issue is the same)...


Anyone got any advice on this ....., particuarly how I trace exactly
where the issue is .... ??

Thanks in advance


John Bell
(e-mail address removed)
 
As a starting point for you; 0x80000002 is "Out of Memory". I would
therefore suggest that perhaps you are not releasing resources after you
have finished with them. As for why this is ok on PPC2003 but not PPC2002,
this interests me as I currently have some guyts looking into exactly the
same problem for me with an application on PPC2002 that crashes with the
same error; unfortunately mine is not as readily reproducable.

Cheers.
 
John,

I have also experienced this. I have a .NET CF program deployed on over
20,000 Pocket PC devices. The memory error occurs on about 1% of the 2002
systems, but never happens on the 2003 systems. I can almost guarantee that
when it does crash this way, it is either on a Dell Axim X5 or a Toshiba
e740 running 2002. *Some* (not all) folks have been able to get running by
performing a "hard reset", which leads me to think that it was a mismatched
DLL or something.

I would guess that we will never see a fix to this issue as 2002 is not
being developed any longer. Unfortunately it is still being deployed,
especially on the PPC phones such as those available through T-Mobile and
Sprint.

Rick
 
Well its nice to know its not just me. I can't think of anything I
have not disposed of ...

For now I have just disabled the system from trying to raise an
automatic email if the device is running the PocketPC 2002 operating
system, not perfect but one way out that avoids the user being
presented with a horrible runtime exception !!!!

Thanks

John
 
Well its nice to know its not just me. I can't think of anything I
have not disposed of ...

For now I have just disabled the system from trying to raise an
automatic email if the device is running the PocketPC 2002 operating
system, not perfect but one way out that avoids the user being
presented with a horrible runtime exception !!!!

Thanks

John
 
Back
Top