Workaround for the CP6 Trip Time bug

PONDEROUS · Posted: Fri Jan 06, 2006 1:13 am Post subject:

Does DPDurst actually believe what he implies in his post above? I can't see it as here is someone who holds him or herself out as being from ALK saying without qualification that a fix for a bug is to be found in a certain version that no one has heard of before. Is such a statement really going to go unnoticed, despite the fact that this is the first that has been heard of the version in question? Or should I say that this is the first that has been heard of the patch since, we understand, ALK's UK technical support people put a date of 15 December 2005 for its release?
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

dpdurst · Posted: Fri Jan 06, 2006 4:24 am Post subject:

You bet I believe what I say, do you expect a patch instantly for something that is broke. Do you work in software in design and know what goes into the fixes? Our company and I'm sure others (I dont know 100%) state a version of software is forthcoming example, we have a fix for our software the version is 2.364. Know one in the field has heard of it till now, yet its still 2 weeks away. Its pretty nieve to think there may or may not be a version in the works or close and version would not be known by ALK, yet not available to the public just yet. So yes, I believe what I said and it does not suprise me at all about the statement. But I would bet if the version is not the 6.0.1 or it takes a bit longer to maybe put a few more fixes in it that you may just come unglued!

Paul-m · Posted: Fri Jan 06, 2006 9:27 am Post subject:

There are many ways of doing this depending on the size of the product and company.

The method that im used to is that there is a schedule of releases of software spaced quarterly or something like that and they have cut-off periods where no more changes will be implemented for each patch or release. Then the coding is froxen and field trialled before being released. They could even be working on 2 releases at once.

So yes they do probably know in general terms thier entire release strategy and versions but will have no idea what the content will be.
_________________
Wife 3 kids.... unversity fees...:-(
oh... and a few PC's and gadgets ;-)

PONDEROUS · Posted: Fri Jan 06, 2006 9:56 am Post subject:

dpdurst says that it is "naive" not to know that xw meant. If so - and if not - I simply suggest that the situation regarding a release is made clear when similar statements are made on future occasions.
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

xw · Occasional Visitor Joined: Jan 05, 2006 Posts: 7

Ken,

I got 6.0.0.68 cab, hardrest my Pocket PC, install the cab, activate license,
confirm no usertip.dat and userstop.dat on the sd card\copilot\save directory.
Start CoPilot, Setting->Map, Mile is the default, click KM, click OK.

I got usertrip.dat with size 829bytes, and userstop.dat with size 85bytes.

Do you have anything you forgot to mention to create this size 0 file?

Thank you very much for helping me find the sequence of operations to create this bug!

XW

PhilB · Lifetime Member Joined: Nov 26, 2004 Posts: 83

KenS · Regular Visitor Joined: Oct 25, 2004 Posts: 73

xw · Occasional Visitor Joined: Jan 05, 2006 Posts: 7

Now, I can regenerate this. As you mentioned, this is the source of the ETA problem.

We were told about this, but just could not successfully regenerate it.

I really appreciate your help.

XW

BMWBiker · Posted: Sat Jan 07, 2006 1:13 am Post subject:

PONDEROUS · Posted: Sat Jan 07, 2006 12:09 pm Post subject:

BMWBiker writes:

PONDEROUS · Posted: Sat Jan 07, 2006 12:13 pm Post subject:

... and not forgetting thanks to xw (and ALK) for listening and contributing.
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

KenS · Regular Visitor Joined: Oct 25, 2004 Posts: 73

SupraCoPilot · Occasional Visitor Joined: Jan 07, 2006 Posts: 7

Ken,
Thanks for all your efforts in sorting the ETA bug. I had the problem with v6.0.0.68, used the fix and decided not to change any routing settings just in case they caused the snag again. Went on a trip and all seemed well, then set up the trip to come home. Half way back when I noticed that the ETA bug had returned. Arrrggggg....

I have since removed every trace of the program and reinstalled it. Everything now appears OK. Laughing

I'm having fun with the tts files now. With TTS-US-M loaded I get John (US male character), except the "in 500 yards" warning and "then" are both spoken by Jane (posh English) in the middle of the phrases. The TTS-AU file is the same as TTS-UK (male English in the style of Stephen Hawking). Also if you try the Ogg Vorbis files, the US Lisa sounds the same as John. My preference is the Australian Jessica as she seems to speak UK English with an Aussie accent, instead of Jane who speaks UK English with an American inflection. "Welcome to CoPilot" is one strange example of this, with the accent on the wrong syllable.
_________________
Steve

Garmin Nuvi 255WT
Mio 168
CoPilot 6.0.4.110

KenS · Regular Visitor Joined: Oct 25, 2004 Posts: 73

xw · Occasional Visitor Joined: Jan 05, 2006 Posts: 7

Thanks all the people who bring up this bug and lead me to regenerate this bug.

I just want to follow up with this.

For 6.0.0.68, this bug happens. You may refers to Ken's suggestion to around it.

For 6.0.0.77 and later, this bug does not happen (or I may say it's fixed). At least, I use Ken's sequence operations, and could not regenerate size 0 usertip. The source of the source of the bug is "useProfile" sets to 1, while there is no profile name and etc related things saved.

For 6.0.1.xx, there is another protection at the loading time when encountered size 0 usertrip, it will not load it.

I talked to the product manager about this and the speech file. He told me there is going to be a patch that fix these and some other things coming soon.

I would encourage you browse ALK tech support web or talk to ALK tech support directly.

Thanks!
XW

	PocketGPS
	Web