4MLA1FN

got gps. your "seats" link is busted.

i can see that hardware update would take a while to implement and certify. but for firm-/soft- ware, i don't necessarily see why it would be tough to get these suggested features happening on a faster cycle. it would be coolest if they'd "open" their architecture so we coders could write our own add-on modules and enhancements. this is the same model used in firefox to let users write their own extensions. just brainstorming.

you can still find CSNAv7 in places but it's getting harder. i recently did this search and can post a few links if you need.

i'm in denial too.

do you mean your manual said: GPS <15m (45 ft) 95% typical

etrex 'x' line manuals: vista cx: http://tinyurl.com/d77pv legend cx: http://tinyurl.com/7wtpm 24mb chip not present apparently. and definately no sirf in the etrex. must be coming later in the year. hmm. should i wait??

it does make me wonder, though, where the retailers got the idea that sirf was included. did they make it up? if i was a retailer, i wouldn't advertise specs i didn't get from the manufacturer. i wouldn't want the headache of angry customers returning product or accusing me of fraud when the product they finally receive doesn't live up to the initial marketing. i've noticed that some of the sites have a "specs subject to change" clause. others do not (amazon, gpscity, etc). maybe amazon and gpscity will get sirf-based units and the others won't.

just to be clear, it is still up for debate whether the 24mb internal will be used for track data. everybody wants it to do that, but it doesn't appear to work that way as yet.

i wonder if it'll be seamless with the card? for example, if i only want to load the southern ontario map from city navigator (which is 25.3mb), will it put the 24MB internal and the remaining 1.3MB on the memory card? hmm. it would be nice if the 24mb was used for tracks and the card exclusively for maps (or at least have it configurable).

a: everything i've read says that any microSD will work. garmin (from a quote posted on the a.s.g.g newsgroup) said that 512mb will work with it and that "most units that can use expandable memory can use up to 2gb cards". since garmin doesn't not currently provide these card sizes, on has to assuming they're using generic cards. b: i think that's a safe assumption. there's not much else to store; we know tracks aren't stored there (yet?). waypoints are likely stored the same as the non-x models (an internal set-aside memory). so it must all be used for maps.

and you know that this cannot be fixed with a firmware upgrade?? i don't know either, which is why i asked above.

significantly greater sensitivity and significantly shorter acquisition time. read this thread completely; i didn't know squat about it until i found this thread.

well, i place my pre-order, but through the US site (change the 'ca' to 'com'). they have no caveats like "specs are subject to change" and say twice that it has sirf3 so they must be pretty certain. we'll see.

dang. nice post. being new to gps, it is stunning how quickly the tech as improved. what will the next 4years bring. will we all be buying galileo devices?

maybe that could that be fixed with a firmware update??

whoa. could that be true? i'll wait until i see it on their webpage. i just returned a vista c i got for christmas because of the miniscule memory, so the x is appearing at the right time. sirf3 would be too good to be true.

i checked several online retailers and given how hard it was to find CSNAv7 (compared to the ease of finding CNv7), one would easily conclude it was indeed discontinued. some sites said it was discontinued; other didn't list CS at all but did list CN; e.g. http://www.gps4fun.com/gar_cityselect.php http://www.gpsnow.com/gmmscsna7.htm http://www.tigergps.com/sofdat.html http://www.thegpsstore.com/GPS-Software.asp http://www.safetracgps.com/road.htm and even if it was not officially discontinued, it was clearly being replaced by what most people would think was a better product. but the availablility or not of CSNAv7 is really besides the point that garmin recommends an add-on (CNv7) that cannot be fully used on their device, which by most definitions is fraud.

http://www.gpsnow.com/gmmscsna7.htm after seeing that and posts on a.s.g.g (alt.satellite.gps.garmin), i was prompted to look at cnv7. i then asked the guy at a highly recommended gps retailer which was better for the vista c: MG or CNv7. he suggested CNv7 because it had data that allows the unit to create its own routes (e.g. without a PC); MG apparently doesn't have this extra info. hence, i purchased CNv7. this has been a very disappointing first foray into gps where the manufacturer recommends an add-on that cannot be conveniently or even fully used. i have heard they may make smaller maps but how long do i/we have to wait? i'd heard their refactoring may only cut the huge pieces into about quarters, not tenths like city select. (CS region sizes were about 1MB; CN region sizes are on avereage 10MB.) for a limiited-memory device like the vista, the smaller the pieces the better. i'd also heard rumors of a soon-to-be-released etrex with SD slot. i'm packing up my vista c to return to amazon, and this rumor is the only thing that's keeping me from jumping ship to get a magellan explorist 600 or xl.

just a fyi. if you have a vista (24mb), don't get city navigator. i made this error over the holidays and i'm totally pissed at garmin and hope to get a refund from them. although garmin recommends CNv7 for the vista c, the CNv7 maps are *huge*; like 15mb per region. this means you can only load one region at a time. if you live on a boundary area like i do (washington dc/northern virginia) and you want to load enough to cover your local area (say a meager 30mile radius), you'd need to load three regions totalling 43mb. additionally, three of the regions are >24mb, so they're not even loadable on the darn thing. another (boston area) is 24mb. yet another (dallas) is 23.9mb. (for these last two, you gotta wonder how much, if any, room you'll have to store waypoints, routes, etc.) bottom line: CNv7 is just plain wrong for the low-mem units. CNv7 replaced the now-discontinued "city select v7" whose regions were 1/10th the size and was a much better fit for the vista, legend, etc. but that's progress for ya.