Switch to full style
Topic locked

IGO PRIMO , NO SYS.TXT file ?

Wed Jan 19, 2011 10:14 pm

My car sat nav runs IGO PRIMO, however When I look at the SD card on my pc I can't see a sys.txt file anywhere. IS there a base file someone can point me to ? My device has problems being recognised and I think it is due to no sys.txt file. thx

Wed Jan 19, 2011 10:24 pm

:confused: problems being recognized? Can you be a bit more specific? And what car sat nav? Build in or not? Brand? This information could prove important for setting up a sys.txt. A perfect sys.txt (IF that exists) depends on the device and on the problems you experience.

If you want sys.txt lines, well there is a whole bunch of them and no documentation at all to apply them correctly. (http://www.navitotal.com/showthread.php?2624-Primo-Sys.txt-lines)

Wed Jan 19, 2011 10:36 pm

I think its a Chinese Head Unit for my Ford Kuga, used on most NEW fords.

The NAV works, but occasionally comes up with a WINCE box mentioning the resolution or device is not supported. The screen is a 7" DVD screen, not sure of resolution or how to find out. I just cant find a sys.txt file anywhere, but the system sort of works...

Just wondered if there was a generic base line file. I can share any of the file data here if that helps...

This is the device...

>http://car-vision.co.uk/ford-navi-dvd/3285-ford-kuga-sony-replacement-head-unit-with-built-in-dvd--gps--bt.html<

Wed Jan 19, 2011 10:41 pm

Forgot to ask: what Primo and where did you get it?
Also what does the screen look like? Filled? Primo smaller or bigger than the screen?

Wed Jan 19, 2011 10:53 pm

Got the SD Card from the guy who installed the Head Unit, it is an OEM unit. I have IGO8 which works ok, and PRIMO which has the start up issue. I think the resolution is 400x240 from what I can see. The Primo screens when they are up all look great, but my thoughts are that maybe there is no config for the correct resolution or device i.e. the device is not recognised. I will make a note of the error, but I just say NO (to select another device) close the next box and hey presto it boots uyp into Primo fully working....

Thu Jan 20, 2011 7:58 am

400*240 isn't a official Primo release, 400*272 is.
Have you tried deleting the save folder? When yes, try this release http://www.navitotal.com/showthread.php?1728-Working-Primo-from-my-device.
Use a clean sd and when a save folder is present, delete it.

Thu Jan 20, 2011 3:49 pm

And that is what I don't understand. Your Primo is working OK for the most part but yet you have a nagging thought that it could work better. Unless it is really, REALLY bothering you "If it ain't broke don't fix it." That is MY opinion.

Thu Jan 20, 2011 9:55 pm

The error I get when it starts up is "GAPI Device MisMatch" it then gives me a drop down of hundreds of devices but not knowing what mine is I dont know if I should enter.

How do I stop this error comign up, does anyone know what causes this ? thx

Thu Jan 20, 2011 10:15 pm

GAPI is a display driver for WinCE based devices, Regarding your sys.txt problem, Have you turned off "Hide known file extensions" on your pc?

Thu Jan 20, 2011 10:16 pm

This error is new. You are the first to report it. Try my advise in #6 and see what happens.
Or follow this manual: http://www.navitotal.com/showthread.php?3521-Guide-to-install-iGO-Primo-on-devices-with-Windows-CE-core.

Thu Jan 20, 2011 10:42 pm

Yep turned off, no difference....

Thu Jan 20, 2011 10:53 pm

Just trued the download from here and I can confirm my resolution must be 800x480 as in the data.zip file I can see that there and the download from here seemed very low res. Interestingly enough I didn't get the GAPI error, but I could not get a GPS lock, maybe the setting in the sys.txt are not correct for my device.

Dont expect you to help me debug, but would be keen to understand the different GPS settings, as I feel I am getting somewhere. The version I have that comes up wit hthe error appears hi res when it works, so somewhere between these two versions is a solution

Sun Jan 23, 2011 1:31 pm

Sorry, I lost this thread out of my eye.
Is your problem solved in the mean time? If not, what is the situation?
Topic locked