gpsrchive wrote: ↑Fri Aug 14, 2020 4:32 pm
You know how 'assumptions' work, right?
To see hidden folders and files on Zumo 595:
Zumo 59x - Enable USB Mass Storage Mode
• The zumo 59x uses MTP mode connection by default.
• MTP mode hides the .system folder.
• Follow the steps below to change the zumo 59x interface to mass storage mode.
• This will allow access to the system folder.
1. Touch Volume.
2. Touch and hold the upper right corner of the screen.
3. Touch Configuration and Settings.
4. Touch MTP Settings (you may need to scroll down).
5. Touch Mass Storage.
6. Touch Save.
Connect the zumo 59x to the computer and open the .system folder on the device.
You may have to revert to MTP for Garmin Express to again see the device for future updates.
Ok, I was able to get in there now, the "GUPDATE.GCD" file that is there is dated 07/27/2019, as a matter of fact, here is a list of its contents...:
Volume in drive H is GARMIN
Volume Serial Number is 22AC-746A
Directory of H:\.System
04/27/2015 09:05 AM <DIR> ..
01/01/1980 12:00 AM <DIR> RemoteSW
07/30/2019 12:28 AM 108,490 locales.xml
01/01/1980 12:00 AM <DIR> RoadsideAssist
01/01/1980 12:00 AM <DIR> Fonts
02/26/2016 12:01 AM 666 Credits.xml
01/01/1980 12:00 AM <DIR> EULA
01/01/1980 12:00 AM <DIR> BTM
01/01/1980 12:00 AM <DIR> ExtData
08/14/2020 11:35 AM 2,600 gmapprom.gma
01/01/1980 12:00 AM <DIR> SQLite
01/01/1980 12:00 AM <DIR> Map
01/01/1980 12:00 AM <DIR> JCV
08/14/2020 11:35 AM 25 gmapprom.unl
03/14/2011 07:43 AM 51,003,392 gmapbmap.img
07/27/2019 09:41 PM 34,677,734 GUPDATE.GCD
01/01/1980 12:00 AM <DIR> SID
12/31/2025 06:00 PM <DIR> Diag
12/31/2025 06:46 PM 559,417 manifest.txt
11/09/2017 11:47 PM <DIR> GPX
11/10/2017 01:37 PM 2,600 0879226634.gma
08/14/2020 11:40 AM 467 .express
07/04/2018 02:08 PM <DIR> Attribution_Logos
07/30/2019 12:27 AM 585,216 gmaptz.img
08/14/2020 11:38 AM 3,391,291,392 gmapprom.img
08/14/2020 11:39 AM 623,591,424 gmapdem.img
12 File(s) 4,101,823,423 bytes
14 Dir(s) 822,980,608 bytes free
As far as the MAP I told you about previously, it seems like when I updated this morning it created a duplicate, and that is the error on BC, but the device seems ok...