Over the speed limit alert possible on 295w?

I did exactly as you said step by step still get the voice file corrupt error. So I proceeded to your second part of the instructions and for some reason my voice folder does not have any files with the extension .sum I even made sure to have my folder viewing to include hidden objects and then I even did a windows search for the garmin drive by typing in sum and check to see if it found anything. Any idea as to why it isn't on mine? Oh if it helps as you know I did the webupdate but when I did it the very first time there wasn't a newer firmware version and I as well made sure the Garmin drivers were up to date on the computer and restarted after that.

sorry I wrote that before your post came up on here. so yah I'm kind of at a loss since I followed everything lol.

As far as I can tell, in addition to the 295w not having .sum files in the voice directory, there is also no series of diagnostic screens that come up when pressing the "battery" for a long time. I didn't find anything on Google for reaching these expected hidden screens for the 295w either.

I know how, At least I think I do. I found it by luck. Click on settings and then hold down on the battery there. Not sure how long it takes but that is where I got to it at.

Yowser, that's amazing. Odd, I still don't see a way to test or view voice files, but there are an amazing series of test pages and factory tools. Whew, I bet a lot of damage can be done here.

There's even a flashlight mode!

I just remember the TTS voice file includes a checksum. It was not checked before. Maybe it is now. Let me see if I can do something easy to test this.

Standing by for orders captain!

I think the voice testing appears in the test pages under Inventory. The voices are listed by number and version but not by name

Using the checksum inside the file could explain why there is no .sum files anymore on the 295W.

I am unsure about how to calculate the checksum. It does not look to be the entire file.

If you have time, make a quick test:

1- Start over with an original Jill.
2- Edit one phrase this way: make a cut and paste so the new and old phrases are the same, On the new one, swap the first 2 letters.

For example: "turn right" should be "utrn right".

See?

This way, the checksum will stay the same. Save and copy to GPS and reboot. My guess is the voice corrupted is not there anymore.

lol k i will try this and report back. not sure how it will work when i want to change the actual phrase. unless you are getting at that if i want make a total right dude instead of turn right that i have to put it like this amake a total right dude but i will attempt it and see what happens with the turn right as utrn right and report back.

You can change "turn right" by "right turn". The most important part is NOT to change any letters to make sure the checksum is not affected.

I made more tests. I am close to Garmin's checksum, but still a little off. Once I get it, I'll modify TTSVE to make the change automatically.

After finding the test pages on the 295w and running an inventory, checksums do now appear for each voice. Using a hexeditor, I see that Jill's checksum on my 295w is 03 D4 4A 67

Yes. It is the same as the one included in the VPM. The checksum must be calculated for the DLLIMG.BIN subfile.

I could not match it a first because I was using a file I thought was the original, but it was modified. Now, it matches perfectly. I'll do this tomorrow or when the wife is asleep.

Turbo

K I did that and still have the error. I also rebooted the GPS just to make sure.

One last thing. Using your TTS Voice Editor, I see that the nuvi 750 and 855 use version 2.60 for Jill while the 295w uses version 2.30 with all three nuvis loaded with the latest firmware and latest Jill updates offered through WebUpdater.

@CraigW: Interesting finding!

@tdsj81: are you sure the original untouched voice still works? Are you sure you really used the same letters? No more. No less. It should really work.

yes and yes. after doing a succesful webupdate earlier i tested the voice file to make sure it worked by selecting it to be my navigation voice. then when i did the copy turn right to turn right and then changed that to utrn right and put it on the garmin voice folder and safley removed hardware and rebooted and when i turned it back on it gave me the error still.

mine uses v2.60? could that mean anything?

Hi tdsj81,

With all the POI Loader v2.6.0 issues, I have been working on my POI_Loader replacement with EPE and forgot to work on your issue.

Please, help me with this. Can you post me a link to your original Jill (the one that works) and the one you modified by swapping 2 words or 2 letters in one prompts?

I will check if what you modified was done correctly. Maybe TTSVE modified something else causing the file checksum to change. Depending on what I see, I may modify myself the original Jill and send you a modified one for testing.

Thanks,

Turbo

I just did a WebUpdater check and see that Jill 2.60 is now offered for my 295w so I just upgraded and match you Jill for Jill now.

Have you tried TTSVE with previous Jill? Was it working? Now I guess you are in the same condition as tdsj81.

Back with Jill 2.3, I did use TTSVE to increase her volume from the default 65 to 95--although the 95 Jill didn't sounds louder than the 65 Jill. I never used your program for changing text--only for volume and version checking. The volume-adjusted Jill 2.3 did work in my 295w. I reverted to volume 65 again from my modified 95 and it also worked in my 295w with no corruption.

On my 750 and 855, increasing Jill's volume # has an effect on the audio level so the way voices work may well be different on the 295w.

k here are the two files.

modified

http://www.2shared.com/file/LRG5LcnP/English_American_Jill.h...

original file (working) unmodified.

http://www.2shared.com/file/s0V_yI-L/English_American_Jill.h...

I compared them abd there is only the 2 letter swap. The file checksum has not changed.

If this is not working, this means Garmin is checking for something else. Probably another checksum/crc elsewhere. I wonder why they are doing this. I can't imagine they are doing this to prevent my program from working. TTSVE is a "+" on their users' buying guide.

Well, it seems it is going to be slightly more difficult. Here's another test for you:

- Instead of swapping 2 consecutive letter, swap the first letter with the 4th one.

Example: "turn right" by "nurt right"

If this is just an odd/even checksum, we'll find out.

Thanks,

Turbo

K, did that and still get the voice file corrupt. I also shut the GPS down and started it back up and still have the voice file corrupt error.

I made a little mistake when I said swap first letter with fourth. It would have been better with 5th.

"turn right" with "turn tighr"

I was trying to be on a 4-byte boundary, but ended up asking you to swap off with even bytes again.

If this does not work, I do not know what to try next. I also checked the voice file to see if I could find other traces of checksums or CRCs. Without disassembling the VPM or the 290W firmware (and spent dozens of hours), I do not see how I am going to find a solution.

looks to be hopeless. did what you said with same results.

Looks like the 295w is going to be a little tough to change the voice instructions.

I do not know why they did that on the 295W. Maybe they are in the process of doing the same to other GPS models. It could be the end of TTSVE...

Please keep us posted, if thats the case I won't be updating my voice files any longer.