Related

birdseye still growing on C drive and taking soo long to be able to use on mSD

Former Member
Former Member over 10 years ago
Every time I connect my montana which has a mSD card inside, which itself has BE images on it.. the PC will take about 1 hour doing something while reading the contents of the mSD card. during which time I cannot do anything with the contents of the mSD..

the PC must be storing the BE images on the C drive "again".. because along with the long wait also I lose another 10-15GB of space on my C drive whenever I connect it.

"THIS IS RIDICULOUS"... I put a case here on this forum in 2012 (username seedee) when it first started to annoy me.. no one answered, now it is beyond a joke.. Hello are you listening GARMIN...????

How can I delete some images and regain my C drive space..? which is basically now being eaten up by BE and wasted.. it would not be so bad if the image quality was good, but the areas which I downloaded (empty quarter desert) are rubbish..

C:\Users\CDADMIN\AppData\Roaming\Garmin\BaseCamp\JnxFiles is more than 200GB
C:\Users\CDADMIN\AppData\Local\Garmin\BaseCamp\TileCache is over 40GB
C:\Users\CDADMIN\AppData\Local\Garmin\BaseCamp\DeviceCache is over 40GB

what sort of software is this..? you can not move the BE files, you can not save them in a different directory at installation...

this is just not good enough..
CD
  • Former Member
    0 Former Member over 10 years ago
    It is something we need to change...


    Thanks for looking into it.

    . o O (Programmers always open files for r/w access even if they only intend to read them :D)
  • Former Member
    0 Former Member over 10 years ago
    This is because we try to write a simple text file on the card that contains a "unique id" for that card. If we fail to write that, we'll treat the card as if it is new each time.

    In the short term, you can make the card writable and allow BaseCamp to create this file. After the copying completes, then you can make it read only again.
  • Former Member
    0 Former Member over 10 years ago
    Thanks for the further information. You're trying to see if the card is writable not just if the .jnx files are. Got it.

    This can only be an issue if one uses their microSD card (what units accept) in an SD adapter in a card reader on a computer. microSD cards don't have a write-protect switch but SD cards, and adapters, do.



    FYI the write-protect switch on cheap cards/adapters can sometimes operate intermittently and some cheap card readers can have issues with it as well.

    PS: If one uses a removeable drive as a "clone device" and it's formatted with NTFS the same issue could arise if file system permissions don't allow full access to the card. That isn't applicable to cards using the FAT or FAT32 file system (which they must to be used in a unit).
  • Former Member
    0 Former Member over 10 years ago
    To answer the question, no. The card was in R/W mode when I did my test. Every time you connect the GPS, it would copy all of the JNX files to a new devicecache folder. I'm not sure if this matters, but the Birdseye images in question were not installed in Basecamp on the computer used for the test.
  • Former Member
    0 Former Member over 10 years ago
    In my case
    1. the mSD was inside the montana, so write protection was not possible
    2. the BE maps have originally been installed on C drive back in 2012, then 'sent to' a variety of mSD cards, which now I am trying to add waypoints and tracks onto.
    3. the mSD cards already have the "ID file" on them, as they have already been populated with BE, tracks and WP's for quite some time now

    cheers
    CD