yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] WolWer:
As indicated on http://www.openstreetmap.org/copyright every map should show (c) openstreetmap.org contributors - most simply to be done by means of additional feature in gcc adding this footer to map view. For use of prerendered maps, hint in options/map screen as multiple choice to be selected by user should meet the requirements, right?

@ Blaustein: If lfp agrees - I guess it's no big effort to add this feature? Thus it would be possible to provide maps for gcc-users. To reduce number of jpg-files: Is it possible to use bigger tiles than 256x256 (only format available in actual MobAC)

cu - WolWer
[Touch Diamond, MDA Compact IV General] WolWer:
Tx to low.flying.pigs: both proposals (regarding map copyright and number of map tiles) are suitable to solve these probs. Only one left: Who to implement this additional features in GCC??? Blaustein seems to be too busy or still in vacation - don't know! cu - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Further to post 2294 part 3c:

MOBAC 2.0.0 alpha 1 is now available for testing. This preview release features a preliminary implementation of the integrated mapsforge renderer functionality, which is a positive and necessary development. Early indications are generally good in this regard.

The aim, when fully functional, is to allow tiles in bulk of wide areas over many zoom levels to be rendered directly from mapsforge maps, or OpenStreetMap raw data, instead of jeopardizing Tile Servers by bulk downloading pre rendered tiles from them. See here.

At the moment, OpenStreetMap raw data must first be converted separately to Mapsforge map format, however, it can be envisaged direct handling / conversion of OpenStreetMap raw data may be integrated at a later date.

Maperitive is currently somewhat resource intensive as detailed in post 2301. Rendering with MOBAC 2.0.0 alpha 1 is far less resource intensive. However, the two being different are not otherwise strictly directly comparable.

Testing as below was carried out on a machine with total 1GB RAM.

In brief, attached screen grabs show MOBAC 2.0.0 alpha 1 in usage and resultant tiles rendered in usage in GPS Cycle Computer 4.12beta22.

For ease of comparison with testing in post 2294, the equivalent same area was rendered: /maps/europe/germany/nordrhein-westfalen.map

This provides another method of acquiring bulk tiles, whilst tiles remain necessary, in the interim until alternative map formats are supported in GPS Cycle Computer, such as Mapsforge itself as detailed in post 2294 part 5d.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Since MyBoot is limited to 5 applications, this seems to be a good alternative - I'll try it on my Medion S3857/S3867. cu - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Firstly, thank you for the 'thanks'. Much appreciated.

GCC Boot as at 1.0.0.alpha2, has 18 buttons in total. Prominent buttons 1 and 2 are intended for either GPS Cycle Computer or the Dedicated Device Native Application, whichever preferred, and both have an automatic time delayed launch option. (whereas alpha1 had that on button 1 only) In addition there are up to a further 16 user configurable buttons (whereas alpha1 had 12) Only user configured buttons are displayed.

GCC Boot is currently alpha simply because the intended feature set is incomplete. This means GCC Boot may change substantially at each new alpha and not be backwards compatible with itself. After the foreseen bulk of development is complete, it will become beta. After beta phase it will have a 1.0 final release. GCC Boot will be further developed as required from there.

GCC Boot is however stable in alpha and as safe to use as any other similar software. Refer to Instructions therein.

Currently, one feature being developed is to cater for users that require to change registry settings, and have to continually do so, as their devices do not retain them. It is intended GCC Boot will ultimately seamlessly and automatically import / merge to the registry any user configured entries in GccBoot.reg

Feedback is encouraged, welcomed, and appreciated. I look forward to your feedback with interest, as with that of all users, that take the time to contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
This would mean a big step, since WIN CE devices forget all user defined settings in registry, stylus cal., date, time, timezone, country ..., which at the time always has to be refreshed after cold boot. cu - WolWer

GCC-Boot works fine with Medion S3867 (WIN CE5) and overcomes the restriction of MyBoot - only 5 applications. Nomencature in ini-file are the same regarding path/file etc.
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
GCC Boot 1.00alpha3 integrates seamless and automatic registry import / merger on start up of any user configured registry entries in GccBoot.reg. It is available from updated post 2307.

Thank you for the feedback. I look forward to your further feedback with interest, as with that of all users, that take the time to contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
You should better start new thread if you like to develop new application..

For all the special device owners - you can always add GCC to system init in registry if you like to start it automatically after boot. But be very careful what you are changing in registry!
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
To address each part in turn:

GCC Boot compliments GPS Cycle Computer. This thread is therefore best suited at this time and there exists no reason or purpose to start another.

Windows CE5 and CE6 devices are not special. They are ordinary recent or current dedicated devices readily available and still in production. They are not therefore old devices either as you have also previously claimed. These issues have all been exhaustively previously documented.

