NotSupportedException - on nearly every app I try

[Guest Bruno1974]

Hi everyone,

First, let me say that I'm fairly new to the world of smart phones, pocket PCs, PDAs, etc. So new, that I'm exactly sure how my device would be classified. Let me also say that I'm very hesitant to post a new topic. For the past 3 days, I've dug around in about every forum I can find regarding this error - and I've seen a lot of people get raked across the coals for not doing enough searching. I feel like I've put forth as much energy and effort as I could muster to try to dig up a resolution on my own, but have had no luck. At the risk of getting hammered for posting a new topic for something that has already been covered, here we go.

Here's what I have:

Samsung BlackJack II (i617UCHJ1 -- H/W revision 0.3)

Running Windows Mobile 6.1 standard (5.2.19208 -- build 1.0.1)

My problem:

Almost every new application I've downloaded and installed comes up with the same error when I attempt to load it -- NotSupportedException, and it always references the same library call -- Microsoft.AGL.Common.MISC.HandleAr(PAL_ERROR ar). It then goes on to list some specific controls in the app itself, such as buttons, list boxes, and other form controls. I've done enough programming in my day to think that it looks like a .DLL or something isn't registered with the OS, but I can't for the life of me figure out how to fix it.

Here's a list of applications that throw the same error at me:

tripYzee

Scrobble

GPSTracka

GpsCycleComputer

I've installed several "aftermarket" apps that work fine -- CPU clocker, a couple of emulators, and Google Maps (thanks for the GPS activator by the way, works great!!!).

And lastly, here's what I've tried:

I've installed the .NET CF 3.5

Installed the .NET Configuration utility

-- set the device policy to 3.5, 2.0, and default - none of which worked

-- set a specific app policy for 3.5, 2.0, and default - none of which worked (tried this for several apps)

I've even considered, and looked into reflashing my ROM as a last resort. Although some of what I've read made me think a cooked ROM might be a good way to go.

I'm hoping there's something I'm missing, this is fairly common, and it's an easy fix. Knowing my luck, probably not the case. If anyone has any suggestions, I could sure use them. Thanks!

(and thanks for reading my long-winded post!)

- Jeff (aka Bruno)

[Guest Bruno1974]

Hi everyone,

First, let me say that I'm fairly new to the world of smart phones, pocket PCs, PDAs, etc. So new, that I'm exactly sure how my device would be classified.

Well, I don't see an option to delete an entire post, so I guess I'll have to leave it up and take my lumps. It seems that the first paragraph of my post was the root of my porblem. After one last "Hail Marry" search for answers, I see that there's a pretty significant difference between smart phones and pocket PCs. I may be way off on this, but I beleive I've run across my answer --

button controls on forms (VB, C++, etc) aren't allowed on smart phones.... which is exactly what I have in a BJII.

Oh well. Maybe I can save some other poor sap a few days of aggravation if they search and run across this post.

Thanks again everyone. Like I said, I'm still new to the mobile world. There's a pretty big learning curve, but the forums here certainly seem to flatten it a bit!