Glenn

I don't own an eTrex 30 but I think I can give you few things to check. The specs say that the unit can hold up to 2000 Waypoints, favorites, and locations. I didn't see anything about geocaches so I assume with limit includes geocaches. You say that you have 1000 waypoints loaded. What about favorites, locations and geocaches? If the total is more than 2000 then this might causing your corruption. You say that you are noticing this after changing the batteries. Are you following the directions in the manual for changing batteries? Specifically are you turning the unit off before the batter gets too low. Using every bit of battery power and allowing the batteries to die in the unit can cause problems. You should be changing the batteries when the unit says that they are low. Don't rely on the unit to shut itself down. Also are you completely shutting the unit down before pulling out the old batteries. If the unit is on or in any kind of sleep or standby mode takeout the batteries can cause corruption.

I actually appreciate your defense of the CO, though I do find your fervor a but puzzling. You obviously haven't read back in my post history or you'd see that I no where near fervor level. I actually agree with you, so far. But we've only heard your side of the story. Don't misunderstand me. I don't think you are attacking the CO. It's just that he isn't here to defend himself. Does he even know we are talking about him? Typically there is little reason to get upset over a Need Archive log to the point of deleting it. It is just recommendation to the reviewer. It is the reviewer that then decides if Archival is warranted. Also the reviewer can see deleted logs. This means that while deleting a log removes it from the cache page it doesn't change the fact that review is going to see it. This leads me to wonder exactly what was said in the Need Archive log.

The CO said that the cache is there and that he is going to check on it. Are you saying that the CO is lying?

How can you be so sure that the cache is missing? The CO said that he is sure that the cache is still there. Experienced cachers are having trouble finding the cache. We know that thing can change at or near the cache location that can cause cache ratings to change over time.

That is exactly what I was thinking. ...Here were the facts at my disposal at the time: The cache is a 1.5/1.5 micro It hasn't been found in 7 months There have been 9 consecutive DNF logs by experienced cachers with 35,000 finds between them ... My caching buddy and I searched for nearly an hour, resorting to reaching and grabbing tools to dig into every place we could think of that might hold a magnetic micro As a last resort, I resorted to using a rather clever little magnetic field detector I have in my bag for locating magnets that might be unreachable, but were unable to find anything ... I agree with the CO's evaluation of his own cache. He should increase the difficulty rating. The log entries tell me that it is definitely NOT a 1.5D. I don't know what cache rating system he is using but by using the standard geocache rating system I'd give the cache at least a 2.5D and possibly a 3D.

This isn't a good solution when the cache owner is inactive and you don't know their status. This is because the cache owner isn't around to make an Owner Maintenance log and clear the Needs Maintenance flag. So now you have two options. You can ask a reviewer to get involved but they are already busy volunteering their valuable time publishing and archiving caches. You could just leave the NM flag set but that isn't good practice because then no one can be really sure which caches actually need maintenance or which have been fix or if a cache has been fix but now needs maintenance again or never got maintained and still needs maintenance. Eventually almost everyone starts ignoring the NM flag because it is now meaningless and if someone posts a NM log it gets ignored. The best options are to let the CO take care of the cache or work with the CO in taking care of the cache (you maintain the cache itself and they maintain the cache listing) or adopt the cache out to someone else or recommend it for archival.

I agree. I've (unscientifically) noticed a phenomenon in suburban America were some people are continuously pressure their neighbors to live and look and be like them. This is particularly strong in neighborhoods that have home owners associations. Diversity isn't celebrated there. In fact it's quite the opposite. If you don't or can't conform you are pressured both mentally and financially to move somewhere else. If a particular race is under represented in a hobby then so be it. There is no reason to pressure someone to be like us if they don't want to be.

Do you have a copy of the manual for you GPS? If not you can download a copy by clicking here. Page 12 lists two methods for getting geocaches on your GPS. The manual calls this Installing Geocaches. The 'send to GPS' method which uploads one geocache listing in the form of a .loc file at a time and the 'drag n drop' method which allows you to update multiple cache listings at once after you've created a pocket query and downloaded the .gpx file. I gave up on the send to GPS feature long ago. It's just to clunky for my tastes. Also there are practical reasons to use pocket queries over send to GPS.

Nobody's talking about forcing anyone. If we're going to go there, you could also say it's a waste of time and money creating programs to encourage more girls and women to study science? There are plenty of succesful programs out there that have reduced barriers and increased opportunity for certain groups. Okay, I'm game. The first thing we must do is identify the barriers that are preventing minorities from enjoying geocaching to same level that the majority does. What are the specific barrier that you see that are keeping minorities from geocaching?

That sounded like a software issue to me since you said both phone are the same model. I was going to suggest that maybe she downloaded an app that you didn't and it was that poorly written app and causing some problems. If it was poorly written it wouldn't even need to access the GPS functions to cause problems with them so it could be almost any app causing the problem. Then I did a quick internet search for Galacy SII GPS problems and found this article on the notaboutthenumbers website. "You may be the victim of something called disabled Static Navigation. Disabling Static Navigation is seen as a desirable feature that intentionally filters out apparently minor position updates once you are going at a low or slow speed. The idea is that your position will not be accurate anyway, due to the GPS signal being degraded by bouncing off buildings, being under trees or walking through a canyon. The weird thing is the phone’s GPS chip is still receiving updates and keeps calculating your position; it simply stops telling you." The fix involves rooting the phone and installing an app. The article has a link to the app and there are many websites that detail the rooting process. Just be aware that rooting your phone usually voids your warranty.

