Re: Problem with Property ***
From: Michael Reim (nospam.reim_at_REMOVENOSPAMANDCAPShelmut-fischer.denospam)
Date: 05/05/04
- Next message: Tweeeek: "Re: Power Management 4.2"
- Previous message: Thats me: "Re: How to build the ad-hoc wireless connection information into CE Image?"
- In reply to: Dean Ramsier: "Re: Problem with Property ***"
- Next in thread: Dean Ramsier: "Re: Problem with Property ***"
- Reply: Dean Ramsier: "Re: Problem with Property ***"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 5 May 2004 12:23:26 +0200
Thank you Dean
this was exactly what I needed.
There are no more error messages.
And more important, there is no more total system crash,
when displaying Propertysheets.
Thank you very much for your help.
-- Michael Reim reim AT helmut-fischer DOT de "Dean Ramsier" <dramsiernospam@accelentnospam.com> schrieb im Newsbeitrag news:#WK7rddMEHA.1484@tk2msftngp13.phx.gbl... > I've seen the same thing. There's a QFE that's just been released that > makes this error message go away. See > > http://www.microsoft.com/downloads/details.aspx?FamilyID=2269f08e-033a-40c4- ba6b-42377036dc6f&DisplayLang=en > > On my system, this is also causing a data abort about the same time the > error messages come through. The data abort only occurs if the application > is XIP from flash. Call stack varies depending on the build and doesn't > seem to have anything to do with the application. If the app is compressed, > or the image is running entirely from RAM, the data abort doesn't occur. > The QFE unfortunately didn't solve this problem. > > I've no idea what might be causing this one. > > -- > Dean Ramsier - eMVP > Accelent Systems > http://www.accelent.com > > > "Michael Reim" <nospam.reim@REMOVENOSPAMANDCAPShelmut-fischer.denospam> > wrote in message news:%23scxyPQLEHA.2388@TK2MSFTNGP09.phx.gbl... > > Hi all > > > > Running an evc application that creates a property*** with 2 > > propertypages, > > I get this debug output in PB4.2: > > 1674978 0x8db69400: Menus in dialogs are not supported! > > 1676651 0x8db69400: ERROR: > > d:\mckendric\private\winceos\coreos\gwe\winmgr\wmbase\wmbase.cpp line 581: > > 1676651 0x8db69400: CreateWindow failed: Could not find > > > class=K6ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ > > > ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ > > ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ > > 1676653 0x8db69400: ERROR: > > d:\mckendric\private\winceos\coreos\gwe\dlgmgr\main\cmncore\loaddlg.cpp > line > > 511: > > 1676653 0x8db69400: CreateDialog() failed: couldn't create dialog > > 1676693 0x8db69400: Menus in dialogs are not supported! > > 1678357 0x8db69400: ERROR: > > d:\mckendric\private\winceos\coreos\gwe\winmgr\wmbase\wmbase.cpp line 581: > > 1678358 0x8db69400: CreateWindow failed: Could not find > > > class=K6ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ > > > ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ > > ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ > > 1678359 0x8db69400: ERROR: > > d:\mckendric\private\winceos\coreos\gwe\dlgmgr\main\cmncore\loaddlg.cpp > line > > 511: > > 1678360 0x8db69400: CreateDialog() failed: couldn't create dialog > > > > What does that mean? > > > > TIA > > -- > > Michael Reim > > reim AT helmut-fischer DOT de > > > > > >
- Next message: Tweeeek: "Re: Power Management 4.2"
- Previous message: Thats me: "Re: How to build the ad-hoc wireless connection information into CE Image?"
- In reply to: Dean Ramsier: "Re: Problem with Property ***"
- Next in thread: Dean Ramsier: "Re: Problem with Property ***"
- Reply: Dean Ramsier: "Re: Problem with Property ***"
- Messages sorted by: [ date ] [ thread ]