Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Two files in folder ExtData appeared: what purpose they have?

bikepc01
over 3 years ago

Some weeks ago two files appeared in the folder ..\Garmin\ExtData on my Edge Explore (firmware 5.10), probably after synching through Garmin Express:
- 006-D0952-07.bin (38 KB)
- 006-D0952-08.bin (37 KB)

Somebody observed the same and maybe more important:
- what are these files and what is their purpose? Once there they remain in place.
- can or should they be deleted from the device, and if not, please explain why not so we can get some more insight?

Specially @aweatherall or @Garmin-Matthew have some clues?

  • 0 over 3 years ago

    I found this information:

    ExtData folder - stores 006-D0952-01.bin, 006-D0952-02.bin, 006-D0952-03.bin, 006-D0952-04.bin, 006-D0952-05.bin, 006-D0952-06.bin, 006-D0952-07.bin, 006-D0952-08.bin files which contains special font for not alphabet languages likes Herbew, Thai, Arabic.

    ExtData folder – also stores for some device with MTK chipset files ARC.BIN, BEE.BIN, 006-D1221-00.bin. 006-D1221-00.bin – GPS Chipset Type M HotFix Data software which updates by webupdater and ARC.BIN & BEE.BIN are files what stores current info for GPS software metioned above

  • 0 over 3 years ago in reply to ldpnl

    Thanks for this exhaustive list. Good info! So they appear to be font files for languages I have not installed on my Explore. Decided to delete the two files after making backup. We'll see if it harms - expect not.

    I've run both Webupdater and Garmin Express and the two deleted files are not re-installed. So question remains: why were these files copied to my device in first instance? Files date / time: 2020-04-25 09:06

    Correction:
    After detaching the Explore, powering down and attaching again (USB) to my laptop, Garmin Express did re-install the two files (2020-05-11 10:54). So they must be essential in some way or another. Or a bug causing this? Some explanation from Garmin available? - greatly apreciated!