Thanx, but how to use it in igo? where to copy it? Something to write in sys.txt?

Copy the file in the main directory of iGO and add these entries to your sys.txt (only with GDI driver PDA working...):

[rawdisplay]
GDIPLUS_force_using_dll=1

[driver]
rawdisplay=GDIPLUS_dll

Regards,

GJM

http://anonym.to/?http://www.4shared.co ... iplus.html

deadlink

Please reupload

why do you wanna use the gdiplus driver? it is an obsolete 2D video driver. Use the default gx or an advanced gx driver from here: http://www.wincesoft.de/html/gapi_for_hpc_s.html
Enjoy!

why do you wanna use the gdiplus driver? it is an obsolete 2D video driver. Use the default gx or an advanced gx driver from here: http://www.wincesoft.de/html/gapi_for_hpc_s.html
Enjoy!

But do you think this GX .dll file will work with PDAS running with GDI drivers?

Because on my Eten X800 don`t work smooth... so anybody.. a new link ?

Because on my Eten X800 don`t work smooth... so anybody.. a new link ?

Here you have;

http://www.megaupload.com/?d=GEO4U89E

Do not forget to add these entries in your sys.txt file and soft-reset your device to see if it works...

[rawdisplay]
driver="gdi"
GDIPLUS_force_using_dll=1

[driver]
rawdisplay=GDIPLUS_dll

Regards,


GJM

grijamor I am sure that gx.dll will work with PDAs with gdi driver because you can "force" the system to use : in sys.txt you must add
[rawdisplay]
driver="gx"
gx_force_using_dll=1

and don't forget to add the gx driver in the igo directory

grijamor I am sure that gx.dll will work with PDAs with gdi driver because you can "force" the system to use : in sys.txt you must add
[rawdisplay]
driver="gx"
gx_force_using_dll=1

and don't forget to add the gx driver in the igo directory

Ok, thank you.
I will give a try...


GJM

8.3.4.117940 Navgear (2009 november) ?

8.3.4.117940 Navgear (2009 november) ?

It looks that have appeared in Germany for ADAC members ..........
http://www.pearl.de/navi/

https://www.gsmfreeboard.com/showthread.php?p=1401738

A translate from German will look like follow:
"Well, the Navi has arrived this morning. As promised, now the first comparison to the GT-50-T.
First surprise. Carton says: Streetmate GT-50-T-3D. The only difference. When the device description of the 128Mb DDR2 Ram are listed.
So unit unpacked. Visually, no difference, according to deduct the protective film can be seen, however, that the surface of the display somehow seems a bit dull. Exactly can not I say that the "old has" GT50 a display film. Laterally considered are any "oil spots" or Newtonian-rings. That had my GT but not 50 by early November.
Accessories as before, save only with manual CD without any software and the manual a bit. Only A6 instead of A5. Car Charger visually different, but unfortunately still without angled charger.
So pure and erstmal memory card to PC in order to secure the software.
IGO is the version 8.3.4.117940
Also, the version number of the TMC receiver is higher. 1:1 In comparison with the "old" GT 50, the brightness and contrast of the display is significantly better.
Negative strikes me that in the main menu when the backlight is not a menu item to find more to stop the deactivation of the display. Was that still the function that the GT50 was just in practice, because only from this "pseudo sleep mode" reached the first-generation practical GT50 GPS fix times.
I've started the new GT50 and GT505, or disconnected from the PC, IGO, and placed on the window sill. First minute fix for 21. For the first time through OK, but what happens after the complete shutdown. Because not a pseudo-sleep more funzt.
Article min after positive surprise of approximately 40th completely eliminated, after switching on and off from IGO Immediately stable satellite reception"

Hello. We (all) got a very big problem with routing igo 8.3.x.xx and 8.4 (amigo).

We start (our GPS position) is a point: A
The problem is that, if i set as destination (a point) - for example B, and a VIA - point (intermediate point) - C, the IGO 8.3.x.xx and 8.4.x.xx software DOES NOT turn at the via point.

Normal routing is: A - C - B
Igo 8.3.x.xx problem: A - C - D - .... - B.

This is a very big problem, because, if you are not patient, you can surround more than 100-200kms only to turn back!
The GPS (igo software) DOES NOT tell you: turn where is possible.

I dont talk about one way streets, or highways. I talk about normal roads (national or european road).


THIS PROBLEM DOES NOT APPEAR ON IGO 8.0.xx devices !

