CF "Fatal Application Error" Exception 0xc0000005

[alfred]

Hi all,

We have a WinCE4.2 PXA25x Platform ARMV4I with
Compact Framework V1.0 incl. SP1.
QFEs from 30.06.03 are installed.


If we create a Smart Device Application under
VS.NET and launch the exe file on the CE-device
an "Fatal Application Error" occurs
"exception 0xC0000005".





After installing all QFEs the CompactFrameWork on device
is more recent as the one from the VS.NET 2003.

OUTPUT from VS.NET

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§

------ Build started: Project: CFTEST, Configuration:
Debug Windows CE ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy CFTEST


------ Deploy started: Project: CFTEST, Configuration:
Debug Windows CE ------
Deploying to CTTEST CE .NET Device using TCP Connect
Transport
Connected to CTTEST CE .NET Device (Windows CE) running on
ARMV4T.
Copying files from 'C:\WINCE420
\OMTT\APPLIC\vsnet\CFTEST\bin\Debug' to '\Program
Files\CFTEST'
Copying CFTEST.exe
Files in the package 'netcf.all.wce4.armv4t.cab' are more
recent on the device than on the development computer.
Consider upgrading to the latest version. Files affected
are:

Microsoft.windowsce.forms.dll
Microsoft.visualbasic.dll
System.data.dll
System.net.irda.dll
System.xml.dll
System.windows.forms.datagrid.dll
System.windows.forms.dll
System.web.services.dll
System.drawing.dll
System.dll
Mscorlib.dll
Netcfagl1_0.dll
Cgacutil.exe
Mscoree1_0.dll
Mscoree.dll
Copying System_SR_enu.cab
Launching device installation of 'System_SR_enu.cab'.
Please check device screen for further
instructions............


---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped


Launching Application


§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

then the Device shows an "Fatal Application Error"

Why compares VS.NET a CompactFrameWork Version armv4t with
the Device - i have a armv4i BSP.

Our Display Driver is modifyed to 8Bpp, is this supported
from the CompactFrameWork?

Best Regards,

Alfred






















"Paul G. Tobey [eMVP]" <[email protected]>
wrote in message

Yes, there's a bug in one of the QFEs for Platform

Builder/CE.NET. You need

to make sure you've installed *all* of the QFEs

available on Microsoft's

site. When you've done that, and rebuilt your OS, it

will work fine.

 

[Paul G. Tobey [eMVP]]

Install *all* of the available QFEs, up through today, to be sure that you
aren't suffering from one which broke Compact Framework operations. The bad
one is KB822606.

Paul T.


Hi all,

We have a WinCE4.2 PXA25x Platform ARMV4I with
Compact Framework V1.0 incl. SP1.
QFEs from 30.06.03 are installed.


If we create a Smart Device Application under
VS.NET and launch the exe file on the CE-device
an "Fatal Application Error" occurs
"exception 0xC0000005".





After installing all QFEs the CompactFrameWork on device
is more recent as the one from the VS.NET 2003.

OUTPUT from VS.NET

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§

------ Build started: Project: CFTEST, Configuration:
Debug Windows CE ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy CFTEST


------ Deploy started: Project: CFTEST, Configuration:
Debug Windows CE ------
Deploying to CTTEST CE .NET Device using TCP Connect
Transport
Connected to CTTEST CE .NET Device (Windows CE) running on
ARMV4T.
Copying files from 'C:\WINCE420
\OMTT\APPLIC\vsnet\CFTEST\bin\Debug' to '\Program
Files\CFTEST'
Copying CFTEST.exe
Files in the package 'netcf.all.wce4.armv4t.cab' are more
recent on the device than on the development computer.
Consider upgrading to the latest version. Files affected
are:

