Page 1 of 31
Re: POIs and tracks in JB
Posted: Wed Oct 15, 2008 10:52 pm
by kchow24
Some POI and Track at Sedenak...
Re: POIs and tracks in JB
Posted: Thu Oct 16, 2008 10:12 am
by WFR8352
map for segamat is not included, yesterday when i travel to segamat, the road stops before the end of Lebuhraya Tun abdul Razak.....then no more road....me using garmin MXT
Re: POIs and tracks in JB
Posted: Thu Oct 16, 2008 10:25 pm
by kchow24
WFR8352 wrote:map for segamat is not included, yesterday when i travel to segamat, the road stops before the end of Lebuhraya Tun abdul Razak.....then no more road....me using garmin MXT
what are you trying to tell....?
Re: POIs and tracks in JB
Posted: Sat Oct 18, 2008 11:13 am
by gerkeng
kchow24 wrote:Some POI and Track at Sedenak...
Updated,Tq
Sedenak, Kangkar pulai, Kulai, Senai and Skudai Track
Posted: Tue Nov 11, 2008 9:39 am
by thiang
track @ poi kulai
Re: Sedenak, Kangkar pulai, Kulai, Senai and Skudai Track
Posted: Mon Nov 24, 2008 1:36 pm
by robo
Noted. Thanks.
Kulai To NSE (E2) - error?
Posted: Fri Nov 28, 2008 6:17 pm
by weipong
Hi,
When leaving Kulai town to join the NSE (E2), the map routed me north, all the way up to the Machap exit instead of using the Kulai exit.
Can u check? Thanks!
Re: Kulai To NSE (E2) - error?
Posted: Fri Nov 28, 2008 6:35 pm
by alyem
What was the setting in your GPS device??
Time or Distance?
Did you click void highway or Toll...???
Just to check....

Re: Kulai To NSE (E2) - error?
Posted: Sat Nov 29, 2008 10:24 am
by sabre23t
weipong wrote:When leaving Kulai town to join the NSE (E2), the map routed me north, all the way up to the Machap exit instead of using the Kulai exit.
There was disconnect between E2(N), E2(S) and 252 Kulai Exit in MFM 1.22. Looks to me it's now corrected in MFM 1.23.
Re: Kulai To NSE (E2) - error?
Posted: Mon Dec 01, 2008 3:54 pm
by robo
weipong wrote:Hi,
When leaving Kulai town to join the NSE (E2), the map routed me north, all the way up to the Machap exit instead of using the Kulai exit.
Can u check? Thanks!
It's connected.
Please use the latest update. Anyway, thanks for the error report.