Pocket OS 2003 SE - Dell AXIMs - anyone having problems?

  • Thread starter Thread starter Glyn Meek
  • Start date Start date
G

Glyn Meek

We have a product written in visual Basic that is Microsoft certified and
that we have sold thousands of copies over the past 18 months. We haven't
had a bug report in months (thank goodness...lol), but now that Microsoft
have released Pocket OS 2003 SE (Second Edition) we have a strange
indeterminate error that occurs on closing the application.

Part of the SE features allow running of Pocket PCs in 'landscape' mode, and
almost ALL commercial products are having some kind of problems working
cleanly in this new mode, but I have also read reports of a whole lot of
products not running correclty under SE.

Anyone have any pointers as to where we might look to find out what has
changed and what we can do to fix it. My understanding is that on the new
Dell AXIM, our product was working fine until Dell (at the behest of
Microsoft I think) issued a patch which, when applied, causes our program
(and god knows how many others) to start failing.

Now, in the usual cynical wisful thinking of developers, I blame all this on
the Microsoft patch...lol...but wonder if anyone else has had problems with
2003 SE?

Thanks

Glyn J Meek
 
Glyn Meek said:
...but wonder if anyone else has had
problems with 2003 SE?
Click to expand...

Yes, I had to redo all my toolbar image code to accommodate WM2003 SE. This
was evidenced by an unhandled exception at startup.

I've had no other reports of problems, though.
 
Hi Glyn,

Couple of weeks ago Dell sent me a Dell X30 running 2003SE so that we could
do some testing. So far I have to say that we have had absolutley no problems
with the device.

James.
 
James...thanks for this. After getting the error report, we actually went
and bought a new Axim, and found the problem was in our code! Never became
apparent in previous OS, but .net CF SE exposed it.

ah well, this really is an art not a science...

LOL


thanks anyhow!

Glyn
 
I have had the same experience with a custom app. I have found out the
setting a form.enable = false and then form.enable = true, does not
re-enable the form. it leave it disabled and unfunctional. This was a
simple coding change, but I have had to re-lease it for SE.

Scott
 
Back
Top