Jump to content

TexasCacheCrew

+Premium Members
  • Posts

    28
  • Joined

  • Last visited

Everything posted by TexasCacheCrew

  1. Thank you both. Not sure which bit of advice did it, but my Oregon is up and loaded with caches again.
  2. The pocket query I've run and loaded on a weekly basis for more than a year failed to load on my Garmin Oregon 550 this week. I reloaded it with no success. I reran the PQ and loaded it with no success. The PQ loads fine on my wife's Garmin 62s and a borrowed Oregon 400T. As for the 550, I keep only one PQ on it. At most it will have fewer than a dozen GPX files on it at one time. And the PQ is for approximately 250 caches. The 550 started acting strangely last week. I turned it on, and the backgrounds changed to the factory settings and my customized icon listings had reverted to factory as well. I've got everything back the way I like it, except for the PQ problem. I've searched this site with finding anything covering this issue. I'm sure it's something simple that I'm overlooking. Doh moments are my middle name. Anyone have any ideas? Thanks.
  3. I am logging all of my visiting and everything from my Mac by going to geocaching.com. No smartphone, no tablet, no apps of any kind.
  4. My profile says I last visited on Feb. 17, 2012. But I have a 2012 Leap Day souvenir from the cache I logged today, on my Mac, while sitting at my desk, while at home. And that's not saying anything about my visit yesterday or the day before or the day before or ... . I must be invisible.
  5. To clarify my point: Your GPSr shows two caches ahead of you during your drive, one is 10 miles, the other is 12 miles. One cache is a 2/2 with a description that says "bison tube have fun." The other cache is a 2/2 with a description that says "bison tube in picnic area accessible from either direction." Which cache are you, the driver, more likely to stop for?
  6. Just back from a 3800-hundred-mile, 12-state road trip. We found some caches and passed up almost as many. The ones we passed all had the same thing in common: not enough information for out-of-towners. "A bison tube, have fun" doesn't cut it for travelers. Cache owners, please consider adding these tips in your cache description, especially if your cache is on or near a well-traveled highway. * Is the cache accessible to travelers going both ways or one way? If one way, which way? * If the cache is off the main highway, list which exit travelers should take. * Tell us if it's easy to get back on the highway. * Give us landmarks such as "just past the Chevy dealership," or "it's across the road from the Whataburger." Your efforts could result in more visitors to your cache. Thanks.
  7. Every time I really want my camera when I am geocaching, it's either at home or sitting in my vehicle. For anyone who has used the built-in camera on the Garmin Oregon 550s, how does it compare to, say, your average point-and-shoot? Or the typical cell phone camera? I don't expect DSLR quality, but I do expect well-exposed, sharp photos. Thanks.
  8. I had been dumping only the .gpx file from my PQs into the gpx folder on my Oregon 400t. Somewhere on this forum I read that I should dump the .gpx and wpts.gpx files in there. I don't see anything different after I fire up my Oregon. What am I missing? Why do I need both? Thanks.
  9. When I ran a "My Finds" PQ, it showed I somehow had found a cache in California – Laffy Taffy (GC1EVHH), now archived – when I have never cached in California. I happened to be in Nebraska that day, finding WW Laffy Taffy (GC1J65R). I can't imagine mistaking a California cache for a Nebraska cache, and my son was running PQs of caches along our route for that road trip. Strange, but I think I fixed it by deleting the California log and logging the Nebraska cache a year and a half later. Any thoughts?
  10. Howdy from Kerrville in the wonderful Texas Hill Country. The cachers here are quite creative and inventive, and they have put out a bunch of make-you-think, scratch-your-head, trust-your-GPS caches. NDgeojean and my favorite cache is "Right Behind the Bench," GC27G5K. As a side note, cachers here have put out 21 new caches within the past week. It's hard to keep up.
  11. I'm in the mood to replace my GPSMAP 60Cx with a new, paperless 62 model, but from reading this forum, it seems like they are not quite there yet. Am I missing something, or should I hold off until most of the bugs are worked out? What do 62s/st owners think? Thanks.
  12. It may be time to move up to a Garmin GPSMAP 62s. I love the ease with which I can use my Garmin GPSMAP 60Cx. I am hoping the buttons and menu functions are close to the same on the 62. Are they close? Or do I have a new learning curve to climb? Thanks.
  13. This was posted recently on the Central Texas Geocachers Yahoo Group's page: FTF Geocacher Magazine - Third Issue Updating the magazine status – the third of three trial issues has been sent to the printer and we have committed to continued publication beyond the trial period. Issue 3 will mail out in the next couple of weeks. Thanks to all who have supported our up-start magazine start-up!
  14. I am on my second Lexerd for my Oregon. The first one saved the screen from several knocks during a year-plus of hard use but took some blemishes in the process. When I decided to replace it, I easily peeled off the old protector. I also have a Lexerd on my Nuvi and am happy with it. All three Lexerds went on easily, and none gave me problems with bubbles.
  15. One of my travel bugs, TB29M60, was picked up in July of '09 by team of geocachers that joined GC.com in 2005. The bug remains in their possession, and they haven't logged on to GC.com since about two weeks after picking up my bug. I emailed a "gentle reminder" sometime in December and have not received a reply. Any suggestions? Since it seems to be the equivalent of lost, can I mark its location as unknown? Should I let it be? I have had bugs stolen, muggled and gone missing, but this is a new one for me. All ideas appreciated. Thanks.
  16. They have a point. A cache owner goes to a lot of trouble to find the right spot and pick the right cache type. Place it and submit it, then keep up with it only to lose it all because of a move too far away to continue the maintenance. Archiving a perfectly good cache to keep the numbers seems counter-productive. But losing the number because you're relocating doesn't make a lot of sense either. USCCouple's point and Caching Scout's suggestion have merit. And, yes, I am among those relocating and putting our caches up for adoption. Three already have gone away. .
  17. Just wondering the status of the armadillo coins. It's even spring in these northern plains. Thanks.
  18. Thanks so much for the quick answers. I did fail to mention that I am a Mac user, which limits PC options.
  19. I am considering buying an Oregon, but the screen is tough to see when I'm outside. Are there any tricks to better viewing? I was only able to briefly handle one in the sunlight. And toying with the backlighting wasn't possible. I did sort through all 17 pages of forum topics that had "Oregon" in the title with no success. Thanks.
  20. Being a Mac user, I can't use GSAK. However I just found a way to go paperless using PDF files. If they are still available since the update, I can't find a way.
  21. Thanks, Eartha. I hadn't thought of that.
  22. A cache owner notified me that they found the paperwork for one of my TBs in their cache long after the bug had moved on. Any suggestions besides hoping the bug's web page suffices on its goals? Thanks,
  23. A finder of one of my bugs sent me a note about where it was dropped off. I got that, but not the "dropped" notification usually sent when a bug is placed in a new cache. Until the problem is fixed, maybe that's a short-term remedy.
  24. Bismarck, ND 5 miles = 56 10 miles = 75 25 miles = 91 50 miles = 119 The drop-off is the city/rural difference.
×
×
  • Create New...