Hi,
Any new maps for middle East area or at least United Arab Emirates?
Thanks,
- Posts 277
- Location GPS Land
- WRZ$
568.40
- Device WinCE5 PND
No new Polnav maps are available on the update website, except for Taiwan.
Newest Polnav version was to be released in January/10, but delayed...AGAIN...for about the 5th time.
Polstar is not seriously in the GPS business from a map update POV!
Newest Polnav version was to be released in January/10, but delayed...AGAIN...for about the 5th time.
Polstar is not seriously in the GPS business from a map update POV!
- Posts 277
- Location GPS Land
- WRZ$
568.40
- Device WinCE5 PND
- Posts 25
- WRZ$
52.60
Does Hsu's upload work with North America map and how to? I found out it does not work even with original Taiwan Map on my 3.5 Curtis GPS. This is the first time I am using this program. Can anyone guide me through? I did try to use the crack .exe file for ver 6.02. Thanks.
- Posts 73
- WRZ$
6.20
- Device ASUS P320
- OS Symbian
hsu wrote:The original retail version Polnav v6.02 ,include TMC,TTS and 2009Q4 Taiwan map.
download link: http://www.megaupload.com/?d=3RHFM5SW
password: ppchsu
Thank you very much, I am just now in Taiwan and use it. It run very well on my Mio C320. Nice voice, the display of the tracks is great.
If I am back home I will give it a chance for Europe.
Thanks again
- Posts 277
- Location GPS Land
- WRZ$
568.40
- Device WinCE5 PND
- Posts 277
- Location GPS Land
- WRZ$
568.40
- Device WinCE5 PND
I posted this on the other board also...
I've been dismayed at some routings calculated by Polnav 6.0.2/4.
There seems to be an inconsistency that is unexplainable.
For example, simulate a trip from your location to these two points, roughly 32.7 km apart on the Nova Scotia coast.
Use Car\Faster\Avoid Ferry as Route Options.
* W64.190316 deg
* N44.577398 deg
Record your distance, look at the best fit routing
Then, Cancel Route, make no changes to any options and travel to
* W63.910127 deg
* N44.684923 deg
Does Polnav give roughly equivalent distance/routing for each destination?
My results are 2105 km, 19:45 hr for the first destination, 1818 km, 18:26 hr for the second and the routing is very different. These results are definitely outside margin of error!
Any suggestions as to cause?
UPDATE:
Removing USA_East.map from the Map folder, the trip to the first destination was forced through Canada (the only available route), for 1845 km, 18:42 hr.
So, the question is, why would the inclusion of the USA_East.map cause the trip to be so much longer, 2105 km, 19:45 hr and go through the USA, when the obvious choice would be the shorter and faster route through Canada? This just doesn't make sense! It certainly calls into question the veracity of Polnav routing calculations. Caveat Emptor!!
Hold everything! - looking at the numbers for the first destination - 2105km/19.75hr=106.58kph and 1845km/18.7hr=98.66kph - hmmm, I got what I asked for - FASTER!
I'd argue that faster means less time on the road, not a faster average speed! Go figure!
FWIW, changing Route Options to SHORTER had both destinations routed through the USA; complete nonsense!
I've been dismayed at some routings calculated by Polnav 6.0.2/4.
There seems to be an inconsistency that is unexplainable.
For example, simulate a trip from your location to these two points, roughly 32.7 km apart on the Nova Scotia coast.
Use Car\Faster\Avoid Ferry as Route Options.
* W64.190316 deg
* N44.577398 deg
Record your distance, look at the best fit routing
Then, Cancel Route, make no changes to any options and travel to
* W63.910127 deg
* N44.684923 deg
Does Polnav give roughly equivalent distance/routing for each destination?
My results are 2105 km, 19:45 hr for the first destination, 1818 km, 18:26 hr for the second and the routing is very different. These results are definitely outside margin of error!
Any suggestions as to cause?
UPDATE:
Removing USA_East.map from the Map folder, the trip to the first destination was forced through Canada (the only available route), for 1845 km, 18:42 hr.
So, the question is, why would the inclusion of the USA_East.map cause the trip to be so much longer, 2105 km, 19:45 hr and go through the USA, when the obvious choice would be the shorter and faster route through Canada? This just doesn't make sense! It certainly calls into question the veracity of Polnav routing calculations. Caveat Emptor!!
Hold everything! - looking at the numbers for the first destination - 2105km/19.75hr=106.58kph and 1845km/18.7hr=98.66kph - hmmm, I got what I asked for - FASTER!
I'd argue that faster means less time on the road, not a faster average speed! Go figure!
FWIW, changing Route Options to SHORTER had both destinations routed through the USA; complete nonsense!
- Posts 1
- WRZ$
50.10
mylnym wrote:walek75 wrote:Damn, its look like, crack is still not complete
i will be working on it...
Taiwan source shows mute bug fix:-
To resolve v6.0.2 mute problem
0x3bfcH: 82->B2
0x3bffH: 1A->EA
Will this fix the mute problem when running on wince 4.2?