I used to use that app, but everytime I did, I would get emails saying my coords are off. How far did they say your coordinance were off and what size cache were you hidding? Even the best GPS units will provide a "worst case" pseudorange accuracy of 7.8 meters at a 95% confidence level. This is where the 30 foot accuracy that you hear about so much came from. For small or larger caches it isn't a big deal. It does come in to play when you are hidding micros. Especially if you provide no hints or poor hints.

I tried this in FF (my preferred browser) and it works as expected. When I delete an entry from my history sidebar it also resets the link color to the not visited color. I opened my IE9 and played around with it a little bit. You would expect that if you deleted a webpage entry from the history sidebar that it would also reset the link style to not visited for the pages you deleted. I don't use IE9 much but that sounds like a bug to me. I did a search in the bug reports for IE9 and nothing turns up so this odd behavior may be how IE9 is intended to work.

It's a better way and one of your Premium Member benefits. Read about it at http://support.Groundspeak.com/index.php?pg=kb.page&id=118. After reading about pocket queries let us know if you have any further questions.

Is there any reason why you are not using Pocket Queries?

Nope, that didn't do it. The only way I have gotten it to 'start over' is by using the deleting options in internet options/tools. I tried just removing cookies, still there, tried just removing temp files, still there, removed it from my favorites and then retried the same with no luck. I had to 'delete all'- THEN GC was 'reset'.- Thats what I was trying to avoid- I just was curious if even that would do it, so I had to try. It sounds like you already deleted all. But for future reference this is how to delete your browsing history according to the Microsoft website. Click the Tools button Tools button, point to Safety, and then click Delete browsing history. If you don't want to delete the cookies and files associated with websites in your favorites list, select the Preserve Favorites website data check box. Select the check box next to each category of information you want to delete. Click Delete.

Well, I sure hope that puzzle isn't still around, 5 years later. That isn't too difficult to figure out. The CO has only found 2 Unknown caches. It looks like both use digital roots as either the solution or part of the solution. Also clicking on 'nearby caches of this type' I found at least one other that uses digital roots. Looks like the digital root thing is popular in that area and once you have it figured out you can solve a bunch of Unknown caches there.

The only issue with rechargeable batteries that know of is if your GPSr doesn't have a setting for rechargeable battery. Alkaline batteries, rechargeable batteries and lithium batteries each have different discharge patterns. This doesn't mean that you can't use rechargeable batteries in your GPSr. It just means you can't trust the battery meter on the GPSr. What will happen is that your GPSr might start to inform you that the battery is extremely low when it really isn't or it might run out of power with little or no warning. The same thing happens on a GPSr that you can set the battery type on but forget to change it when you change battery types.

I totally disagree. Poor hints can tell a LOT about the hide. If I'm having trouble finding the cache and decode the hint only to see NO HINT NEEDED or ITS TO EASY FOR A HINT then I stop my search immediately. It's either a really easy cache that's gone missing or it's a poor hide. Either way it's getting a DNF and doesn't deserve anymore of my time. It is also a good way to screen out questionable caches in an area that you are unfamiliar with.

Both are good units. If you like Garmin then stick with Garmin. If you're satisfied with the Garmin brand then why change? If feel like it's time for a change then this might the opportunity to do so. But expect there to be a learning curve.

Sensitivity isn't a measurement of received signal strength. It is a measurement of signal to noise. The noise isn't environmental noise. It is noise that is generated by the amplifier in the receiver itself. A quieter (aka more sensitive) receiver will help with the reception of weak signals, most notably from satellites that are located near the horizon. It does not do a good job correcting for poor antenna placement or environmental noise. All things being equal, except antenna placement, the GPS/phone/device with the better antenna placement will be more accurate. This is because the other devices will not receive as many satellites and be subject to poor constellation geometry and may also be subject to more multipath signals.

That's sign language for lesbian, right? IIRC, He was trying to do a Dr. Evil from memory.

No. I really like the eXplorist GC. The eXplorist 310 is also highly recommended in these forums.

This results in a sencitivity issue (not accuracy). Of course, once the GPS signal is attenuated enough that you approach your sencitivity limit, accuracy drops. My Samsung Galaxy SII HD LTE is very accuriate, but not very sencitive. Under tree cover, it can not get updated coordinates. For someone who doesn't pay attention to their equipment, this could result in large errors. It is important to know the limitations of your hardware. No mater what GPSr you use, it will have limitations. Once you know them, you can work around them. I understand what you are saying but I think you have some technical terms mixed. In GPSr sensitivity and accuracy are related in that a unit with high sensitivity is better at receiving more satellites therefore increasing accuracy. Which as you said isn't the issue with mobile phones that are able to receive the GPS signal. The issue with antenna position is that if the antenna is a location were your hand blocks some of the signals then no amount of sensitivity is going to make a your phone "hear" the signals that aren't strong enough to get to it in the first place.

I see ignoring the situation and not acknowledging the cache thief as two different points of view. You don't want to ignore the situation but at the same time you don't want to directly acknowledge the cache thief. Putting on cache page "There is a cache thief in the area" is only going to feed their ego, if that is their motivation. I'd word it something like "This cache is frequently going missing". Although if cachers check the logs they will see this. Whatever their motivation it is best to just keep going on like everything is normal. Which it is because caches go missing all the time. Because of this there is a process for reporting missing caches and replacing them.

I like this idea but I wouldn't acknowledge the cache thief with a note on the cache page. I also wouldn't burden visitors to our area by asking them to help out. It is really up to the CO if they want community help in maintaining their caches. CO involvement is important because there are going to NM posts made on the caches and only the CO (and reviews) can clear the NM flag. What would be nice is if someone could contact all the CO in the affected area and see if we can't blanket approval, or at least a majority approval, to replace missing caches. Just don't forget to email the CO when you've replaced a cache, especially if the cache page has the NM attribute set.