The primary purpose of registry merge / import is for devices where changes are not retained in the first instance. As has been clearly stated previously on a number of occasions. The primary purpose of a boot menu is not to boot in to any particular application, but a menu from which desired applications or actions can be chosen.

Registry can be backed up, and restored, with the tools provided. Somewhat irrelevant where changes are not retained in the first instance.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] ElfKaa:
Application Autostart

For all who would like to autostart GCC on the device boot I created two simple scripts:

GCCAutostart.exe - this will add the registry key to your device to start GCC automatically after device bootup.

AutoRemove.exe - this will remove this autostart key (autoremove will always try to remove and will remove the key even if it does exist or not).

Note:

Not tested for all devices! Probably it will work for all.. But this program is changing registry, so you are using it on your own risk!
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Application Autostart

Alternatively, in brief, the usual methods ordinarily used to launch a single application, such as GPS Cycle Computer are below.

These are easy to use and remove, require no downloads, no changes of registry, using only the standard Operating System functionality provided for the sole purpose. They are accordingly safe to use requiring nothing other than what users already have.

Notably, for Windows CE, registry alteration would not be reliable anyway as has been repeatedly previously stated.

Windows Mobile: (Any version)

A forthcoming version of GPS Cycle Computer will offer short cut based automatic start, as previously documented, either at the time of installation, or as an option within GPS Cycle Computer, or both.

In the interim: The Startup folder was specifically provided by Microsoft as part of basic Operating System functionality for the sole purpose of starting applications using short cuts placed in the folder that link to the application .exe files. It was designed to enable ordinary end users to easily start applications without requirement of anything further than they already have.

In brief, the basic generalised steps are: Using Windows Explorer (or any File Manager), locate the desired application .exe file. Select create short cut, usually from a menu or context menu. Copy that short cut to the Startup folder (located at root, along with Program Files and Windows folders). The application will then automatically start each time the device is started.

To remove, simply delete the short cut form the Startup folder.

Windows CE 5.0 and 6.0:

The dedicated device native application .exe is simply backed up and replaced with that of the desired application and renamed the same.

To remove, simply restore the original .exe file.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, low.flying pigs! I know, how to change registry entries manually with registry editor, but what I've got to enter via GCCBoot.reg to alter existing registry entries, e. g.

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Touch

Name Type Data:

CalibrationData REG_SZ 513,997 322,1352 311,717 704,509 700,1364

MaxCalError REG_DWORD 32

As far as I understand, it should be like this:

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Touch]

"CalibrationData"=SZ:513,997 322,1352 311,717 704,509 700,1364

"MaxCalError"=DWORD:00000032

Am I right? Thanks a lot - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
GccBoot.reg is standard REGEDIT4 format.

It is important to note that the standard requires for all .reg files that the first line must be REGEDIT4 followed by a clear line before the first entry. A clear line after the last entry is also required. A clear line is a line that is present, but with nothing on that line.

In this instance a missing REGEDIT4 followed by a clear line before the first entry is tolerated. A missing clear line after the last entry is also tolerated but a Syntax Error message will be shown, however the registry entries themselves will still be imported / merged.

An easy method of ensuring correct entry is to make the required change in the Registry Editor provided, and then export that entry as GccBoot.reg

Multiple changes can be similarly made and exported, and manually added to a single GccBoot.reg file. Notepad, or any text editor, can be used for manually editing / creating .reg files.

GCC Boot 1.0.0.alpha4 will include further documentation in relation to the Registry.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
I've found to different entries:

