Thread: Lifetime Maps Terms & Conditions

I think that maybe the whole 'forward dating' thing somehow got away from them when they tried to sneak things forward a bit [in some parts of the World] and got caught up in their own web of attempting to deceive ppl into believing the maps were more advanced than what they are. We know that in fact CNs called 2014.x aren't really even 2013.x, they should be called 2012.x because the data isn't a year ahead [how could it be, and so who's gonna believe that anyway?], it's in fact about one year behind mostly. You are being way more than charitable dasil, when counting from 2000 [zero, 1, 2, 3 etc] where zero is actually the first number and therefore 13 is the 14th number ...? Sorry, but that's a bit of a crock. As to Giomen's mention of Christ's birth-date [year] being involved in this, well it's actually the other way around to the '14th year of the new millennium' because in those days there was no concept of zero as a number so Christ was actually born in the year 1 according to the calender that we now follow. So 'Y2K' was another big Crock in the sense that it wasn't really the start of the 3rd millennium, because it actually happened on 1st January 2001. The thing is that computers only know what the programmers tell them so as far as one of my old 16bit programs was concerned, on 1st January 2000 it was actually 1st January 1900. Anyway, if the guys who decided that Christ was born in the year AD 1 knew anything about maths, they would have called it AD 0 and we would now be in the year 2012. My head now hurts, so i need to cr@ck open a bottle of red ... the simple answer?: Garmin is so Garmin.

@kanopus
That first statement by Garmin quoted by me has nothing to do with the physical capacity of the unit's memory, only the second statement you quoted refers to that and so they are actually two different things entirely. The first is a legal statement only and that's clear if it's read in context. The second is both a legal statement and a forewarning that your device may not be able by itself to hold the required updated OEM map data even though it could originally hold the outdated/oem data. Even if it has the extra capacity, nothing more than the original OEM coverage will be loaded to the unit's memory during the direct update process after an LM NA has been purchased. That extra mapping loading has to be done as a separate second step from the PC's full NA gmap folder as i stated. If it's a 8GM unit there is no problem to also put that on the unit. The device i was referring to has only 2GB [1.76GB usable] and the base, time and lower 49 detail maps take up 1.52GB alone and there's another 435MB in AL/CA & MX. This is in contrast to a modern unit which has full NA as OEM but has limited memory, in that case the user will be prompted to insert a media card so that all data can be loaded. That doesn't happen with a lower 49 OEM device unless the lower 49 data in itself causes the overflow.