simplysup

I believe there may be longer than usual delays in place. I triggered a PQ this morning (one I haven't run for over a month). It was 5 hours later that I received it. As the OP states, the usual delay is more of the order of 10 minutes, and frequently less. Hopefully this is a temporary issue: I'll wait and see what happens to other PQ's I trigger.

Behind drsolly is an admirable place to be, I'm sure! Thanks for the update.

I'm sure I should be on there somewhere..

Hi, I was (and I guess Delta68 was as well) referring to two large series in the South of England, see GC1JZKT and GC1PP7F. Nothing to do with Mega Events.

Yup, I find myself facing that difficulty. Most of my caching is series, and where a series is more rememberable, for whatever reason, I'd like to acknowledge that. Series like the UK Mega, Mega 2, Chiltern Hundreds, all (for me) fall into this category. I'm tempted to fav-place (my preferred verb, I just don't like "favoured"!) the last in such a series, as that's where, usually, the logs are fuller, and aren't c&p'd, so people get a good idea of the series.

Whilst I can't help thekennelat79 with their issue (sorry), I am glad I found this thread. Three Garmins, three extra months - thanks!

After a recent (I can't remember which) software update, Garmins which have the Geocaching profile selected would not display the Man Overboard (and a couple of other) menu icons - at least, they don't on the Oregon 550t and Dakota 20 I have. The fix is to go to Setup > Main Menu. Scroll to the last page and you will see the menu icons there, greyed out. Select each in turn, and put it in a different place, and they then become - and will remain - activated, as will the replaced menu items.

Red frilly knickers: size 16.

Copy & pasted logs which are paragraphs long. Really annoying when you're checking previous logs out on the trail.

Hi, I don't contribute much to these forums but feel honour-bound to reply to this topic, as I was the logger in question. The cache diff was 1.5, so not designed to be a tricky hide. The log previous to mine was from an experienced cacher(s) with 3700+ finds, who spent 20 minutes searching. I searched for a similar length of time, and there were only so many places it could have been. For anyone with doubts about my motivation in replacing the cache, it was indeed to save the CO a maintenance visit, but also to save the cache from being disabled for other finders until the CO could arrange to replace it. When you are finding up to a 100 caches a week, you don't bother replace a missing cache just to "keep the numbers up", as I think one or two might be suggesting or hinting at. This is something I've done a few times in the past, because I had previously seen a number of logs where other cachers have done the same: indeed, once or twice also allowing me to log a find on the cache so replaced, as the CO still hadn't been able to visit themselves. I've also had an instance, on the Weavers Way, where a cache had been replaced thusly, only for me to then find the original on my visit, so I realise the dangers involved in leaving a replacement. I acknowledge all the comments made in this thread, and the clear consensus that this was "a bad thing". I don't agree, and I would be - and will remain - perfectly happy for someone to replace any of my caches should they have gone missing, but given the sentiments in this thread it is not something I will personally do in the future. I must take umbrage with the statement "If so no wonder he has managed to find 5168 in 16 months. ". I am in the fortunate position of being able to cache whenever I want to, usually 3 or 4 days a week, and I cover a lot of ground - I am of course totally addicted to this game of ours! - so I take it as an attack on my personal integrity if someone questions the validity of my caching exploits. I have deleted the log in question. Nigel

Excellent guide, appears to have worked fine for me, thanks very much. One small point I noticed, when you initially start MapCToMapC, you need to edit the preferences to place a checkmark in the "Garmin Tile Control Screen" to allow this screen to appear when you write the Garmin custom map. Nigel

Has my location pretty nailed on.

I have resolved my issue. With the "Map Loading.." message showing, I clicked the Refresh button on Firefox's menubar, and the caches were loaded. From then on, accessing maps from other geocaches works straight away, no loading delay. The fix has worked for me on two different machines. Why - or how - it works, I have no idea, but others may want to give it a try. Nigel

I have resolved my issue. With the "Map Loading.." message showing, I clicked the Refresh button on Firefox's menubar, and the caches were loaded. From then on, accessing maps from other geocaches works straight away, no loading delay. The fix has worked for me on two different machines. Why - or how - it works, I have no idea, but others may want to give it a try. Nigel

Aha! So... I'm not going crazy! I saw the same thing. I set it to 1.0.1 yesterday, clicked Save, and when I went back there just now, it was back to 1.0. Seems to be sticking now, at any rate. I had to do it twice to get it to stick.

Trying to use Google maps from both a single geocache (by clicking on the small map there), or by attempting a geocache search using Google Maps, the map fails to load the caches. The map appears, and can be toggled between satellite, terrain and map, but the message "Loading Map.." does not go away. The map can even be re-sized. Firefox 3.57 (and Firefox 3.5.4, on a machine I have not updated). The issue is OS independent, i.e. it is occurring (for me) on Vista Home Premium SP2, XP Pro SP3 and Windows 7 Ultimate. The maps work correctly using Internet Explorer, on all the above machines. Nigel

Yes I am having the same problem. Since yesterday's update. It must be a problem with Safari and Snow Leopard. Works fine on my daughter's Mac which has OSX 10.5.8. Firefox is ok with me too Firefox (3.5.7) is failing in the same way for me. IE (8) is working correctly.