MFC problem

In
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncenet/html/wincenet_cepcc_app.asp
Mike Hall discusses at the end, compatibility issues with MFC on WinCE4.2.

My situation is that a device driver for a CF A2D device has been built with
MFC3 targetting Pocket PC 2002 devices (eg iPaqs). This requires:
- The device DLL
- mfc300.dll
- mfc300d.dll
- docview.dll

With a little dexterity I have been able to install and program the device
with EVC 4 on a Pocket PC 2003 (iPaq) device.

I want to run the A2D device on an embedded CE 4.2 device: Intrinsyc
CefrBoard (PXA255). I can't run the device install (via activesync (AS)) to
the device when the image is up becuase AS install says the device is not
suitable (** see footnote).
So I try tried the copy mode. I can get all of the files except
docview.dll. When I try to copy it from the iPaq the system won't let me
(says its busy). Have tried rebooting device and copying (via activesync and
evc File tool) but fails.

A rebuild of the device driver with MFC4 is in order but don't have source
code.

Any ideas??

================
Footnote: Its a real pain that Activesync install won't let you install
PPC2003 devices to embedded CE.NET 4.2 devices when using the same device
hardware (ie CF) and embedded COU is XSCAL (same as iPaq). Surely tthis
should be an option (you decide) liek some of the Socket device installs. Is
there a way around this. I have partially built a program that snapshots
file system and registry before and after an install and differences. Not
quite complete yet though.
--
--
David Jones
Senior Lecturer
School of Electrical & Computer Engineering
RMIT University
+61 3 99255318

Chris
Sun Oct 03 10:10:25 CDT 2004

Just becasue a CE 4.2 device has the same base OS doesn't mean it will have
any of the components that the PPC has. CE is a very flexible thing, so
there could be a lot of stuff you're dependent on that are there in the
standard PPC but not in the CE device CE builds many of its libraries
dynamically when the image is created, so even having a DLL present doesn't
mean all the exported functions you need will be there. There simply no way
to ensure that an app written for the PPC will run on every CE device. You
just can't do it. For this reason, the installer looks at the target
platform.

Now with all that said, there are a few other notes:
1. There's no reason you can't extract the files from the CAB and manually
copy them to the device.
2. I view anything that ships a debug build of MFC as highly suspect.

-Chris



"David Jones" <davejones@rmit.edu.au.nospamplease> wrote in message
news:038E5CC6-84D6-4259-8C1A-2A9C29007671@microsoft.com...
> In
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncenet/html/wincenet_cepcc_app.asp
> Mike Hall discusses at the end, compatibility issues with MFC on WinCE4.2.
>
> My situation is that a device driver for a CF A2D device has been built
with
> MFC3 targetting Pocket PC 2002 devices (eg iPaqs). This requires:
> - The device DLL
> - mfc300.dll
> - mfc300d.dll
> - docview.dll
>
> With a little dexterity I have been able to install and program the device
> with EVC 4 on a Pocket PC 2003 (iPaq) device.
>
> I want to run the A2D device on an embedded CE 4.2 device: Intrinsyc
> CefrBoard (PXA255). I can't run the device install (via activesync (AS))
to
> the device when the image is up becuase AS install says the device is not
> suitable (** see footnote).
> So I try tried the copy mode. I can get all of the files except
> docview.dll. When I try to copy it from the iPaq the system won't let me
> (says its busy). Have tried rebooting device and copying (via activesync
and
> evc File tool) but fails.
>
> A rebuild of the device driver with MFC4 is in order but don't have source
> code.
>
> Any ideas??
>
> ================
> Footnote: Its a real pain that Activesync install won't let you install
> PPC2003 devices to embedded CE.NET 4.2 devices when using the same device
> hardware (ie CF) and embedded COU is XSCAL (same as iPaq). Surely tthis
> should be an option (you decide) liek some of the Socket device installs.
Is
> there a way around this. I have partially built a program that snapshots
> file system and registry before and after an install and differences. Not
> quite complete yet though.
> --
> --
> David Jones
> Senior Lecturer
> School of Electrical & Computer Engineering
> RMIT University
> +61 3 99255318