- general difference in usage of capital letters (I assume, that doesn't matter)

- in exported RegFiles is an "@" instead of "default"

Tomorrow I'll test the registry merge with S3857, where it is urgently required, specially because of severe deviation of preset stylus calibration data and actual calibration values. cu - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Thank you for the interesting feedback and the 'thanks'. Much appreciated.

Generally and briefly:

Windows registry (in any Windows Operating System) names are not case sensitive. Where there is capitalisation it is usually only for the purposes of human readability.

If there is a registry entry that does not have a specific name, registry editors often will show the word default, sometimes inside brackets, as the name. When such an entry with no actual name is exported, the export shows @ as the name.

This behaviour is part of the REGEDIT standard. It can be observed on other Windows systems, such as Windows XP SP3 and the included standard Microsoft Registry Editor 5.1 which uses REGEDIT5 standard.

I look forward to your further feedback with interest, as with that of all users, that take the time to contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello,

attached the pre release beta23 of the final 4.12 version of GCC.

Please have also a look on the documentation Readme.htm in the cab.

Improvements in advance to beta22:

- battery display in map improved

- copyright message in map (place a file "copyright.txt" with the message into the top folder of the map folder)

Regards, Klaus
[Touch Diamond, MDA Compact IV General] WolWer:
@ blaustein: Thanks a lot for new version. Regarding cr-overlay in map view: copyright.txt as required can be provided within maps folder for download.

@ low flying pigs: Something's wrong with registry merging: Also when reducing GCCBoot.reg to

[HKEY_LOCAL_MACHINE\Hardware\DEVICEMAP\Touch]

"MaxCalError"=dword:00000020

(blank line present at the end!) every reboot of S3857 (WIN CE5) results in "Win32Exception". This may be acknoledged by ok-Button, but nothing happens - til SR or HR, producing the next "Win32Exception". cu - WolWer

p s.: complete GCCBoot.reg attached
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Thank you for the interesting feedback and your attached GccBoot.reg file.

I am somewhat limited in the testing I can do at the moment but will investigate your specific issue and error described fully when I return from a short break.

I do however note that the first line of your provided file is a clear line. This is incorrect. It may be this is not tolerated as when both REGEDIT4 and the following clear line are both missing as detailed in post 2317.

For standards compliance, the first line must be REGEDIT4, the second line must be a clear line, and the third line must be the first part of the first registry entry, in this case [HKEY_LOCAL_MACHINE\Hardware\DEVICEMAP\Touch]

The attached contains these changes already made for ease of testing. Just extract and place in the same location as GCC Boot.

If this does not resolve the issue, it would be useful if you could confirm:

Does the GccBoot.reg test file provided with GCC_Boot_1.0.0.alpha3 successfully import on your device?

If so, using the provided registry editor, there should be HKEY_LOCAL_MACHINE\System\Test\01, HKEY_LOCAL_MACHINE\System\Test\02, and HKEY_LOCAL_MACHINE\System\Test\03, each with 10 entries as per the file.

If not, what happens? Also:

Does GCC Boot 1.0.0.alpha3 start without error when GccBoot.reg is removed?

It would be further useful to know if there is any difference in behaviour between the S3857 and the S3867.

It can be confirmed all GCC Boot functionality is tested working before release in both Windows CE5 and CE6 Emulated Environments.

Additionally, there may or may not be an issue with the syntax of the string values in the file your provided. However I cannot test or confirm that at the moment until I return.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Ouh, **** - I didn't care for your post #2317, but only to GCCBoot.reg and Instructions - English.txt included in GCC_Boot_1.0.0.alpha3.zip - where this detail isn't present. Adding REGEDIT4 and blank line to GCCBoot.reg improves restart (no Win32Exception), but freezing with hourglas-symbol, which can only be overcome by hard reset - soft reset doesn't work at this stage. I'll check this issue by consecutively removing entries from GCCBoot.reg and report result. cu - WolWer

Checking on S3857: Removal of HKLM\Time from GCCBoot.reg => Win32Exception. Same on removal of other sections: Boot stopped, SR required.

Checking on S3867: Win32Exeption. Acknowledging with ok => boot continues successfully, but there are no changes made in registry. GCCBoot.reg as supplied with zip-archive (REGEDIT4 followed by blank lin added): Win32Exception. OK => boot continues, but no entries "test" are found in HKLM\System
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, Blaustein!

copyright.txt (contents "(c) OpenStreetMap contributors" as required by OSM) is to be seen in map view, but extrem small and in line with track informations at bottom. Would be better situated on top beyond scale - same colour and figures hight. cu - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Modified and replacement 4.12beta23 GpsCycleComputer.exe

Attached:

Modified and replacement 4.12beta23 GpsCycleComputer.exe

Sample copyright.txt with the attribution © OpenStreetMap contributors.

Screen grab demonstration of the above using map created with the MOBAC integrated mapsforge renderer detailed in post 2306.

The modified beta addresses several issues which combine to create the impression the copyright.txt copyright attribution text is not displayed. It is displayed however it is obscured. It further addresses a separate issue of lack of copyright.txt support for the © copyright symbol in the copyright attribution text.

As a single character instead of three, the © copyright symbol is preferable to (C) as it uses less screen space and is of tidier appearance. It is typed by holding down the ALT key, and whilst doing so then typing 0169, and then releasing the ALT key.

Changes:

copyright.txt copyright attribution text colour as per user map label colour preference.

(because previously as per map background colour)

copyright.txt copyright attribution text repositioned top right below tile information.

(because previously hidden behind any bottom buttons or info fields)

copyright.txt copyright attribution text resized as per other map label text.

(because previously small text)

copyright.txt copyright attribution text support of © copyright symbol.

(because previously not displayed even if correctly present in file)

On tap coordinate information repositioned below copyright attribution text.

(because was previously below tile information where copyright attribution text is now positioned)

This modified beta is in all other respects identical to standard 4.12beta23 and source code of changes is below.

It is provided in the interim until 4.12beta24 officially addresses the issues, and implements the additional copyright attribution measures required detailed in post 2321.

Source Code:

MapUtils.cs line 873 was changed to:

sr = new StreamReader(crFile, Encoding.UTF7);

MapUtils.cs line 2053 was changed to:

g.DrawString(clickLatLon, drawFont, drawBrush, ScreenX - size2.Width - 2, size.Height + 30);

MapUtils.cs lines 2331 to 2334 were changed to:

Font drawFont = new Font("Arial", 8 * parent.df, FontStyle.Bold);

SolidBrush drawBrush = new SolidBrush(mapLabelColor);

SizeF size = BackBufferGraphics.MeasureString(mapCopyright, drawFont);

BackBufferGraphics.DrawString(mapCopyright, drawFont, drawBrush, ScreenX - size.Width - 2, size.Height);

low.flying.pigs
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Thank you for the interesting feedback. I have now been able to conduct some further testing.

The GccBoot.reg provided attached to post 2323 imports / merges using GCC Boot 1.0.0.alpha3 fully and without issue when tested on

Windows CE5 and CE6 Emulated Environment and on Memory-Map™ Adventurer 2800. Windows CE 5 based. This shows import / merge and the .reg do work in the right circumstances.

I have a suspicion of some potential issues that may be causing your problems. It would aid troubleshooting and confirmation if you could do the following on S3857 and S3867:

Remove any GccBoot.reg from the location of GCC Boot, to stop it trying to import / merge on startup.

Place the GccBoot.reg from post 2323 in the GccBoot_Tools folder so it can be easily located.

Restart and from GCC Boot, using only the registry editor provided (with GCC Boot 1.0.0.alpha3 in the GccBoot_Tools folder) from the menu via 'File' > 'Import Registry', attempt to manually import GccBoot.reg from post 2323

Advise results.

I look forward to your further feedback with interest, as with that of all users, that take the time to contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, low.flying.pigs! GCCBoot.reg (without REGEDIT4 <return>) was imported successfully on both devices with tre.exe as described in your post - same with my special GCCBoot.reg for S3857! cu - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Thank you for the interesting feedback.

As that test was successful, it would be useful if you could perform the following test for confirmation purposes on both S3857 and S3867.

Ensure your user entries in registry are removed, so as to not confuse testing.

Temporarily remove GCC Boot. Replace with MyBoot previously used. Ensure a File Manager is a configured button.

Copy GCC Boot 1.0.0.alpha3 in full, including all files and folders, to a folder on the device.

Copy the GccBoot.reg from post 2323 that includes your desired entries to the GCC Boot folder from above so it is in the same location as GccBoot.exe

Restart the device. It will now boot with MyBoot.

Using a file manager, go to the GCC Boot folder and run GccBoot.exe which will then attempt to import / merge your desired entries in GccBoot.reg and then show the menu buttons page.

Using only the Registry Editor provided with GCC Boot, check your entries have been successfully imported / merged when GCC Boot 1.0.0.alpha3 was run as above.

Advise results.

I look forward to your further feedback with interest, as with that of all users, that take the time to contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
Hi, low.flying.pigs! I've perfomed test as described in your post on S3867. Result: Win32Exception, on acknowledging with ok GCCBoot.exe starts with GCCBoot.ini supplied with. No changes in registry were made.

I avoid testing with S3857, since deviation of stylus calibration data stored in original registry difer that much from that required, that it's very difficult to get it back to proper operation (first two entries in my GCCBoot.reg). cu - WolWer
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Thank you for the interesting feedback.

Attached for your testing in attempt to address these issues ahead of 1.0.0.alpha4 release.

GCC Boot 1.0.0.alpha3 Mod 01 modified and replacement GccBoot.exe

Kindly advise results.

I look forward to your further feedback with interest, as with that of all users, that take the time to contribute.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] WolWer:
S3867: :confused: "Pre Registry Import / Merge Integrity check failure. Aborted due to GCC_Tools folder detected as missing or incomolete. For correct operation ....." Ok, GccBoot_Tools folder is now essentially required, containing tre.exe and cecmd.exe. Both files in root of MFD as menu.exe (resp. GCCBoot.exe) is in this version not sufficient. On HR and SR all entries in GCCBoot.reg are successfully merged to registry:good: - cu WolWer

p. s.: Tested on S3857 too: On both SR and HR entries from GCCBoot.reg were merged to registry. Thus I don't have to be afraid of an HR any more! Thanks a lot, low.ffying.pigs!
[Touch Diamond, MDA Compact IV General] WolWer:
@ Blaustein: a "nice to have": button for screenshot, I'd suggest to place it in the bottom bar in all views! Tx & cu - WolWer