PPC 2003 deployment issue

  • Thread starter Thread starter Blaine
  • Start date Start date
B

Blaine

I have used the installation and setup suggestions in
the "Developing and Deploying Pocket PC Setup
Applications" article. The installation program
correctly installs NCF and the application in PPC 2002
devices. When installing to PPC 2003, however, the
installation appears to be successful, but on the device
an error dialog appears indicating that the installation
was not successful and advises to re-install. Re-
installation simply produces the same error.

If I copy the App.ARM.CAB file to the device, it installs
without a problem. Has anyone had a similar problem?

Blaine Fields
 
Is this with a single device or all Pocket PC 2003 devices? If so which
models are affected?

Peter
 
Peter,

I have a Viewsonic V37. Initially the device was running
PPC 2002 and the installation was O.K. Others who have
successfully installed it were using a variety of devices
from Dell and others, but all apparently running PPC
2002. The problem first arose when a user tried
installing to an iPAQ 4000 series later determined to be
running PPC 2003. When I upgraded my Viewsonic with PPC
2003, I got the identical error as the iPAQ. I therefore
assumed the problem was related to the PPC 2003.

Blaine Fields
 
Blaine,

If you use the .NET CF Web redist to deploy to your Viewsonic with PPC
2003, does it succeed? Also, which .cab file does it deploy to this
device? Remember, .cabs for PPC 2002 and older will have PPC3 in the name,
while PPC 2003 and newer will have WCE4 in the name.

Stan Adermann
Developer
Microsoft .NET Compact Framework

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

--------------------
| From: "Blaine" <[email protected]>
| Subject: Re: PPC 2003 deployment issue
|
| Peter,
|
| I have a Viewsonic V37. Initially the device was running
| PPC 2002 and the installation was O.K. Others who have
| successfully installed it were using a variety of devices
| from Dell and others, but all apparently running PPC
| 2002. The problem first arose when a user tried
| installing to an iPAQ 4000 series later determined to be
| running PPC 2003. When I upgraded my Viewsonic with PPC
| 2003, I got the identical error as the iPAQ. I therefore
| assumed the problem was related to the PPC 2003.
|
| Blaine Fields
|
 
Stan, I don't understand. Currently I have netcf...pp3
files included in the MSI but did not load the
netcf...WCE4 files because I understood that PPC 2003 had
netcf already included in the OS. Am I not thinking
properly about this?

Blaine Fields
 
It occurs to me that in the Visual Studio environment,
clicking on the "make cabs" button produces only cabs
based upon the netcf found in WCE300 subdirectory. The
resulting BAT file and INF file don't reference
application cabs for CE 4.0. I tried your idea of simply
incorporating netcf...WCE4 in the MSI, but this had no
effect, of course. Nothing in any INF file references
these files or the application CAB files related to
them.

Blaine Fields
 
PocketPC 2003 devices run WindowsCE 4.0+, and therefore should not be using
NETCF built for the earlier platforms. It may work, but that version of CF
has not been tested against that version of CE, and there may be unforseen
problems.

While PocketPC 2003 devices may have CF in ROM, you may still wish to
install the CF service pack, so it's not a bad idea to include the cab if
you believe you need the newer version. It's also possible that the device
may not have it at all, even though it's 2003. To verify the presence of
NETCF, use File Explorer to browse to the \windows\ directory and run
cgacutil. It will pop a dialog that tells what version of NETCF is
present. No cgacutil, no NETCF.

Also, the sample you based your MSI on has a set of variables for including
or excluding support for different platforms. If you directly copied this,
make sure the variable is set for the CE4ARMV4 device.

Stan Adermann
Developer
Microsoft .NET Compact Framework

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

--------------------
| From: "Blaine" <[email protected]>
| Subject: Re: PPC 2003 deployment issue
|
| It occurs to me that in the Visual Studio environment,
| clicking on the "make cabs" button produces only cabs
| based upon the netcf found in WCE300 subdirectory. The
| resulting BAT file and INF file don't reference
| application cabs for CE 4.0. I tried your idea of simply
| incorporating netcf...WCE4 in the MSI, but this had no
| effect, of course. Nothing in any INF file references
| these files or the application CAB files related to
| them.
|
| Blaine Fields
|
|
| >-----Original Message-----
| >Blaine,
| >
| >If you use the .NET CF Web redist to deploy to your
| Viewsonic with PPC
| >2003, does it succeed? Also, which .cab file does it
| deploy to this
| >device? Remember, .cabs for PPC 2002 and older will
| have PPC3 in the name,
| >while PPC 2003 and newer will have WCE4 in the name.
| >
| >Stan Adermann
| >Developer
| >Microsoft .NET Compact Framework
| >
| >This posting is provided "AS IS" with no warranties, and
| confers no rights.
| >
| >--------------------
| >| From: "Blaine" <[email protected]>
| >| Subject: Re: PPC 2003 deployment issue
| >|
| >| Peter,
| >|
| >| I have a Viewsonic V37. Initially the device was
| running
| >| PPC 2002 and the installation was O.K. Others who
| have
| >| successfully installed it were using a variety of
| devices
| >| from Dell and others, but all apparently running PPC
| >| 2002. The problem first arose when a user tried
| >| installing to an iPAQ 4000 series later determined to
| be
| >| running PPC 2003. When I upgraded my Viewsonic with
| PPC
| >| 2003, I got the identical error as the iPAQ. I
| therefore
| >| assumed the problem was related to the PPC 2003.
| >|
| >| Blaine Fields
| >|
| >
| >.
| >
|
 
Back
Top