Re: Deploying Pocket PC Setup Applications (Vista Ultimate 64-bit)

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi all,

I am in the same boat too. I have a general market Pocket PC app that has
been working fine over the past 3 years being deployed via various desktop
Windows versions, also using a customized MSI approach. In my case I also
need to install some files on the desktop side and to create a directory on
the desktop and copy some files into that directory during the installation.
I also write some entries into the desktop registry too. All this is
accomplished by my CustomInstaller.

I have had reports that my app does not install onto a Windows Vista
Ultimate (64-bit version). I just recently purchased a new laptop with
Windows Vista Ultimate (64-bit) on it and I am currently trying to track
this problem down.

My MSI was created in VS .NET 2003 and is installed via the VS generated
Setup.exe bootstrapper. The app is also unsigned but I would not expect that
give this sort of problem in Vista. The error I get when simply running this
Setup.exe (with my MSI) on Vista Ultimate (64-bit) is: "The installer has
encountered an unexpected error installing this package. This may indicate a
problem with this package. The error code is 2869."

The error code does not reveal very much. Scanning the internet did not show
up too much either on this topic except that one post indicated that the
Setup.exe must have an embedded manifest in it. I do not know whether the
Setup.exe produced by VS .NET 2003 has this in it or can do it. Another post
indicated that VS 2005 generated Setup.exe can add a manifest.

I have not yet moved my app to my VS 2005 Pro on my WinXP (32-bit)
development computer, even though I have VS 2005 Pro installed there.

My next thought was to simply install VS 2005 Pro onto my Vista Ultimate
(64-bit). What I found was that VS 2005 keeps giving an error during its
installation. It comes up with "Setup Failed. The following component failed
to install: MSXML 6.0 Parser x64". Has anyone here been able to install VS
2005 Pro onto Vista Ultimate (64-bit) version? I have since passed this
problem onto Microsoft tech. support so I am waiting a reply.

I am now held up in trying to resolve my initial problem for one of my
customer's Vista Ultimate (64-bit) version.

I am open to any ideas.


Regards,
Neville Lang





"Nathan" <nmsurv@xxxxxxxxxxx> wrote in message
news:1173595410.882266.79100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I've developed an MSI Installer a while back according to this
pattern.

http://msdn2.microsoft.com/en-us/library/ms838273.aspx

Of course, it has been updated with VS 2005 and .NET CF 2.0.

It installs the .NET CF 2.0 cab, the English string resources for .NET
CF 2 ( not really optional in practice), and my application CAB. It
uses a custom action of an executable to call winceappmanager with the
name of the cabs.

What part of it is likely to fail on Vista? And give an error like:

"There is a problem with this Windows Installer package. A program
required for this install to complete could not be run. Contact your
Support personnel or package vendor"

I don't have a Vista system myself to test with, so I have to rely on
the reports from end users.

Are there rules I can follow to make the MSI install work?

I don't have the budget to hire an install expert nor become one
myself, so I'm open to non MSI solutions to the problem. I've rejected
solutions like EzPocketSetup in the past because they don't install
more than one cab.

Nathan



.

Relevant Pages

  • RE: CAB installation
    ... Before you can determine whether it is your app or not you need to determine ... safe to install sql server compact edition in Flashdisk instead of RAM. ... The default directory is specified by the CAB file, you can't change it, you ... But its not working for .net compact framework. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: CreateProcess/WaitForSingleObject Infininte does NOT work w/ M
    ... You can enter whatever CAB name you want. ... Yes, it uses CreateProcess() to start the application, using the command ... when you're trying to install that CAB file, either the installer or the OS ... > the app file menu didnt show up on the newer model so i couldnt test it on ...
    (microsoft.public.dotnet.framework.compactframework)
  • 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: One touch Restore
    ... > Many of the settings can be stored in XML, by querying these settings, ... >> created a nice install app using NSIS open source stuff. ... Install the Symbol library cab ...
    (microsoft.public.pocketpc.developer)
  • Re: Hard Reset Recovery
    ... the Application folder on a Symbol device is non-volatile memory and ... the compact framework cab file and install it. ... > Could I write managed app in VS2003 to run the cabs ...
    (microsoft.public.dotnet.framework.compactframework)