NullReference Error when no Cursor Present?

  • Thread starter Thread starter Vince
  • Start date Start date
V

Vince

Hi,

The Platforms (All have .NetCF 1.0 SP2):

Emulators: WinCE.Net, PPC2002, PPC2003
Compaq iPaq 3870: PPPC2002
PSION 7535: WinCE.Net 4.1

My vb.net app runs fine on the emulators & iPaq on either
SP1 or SP2 but when I try running on the PSION 7535 it
fails intermittently with a NullReference error. Failure
appears to happen whenever a button is clicked, and
whenever a button is clicked I change the Cursor to:
Cursor.Current = Cursors.WaitCursor.

The 7535 comes with a reduced OS, and one of the missing
components I'd guess is the Cursor. I came to that
conclusion by loading coredll's functions LoadCursor and
SetCursor, but still the cursor doesn't appear on the
PSION although it does on all the other platforms.

Would the lack of a Cursor in the OS cause intermmittent
NullReference Errors?

BTW I can't debug the 7535 via VisStud.net 2003 as I
cannot connect to it through VisStud.net 2003.

Many Thanks All

Vince
 
Vince,

The sp2 patch was recalled due to some problems. Can you revert to sp1 and
see if you get the same error?
 
Ginny said:
Vince,

The sp2 patch was recalled due to some problems. Can you revert to sp1 and
see if you get the same error?
Click to expand...

Depends which SP2 you're running... :| Microsoft (UNFORTUNATELY - sorry
couldn't resist) is currently shipping two (very different) SP2 patches.
One is in Beta right now - they still have a chance to call it SP3 before
they really release it - hint hint hint! OK, now I really promise not to
mention this mess again...

Hilton
 
Hilton,

;-) It is a bit confusing, but calling the new patch sp3 might be confusing
in a different way. In any case, I don't think the name is likely to change.
 
Hi Ginny,
Hilton,

;-) It is a bit confusing, but calling the new patch sp3 might be confusing
in a different way.
Click to expand...

I can see no reason for the confusion. Just put SP3 on the website, easy.
When someone says "I'm running SP2" you actually know what they're running.
I think it's just MS's way of pretending SP2 never shipped and they caught
it before anyone actually downloaded it - at our expense. Look how many
posts there have been just on these NGs asking about a bug in SP2 - you
know, the original SP2, not the new SP2. :| At least, I think they're
referring to the old one.

In any case, I don't think the name is likely to change.
Click to expand...

But I get 10 outa 10 for trying! :) Jonathan, Geoff, Serg, Michael, et
al - just call this one SP3.

I keep breaking my vow of silence. (a)

Anyway, guys have a great weekend, and thanks to Jonathan, Geoff, Peter,
Chris etc for all your help and contributions!

Hilton
 
I fully agree that the new release should not be called SP2. It's just an
name, and having 2 SP2s in existence is just a bad, bad idea. It's like
releasing a version of anything, finding a bug, and re-releasing under the
same number. I've done it before, and it became a support nightmare fixed
only by releasing yet another version with an incremented version number.
 
Back
Top