Microsoft.windowsce.forms.dll
Microsoft.visualbasic.dll
System.data.dll
System.net.irda.dll
System.xml.dll
System.windows.forms.datagrid.dll
System.windows.forms.dll
System.web.services.dll
System.drawing.dll
System.dll
Mscorlib.dll
Netcfagl1_0.dll
Cgacutil.exe
Mscoree1_0.dll
Mscoree.dll
Copying System_SR_enu.cab
Launching device installation of 'System_SR_enu.cab'.
Please check device screen for further
instructions............


---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped


Launching Application


§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

then the Device shows an "Fatal Application Error"

Why compares VS.NET a CompactFrameWork Version armv4t with
the Device - i have a armv4i BSP.

Our Display Driver is modifyed to 8Bpp, is this supported
from the CompactFrameWork?

Best Regards,

Alfred






















"Paul G. Tobey [eMVP]" <[email protected]>
wrote in message

Yes, there's a bug in one of the QFEs for Platform

Builder/CE.NET. You need

to make sure you've installed *all* of the QFEs

available on Microsoft's

site. When you've done that, and rebuilt your OS, it

will work fine.

 

[alfred]

Hello Paul,

now we have installed all QFEs.
cf.exe launched from flashdisk works fine.

but then i launch the application from VS.NET, only a
download happens. Then a "sand watch" for a few seconds on
device Desktop and nothing else.

I work with the SDAuth... tool - TCP transport.

should debugger know CPU TYP, how can i configure without
Active Sync ?

thanks in advance,
Alfred

-----Original Message-----
Install *all* of the available QFEs, up through today, to be sure that you
aren't suffering from one which broke Compact Framework operations. The bad
one is KB822606.

Paul T.


Hi all,

We have a WinCE4.2 PXA25x Platform ARMV4I with
Compact Framework V1.0 incl. SP1.
QFEs from 30.06.03 are installed.


If we create a Smart Device Application under
VS.NET and launch the exe file on the CE-device
an "Fatal Application Error" occurs
"exception 0xC0000005".





After installing all QFEs the CompactFrameWork on device
is more recent as the one from the VS.NET 2003.

OUTPUT from VS.NET

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§ §
§§§§§§§§§§§§§§§§§§§§§§§

------ Build started: Project: CFTEST, Configuration:
Debug Windows CE ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy CFTEST


------ Deploy started: Project: CFTEST, Configuration:
Debug Windows CE ------
Deploying to CTTEST CE .NET Device using TCP Connect
Transport
Connected to CTTEST CE .NET Device (Windows CE) running on
ARMV4T.
Copying files from 'C:\WINCE420
\OMTT\APPLIC\vsnet\CFTEST\bin\Debug' to '\Program
Files\CFTEST'
Copying CFTEST.exe
Files in the package 'netcf.all.wce4.armv4t.cab' are more
recent on the device than on the development computer.
Consider upgrading to the latest version. Files affected
are:

Microsoft.windowsce.forms.dll
Microsoft.visualbasic.dll
System.data.dll
System.net.irda.dll
System.xml.dll
System.windows.forms.datagrid.dll
System.windows.forms.dll
System.web.services.dll
System.drawing.dll
System.dll
Mscorlib.dll
Netcfagl1_0.dll
Cgacutil.exe
Mscoree1_0.dll
Mscoree.dll
Copying System_SR_enu.cab
Launching device installation of 'System_SR_enu.cab'.
Please check device screen for further
instructions............


---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped


Launching Application


§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§ §
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

then the Device shows an "Fatal Application Error"

Why compares VS.NET a CompactFrameWork Version armv4t with
the Device - i have a armv4i BSP.

Our Display Driver is modifyed to 8Bpp, is this supported
from the CompactFrameWork?

Best Regards,

Alfred






















"Paul G. Tobey [eMVP]" <[email protected]>
wrote in message

Yes, there's a bug in one of the QFEs for Platform

Builder/CE.NET. You need

to make sure you've installed *all* of the QFEs

available on Microsoft's

site. When you've done that, and rebuilt your OS, it

will work fine.

Paul T.


FrameWork
Unhandled

Violation). Compact

netcf.all.wce4.armv4t.cab

.

 

