igo sys.txt

[Guest j0hnd0e82]

Can someone explain to me what the sys.txt really does?

i installed igo 8.3.2 to my omnia and everything seems to work fine as far as i can tell.

when i look at my sys.txt file in program files, its pretty bare, it doesnt contain that much information other than a couple of fields like program location etc. So my question is how important is this file? and is it neccesary to edit this file appropriately for certain things to work? like for instance speedcam, i have it enabled in the settings menu but it does not show up in the sys.txt which i thought it should be there? does this mean it will not work if the commands are not in the sys.txt file?

somewhat confusing to me, this the igo app rely 100% on this file its configuration?

any help is appreciated.

[Guest necosino]

The sys.txt file just shows the app where to locate the rest of the files, without it, the .exe wouldn't know where to find the maps, voices, etc. Speedcams directories aren't legal in the US/CAN, so they won't "work" if you live here. Hope that answers your question :excl:

[Guest j0hnd0e82]

ive seen others post their sys.txt with far more entries than just app location settings. It seems like its used to customize in detail how the app runs?

speedcams areant important to me, i was just using it as an example. I just assumed that any settings change in the settings menu of the application would reflect on the sys.txt since it seems that you can configure that file to run a detailed configuration of the application.

the application has to be saving the settings somewhere. So wouldnt it makes sense that if i make a change in the settings it should make the change in the sys.txt? unless theres another configuration file?

Edited April 14, 2009 by j0hnd0e82

[Guest Neil5459]

sys.txt seems to just save the parameters relating to the function of the program itself, rather than the facilities within the software. It is totally programmable so you could have entries for appearance, loading of contacts into POIs etc plus the basic file locations. Some examples can extend to a full page of text, though most users need very small sys.txt files.

For items such as speedcams, there are other ini files within the program structure, though custom speedcam warnings will appear in sys.txt.

Speedcams only become selectable within Settings/Warnings if you have a valid current GPS fix (I suppose on the basis that a speedcam database isn't much use without a GPS locator!); as long as the speedcam data is in the relevant Content/Speedcam folder it should be available to you once you have a fix.

[Guest j0hnd0e82]

sys.txt seems to just save the parameters relating to the function of the program itself, rather than the facilities within the software. It is totally programmable so you could have entries for appearance, loading of contacts into POIs etc plus the basic file locations. Some examples can extend to a full page of text, though most users need very small sys.txt files.

For items such as speedcams, there are other ini files within the program structure, though custom speedcam warnings will appear in sys.txt.

Speedcams only become selectable within Settings/Warnings if you have a valid current GPS fix (I suppose on the basis that a speedcam database isn't much use without a GPS locator!); as long as the speedcam data is in the relevant Content/Speedcam folder it should be available to you once you have a fix.

Thanks for the detailed explanation Neil, I now understand it completely

[Guest ahcor1991]

Is it possible to change the storage card for my storage?

[Guest necosino]

Yeah, if that's where all the maps and info are.

[Guest Neil5459]

Thanks for the detailed explanation Neil, I now understand it completely

HeHe- I still don't fully understand the complexity of sys.txt, though I do run a fully standard, off the shelf R3 version supplied as a review sample by Nav'N'Go, so I don't currently need to modify it.

My previous iGO8 R1 review copy, and my own paid-for iGO2006 needed a few more sys.txt tweaks!