Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 49
  1. #21
    Member
    Join Date
    Jan 2016
    Location
    Nashville, TN
    Posts
    21
    Rep Power
    1

    Default

    Well, no joy as my Chinese GPS says there is no '800X480' skin available. There's probably another parameter to set somewhere but I can't seem to find it.

  2.    Advertissements


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

    Default

    Very strange - worked fine on my 800x480 head unit. You may have to delete the "save" folder - not sure why you would, but it's worth a shot.

    So you get that message after you select the skin and then restart Primo (as it's starting up)?

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  4. #23
    Master G-ulash's Avatar
    Join Date
    May 2014
    Location
    Yellow Brick Road
    Posts
    268
    Rep Power
    6

    Default

    Better to rename the save folder to save.old. That way the old settings are recovered easy without going over all again.

  5. #24
    Member
    Join Date
    Jan 2016
    Location
    Nashville, TN
    Posts
    21
    Rep Power
    1

    Default

    I could not even get Primo up far enough to pick a skin - it gives me the error message right as it tries to start. Let me make sure I'm 'installing' correctly. I unzip your download which creates the content folders, etc. I create a PRIMO folder on a 'fresh' microsd card then I copy all of your stuff to that folder. I then copy the MAP, VOICE, and LANG folders I have into the CONTENT folder and the Primo.exe to the card. Am I missing anything?

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

    Default

    Hmmm - that doesn't make any sense since this skin shouldn't have anything to do with Primo startup since it's not the active skin yet.

    You aren't copying the sys.txt file from the skin over your sys.txt are you? Make sure that you use your normal sys.txt and not the one in the skin archive.

    Personally, I wouldn't copy of the save folder either (I'd delete the save folder on your SD card as well so that you can start fresh).

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  7. #26
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    640

    Default

    Actually a bad skin will cause start up to failed. It's best just to temporarily remove/rename the skin directory and start with default skin. You also can rename the save folder just in case you need it later. Then you can copy over the new skin; restart Primo and see if it let you select it inside Primo.

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

    Default

    But this is a new skin - he's not replacing the skin that he's currently running with a new version. Basically, he's just installing a brand new skin. So there is no reason why he shouldn't be able to boot Primo into his existing skin?

    I suspect it might be because he replaced his sys.txt with the version that is included in the skin archive (which includes the skin itself as well as other files). It also includes the save folder which you wouldn't want to use since it's a save folder from the new skin, which he isn't running yet.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  9. #28
    Important User

    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Farside of the Sun
    Posts
    2,646
    Rep Power
    640

    Default

    If he's trying to use the "DECENT" skin, then no sys.txt nor save directory in .rar (I'd cheched before replying) So unless he's manually copying it over the only way it would crash is that he already selected the skin; but we'll see his replied later. I wonder if he got a crash.txt file.

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

    Default

    No, he's trying to use the modified Moto skin that someone converted to 800x480 for him and posted a few posts back (originally it was only for lower resolutions). The Moto skin archive has both a sys.txt file and a save folder included in it (as well as a branding.zip).

    Worst case, he could enable logging with the log_1 [debug] entry - I'm sure that would help diagnose the problem as well.

    Sent from my HP SlateBook 10 x2 PC using Tapatalk

  11. #30
    Member
    Join Date
    Jan 2016
    Location
    Nashville, TN
    Posts
    21
    Rep Power
    1

    Default

    This is the same issue if I try to use the 'original' MC 1 9 skin - it complains about no 800x480 skin available (PRIMO 2.4 based). There are no parameters in the sys.txt specifying resolution. It appears that PRIMO gets the resolution from the device (if not specified in the sys.txt) and if it can't 'find' a skin (either additional or new) with the proper resolution, it quits. The version of 'standard' PRIMO 2.4 I have works fine (it has a 800X480 standard skin) so I'm wondering what I'm missing. Would I be better to create the sd with the standard PRIMO 2.4 then copy the 800X480 MC stuff you created into it? Note the way I did it in post 24 which may be the problem. Also, if I wanted to do the mods you suggested, I presume that I 'unzip' those zip files that contain the data to be changed, then zip them back (haven't done that yet).

 

 
Page 3 of 5 FirstFirst 12345 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.