[Paul G. Tobey [eMVP]]

I've never bothered to do anything without ActiveSync. If you can, I'd try
to connect to the device first with ActiveSync, then switch to network only.
There's an article on MSDN about connecting to the device when ActiveSync is
not available. You might read through that and see what you get from it.

Paul T.


Hello Paul,

now we have installed all QFEs.
cf.exe launched from flashdisk works fine.

but then i launch the application from VS.NET, only a
download happens. Then a "sand watch" for a few seconds on
device Desktop and nothing else.

I work with the SDAuth... tool - TCP transport.

should debugger know CPU TYP, how can i configure without
Active Sync ?

thanks in advance,
Alfred

-----Original Message-----
Install *all* of the available QFEs, up through today, to be sure that you
aren't suffering from one which broke Compact Framework operations. The bad
one is KB822606.

Paul T.


Hi all,

We have a WinCE4.2 PXA25x Platform ARMV4I with
Compact Framework V1.0 incl. SP1.
QFEs from 30.06.03 are installed.


If we create a Smart Device Application under
VS.NET and launch the exe file on the CE-device
an "Fatal Application Error" occurs
"exception 0xC0000005".





After installing all QFEs the CompactFrameWork on device
is more recent as the one from the VS.NET 2003.

OUTPUT from VS.NET

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§ §
§§§§§§§§§§§§§§§§§§§§§§§

------ Build started: Project: CFTEST, Configuration:
Debug Windows CE ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy CFTEST


------ Deploy started: Project: CFTEST, Configuration:
Debug Windows CE ------
Deploying to CTTEST CE .NET Device using TCP Connect
Transport
Connected to CTTEST CE .NET Device (Windows CE) running on
ARMV4T.
Copying files from 'C:\WINCE420
\OMTT\APPLIC\vsnet\CFTEST\bin\Debug' to '\Program
Files\CFTEST'
Copying CFTEST.exe
Files in the package 'netcf.all.wce4.armv4t.cab' are more
recent on the device than on the development computer.
Consider upgrading to the latest version. Files affected
are:

Microsoft.windowsce.forms.dll
Microsoft.visualbasic.dll
System.data.dll
System.net.irda.dll
System.xml.dll
System.windows.forms.datagrid.dll
System.windows.forms.dll
System.web.services.dll
System.drawing.dll
System.dll
Mscorlib.dll
Netcfagl1_0.dll
Cgacutil.exe
Mscoree1_0.dll
Mscoree.dll
Copying System_SR_enu.cab
Launching device installation of 'System_SR_enu.cab'.
Please check device screen for further
instructions............


---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped


Launching Application


§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§ §
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

then the Device shows an "Fatal Application Error"

Why compares VS.NET a CompactFrameWork Version armv4t with
the Device - i have a armv4i BSP.

Our Display Driver is modifyed to 8Bpp, is this supported
from the CompactFrameWork?

Best Regards,

Alfred






















"Paul G. Tobey [eMVP]" <[email protected]>
wrote in message

Yes, there's a bug in one of the QFEs for Platform

Builder/CE.NET. You need

to make sure you've installed *all* of the QFEs

available on Microsoft's

site. When you've done that, and rebuilt your OS, it

will work fine.

Paul T.


FrameWork
Unhandled

Violation). Compact

netcf.all.wce4.armv4t.cab

.

 

[alfred]

Hello Paul,

I know, something about my next problem is posted in
newsgroups.
But what is to do?

Now I have a connection from vs.net via Active Sync to my
CE.NET 4.2 Device.

"Start without debugging" the application comes up.

With a simple "GO" no launch on desktop happens.


My Installation order: AS 3.5 / VS.NET 2003 / AS 3.7 -
nothing uninstalled.


I have tried ARMV4I / ARMV4T / POCKET PC / Win.CE - no
success.

Best regards,
alfred

