Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 32
  1. #11
    Junior Member
    Join Date
    Jul 2016
    Location
    Belgium
    Posts
    6
    Rep Power
    0

    Default

    it worked on my device (Clarion MAP780) with version primo 9.6.5.221194, but then I decided to upgrade to this (suppose this is the latest and greatest version out there for windows ce?)
    downloaded this version, first trying to keep the content and then with the provided content folder, both have the same issue hard reset happens and i see the above message in crash.log.

  2.    Advertissements


  3. #12
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    Can you post the crash.oog file? It might help us to identify the issue. Also, are you using your original sys.txt file or the sys.txt file that came in the archive? I would use your original sys.txt file. You can also try renaming the save folder to "save.old".

    All of that being said, this is not the newest version. The newest/best version I've found for WinCE is 9.6.13.405512. Can d/l here (use WD executable):

    [Only registered and activated users can see links. ]

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  4. #13
    Junior Member
    Join Date
    Jul 2016
    Location
    Belgium
    Posts
    6
    Rep Power
    0

    Default

    Unless missing something, this thread is about 9.8.X, your version is 9.6.X. Regardless I tried it and had exactly the same issue (reboot at once starting it).
    Maybe doing something stupid like running CE 6.0 executable on CE 5.0 or so.
    Reverted to my version and everything running fine, strange.
    P.S. Also this one [Only registered and activated users can see links. ] did something, started a logo and crashed then. Go figure.
    Last edited by girtsn; 5th July 2016 at 16:24.

  5. #14
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    You can't go by the 9.x.x part of the version numebr to tell you which is newer. As far as I know, the higher the ending number (405512, for example), the newer the software is (release date). I checked this 9.8.0 version previously and from what I can tell, it's a 2.0 or 2.1 version of Primo, not a 2.4 version.

    405512 may not be the very latest, but it's the latest version I've found that supports both Nuance *and* Loquendo TTS engines. The newer versions that I did try (mainly the Blapunkt 491814 release), don't support the Loquendo TTS engine. Personally, I prefer the Loquendo TTS voices as they sound more natural, so I will only use versions that support Loquendo and Nuance. The only other newer version (for WinCE) that I'm aware of is the Alpine 462295 release, but it's very Alpine-specific. In my experience, Alpine and Clarion versions are not so great for "generic" devices.

    Anyway - back to your problem though... Are you using your original sys.txt file? Have you tried renaming the save folder? Can you post the contents of the crash file? The 405512 release definitely works on both WinCE 5 and WInCE6 devices. Generally, iGo releases do not require a specific version of WinCE.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  6. #15
    Junior Member
    Join Date
    Jul 2016
    Location
    Belgium
    Posts
    6
    Rep Power
    0

    Default

    i am using the sys.txt that cames with the downloaded version, but I tried overwriting it with mine, no difference
    Code:
    Please Login or Register to see the links

  7. #16
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    Hmm - being that it's crashing so soon (5 seconds) and you have a small amout of "TotalUsableMemory", I wonder if you just don't have enough RAM to run these newer versions... The version that came with your radio may be a special "small RAM" version? Just for comparison, my headunit typically has about 77mb of TotalUsableMemory listed in iGo crash files.

    Are you also using the "license" directory from the new versions and deleting or renaming the "save" directory when you try to run the newer versions?

    Sent from my HP SlateBook 10 x2 PC using Tapatalk
    Last edited by jtrosky; 6th July 2016 at 15:12.

  8. #17
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    I looked into your device a little more. When you mentioned Clarion, I just assumed it was a car radio. Sorry about that. What's strange is that it has 128MB RAM, but only 44mb is usable? Any chance that your original version of iGO is still running when you try to start the new versions?

    I also found that it's 480x272, so the 405512 version that I supplied will definitely not work (it only has a data.zip for 800x480 resolution - since I thought it was a car radio, I also assumed it was 800x480).

    I just can't figure out where all of your RAM is going, unless you have the original version of iGo still running when you try to start the newer versions (it can be "minimized" in the background, for example). That would explain why the other versions won't run (I think iGo checks to make sure it's not already running) - and would explain why you only have 44mb free (out of 128mb).

    Just throwing some things out there... Since your device has 128mb of RAM, you should definitely be able to run any version of iGo Primo.

    Are you installing these new versions onto completely separate SD cards or just replacing certain files on your existing SD card when you try to run them?

    Another thing that would be helpful is if you could post your original sys.txt file - it may shed some light onto some things (like if it's using a "device=" statement, which uses settings from a file in the data.zip file, memory settings, folder settings, etc).

    Sent from my HP SlateBook 10 x2 PC using Tapatalk
    Last edited by jtrosky; 6th July 2016 at 15:15.

  9. #18
    Junior Member
    Join Date
    Jul 2016
    Location
    Belgium
    Posts
    6
    Rep Power
    0

    Default

    The site which you were probably looking at indeed mentions 128MB, but I checked and it is 64mb out of which 60 are usable, and some are gone for os, so indeed you seem to be right I am running a version that allows a smaller memory size. Guess I will stick with that one, thanks for the help!

  10. #19
    Super Member
    Join Date
    Nov 2014
    Location
    USA
    Age
    43
    Posts
    197
    Rep Power
    48

    Default

    Actually, the crash file also says that it has 128mb of RAM (but only 44mb "usable"). I'm not an expert on exactly what those values mean in the crash file, but it sure sounds like it sees 128mb of RAM - when a crash file in generated on my unit, it also says "MaxMemory 129MB", so I'm assuming that is reporting how much RAM the device has. But what's different on mine is that my "TotalUseableMemory" value is much higher (70mb+)....

    Can anyone confirm what those RAM values really mean in the crash file (MaxMemory and TotalUseableMemory)?

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  11. #20
    Junior Member
    Join Date
    Jul 2016
    Location
    Belgium
    Posts
    6
    Rep Power
    0

    Default

    I entered control panel of windows ce and that shows 62462KB, which is the correct value I assume
    and this is indeed set in my current sys.txt, though I did try to run the provided program with my sys.txt with no success
    [debug]
    cache=524288
    experimental_features=1
    max_memory=61865984
    Last edited by girtsn; 7th July 2016 at 18:25.

 

 
Page 2 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.