Switch to full style
Post a reply

Re: No need to unlock Navman S-series (S30 example)

Thu Apr 16, 2015 2:08 pm

The device is limited to 32 MB and igo eats already a big part of that, also in minimal setup. Adding anything ads up to that setup and memory use.
As we see it, you have 2 choices
1. limit the speedcam file to the area you drive in
2. do not use any speedcam file, in fact, do not load any file you do not really need.


how-to-f128/how-solve-memory-issues-t915.html

Re: No need to unlock Navman S-series (S30 example)

Thu Apr 16, 2015 7:02 pm

If you manually kill AppStartupSec.exe you will reclaim some memory.

This depends on how it was unlocked in the first place.

Re: No need to unlock Navman S-series (S30 example)

Mon Apr 20, 2015 7:51 pm

And how do you explain that i've puted 7 or 8 contrys with all the additional files (fpa,fsp,fda) and the igo loads them but when i put a .txt file that is nearly 60 kb it blocks always when it's loading "inizializing warning data". ?

Re: No need to unlock Navman S-series (S30 example)

Mon Apr 20, 2015 8:38 pm

ionutzdan02 wrote:And how do you explain that i've puted 7 or 8 contrys with all the additional files (fpa,fsp,fda) and the igo loads them but when i put a .txt file that is nearly 60 kb it blocks always when it's loading "inizializing warning data". ?


Very simple. You're trying to load too much content when the program is starting. Start reducing.
Post a reply