CF 2.0 won't install on HP rz1710

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is this a known issue - has anyone got a workaround for this?
My project needs CF2.0 and according to MS this should load on any PPC with
CE 2003 or later. Now a customer with an otherwise fully functional HP
rz1710 device can not install the .CAB with the ActiveSync error that CF2.0
is not appropriate for this device!!!!!
I have found so support from HP and MS seem to have only ever released one
..CAB for CF2.0 for CE2003 devices. How do I solve this one?

Peter Beedell
 
The OpSys is Windows CE 2003 SE, version 4.21.1088.
The hp iPAQ rz1710 uses an Intel PXA270 processor.
The named CAB is the only one MS offers for CE4 devices!!!!
 
Please see this for installation issues:

http://blogs.msdn.com/netcfteam/archive/2005/10/11/479793.aspx

That's probably the reason of failure:

http://support.microsoft.com/default.aspx?scid=kb;en-us;824409

--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
Can I interpret all this information as follows: if CeAppMgr chooses not to
install CF 2.0 on a CE 2003 device, I can physically copy the CF .CAB file
onto the device and install it myself?
Trouble is, I don't have any such device to test this on - but my customers
do! I don't want to ask them to do someting that is doomed to failure. The
CF team wrote "There’s no workaround besides ROM upgrade." - but there is no
new ROM from HP for this device!
Living in hope!
Peter Beedell.
 
Since you stated you're using particular CAB file, I assumed you've tried
installing CAB manually already.

Note NETCF V2 Active Sync deployment would only work if you have AS 4.0 or
above (as stated on download page).

If you're using AS 3.x, wrong CAB can be pushed by it and manual
installation might work.



If that's indeed problem with ROM image (and not old AS pushing down wrong
CAB) and there's no ROM upgrade, I'm afraid this device is NETCF V2
incompatible.


--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
I am waiting to try the manual installation with my customer because I dont
have a device like this - we will see if it works!
Has anybody got a list of devices that are NETCF V2 compatable (and if not,
then information if the supplier has provided a firmware update to allow for
the installation of NETCF V2) - I think I am not the only one who is going to
start hitting this issue in a big way!
Keep up the good work!
Peter Beedell.
 
I don't have a full list of problematic devices as there are way to many
devices on the market.

I've seen reports of this issue, but it is in fact quite rare and updates
are available in most cases.



Here's few devices I know of:



Toshiba e35x

Toshiba e40x

"Wallaby" based devices.

--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
Back
Top