Map Monkey & Windows Vista - Working.

toc · 03-22-2007, 04:21 AM

How to Fix - Font Tahoma not found, and Vista!

As previous post in Bugs, I though I would start a new thread for ease of searching Vista Solution.

--------------------------------------------------

Hi all,

I see a lot of peeps had this issue being a tech head I couldnt let it beat me on all my development PCs which include Visual studio and XP the program runs fine so I never needed a solution, then I brought a Vista laptop to trip to OZ and installed Mapmonkey as a back up to my GPS and bang!!! "Font Not Found!" - I can live with the error box, but none of the setting windows opened without crashing the program.... now I have no idea of the internals of font registering for the windows system but I tried every/all the steps of removing the font reinstalling the font... intalling an old font.. vista one is twice as large as my xp ones 600k instread of 300k... blah blah... and the same errors.

It annoyed me so much it was time for a little reverse engineering...

How to Fix Missing Font Error.

1) If you haven't already edit with notepad the 'c:\DestinatorApps\Destinator\Common\Interface\Vis ual\All\Destinator.inf'
there may be 2 referances to "Tahoma" in there do a find and replace "Tahoma" for "Arial" and save it, this will remove 2 font errors.

2) the other reference to "Tahoma" as already stated is in the 'DestDLL.dll' so this is a little more tricky to change this one... make a back up of this before you start playing.

Using a Hex Editor open the 'DestDLL.dll'
Goto Address 000092A26 which should read 'PUSH 01012A608' or in Hex '6808A61210' <- Tahoma Font call
Change the Hex to '68584F1210' <- which will call for the 'Arial' font instead.
Save the file and your done.

No more Font errors, also you may have to check your skin isnt calling the font but I dont change those.

This allows Map Monkey and Destinator 3 SDK to work fine on VISTA!!!! hurray! Job done.

I know this sounds a little complicated but its pretty straight forward as long as you know how to use a hex editor, alternitvely I could create a patch to do the work for you and this would NOT contain any copyright material, admins just let me know.

Hope this helps.

Nomader · 03-22-2007, 05:10 AM

i wish we find a way to use PN (even in win95)

wizz · 04-04-2007, 03:17 PM

Quote: Originally Posted by toc

How to Fix - Font Tahoma not found, and Vista!

As previous post in Bugs, I though I would start a new thread for ease of searching Vista Solution.

2) the other reference to "Tahoma" as already stated is in the 'DestDLL.dll' so this is a little more tricky to change this one... make a back up of this before you start playing.

Using a Hex Editor open the 'DestDLL.dll'
Goto Address 000092A26 which should read 'PUSH 01012A608' or in Hex '6808A61210' <- Tahoma Font call
Change the Hex to '68584F1210' <- which will call for the 'Arial' font instead.
Save the file and your done.[/color][/b]

No more Font errors, also you may have to check your skin isnt calling the font but I dont change those.

This allows Map Monkey and Destinator 3 SDK to work fine on VISTA!!!! hurray! Job done.

I know this sounds a little complicated but its pretty straight forward as long as you know how to use a hex editor, alternitvely I could create a patch to do the work for you and this would NOT contain any copyright material, admins just let me know.

Hope this helps.

My Hex Editor is telling me that there is no "Address 000092A26"
So how has anyone got this fix to work

I have been using my Desktop PC to try out updates etc. before comiting them to my carpc, but since upgrading (what a laugh

) to Vista Ultimate, I'm stuck with the "Tahoma" problem.
So, please someone help me out !

damienwright · 05-19-2007, 08:01 AM

Made the recommended changes on my vista partition. All works ok but I still get one error on launching the application saying Tahoma not found. I have checked with the HexEditor and changed the address specified and Have run the Tahoma utility though this says the file is already modified or a different version. I have checked through all of the ini files in the DestinatorApps folder tree and replaced all references with Arial. Anyone any ideas where I should look next ?

Best regards and many thanks for the excellent write up.

Damien Wright.

wizz · 05-20-2007, 01:34 AM

Same problem still exists for me......despite extensive help from Toc

docangle · 05-23-2007, 01:21 PM

I am having the same problem with Map Monkey and Vista. On my desktop PC (running Vista Business), I ran the font patch and changed the 'inf' file to Arial and all is fine. On my laptop however, I am running Windows Vista Ultimate and made the same changes but I am getting the message, 'Application Font Arial not found..', 'Maneuver Windows Font Arial not found..', 'Font Arial not found..'

Why would it work on one machine but not the other. I checked the Font folder to see if 'Arial' was present and it was, I have 853 items on my Font Folder.

OKA · 05-30-2007, 02:15 AM

Address 000092A26 which should read 'PUSH 01012A608' or in Hex '6808A61210' <- Tahoma Font call
Cant find any of the above to change
Any one found a solution Yet?

ephect · 10-24-2007, 10:55 PM

It might be worth, eveyone posting up what version of vista.. remember there are 5, and each do differ..

toc: what version of vista u running? and what version of destdll.dll?

hakhawk · 10-29-2007, 07:07 AM

to those that cant find the values stated above, i had the same problem. i decided to backup the dll and have a play tonight.

i searched "arial" in the dll using a hex editor, copied the hex values(there was only one instance found). then i found "tahoma", again only one instance was found. i then proceeded to copy the hex values for arial to the tahoma section. you're then left with the "a" at the end of tahoma. this is what i wasnt sure on. change the hex value to 00 for a blank. save the file and run map monkey. it worked fine for me, got rid of that last error message and so far no crashes of any sort.

theoretically, for the lazy, one could type arial in over top of tahoma using a hex editor and it should work, but i didnt try that way.

hope that helps