[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Installation: GPS Cycle Computer 4.11 beta versions

For ease of use, most users that wish to run GCC 4.11 beta versions would currently be best advised:

To ensure a known initial condition and for avoidance of potential issues, having taken backups of files if desired, these two initial optional steps are recommended: Uninstall any existing GCC. Soft reset / restart the device. Then, using the links below:

Step 1: Download and install 4.11 beta 3.

http://xdaforums.com/attachment.php?attachmentid=2038317&d=1371078032

Step 2: Download and install the latest 4.11 beta version, currently 4.11 beta 20 at time of writing. Manually copy GpsCycleComputer.exe therein to the GCC installation directory, replacing the existing file (having taken a backup if desired)

http://xdaforums.com/attachment.php?attachmentid=2409111&d=1385154603

Why is this necessary?

GCC versions prior to and including 4.10 Final do not upgrade fully, directly to 4.11 beta3 onwards by simply replacing GpsCycleComputer.exe with that from a 4.11 beta version. GCC 4.11 beta3 included an additional file and was accordingly distributed as a .cab installation file. Unless 4.11 beta 3 is installed first, as a minimum, the file TurnOver.wav will be missing which may or many not cause issues, but definitely will not if present as intended. Additionally, an assortment of erratic behaviours have been reported by various users and confirmed resolved by installation as above.

Microsoft .Net Compact Framework:

As a minimum, .Net CF 2.0 is required by GCC, which is compatible up to .Net CF 3.5, which encompasses 1.0 and 2.0 .Net CF versions (there is no 3.0 version). Installation of .Net Messages provides additional diagnostic detail to error / crash reports. Many devices already have at least 2.0 pre installed. If not, when attempting to run GCC an error message will display prompting the user to install. Most users will find this easiest by direct download from Microsoft and installation by ActiveSync, which automatically selects the correct files for the device based on Operating System and CPU architecture type, avoiding the usual issues in that regard.

Microsoft .NET Compact Framework 2.0 Service Pack 2 Redistributable

Microsoft .NET Compact Framework 3.5 Redistributable

Alternatively, the correct .cab installation files can be extracted and manually installed.

Testing and Troubleshooting:

Switching between versions:

For those that switch back and forth between GCC versions by replacing the .exe by whatever method for whatever reason, it has been previously observed that doing so on some occasions and in some circumstances appears to cause odd effects. It is thought this may be related to the GpsCycleComputer.dat settings file. When upgrading, the usual intended action, it works usually without issue, although not always. When downgrading, settings present in the higher version not present or different in the lower downgraded version seem to cause odd effects.

Error Logs:

GCC has in built error logging. Log files are located within the installation directory, entries therein remain persistently, with each new entry appended below the previous entry. When the current GpsCycleComputer.log file is full, it's file name is appended. Then a new separate GpsCycleComputer.log created.

For example, when full, each GpsCycleComputer.log becomes GpsCycleComputer.log2013531_122814889.log

The string of numbers represents year month day _ hour minute second millisecond and will vary for each file.

The .log files are in fact ordinary text files readable with Windows Notepad or similar. To upload a log file for analysis as an attachment to a post on this forum, as .log extension files cannot be uploaded directly, it must either be renamed .txt or if there are many, it may be easier to combine and compress with a zip archive file and upload that.

To clear the error log files, simply delete them, having taken a backup if required. It will then be more readily apparent when actual new errors occur.

Troubleshooting:

Before proceeding further:

If the device has limited available resources, either because it is an older lower specification device, or has many installed applications and background tasks, ensure Data Array Size is set to 4k by selecting Menu > Options > Main Screen > Data Array Size. Then exit and restart GCC. If issues persist, proceed as below:

In brief, when troubleshooting, to actually identify an issue methodically, it is usually best to start afresh. Simply deleting or renaming the existing GpsCycleComputer.dat (having taken a backup if desired) will cause another to be automatically created with default settings, the default starting point.

Testing can then be carried out from the default, with the minimum additional settings required to commence testing the issue in question. User settings can then be added methodically and sequentially one at a time until the problem is identified.

Identifying intermittent issues can be particularly troublesome and misleading if not following basic principles and testing rigorously and thoroughly. Issues can appear resolved when in fact by nature of their intermittency have simply not been observed to have occurred again, but remain nonetheless and will reappear.

An essential part of troubleshooting is to identify and determine what the issue actually is and in what circumstances it can be observed, not simply what appears to be the case. For instance, where an issue appears to occur when the screen is off, it needs to be determined whether the screen being off is actually a factor, or whether in fact the issue still occurs when the screen is on. In this instance, simply not turning the screen off automatically via Window Power and or Backlight Settings, or pressing the power button on the device, or the backlight button within GCC will suffice. If an issue persists, at least with the screen on useful information might be derived from what is seen on the screen.

Essentially the above are first principles in brief. Jumping to conclusions or extremes such as hard resetting devices and other irrational actions are ultimately unhelpful if underlying issues are not actually identified so they can be resolved so as to not occur in the first instance and not effect other users.

When providing feedback, ensure your device manufacturer, model, Windows Mobile OS and .Net Compact Framework and GCC versions are detailed. If providing a bug report, ensure details are included of how this can be observed and reproduced.

low.flying.pigs