This happens on every iGO software versions 8.3 and Amigo.
On IGO 8.0 the problem DOESNT appear (if you are at least 100-200m before the VIA Point, the IGO says: In 100m you reach the VIA Point THEN Turn if possible
Thanks in advance, and please write back soon.

No ideea?? IS IT a bug?

@grijamor Thanks, i will give a try and post feedback.

Hello. We (all) got a very big problem with routing igo 8.3.x.xx and 8.4 (amigo).

We start (our GPS position) is a point: A
The problem is that, if i set as destination (a point) - for example B, and a VIA - point (intermediate point) - C, the IGO 8.3.x.xx and 8.4.x.xx software DOES NOT turn at the via point.

Normal routing is: A - C - B
Igo 8.3.x.xx problem: A - C - D - .... - B.

This is a very big problem, because, if you are not patient, you can surround more than 100-200kms only to turn back!
The GPS (igo software) DOES NOT tell you: turn where is possible.

I dont talk about one way streets, or highways. I talk about normal roads (national or european road).


THIS PROBLEM DOES NOT APPEAR ON IGO 8.0.xx devices !

This happens on every iGO software versions 8.3 and Amigo.
On IGO 8.0 the problem DOESNT appear (if you are at least 100-200m before the VIA Point, the IGO says: In 100m you reach the VIA Point THEN Turn if possible
Thanks in advance, and please write back soon.

No idea?? Is it a bug?

I would check my Regional Settings to make sure you have the right country choice made. I always select the smallest choice which for me is miles and feet. Chances are this is not the problem but could be part of it.

Then I would go into Route Planning tab and see what the settings are for when iGO8 makes its announcements. I like my first announcement to me about three miles prior to the turn. A low value set here could possibly cause the problem. This is one of the few times I like have a larger value set for announcements versus smaller values for map display and replanning/u-turn options. While in this tab, I believe you can check what the Replanning option is too (when iGO8 will replan the route). I usually set this to a real low value. Why?

Well, if you have iGO8 set to display the raw GPS position, iGO8 can merrily go along its merry way while you are exitting a highway or even turning perpendicular to where the route is displayed. In the case of using an access road or even a turn-out to get off a highway, iGO8 will continue to display the route and cursor as being on route even if you have chosen to depart the planned route. I want iGO8 to keep up with my car versus where it plots the route out.

When I set up a route and then add an intermediate point by using the Edit key in the Route tab, I always check or have iGO8 show me the entire route by selecting the button at the lower right which plans the route on the map. Then if it is a new intermediate point or route I have never used before, I will have iGO8 simulate the route using the Fast option.

I've noticed that with some skins if you set up an intermediate via point using the Via Point button on the Map display page, sometimes iGO8 will not incorporate the Via Point into the route calculation. For this reason I will always plan my route using the Find tab first. Then I will ONLY select the Destination. Once I see that the route has been calculated, I will go to the Route tab and use the Edit function to add Via Points (if needed) and verify the route using the Route map display button.

Hope this helps.

My current igo 8.3 has this problem. I have selected Allow U-TURN in the settings tab, i have selected an intermediate point, BUT when I make a simulation (fast), i saw, that the IGO DOESNT turn me, at the VIA-POINT. It (igo) puts me to go forward 30km, to the FIRST ROUNDABOUT, to turn me back. I have selected all what you said.

On IGO8.0, THE problem doesnt appear!!
Try this (on igo 8.3):
The start point: Country: ROMANIA, City: Baia-Mare, Middle of city
The destination: Country: ROMANIA, City: Baia-Mare, street: Soseaua de Centura, middle of street
The via-point: Country: ROMANIA, City: Recea with subdetail: Maramures, middle of country.


In the first picture you will see the normal route, made by IGO8.0
In the second picture you will see the abnormal route, made by IGO8.3


Please post back, a screenshot with the route, and tell us if represent the first(normal) or the second (abnormal) picture

My current igo 8.3 has this problem. I have selected Allow U-TURN in the settings tab, i have selected an intermediate point, BUT when I make a simulation (fast), i saw, that the IGO DOESNT turn me, at the VIA-POINT. It (igo) puts me to go forward 30km, to the FIRST ROUNDABOUT, to turn me back. I have selected all what you said.

On IGO8.0, THE problem doesnt appear!!
Try this (on igo 8.3):
The start point: Country: ROMANIA, City: Baia-Mare, Middle of city
The destination: Country: ROMANIA, City: Baia-Mare, street: Soseaua de Centura, middle of street
The via-point: Country: ROMANIA, City: Recea with subdetail: Maramures, middle of country.


In the first picture you will see the normal route, made by IGO8.0
In the second picture you will see the abnormal route, made by IGO8.3

Please post back, a screenshot with the route, and tell us if represent the first(normal) or the second (abnormal) picture

How do you build your Via Points in iGO8.3? Do you verify all your points using the Route tab to verify the order of points both in the list function and on a map? If you see more than what be considered valid route points, you know you have an error.

If I build a route with point A as the Start Point and B as the Destination, I go to the Route tab and use the Edit function to insert point C as a Via Point, I will see them listed as:

Point A
Point C
Point B

Then when I do the Fly Over simulation, I hit the Via Point every time in both in Simulations and actual driving conditions.

The only other thing I can think of (assuming that your Via Points are being built correctly) is that the Via Point may be inaccessi ble for some strange reason. On a rural highway with no turn-outs or off-ramps - if the distance between a turn-out (t-o) or off-ramp (o-r) is too great and iG08 cannot devise a route that it can access by the closest t-o or o-r, it will make you go to the next t-o or o-r.

This could happen because:

1) one way roads do not permit the Via Point (VP) to be reached;
2) permits are needed (usually a private road either with a toll or expressway that needs a special device to permit passage);
3) private road that is closed;
4) a routing factor ,like u-turns, is not enabled (Fast or Economical should not make a difference in this matter but could in some situations);
5) map does not allow all access or service roads to be used in getting to some destinations. *Note 1

