Wed Dec 12, 2012 1:52 pm
Ok when I'm home later I'll sort something out, 64mb refers to the sd card size.
Wed Dec 12, 2012 2:36 pm
okay thanks..:D No I also have a 1GB SD card from my camera for testing, but rather not give it to him ;)
Wed Dec 12, 2012 5:24 pm
I took a peep over there.
The only error message that makes any sense is this one :[INDENT=2]Error message:
User interface resolution [480x272] is not supported or compatible skin can not be found.
Exiting application.
From the other crashes there is no conclusion that can be made.
Except this one : since the crash.txt is in the root of an install, unless it's deleted, the same crash.txt is used over and over again. Like yours. It clearly shows someone (probably you) made a mess of different builds one over another.
How can someone up here correct what you did - or should I say messed up ? - down there. We didn't see what you did and by the look of your crash.txt, you did a lot but did not tell us all. Did you only replace exe files? Or data.zip files as well? Other files perhaps? That could have a big influence on the (non) behavior of iGO. Mixing too many files from too many different builds mixed together is a sure way to failure. Mixing just two incompatible builds is sometimes enough.
Nah, who cares? Too late now to correct such mess.
My advice? Start again from scratch and stick to one build. When it doesn't work, we have a real chance to help. And be precise in what you see happening as an error. What? When? What message? What did you do exactly? And by exactly, I mean exactly!
The only error message that makes any sense is this one :[INDENT=2]Error message:
User interface resolution [480x272] is not supported or compatible skin can not be found.
Exiting application.
From the other crashes there is no conclusion that can be made.
Except this one : since the crash.txt is in the root of an install, unless it's deleted, the same crash.txt is used over and over again. Like yours. It clearly shows someone (probably you) made a mess of different builds one over another.
How can someone up here correct what you did - or should I say messed up ? - down there. We didn't see what you did and by the look of your crash.txt, you did a lot but did not tell us all. Did you only replace exe files? Or data.zip files as well? Other files perhaps? That could have a big influence on the (non) behavior of iGO. Mixing too many files from too many different builds mixed together is a sure way to failure. Mixing just two incompatible builds is sometimes enough.
Nah, who cares? Too late now to correct such mess.
My advice? Start again from scratch and stick to one build. When it doesn't work, we have a real chance to help. And be precise in what you see happening as an error. What? When? What message? What did you do exactly? And by exactly, I mean exactly!
Wed Dec 12, 2012 9:33 pm
[Please Register or Login to download file]
(No password)
Clear everything off the SD card
Copy the iGO8 folder as it is from the above archive to the SD card
Do not add anything including content!
Run iGO8.exe
There are two sys.txt's, one has resolution entries and the other doesn't, this version of iGO 8 does not need them normally.
The iGO8Uncompressed.exe is the original uncompressed executable.
Even though there are no maps, the basemap will allow iGO to start with no content, This is useful to diagnose a faulty install or bad maps/license
If it starts, add maps and other content, ONE FILE AT A TIME and start iGO in-between each file, when it fails to load, you will have identified the problem.
(No password)
Clear everything off the SD card
Copy the iGO8 folder as it is from the above archive to the SD card
Do not add anything including content!
Run iGO8.exe
There are two sys.txt's, one has resolution entries and the other doesn't, this version of iGO 8 does not need them normally.
The iGO8Uncompressed.exe is the original uncompressed executable.
Even though there are no maps, the basemap will allow iGO to start with no content, This is useful to diagnose a faulty install or bad maps/license
If it starts, add maps and other content, ONE FILE AT A TIME and start iGO in-between each file, when it fails to load, you will have identified the problem.
Wed Dec 12, 2012 11:50 pm
nabi wrote:I took a peep over there.
The only error message that makes any sense is this one :[INDENT=2]Error message:
User interface resolution [480x272] is not supported or compatible skin can not be found.
Exiting application.
From the other crashes there is no conclusion that can be made.
Except this one : since the crash.txt is in the root of an install, unless it's deleted, the same crash.txt is used over and over again. Like yours. It clearly shows someone (probably you) made a mess of different builds one over another.
How can someone up here correct what you did - or should I say messed up ? - down there. We didn't see what you did and by the look of your crash.txt, you did a lot but did not tell us all. Did you only replace exe files? Or data.zip files as well? Other files perhaps? That could have a big influence on the (non) behavior of iGO. Mixing too many files from too many different builds mixed together is a sure way to failure. Mixing just two incompatible builds is sometimes enough.
Nah, who cares? Too late now to correct such mess.
My advice? Start again from scratch and stick to one build. When it doesn't work, we have a real chance to help. And be precise in what you see happening as an error. What? When? What message? What did you do exactly? And by exactly, I mean exactly!
What? What? What did I do? stop assuming so many things man..all I did was after unzipping I just copied the igo folder from my hard disk to the sd card, each time I copied it I cleared the sd card of anything else including previous igo folders.. only thing I edited would be the sys.txt file as you sugggested and compressing igo8.exe with upxshell as fatboy suggested, thats all, I didn't do anything ele. I think the crash txt creates new entries everytime it failes to launch. look I dont know, all I did was follow as I was told. I just want to get my friends gps working..
Wed Dec 12, 2012 11:55 pm
Fatboyfun wrote:[Please Register or Login to download file]
(No password)
Clear everything off the SD card
Copy the iGO8 folder as it is from the above archive to the SD card
Do not add anything including content!
Run iGO8.exe
There are two sys.txt's, one has resolution entries and the other doesn't, this version of iGO 8 does not need them normally.
The iGO8Uncompressed.exe is the original uncompressed executable.
Even though there are no maps, the basemap will allow iGO to start with no content, This is useful to diagnose a faulty install or bad maps/license
If it starts, add maps and other content, ONE FILE AT A TIME and start iGO in-between each file, when it fails to load, you will have identified the problem.
bad news fatboy, I downloaded it , cleared the sd card, copied the extracted igo folder to the sd card, I didn't add anything, simply reset the device and then launched the igo8.exe and same thing, INTI API on right bottom corner, 1 sec display of igo8 starting screen then crash.
Thu Dec 13, 2012 4:36 am
The reason I said it's probably not a license thing [could be wrong I guess] is that he tried my program [which has the correct license] and that didn't work correctly.
Thu Dec 13, 2012 8:07 am
Does an error dialogue box come up?
Thu Dec 13, 2012 10:27 am
no man, no dialogue boxes ... :(
Thu Dec 13, 2012 11:29 am
At this point I don't know, I will look into it and get back to you...
Thu Dec 13, 2012 1:51 pm
Navcan wrote:What? What? What did I do? stop assuming so many things man..all I did was after unzipping I just copied the igo folder from my hard disk to the sd card, each time I copied it I cleared the sd card of anything else including previous igo folders.. only thing I edited would be the sys.txt file as you sugggested and compressing igo8.exe with upxshell as fatboy suggested, thats all, I didn't do anything ele. I think the crash txt creates new entries everytime it failes to launch. look I dont know, all I did was follow as I was told. I just want to get my friends gps working..
Then please explain to me why you wrote you used the iGO provided by us while the crash.txt that is in the igo folder you cleared and reinstalled, involves at least 4 different builds, including a Primo:
Current System time: "2007-04-01 16:00:28"
Build version: 8.5.9.142948
Current System time: "2007-04-01 16:03:23"
Build version: 8.5.9.142948
Current System time: "2007-04-01 16:00:44"
Build: 8.3.2.96054 Built @ Jun 25 2009 - 13:56:56
Current System time: "2007-04-01 16:01:53"
Build: 8.3.2.96054 Built @ Jun 25 2009 - 13:56:56
Current System time: "2007-04-01 16:00:58"
Build: 8.3.4.142975 Built @ May 11 2010 - 13:08:17
Current System time: "2007-04-01 16:00:50"
Build: 8.3.4.142975 Built @ May 11 2010 - 13:08:17
Current System time: "2007-04-01 16:01:36"
Build: 8.3.4.142975 Built @ May 11 2010 - 13:08:17
Current System time: "2007-04-01 16:01:04"
Build: 8.3.4.142975 Built @ May 11 2010 - 13:08:17
Current System time: "2007-04-01 16:01:00"
Build: 8.3.4.142975 Built @ May 11 2010 - 13:08:17
Current System time: "2007-04-01 16:00:53"
Build: 8.3.4.142975 Built @ May 11 2010 - 13:08:17
Current System time: "2007-04-01 16:01:00"
Build: 8.3.5.183522 Built @ Mar 16 2011 - 11:59:34
And this is just a part of the builds list. I did not go down to the very end.
The sequence of the build list in the crash.txt is certainly the least logical (by the sequence of the build number).
When you cleared the sd, and started over, you cleared the crash.txt as well and started fresh. But the crash.txt proves different.
And more. The crashes from top to bottom in your crash.txt all occur on the same date and around the same time, 1 minute after 4PM. Meaning the device is likely the same device every time. I think that is at least very odd.
The install is a mess. No doubt. And you got it from one of us? Hmmm.
Thu Dec 13, 2012 7:03 pm
Look I told you what I did, I deleted the igo8 folder before copying the new one, if the crash txt shows such things as different builds then maybe it created new entries every time? but then again it should have been deleted with the folder. I don't know why..thats very odd, I've only done what I said.
Thu Dec 13, 2012 9:55 pm
Please understand where we are coming from. It's as frustrating to us as it is to you. No one here is taking personal shots at you. Your device is not in front of us and it's not an easy thing at times to give advice and support because of this. You're not the first person who has had some difficulty and although it hasn't been solved yet just know that no one is giving up on you! Our advice so far has been the advice that has worked in the past. Please be patient and bear with us. Thanks.
We're going to support you as if this is post #1 - starting all over again. If all these questions have been answered before, sorry, but make believe they haven't. OK?
Now, what are you trying to do? What is the name of your device and can you link us to its specifications?
Remember, we're only trying to help you. :D
We're going to support you as if this is post #1 - starting all over again. If all these questions have been answered before, sorry, but make believe they haven't. OK?
Now, what are you trying to do? What is the name of your device and can you link us to its specifications?
Remember, we're only trying to help you. :D
Fri Dec 14, 2012 3:02 am
Fri Dec 14, 2012 9:09 am
by the way, if iGO won't work for some reason I am open to other good GPS softwares aswell as long as I get some latest maps and the interface is good like igo or atleast navman...tomtom or something you know..