Switch to full style
Post a reply

Sat Dec 08, 2012 1:33 pm

jcocker wrote:See full list of files and folders under iGO 8.3.5.183522_16Mar2011 attached.

Also, I tried to delete the two files you mentioned above (and the save folder). As soon as I get to the screen asking me to choose between "Simple" and "Advanced" mode, regardless of the one I choose, the device boots, so I cannot go past it... All is well again (at least past the mode selection screen) once I return the two files.


I may have confused you somewhat - for that, I apologize. In the GFX folder are five files, not two files that have to be deleted. 1. Car.mdl, 2. Car_ghost.mdl, 3. Car_grey.mdl, 4. Car_night.mdl 5. Civic_blue.tex.

I wanted to see what your content folder looked like. Whether you were putting the custom POIs in the right place. Put .KML file[s] in ... content\userdata\poi. Create the folder if you don't have it already on your SD card.

Sat Dec 08, 2012 3:14 pm

chas521 wrote:I may have confused you somewhat - for that, I apologize. In the GFX folder are five files, not two files that have to be deleted. 1. Car.mdl, 2. Car_ghost.mdl, 3. Car_grey.mdl, 4. Car_night.mdl 5. Civic_blue.tex.

I wanted to see what your content folder looked like. Whether you were putting the custom POIs in the right place. Put .KML file[s] in ... content\userdata\poi. Create the folder if you don't have it already on your SD card.


Right, so I now removed all 5 files in the GFX folder, and have my beloved blue arrow back!

I am very familiar with the folder structure of igo (I have been using it for many years now), and all my pois are in the ... content\userdata\poi folder in kml form + a bmp file per group. All is working fine with v8.3.5.193799, but not with "your" version. I even tried to delete the userdata folder (and the save folder, just in case), and I still get the error message mentioned in reply #13 above...

Sat Dec 08, 2012 5:36 pm

jcocker wrote:Right, so I now removed all 5 files in the GFX folder, and have my beloved blue arrow back!

I am very familiar with the folder structure of igo (I have been using it for many years now), and all my pois are in the ... content\userdata\poi folder in kml form + a bmp file per group. All is working fine with v8.3.5.193799, but not with "your" version. I even tried to delete the userdata folder (and the save folder, just in case), and I still get the error message mentioned in reply #13 above...


Glad to hear that you got the arrow back. If for some reason you can't get my program to work correctly, then I would recommend that you again start using 193799 and maybe Fatboyfun can guide you with it.

Sat Dec 08, 2012 6:34 pm

chas521 wrote:Glad to hear that you got the arrow back. If for some reason you can't get my program to work correctly, then I would recommend that you again start using 193799 and maybe Fatboyfun can guide you with it.


Thanks again. There is clearly a problem here. I've just tried the following:
- deleted ALL my POIs
- I already had dem, system pois, tts, LANGS, ETC ALL REMOVED
- Removed skin

I then started a route of around 400 miles, and simulated it on the device using the "Route->Simulate". The program crashed after around 100 miles with "Low on Resources"...

