Jump to content

jinj

Members
  • Posts

    49
  • Joined

  • Last visited

Everything posted by jinj

  1. How can you be "forced" to litter. Like when I'm drinking something in the car and then all of asudden I spill the coffee on me, I'm burning and both of my cup holders are taken, in order to clean up the coffee I have to get my napkins. So I threw my coffee out the window to stop the burn... Yes, things like this happen about twice a year... Wow, just wow. Wow. Terrible.
  2. The 2 axis compass isn't really usable. Go for one of the 450/450T/550/550T/Dakota20. These all have the 3 axis compass.
  3. Avoid the 400T, the compass is useless.
  4. Transfer/sync using bluetooth, works ok for me. USB won't work.
  5. Can I copy my built in topo map from my 400t and put it in a 450 (none t)?
  6. I find the 2D compass in the 400t Oregon to be terrible, is the 3D version that much better? Is the 3D version very usable?
  7. Use a 8GB card in the 400t, so it should work. Now using the whole 8GB space is another matter.
  8. Whats wrong with the compass? Its terrible. If you want an Oregon with a good or better compass, get the 550t or even the Dakota 20.
  9. I have the Oregon 400t, the touch screen isn't the greatest thing on it and the compass is horrible. I have seen the Colorado 400t screen and it looks so much clearer, it'll get no finger smudges either, no touch membrane that makes it look cloudy all the time.
  10. I might 'upgrade' mine to the Dakota 20 though, as the current compass in the 400t is junk. I should've just got a Oregon 200.
  11. It still crashes on shutdown with an active route when powered by USB, never did that in 2.99
  12. Its too small, and the compass in general is pretty poor. It keeps saying hold it level, even though its on a flat surface.
  13. I have the same one. http://www.newegg.com/Product/Product.aspx...N82E16820211351
  14. Works fine for me too. The shutdown screen is rather strange, but I have seen that sometimes before, just not as bad. The map selection works well now, I wish the file name was listed below the map titles, there is room.
  15. Thanks! I didn't think or know about the 429 for the builtin Topo.
  16. Actually I'd be quite happy with 6 hours to build a 3000 segment map. I've seen times in the 20-30 hour range to build map sets with close to 4000 segments. The time to build a mapset gets exponentially higher with more segments. It has very little to do with the size of the maps other than the time to transfer the maps to the GPS/SD card. Just finished building the 3700 map segment, its estimates are way off, it says 6 hours, but it really means 16+ hours, it just doesn't count very well. Also, when powering on the GPS, it takes a minute or two, the status on the screen says 'loading maps' When it has loaded up, the City NT 2008 maps (64 maps, 1GB) I loaded previously to the internal 400t's memory isn't selectable, even though it is there. Only the maps in the uSD card were visible, along with the included internal topo. So, all in all, not good.
  17. No it's not normal. My laptop (2ghz dualcore) needed 20 minutes for 2gb map (building and transfering it). And that was a few maps (topo and routable). How many segments did it have?
  18. Also put in an 8GB uSD card (A-Data, works ok), currently building a MapSource collection of maps, it says there is 3700 in the selection I made, mostly Ibycus and WA Topo. 3.3 GB file size. It is taking almost 6 hours to build the map set, is this normal? I have a Core Duo 3Ghz and its really only using a single core.
  19. When you get it back, back it up to a dvd or your PC at the very least. Its kinda funny how its just so easy to delete.
  20. I created two map sets with mapsource, different US states city nav '08 data, sent a few states to the uSD card and a few to the main memory. The device joined them up into one single map in the setup/map selection. So I guess this wouldn't get by the limitation, unless I used the '08 map for some and the '09 map for some more. How in mapsource can I see the segment count?
  21. A map segment is a segment of a larger map. [] You don't control the size, unless you are the one creating the map. From this one can infer/deduce that the Topo maps loaded on the Oregon 400t are 429 segments/tiles in size (about 2.6GB file size). The Topo 2008 DVD as over 6000 segments/tiles (and over 4GB space needed) Good info, thanks. If these are per map then, can I for example load the Topo 2008 Dvd map into two different map files, splitting it?
  22. What is a map segment? How do we control the size? What is the limit on a 400t? I know a map's max size if 4GB.
  23. If its 64 bit Vista, you need to sync over bluetooth.
  24. The REI sales guy told me the 400t has greater detail than the topo 100k maps, I don't know if thats true. Well o got my info from the same place and wonder if it is valid. So did you get yours during the "Big Sale" as well??. Yep, The sales guy also told that the 400t has greater detail in the national parks too. He seemed like a big 400t fan, knew what he was doing with it. Maybe he was right. Also I think the 24k maps are routable, so that could be an advantage of the software you bought.
×
×
  • Create New...