Re: CF 2.0 won't install on HP rz1710

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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.

"Ilya Tumanov [MS]" wrote:

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).

"Puddles" <Puddles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C39DE8AF-87D5-4337-8B67-7F5736ABD529@xxxxxxxxxxxxxxxx
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!!!!

"Puddles" wrote:

NETCFv2.ppc.armv4.cab, size 5.355KB, date 1st Sept 2005

"Alex Feinman [MVP]" wrote:

Which CAB are you installing?

"Puddles" <Puddles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6AE7BB5-8B30-44BB-85EB-1D9CF0AF3181@xxxxxxxxxxxxxxxx
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





.

Relevant Pages

  • Re: How to cause IE to use specific plugin?
    ... to install 1.4 version if there is already 1.5 version installed. ... JRE - the console confirmed the applet was now running in ... So we have 1 'failure to reproduce the problem' using a .CAB ...
    (comp.lang.java.help)
  • Re: How to cause IE to use specific plugin?
    ... to install 1.4 version if there is already 1.5 version installed. ... JRE - the console confirmed the applet was now running in ... So we have 1 'failure to reproduce the problem' using a .CAB ...
    (comp.lang.java.help)
  • Re: How to get a WM5 devices O/S Version in a call without using RAPI?
    ... separate INI and install NETCF the same way as your application. ... > o/s to install the right CAB file. ... > As for WM5 devices, it seems I still may need to detect the operating ... > install my app onto a WM5 device, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: VS2003 and WM5.0 Devices
    ... The problem I have is that a customer who has a JasJar has reported that my installer will not install my app at all. ... I still have some customers who have the ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: WARNING : KB977165 Can/May/Will Cause BSODs for Some Windows XP Users
    ... In our continuing investigation in to the restart issues related to MS10-015 that a limited number of customers are experiencing, we have determined that malware on the system can cause the behavior. ... One of the key components when investigating issues like this are obtaining memory dumps from computers experiencing the problem. ... For customers who do not have anti-virus software, you can either scan your system using our online tool at http://safety.live.com or you can install Microsoft Security Essentials for free. ... We are still investigating this but I wanted to provide some additional clarity on what I mean when I said we stopped offering the update via Windows Update. ...
    (microsoft.public.windowsupdate)