There are devices with low internal memory , in these cases, the path is divided into sections up to the arrival
Printable View
There are devices with low internal memory , in these cases, the path is divided into sections up to the arrival
I agree ;)Quote:
Originally Posted by Ipmark [Only registered and activated users can see links. Click Here To Register...]
@ Guys,please....expect to know the problem of barca5928. Do not you think? ;))
Bye,bye
I'm sorry the problem is in germany , he have a straight line .
Ok, it's a good start...but......where ? a straight line is too ..........how can I say.. generical ...that's it.Quote:
Originally Posted by barca5928 [Only registered and activated users can see links. Click Here To Register...]
Best we stop assuming now. As Roger & Ipmark said he needs to be more specific and if he wants he can post detailed info. But i suspect he has his answer and we won't hear any more, and that is probably simply his limited memory unit ran out of puff in the middle of Germany because the route is too long. If the route was actually being driven it would be recalculated properly for the remainder of the route eventually.
add mirror mega & zippyshare& ex.ua - mapsource installer unlocked in post [Only registered and activated users can see links. Click Here To Register...]
I've tried making a map of only 2 adjacent countries with mapinstall but I've found a problem. Instasearch only works if I use the full .img not the cut down image, anyone noticed this before and knows of a solution?
There is also something that has been bugging me, the D*.db is supposed to have traffictrends info inside and we are supposed to copy it to .System/SQLite but how can we check if it really is being used? If i use only the .sid files and enable traffictrends in the options I get a delay estimate even if not using the D*.db
file.
The other thing is that inside the D*.db file, there is one table called "garmin_metadata", in that table there is one field called "description" that contains "CSC Boundary Index", this doesn't seem to be related to traffictrends. The other detail that is bugging me is that in the SQLite directory there is one system.db file that inside has a field that points to the device's original D*.db and it doesn't get updated when we copy a new .db file there, does the new map automatically use the new D*.db file? How to test it is working?
Device: nuvi 2545
Map in SD:/Map
SID and JCV in SD:/Garmin/{SID,JCV} (JCV tested to be working, SID seems to also work on SD card for my unit).
Edit:
Added device details and location of files.
Please, ASR-SRX files for 37** if any...
Note by MOD: request for additional files to maps no yet released : useless ;)
Can we use SRX+ASR files of previous version for this version
No, ASR files are version specificQuote:
Originally Posted by aajuno [Only registered and activated users can see links. Click Here To Register...]