Switch to full style
Post a reply

Tue Dec 17, 2013 9:07 pm

for igo 8.3.4.117940.

the Portuguese language works only with igo8.

primo always out of memory

------------------ Crash Log Begin -------------------


Current System time: "2013-12-17 19:52:49"
Build version: 9.6.13.267029
Build configuration: Product--ARCHFAM
OS version: 6.0

Uptime: 0 h 0 m 6 sec 0 msec

Memory Stats:

FreeMemory: 128 MB, 224 KB, 0 B
TotalUseableMemory: 129 MB, 0 KB, 0 B
MaxMemory: 129 MB, 0 KB, 0 B
ReservedMemory: 0 MB, 0 KB, 0 B
LastRequestSize: 1623 MB, 136 KB, 115 B
ActualCacheSize: 0 MB, 0 KB, 0 B
GarbageSize: 0 MB, 0 KB, 0 B


WinCE CallStack snapshot (function names unknown - map file \SDMMC\primo 2\iGO.map not found):

0x40029518 (A)
0x008ccd14 (A)
0x008cc2ec (A)
0x008cc49c (A)
0x00021570 (A)
0x00021b2c (A)
0x00022ab0 (A)
0x001b137c (A)
0x001b3ca0 (A)
0x001b53c4 (A)
0x008d8cc4 (A)
0x00429350 (A)
0x000611d4 (A)
0x00061380 (A)
0x008f6d14 (A)
0x0005ece8 (A)
0x00429350 (A)
0x0009d048 (A)
0x0009d0c0 (A)
0x0005ca8c (A)
0x0005c794 (A)
0x0005efb8 (A)
0x0005ffe8 (A)
0x0028c3d8 (A)
0x0028c5ec (A)
0x0009cd18 (A)


Error message:

Out of memory.
Requested: 1701978227
Cache: 0


Global status:

bInFocus: 0
bMouseDown: 0
bInLogic: 0
bInRender: 0
CurrentState[128]:
GPS Pos: (0.000000,0.000000)
Camera: pos:(0.000000,0.000000) rot:0 persp:0 zoom:0.000000 eng=0)

Thu Dec 19, 2013 12:08 am

I finally mod my "magic" portuguese language file, now nav n go igo 8.3.4.117940 are in french, in 800 x 480 with France_TomTom_2013.06_131017 map!
All works great thanks for your help.

Now What are differences between igo and primo?

Thu Dec 19, 2013 3:31 pm

Primo is newer (newer voices than iGO), needs more memory and system resources, is "out of the box" more elegant, ...

Fri Dec 20, 2013 4:32 am

I dl another version "romania version" this time, of primo 2.4.13.267029 and Primo finally work really fine!

Why other don't work? i don't know
thank you so much for your time.

Fri Dec 20, 2013 6:14 am

I don't know either. Something completely wrong with a file. One faulty bit may be enough. Or/and it could be that the way you installed or corrected/renewed the install was the issue. Or/and what was left - and shouldn't be - from a previous install. Or ...
But we can keep guessing, while the most important is that it works!

Enjoy!!
Post a reply