WaldenRun

Non-hiders know one thing. If everyone played the game the way they do, there would be no game. If they can live with that, so can I. -WR

Anyone trying to access WaldenRun's gallery from his profile page receives this error message: ====================== Server Error in '/' Application. -------------------------------------------------------------------------------- Item has already been added. Key in dictionary: "64332" Key being added: "64332" Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.ArgumentException: Item has already been added. Key in dictionary: "64332" Key being added: "64332" Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ArgumentException: Item has already been added. Key in dictionary: "64332" Key being added: "64332"] System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) +931 System.Collections.Hashtable.Add(Object key, Object value) +11 Groundspeak.Web.Gallery.GalleryImageList._FillData(DataSet& GalleryImageData) +301 Groundspeak.Web.Gallery.GalleryImageList..ctor(DataSet GalleryImageData) +83 Groundspeak.Web.Gallery.Gallery._FillImageValues(DataSet& GalleryImageData) +73 Groundspeak.Web.Gallery.Gallery..ctor(Int64 GalleryID, ImageDataSources ImageDataSource) +231 Geocaching.UI.GalleryControl.get_Gallery() +301 Geocaching.UI.GalleryControl.DisplayGallery() +18 Geocaching.UI.ProfilePanel.btnGallery_Click(Object sender, ImageClickEventArgs e) +279 System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +109 System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +71 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain() +1315 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573 ====================== Thanks, WaldenRun

Do you have an example cache we can look at? I used GCJ4EY as a text case and do not see any issues. The listed coordinates are: N 42° 43.889 W 071° 02.279 1) I clicked on the "Topo Zone - topographical maps" link 2) For the "Coordinate Format" I chose "DD MM.MM" 3) For the "Coordinate Datum" I chose "WGS84/NAD83" The displayed coordinates atop the map are: 42° 43.89'N, 71° 2.28'W They are rounded off but look correct to me. -WR

Looks like a fine recovery to me. Now you are ready to find one that is not "PROJECTING 6 INCHES", but rather "6 INCHES BELOW GRADE"! -WR

Taking a break from hunting and creating a quality cache yourself may renew your geocaching spirit. Search out a nice walk (or hike) that brings you to an inspiring site. Pick a theme and fill one of those ammo cans to the brim with things that you want to keep for yourself. Post the cache and read the admiring logs as they roll in. Whatever you do, don't hide a micro someone can drive up to. -WR

I found the log of SOMEONE who made an actual find using their metal detector. -WR

I'm showing it about 25 feet down the slope from the trail atop the berm. Looks to be in a clump of vegetation growing up from the ditch. -WR

Here are the Jeeps that went to Maine (courtesy of Brdad): -WR

I agree. Yoy have pictured a mark that is in "poor condition". -WR

True story. -WR

Yes, and then you hope you have a local cacher who goes overboard and gives you one of these: -WR

Usually it is just the FTF, but we went out of our way to pick up this prize: -WR

You could try making up your own laminated cards that have travel bug etiquette printed on them. If you find a bug that has no documention attached, add one of your cards. Also, I often put the TB into a freezer-quality ziplock and label the bag. Your real goal is to prevent future finders from losing the travel bug. The best way to protect the TB is to place it in a cache that most cachers won't bother going after. -WR

A pic from last week. Full suspension for these old bones: -WR

Yes, Berti is the nimble one. I believe FIVE states is his current count. -WR

I usually go for the simple, "Please let me know if my <TB name> travel bug has been lost. I would like to release a replacement if you do not know where the original is." The number one reason for dead bugs is that the current holder has lost it. -WR

Rumor has it that one of the bugs may be doing just that, going from Colorado to New Hampshire via the highways. -WR

As you'll recall, you did visit a couple of caches after you picked up the TB, but forgot to bring the bug with you. I can't see blaming that on the weather. -WR

I believe it is less usual here because most of our hilltops have exposed ledge and boulders. The disks are normally set into granite, making it VERY difficult to fix nails around them! -WR

I thought we were making a pretty standard recovery with three reference marks with arrows pointing toward the station. Hoever, we when got to the station, it was pointing back!: -WR

I would ask, "Should A Virtual Cache Trump A Phyical?" One of the first micros in MA was Proof of Concept. It eventually was archived after going missing. I was thinking about resurrecting it (via adoption), when I discovered a virtual had been placed 50 FEET (!) away. I decided the virtual should stand. -WR

1) U 2 - I Still Haven't Found What I'm Looking For 2) Beach Boys - Surfer Girl 3) Boomtown Rats - I Don't Like Mondays -WR

Well RJ, I found that cache before it was co-located. Normally, I would give you grief about the 2-for-1, but it seems my Sis is responsible for starting that trend! -WR

Ah yes, the infamous Hobo Haven cache. Let me see, what was the first line of my log for that cache? I remember now: "I would suggest changing one letter in the cache name." -WR

I picked up a similar FTF prize from a cache a while back: -WR