canderson
Moderator
- Joined
- Dec 28, 2007
- Messages
- 13,455
- Location
- Colorado, USA
- TomTom Model(s)
- GO720, GO740, GO 1535, Via 1535, Via 1605, GO 52, GO 600, GO 620, GO 630, GO Discover, TomTom Bridge
Just sorry it took so many back-and-forth to get you there. Having never actually looked at the old Vocalizer file/folder structure, I wasn't confident that I knew where all the pieces were. Guess there's enough gone now to keep Home from complaining.Ah, it would appear that has resolved the problem! I'm no longer receiving the error at all.
Fine work, gentlemen. +Rep for excellent service!
I have no idea why Home suddenly takes offense to some older file data. As I say, when I updated Home to 2.8, it immediately started to gripe about an OLD map (715) that was part of the first backup I ever did with Home of my original 720 unit - before I knew better than to use Home, of course! As the map files weren't corrupted in any way - I checked that - it seems that new versions of Home are simply no longer able to understand some of the subsystem structures used back in the 'days of yesteryear', then starts to gripe about them. In my case, old maps. In your case, an old TTS voice.
Now that you are functional again, you might want to consider grabbing a "computer" voice with Home and seeing what you think when your unit pronounces street and exit names. It really is pretty nice, although it will blow the pronunciation now and again.
And of course, before you do ANYTHING, make yourself a fresh Explorer backup of your unit in its "new" and happy condition.