Team Batpony

http://lmgtfy.com/?q=GSAK&l=1

You'll want GSAK.

I have had SOOO much trouble with serial to USB converters... Just Google "usb to serial drivers" and you should eventually find one that works.

LOL ^^

I personally am new to geocaching. I never have very much time to go out caching, as I am very busy. I am looking for anyone's opinion on any of my hides. Here is my personal favorite of my 5ish hides. http://www.geocaching.com/seek/cache_details.aspx?guid=63327af9-e41e-49d6-bd4a-812e9f0e5c3d Sometimes I feel bad about having 5ish hides but 45ish finds.

You must go to the cache page on geocaching.com and then click "Log Your Find" in the upper right hand corner. Select whether you found or didn't, choose the date, and add some comments.

The OT forum is PMO? I thought it just didn't show if you were logged out...

The OT forum is PMO? I thought it just didn't show if you were logged out...

ok thank-you for your advise, i will stay as i am probally. 1) I use a smart phone to search and this has every feature if not more than any GPS unit the only down point is battery life but i carry a charged spare normally. 2)I have over 300 caches within a 10 mile radius of me that are open to basic members and am only missing out on about 20 that are only open to premium members. so as you see I can't see a reason to subscribe to premium and really was looking for a trial to give it a chance to prove to me it would be a good idea.. The only reason premium members are premium is not premium caches. One of the main reasons for me and for a lot of others is PQ's.

How about something much more simple. To verify your find, you just have to take a picture of the logbook with your name and the previous finder's names and upload the picture with your log.

Go to the cache page and look at the logs.

We go to wal-mart to get our camo tape. They have it with the duct tape.

Probably.

SUCCESS:

A challenge cache requires that geocachers meet a geocaching-related qualification or series of tasks before the challenge cache can be logged. Waymarking and Wherigo qualify too, of course. The additional qualification or tasks are considered the basis of a challenge cache, rather than Additional Logging Requirements (ALRs). Challenge caches vary in scope and format. All challenge caches must be in the affirmative and require that something be accomplished. Challenge caches are listed as Mystery/Unknown cache type. Challenge cache owners must demonstrate that the challenge is attainable. Reviewers may ask the cache owner to demonstrate that they have previously met the challenge and/or that a substantial number of other geocachers would be able to do so. Importantly, cache owners must consider how they will substantiate claims that the challenge has been met. The logging requirements on the cache page must reflect this consideration, and must be logistically viable. Challenge cache owners may also be asked to outline a long-term cache maintenance plan. Some points to consider when creating a challenge cache: Challenge caches must contain the word "Challenge" in the cache name. It is generally considered "bad form" to log one's own physical cache. A challenge cache concept that severely limits the number of cachers who can achieve the challenge will likely not be published. A challenge cache based on one or more non-accomplishments, such as DNFs, will likely not be published. Challenge caches may not require the publication of a new cache as a logging requirement. Challenges must be achievable by those who do not own caches. Challenge caches may not require cachers to log caches that are disabled or archived. An individual's attempt to complete a challenge should be independent of the actions of other cachers. A challenge is supposed to recognize the completion of an achievement, rather than the winner of a competition. For example, a challenge based on "First to Finds" is dependent on the actions of other cachers, is a competition, and cannot be verified, so would likely not be published. Requiring cachers to find an explicit list of caches (rather than a broader category of caches) will likely prevent the cache from being published. Using a challenge cache to promote one's own caches will likely prevent the cache from being published. The challenge cache must be findable without needing to email the owner, either by posting the true coordinates or by posting instructions for a puzzle or multi-cache. Cache owners are reminded that some caches may appear to meet the listing requirements, but reviewers as experienced cachers may see additional concerns that a cache owner may not have noticed. Consequently the cache page may not be publishable. As with all caches, each challenge cache is reviewed and published or denied on its own merits. Some grandfathered caches do exist which would not be published today. Taken from Geocaching. com on Challenge caches i meant http://geocaching.com/challenges/ not challenge caches. Thanks anyways!

What are they? I havent been able to check them out due to the site being down. And why does everyone seem to hate these challenges?

Breathe in, breathe out. Breathe in...

This is just what I keep getting... Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off". <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration> Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL. <!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

I think they need a better server to handle all the new "features"...

I just get the "connecting... connecting..." in my browser when I try to load gc.com.

Can someone tell me what they DID to the website??? It's ugly []

May I ask why you need permission to use the web address? Web addresses are public, almost anyone can access them, I just don't get it. That's like saying you need permission to, say, wear a Coca Cola shirt, am I right?

A simple sticker with the Geocaching logo and maybe the cache name should do.

No biggie, we all make mistakes. Hey, did you ever get the axe to get that cache out? (thread from the Canada forum). Nope, I never got the axe. Another geocacher in my area had the idea of using a loooooong pole...

Grrr I am so sorry, and stupid. I did not realize that was a multi. When searching for nearby caches, I just checked the distance, and not the cache TYPE... Lesson learned.