The error dialogue box in the image is neither an iGO or a wince error message, it could be part of the devices shell, or some kind of memory monitor/task manager which is running.

I would use resinfo or similar to see what processes are running, and try stopping anything that looks suspicious, this might crash the device if you stop a system process, but you can reboot to recover.

Fatboyfun wrote:The error dialogue box in the image is neither an iGO or a wince error message, it could be part of the devices shell, or some kind of memory monitor/task manager which is running.

I would use resinfo or similar to see what processes are running, and try stopping anything that looks suspicious, this might crash the device if you stop a system process, but you can reboot to recover.

I think you are on to something... Haven't thought in that direction, but I am now sure that the error message is triggered by the apps luncher/shell. I will have to look a bit closer at the device to see what is going on there, and will report back.

jcocker wrote:I think you are on to something... Haven't thought in that direction, but I am now sure that the error message is triggered by the apps luncher/shell. I will have to look a bit closer at the device to see what is going on there, and will report back.

I think you were right! I exited the shell, and run iGo 8.3.5 directly from Win CE. It managed an 800+ mile trip without a problem! Clearly the problem is with (memory management within the) shell.

Problem I have now is how to set the device up so that it does not use this shell (or at least allows me to try the reduce the shell's RAM footprint.

Looking at the registry of the device it seems to use the YFloader6 menu. However, I cannot seem to find where the settings are... I allow WinCE explorer to show hidden files, etc, but I still can't see it...

I wouldn't touch the registry, I would use a script to kill the shell, start igo and wait, then restart the shell when igo has closed.

Use Resinfo to list the processes...

http://www.navitotal.com/showthread.php?3734-ResInfo-A-useful-tool-for-system-information

Before doing anything major I decided to give the iGo software a last chance...

I put iGO8 8.3.4.142975 on the device, and everything works fine! It even includes dem and buildings...

It appears that the problem could be to do with v8.3.5. I've now tried two versions 27/05 and 16/03, and both failed.

Any idea what I am standing to miss if I stay with v8.3.4 - could spot any difference between than and 8.3.5.

jcocker wrote:Before doing anything major I decided to give the iGo software a last chance...

I put iGO8 8.3.4.142975 on the device, and everything works fine! It even includes dem and buildings...

It appears that the problem could be to do with v8.3.5. I've now tried two versions 27/05 and 16/03, and both failed.

Any idea what I am standing to miss if I stay with v8.3.4 - could spot any difference between than and 8.3.5.

That's VERY strange. If 8.3.4 works then 8.3.5 should also work. However, go with what works. There won't be much of a difference.