PDA permanently freezes when enumerating processes

[Guest]

Hi,
I am building a "task manager" type of application that sits on a loop and
enumerates the system processes. I used this

http://msdn.microsoft.com/library/d.../dnnetcomp/html/ProcessManager.asp?frame=true

article to assist me with the "technical" details and I am using the same
practices shown in the article.
The whole thing functions as expected... until I sort-reset the device while
the loop is still going, The PDA never recoveres from the soft reset, I had
to hard-reset the device in order to get it running again.

At first I thought it was just a freak incedent, but since I'm through about
six attempts, I know it's not.

Whats going on?
How can I stop it?

So far I don't event understand the problem because I would have to know
what's going on in the core operating system just before or during a
soft-reset.

Also, a workaround would be if I could somehow detect that a soft-reset is
coming, I could quickly terminate the application. However, I kind-of doubt
that this would work, since soft-resets happen in a snap and wouldn't leave
time to take any action.

Any help is greatly appreciated.

 

[Nathan Arora]

Zachovich:

I am a software engineer within the .NET Compact Framework group here
at Microsoft. Could you provide me with additional resources to
reproduce the issue described below? Helpful resources could include
source code, the device you are using, the version number of the WinCE
OS, and the version number of the .NET Compact Framework installed on
the device.

If you need assistance finding any of this information or have
addition issues, please email me at [nathanar <at> microsoft <dot>
com]

Thanks,

Nathan

 

[Guest]

Nathan,
Thank you for the reply, highly appreciated!

Sorry for the belated response.

The actual problem behind the effects I reported was not related with
enumerating the processes or running a loop at all. I did a lot of testing
and many hard-resets to locate the actual problem. I used a Toshiba e755
Pocket PC device for the tests and I didn't try the solution on the
emulator(s).

I eventually found the real conflict in my solution, I had built a managed
VB.NET DLL named "ToolHelp.dll" and placed it within in the application's
directory. Windows Mobile apparently has a dll with the same name in the
Windows directory and I suppose they conflicted. this is where I placed the
blame, anyways.

I also tried the same thing on an iPAQ h2215 and could not duplicate the
results. Apperently, hp protects it's ROM more extensively.... i don't know

Either way, I don't know why even the toshiba would hard reset. Did it allow
me to overwrite the native system dll in the ROM with my managed thingy?

In all the projects under the solution, I made sure that the target path was
not directed to "\windows" so, even if the dll names matched, it had no
reason to overwrite. However, as soon as I renamed the dll, my problems
vanished, now everything works fine.