*Note 1 - In the United States, I have noticed that TeleAtlas can use service roads, private alleys and access roads that Navteq does not see or permit usage of. In my neighborhood, there are alleys that appear on all good map services like Google and Yahoo. Mail, packages and road service can be directed to these publicized alleys which have street numbers corresponding to the road they off-shoot from. My garage sits on one of these major alleys. I used to use Navteq but when I drive off my street the cursor stays on the street while the GPS dot is shown going off into no-where land (nothing depicted). When I tried TA, I was amazed to see that the cursor followed my vehicle onto the alley (first the narrow entrance and then the alley). The only reason I can see or imagine why NT does allow usage of these alleys is because a large truck or vehicle cannot enter the narrow entrance even though the alley parallels my street and can be accessed at wide points off two other roads that are perpendicular to my street. Bottom line: these alleys or service roads may be somewhat like you may be encountering.

Recommendation
I would recommend that you build your Via Points using the Route tab Edit feature after building and selecting the Destination. Use Find to build the Destination. Then go to the Route tab and select the Edit feature. You should just see two points (A and B). If you place your cursor on Point A and Insert a point as a Via Point here, you would now have Points A, C and B. Then you can use the Simulate/Over-Fly to see if the route points are being used in the correct manner.

Good luck!

Now, i am doing what you said:

I add the city: Baia Mare, from ROMANIA, centre as a start POINT
Then I add the street Soseaua de Centura middle, from Baia Mare, Romania as destination
Then I go to the Route tab - Edit Route - Add then i find city: RECEA with subdetail Maramures, Romania, and then i press Select tab.
Then, i verify if the points are in the correct order (and it is): Baia Mare middle 1st, Recea 2nd and Soseaua Centura 3rd.
Then, i go Simulate, and I saw THAT nothing changes.

This happends, not only with my PDA (MIOP560). My friend, had this problem too... but ONLY at igo 8.3 , 8.4 (from nov .2008 till Aug 13 2009).

On IGO 8.0, i say again, I HAVE NOT this problem.
I made exactly what you said.

PS:
1. The road IS NOT one way (lol it is a National Street...)
2. The u-turn is check in settings.
3. The picture in my last post is from a IGO PC (which use igo8.0 maps results i got no PROBLEM)
4. I created those via points points, to creat the route on igo 8.3
5. I have tried i think.... 6 maps (2008.04, 2008.10, 2009.02, 2009.06, 2009.09 (actually) ), from 3 type (TopMap - the best, TeleAtlas and Navteq). The same problem... this rapid, easy, short etc, etc... etc... type of ways
6. The problems with Private road, or uturn inaccesible what you said, ARE EXCLUDED as long as is a national way (the 3rd from Romania)...

Have you tried on your GPS, what i said? I think it is an iGO 8.3 bug.
How could you explain, that, on igo8.0 the problem does not appear?