If you were Registered and logged in, you could reply and use other advanced thread options
Using previous versions of MapSource let me load 1952.7mb into my 2gb
cards but now after 40 minutes of building index files MapSorce 6.13.1
told me to lower my limit to 1936.9mb. Just to let other users know
what the limit is for latest version.
Jerry
Jerry M wrote:
That seem kind of strange. Are there some *.gpx files on the card or
something that may have reduced the available space on the card? If you
have the Log Track to Data Card feature turned on, you will have been
accumulating a *.gpx file for each day it was turned on.
Jack
--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)
This is not just a function of 6.13.1 - it was the same on at least 6.12.x.
If you convert the 2 GB card's capacity in bytes (2,030,960,640) into MB it
comes out to just under 1936.9 MB. And MapSource won't let you put a mapset
larger than that on the card. BUT - here's the odd thing. I built a mapset
that, according to the readout on MapSource, was just a fuzz under 1936.9 MB
and transferred it to the card. I then checked the card with My Computer and
it showed the .IMG file was only about 1880 MB, with about 55 MB still
available, and no other file on the card. Reloading the mapset into
MapSource still showed it to be 1936+ MB. Just for fun I tried a similar
test on a 1 GB card, putting as much as MapSource would allow into a mapset
(I don't remember all the numbers). Again when I checked it in the card
reader it showed a smaller .IMG file with about 20 MB still available. All
of which makes me wonder if MapSource purposely reports an artificially
large number in order to leave room on the card for things like tracks. And
will we ever know all the sneaky little things Garmin does to us just to
drive us nuts? Only The Shadow knows!
> Jerry M wrote:
>> Using previous versions of MapSource let me load 1952.7mb into my 2gb
>> cards but now after 40 minutes of building index files MapSorce 6.13.1
>> told me to lower my limit to 1936.9mb. Just to let other users know
>> what the limit is for latest version.
>> Jerry
>> cards but now after 40 minutes of building index files MapSorce 6.13.1
>> told me to lower my limit to 1936.9mb. Just to let other users know
>> what the limit is for latest version.
>> Jerry
> That seem kind of strange. Are there some *.gpx files on the card or
> something that may have reduced the available space on the card? If you
> have the Log Track to Data Card feature turned on, you will have been
> accumulating a *.gpx file for each day it was turned on.
> Jack
> --
> Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
> (also receiving email at jacker at midmaine.com)
> something that may have reduced the available space on the card? If you
> have the Log Track to Data Card feature turned on, you will have been
> accumulating a *.gpx file for each day it was turned on.
> Jack
> --
> Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
> (also receiving email at jacker at midmaine.com)
Cooter wrote:
> This is not just a function of 6.13.1 - it was the same on at least 6.12.x.
> If you convert the 2 GB card's capacity in bytes (2,030,960,640) into MB it
> comes out to just under 1936.9 MB. And MapSource won't let you put a mapset
> larger than that on the card. BUT - here's the odd thing. I built a mapset
> that, according to the readout on MapSource, was just a fuzz under 1936.9 MB
> and transferred it to the card. I then checked the card with My Computer and
> it showed the .IMG file was only about 1880 MB, with about 55 MB still
> available, and no other file on the card. Reloading the mapset into
> MapSource still showed it to be 1936+ MB. Just for fun I tried a similar
> test on a 1 GB card, putting as much as MapSource would allow into a mapset
> (I don't remember all the numbers). Again when I checked it in the card
> reader it showed a smaller .IMG file with about 20 MB still available. All
> of which makes me wonder if MapSource purposely reports an artificially
> large number in order to leave room on the card for things like tracks. And
> will we ever know all the sneaky little things Garmin does to us just to
> drive us nuts? Only The Shadow knows!
> If you convert the 2 GB card's capacity in bytes (2,030,960,640) into MB it
> comes out to just under 1936.9 MB. And MapSource won't let you put a mapset
> larger than that on the card. BUT - here's the odd thing. I built a mapset
> that, according to the readout on MapSource, was just a fuzz under 1936.9 MB
> and transferred it to the card. I then checked the card with My Computer and
> it showed the .IMG file was only about 1880 MB, with about 55 MB still
> available, and no other file on the card. Reloading the mapset into
> MapSource still showed it to be 1936+ MB. Just for fun I tried a similar
> test on a 1 GB card, putting as much as MapSource would allow into a mapset
> (I don't remember all the numbers). Again when I checked it in the card
> reader it showed a smaller .IMG file with about 20 MB still available. All
> of which makes me wonder if MapSource purposely reports an artificially
> large number in order to leave room on the card for things like tracks. And
> will we ever know all the sneaky little things Garmin does to us just to
> drive us nuts? Only The Shadow knows!
Thanks for the details, I've always been a little confused by the
numbers and the permutations on the numbers as far as media capacities
and it causes pains in my head when I try to sort it out.
For that reason I tend to not dig into it all much deeper than to make
sure there is enough room. But I use the track log and make sure not to
get a card too full for those.
Jack
--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)
> Jerry M wrote:
> > Using previous versions of MapSource let me load 1952.7mb into my 2gb
> > cards but now after 40 minutes of building index files MapSorce 6.13.1
> > told me to lower my limit to 1936.9mb. Just to let other users know
> > what the limit is for latest version.
> > Jerry
> > cards but now after 40 minutes of building index files MapSorce 6.13.1
> > told me to lower my limit to 1936.9mb. Just to let other users know
> > what the limit is for latest version.
> > Jerry
> That seem kind of strange. Are there some *.gpx files on the card or
> something that may have reduced the available space on the card? If you
> have the Log Track to Data Card feature turned on, you will have been
> accumulating a *.gpx file for each day it was turned on.
> Jack
> --
> Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
> (also receiving email at jacker at midmaine.com)
> something that may have reduced the available space on the card? If you
> have the Log Track to Data Card feature turned on, you will have been
> accumulating a *.gpx file for each day it was turned on.
> Jack
> --
> Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
> (also receiving email at jacker at midmaine.com)
Jack always when I reload maps in my 2gb cards I use my card reader
and delete the garmin folder in card so I always have nothing on card
when reloading.
Jerry
- problem with mapsource on a netbook?
- Garmin GPS
- 2011-07-01
- Mapsource version 6.16.3
- Garmin GPS
- 2010-10-27
- Archive of old versions of MapSource?
- Garmin GPS
- 2010-11-01
- Mapsource still shows old map... Help!
- Garmin GPS
- 2010-06-09









> cards but now after 40 minutes of building index files MapSorce 6.13.1
> told me to lower my limit to 1936.9mb. Just to let other users know
> what the limit is for latest version.
> Jerry