1 Reply Latest reply on Mar 31, 2016 5:51 AM by Darryn Campbell

    How to install EnterpriseBrowser v1.4 on VC5090 with Windows CE 5.0?

    Jean-Marc Hilson

      Hello,

      When trying to install EnterpriseBrowser v1.4 on VC5090 Windows CE 5.0 I receive an error message stating that EnterpriseBrowser.exe was not correctly copied.

       

       

      The install is continuing after that I click on OK and once installed, I cannot launch the browser:

       

       

      Cannot find 'EnterpriseBrowser' (or one of its components). etc.

       

      I am trying to install EnterpriseBrowser into the Application folder.

      2 Installation methods were ending with same result: installing from the Runtime copied on the device itself / installing from the installation tool from my computer with the device connected to it (USB).

       

      In the page below, the device seems compatible with this version:

      https://developer.zebra.com/docs/DOC-2566#mobile

       

      Thank you.

       

      JM

       

        • Re: How to install EnterpriseBrowser v1.4 on VC5090 with Windows CE 5.0?
          Darryn Campbell

          Hi JM,

           

          The VC5090 will only cope with running the IE (Internet Explorer) engine.  To install into the Application folder run the Enterprise Browser desktop installer and select "Enterprise Browser - IE (Persistent)" under the 'Windows CE' options.

           

          Once the .cab file is deployed and installed you should see an Enterprise Browser folder structure somewhere under \Application.

           

          To complete installation, you'll need to cold boot the device.  Given the error message you describe I suspect that's the missing step.  You can find instructions to cold boot in the device integration guide from support.symbol.com (https://atgsupportcentral.motorolasolutions.com/content/emb/docs/manuals/7634606a.pdf )

           

          Whilst Enterprise Browser will work in the technical sense I would advise against using it for developing new applications on the device.  Exactly which APIs are and aren't supported with the IE engine isn't explicitly documented, the primary design here is to support older applications written for PocketBrowser