-----Original Message-----
I've never bothered to do anything without ActiveSync. If you can, I'd try
to connect to the device first with ActiveSync, then switch to network only.
There's an article on MSDN about connecting to the device when ActiveSync is
not available. You might read through that and see what you get from it.

Paul T.


Hello Paul,

now we have installed all QFEs.
cf.exe launched from flashdisk works fine.

but then i launch the application from VS.NET, only a
download happens. Then a "sand watch" for a few seconds on
device Desktop and nothing else.

I work with the SDAuth... tool - TCP transport.

should debugger know CPU TYP, how can i configure without
Active Sync ?

thanks in advance,
Alfred

-----Original Message-----
Install *all* of the available QFEs, up through today, to be sure that you
aren't suffering from one which broke Compact Framework operations. The bad
one is KB822606.

Paul T.


Hi all,

We have a WinCE4.2 PXA25x Platform ARMV4I with
Compact Framework V1.0 incl. SP1.
QFEs from 30.06.03 are installed.


If we create a Smart Device Application under
VS.NET and launch the exe file on the CE-device
an "Fatal Application Error" occurs
"exception 0xC0000005".





After installing all QFEs the CompactFrameWork on device
is more recent as the one from the VS.NET 2003.

OUTPUT from VS.NET

§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

§

§
§§§§§§§§§§§§§§§§§§§§§§§

------ Build started: Project: CFTEST, Configuration:
Debug Windows CE ------
Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy CFTEST


------ Deploy started: Project: CFTEST, Configuration:
Debug Windows CE ------
Deploying to CTTEST CE .NET Device using TCP Connect
Transport
Connected to CTTEST CE .NET Device (Windows CE) running on
ARMV4T.
Copying files from 'C:\WINCE420
\OMTT\APPLIC\vsnet\CFTEST\bin\Debug' to '\Program
Files\CFTEST'
Copying CFTEST.exe
Files in the package 'netcf.all.wce4.armv4t.cab' are more
recent on the device than on the development computer.
Consider upgrading to the latest version. Files affected
are:

Microsoft.windowsce.forms.dll
Microsoft.visualbasic.dll
System.data.dll
System.net.irda.dll
System.xml.dll
System.windows.forms.datagrid.dll
System.windows.forms.dll
System.web.services.dll
System.drawing.dll
System.dll
Mscorlib.dll
Netcfagl1_0.dll
Cgacutil.exe
Mscoree1_0.dll
Mscoree.dll
Copying System_SR_enu.cab
Launching device installation of 'System_SR_enu.cab'.
Please check device screen for further
instructions............


---------------------- Done ----------------------
Build: 1 succeeded, 0 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped


Launching Application


§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

§

§
§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§§

then the Device shows an "Fatal Application Error"

Why compares VS.NET a CompactFrameWork Version armv4t with
the Device - i have a armv4i BSP.

Our Display Driver is modifyed to 8Bpp, is this supported
from the CompactFrameWork?

Best Regards,

Alfred






















"Paul G. Tobey [eMVP]" <[email protected]>
wrote in message

Yes, there's a bug in one of the QFEs for Platform

Builder/CE.NET. You need

to make sure you've installed *all* of the QFEs

available on Microsoft's

site. When you've done that, and rebuilt your OS, it

will work fine.

Paul T.





I have a WinCE4.2 PXA25x Platform with Compact FrameWork

1.0 included.

When i start a Managed Code Programm, PB shows a Unhandled

exception in COREDLL.DLL (0xC0000005 Access

Violation).

has anyone a idea ?

A Registry entry from my Device:

HKEY_LOCAL_MACHINE/SOFTWARE/Apps/Microsoft .NET

Compact

Framework/CabFile = netcf.all.wce4.armv4t.cab

Is armv4t right, i have a armv4i BSP.

VS.NET 2003 also trys to install netcf.all.wce4.armv4t.cab


I have no Active Sync Connection, i connect with the

SDAuthenthication Utility.

How can i select the right CPU Type ?

VS.NET | Tools | Select Windows CE Device CPU

needs Active Sync

Best Regards

.

.