Re: MSI Installation failure

From: Tony Questad (Tony.Questad_at_Datalight.com)
Date: 06/29/04

  • Next message: remcow: "How does one build an image to be stored in flash, running from ram?" 
    Date: Tue, 29 Jun 2004 12:45:32 -0700

    You know, I haven't checked exact version numbers (from the vendor, or my
    systems), so I'll sanity check those.

    As for copying the BSP - our minds were on the same track :)

    I did copy the BSP over in it's entirety from the other system, and imported
    it just fine into my catalog on this system. This does get me where I need
    to go for this one, and I'll probably do the same for the other 9 MSI files
    (each driver is version controlled and has it's own MSI) - and just coy the
    whole lot over and deal with the install problem later. Sure would be good
    to know what's going on though.

    I greatly apprecaite the suggestions, and if/when I do figure out what is
    blocking the install, I promise to share. I'll check versions, etc.

    Thanks Bruce -
    Tony

    "Bruce Eitman (eMVP)" <beitmannospam@nospam.neo.rr.com> wrote in message
    news:%23kizcAhXEHA.3944@tk2msftngp13.phx.gbl...
    > So, can you copy the cec file over from one of the other systems. Don't
    > think that it is the problem right now, but wouldn't hurt to rule it out.
    >
    > Argh, I forgot that this happens when the MSI is created with an older
    > version of PB. Could it be that the systems that work have an older
    version
    > of PB installed also?
    >
    > If that is the case, the BSP probably isn't installing anything other than
    a
    > new Platform directory and the CEC file. You may need to just zip it up
    and
    > transfer it to the other workstation. Heck you might just want to put it
    in
    > version control since you will most likely need to modify it a little
    > anyway.
    >
    > --
    > Bruce Eitman (eMVP)
    > Senior Engineer
    >
    >
    >

  • Next message: remcow: "How does one build an image to be stored in flash, running from ram?"

    Relevant Pages

    • Re: MSI Installation failure
      ... > As for copying the BSP - our minds were on the same track:) ... > to go for this one, and I'll probably do the same for the other 9 MSI ... > whole lot over and deal with the install problem later. ... can you copy the cec file over from one of the other systems. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Recent QFEs
      ... Try a logged install. ... Zip it up (ZIP will typically get 20-to-1 compression on MSI logs). ... Works fine and, when I run PB4.2, it shows up in the catalog correctly. ... I suspect that importing the CEC file by hand would result ...
      (microsoft.public.windowsce.platbuilder)
    • Re: Error while compiling WINCE OS 6.0 with Emulator ARMV4I
      ... Augustin schreef: ... I have send you the link to your ID,for the WINCE 6.0 BSP whatever i am using. ... Sysgening platform C:\WINCE500\platform\Adelaide_298 ... For every QFE they include a read me which tells you exaclty what will change/update when you install the QFE. ...
      (microsoft.public.windowsce.app.development)
    • Re: wince 5.0 evaluation version
      ... But the PB cannot build OS if the support for XScale is not included. ... Armv4i and XScale. ... Install support for XSCALE ... Create a new BSP form BSP Wizard selecting Armv4i ...
      (microsoft.public.windowsce.platbuilder)
    • Re: wince 5.0 evaluation version
      ... I'm able to build for a 270 and I've never installed the XSCALE stuff (as ... But the PB cannot build OS if the support for XScale is not included. ... Install support for XSCALE ... Create a new BSP form BSP Wizard selecting Armv4i ...
      (microsoft.public.windowsce.platbuilder)