Pulling my hair at the moment... ;-(

Sat Dec 08, 2012 9:06 pm

jcocker wrote:Thanks again. There is clearly a problem here. I've just tried the following:
- deleted ALL my POIs
- I already had dem, system pois, tts, LANGS, ETC ALL REMOVED
- Removed skin

I then started a route of around 400 miles, and simulated it on the device using the "Route->Simulate". The program crashed after around 100 miles with "Low on Resources"...

Pulling my hair at the moment... ;-(


Which program are you talking about? As you have already figured there is a memory or conflict problem. You have plenty of RAM so you should safely be able to include everything. My only thought right now is that another program [in the background?] is taking away necessary memory. Sorry if asked and answered before, but when did this problem start? Did it ever work normally?

Sat Dec 08, 2012 10:59 pm

Let's see what we're working with, Give this tool a run and copy/paste the created text file here...

WINCE DEVICE INFORMATION V2.
http://www.navitotal.com/showthread.php?8930-Mortscript-applications-repository&p=44922#post44922

Sat Dec 08, 2012 11:04 pm

chas521 wrote:Which program are you talking about? As you have already figured there is a memory or conflict problem. You have plenty of RAM so you should safely be able to include everything. My only thought right now is that another program [in the background?] is taking away necessary memory. Sorry if asked and answered before, but when did this problem start? Did it ever work normally?


Sorry, should have explain more clearly...

GPS was bought 2-3 months ago. It came with iGo v8.3.2 installed that I proceeded to replace with v8.3.5.193799 that I had used on an old GPS.

I had used it on a daily basis for short trips and everything worked fine. I then had to make a 600 mile round trip, and every 100-200 miles got the low on resources error. I then proceeded to remove all the unnecesarries (dem, buildings, etc) thinking that this would resolve it. But it did not.

When I check for available RAM, I seem to have just over 90MB free out of the 128MB total.

I don't think that there is anything running in the background.

Sat Dec 08, 2012 11:12 pm

Fatboyfun wrote:Let's see what we're working with, Give this tool a run and copy/paste the created text file here...

WINCE DEVICE INFORMATION V2.
http://www.navitotal.com/showthread.php?8930-Mortscript-applications-repository&p=44922#post44922


Thanks a lot - here it is:

WinCE Device Information V2, 2011 Fatboyfun http://www.navitotal.com

DEVICE INFORMATION.
Screen resolution 800x480
Windows CE 6
Free / Total RAM available 94212 KB / 112388KB

AVAILABLE DRIVES GREATER THAN 128MB. (Free / Total)
NOTE: Mortscript only reads up to 2047MB
\residentflash (716MB/2047MB)
\SDMMC (2047MB/2047MB)

GPS INFORMATION.
Port=1
Baudrate=4800

Visit http://www.navitotal.com for all your GPS needs!

Sat Dec 08, 2012 11:20 pm

Memory looks good to me. Does your sys.txt have any entries that conflict? Could you post it so we can take a look?

Sat Dec 08, 2012 11:31 pm

chas521 wrote:Memory looks good to me. Does your sys.txt have any entries that conflict? Could you post it so we can take a look?


See my sys.txt attached to the first message in this thread.

Sun Dec 09, 2012 1:04 pm

jcocker wrote:See my sys.txt attached to the first message in this thread.


Thanks for that. I should have realized that you knew enough to include it right away. I don't see anything that might cause a problem. Only thing [I don't think it's a problem though] is the space between ; and the written line when you are remming out the identification information of the entries. Actually, you are the first person ever to bring up this problem of the program crashing during a longer trip. This is going to require more thought. If [color="#FF0000"]anyone[/color] has the definitive answer please chime in.

EDIT: Sorry but have to wonder if it isn't some sort of hardware problem. Have you tried a new SD card? Or formatted the old one [FAT32] and reinstalled the software?

Sun Dec 09, 2012 1:40 pm

Can you take a photo of the error message...

Wince error messages are not the most helpful of messages.

Sun Dec 09, 2012 3:14 pm

Fatboyfun wrote:Can you take a photo of the error message...

Wince error messages are not the most helpful of messages.


See photo attached.

Sun Dec 09, 2012 5:37 pm

chas521 wrote:Thanks for that. I should have realized that you knew enough to include it right away. I don't see anything that might cause a problem. Only thing [I don't think it's a problem though] is the space between ; and the written line when you are remming out the identification information of the entries. Actually, you are the first person ever to bring up this problem of the program crashing during a longer trip. This is going to require more thought. If [color="#FF0000"]anyone[/color] has the definitive answer please chime in.

EDIT: Sorry but have to wonder if it isn't some sort of hardware problem. Have you tried a new SD card? Or formatted the old one [FAT32] and reinstalled the software?


That was my thought as well - i.e. SD card, as I couldn't think of anything else...

I always run the program from internal memory, but just to be sure I took the SD card out. Still crashing... ;-(

Mon Dec 10, 2012 4:36 am

jcocker wrote:That was my thought as well - i.e. SD card, as I couldn't think of anything else...

I always run the program from internal memory, but just to be sure I took the SD card out. Still crashing... ;-(


Just guessing now. I wonder if you got a bad download that got broken? What about if you did another download and installed fresh? It may not be the program but the maps download themselves or other content.
Post a reply