TheManInStripes

Thanks for all the info. While I do see that there was a change back in February, one of the caches in the vicinity WAS placed before that time frame. Again, I was just curious as to the reason why these were allowed to be placed so close. I think I got my answer, and it's all good.

Consider this: I also like to be FTF. I get up at 4:30 AM and drive 25 miles and then hike 1.5 miles to find a cache and be FTF. You found it the previous evening and didn't log it just to "mess with me". I discover your tactics and then track you down and remove your liver with a spork. It's ALWAYS a bad idea to "mess with people". Why would screwing with someone else's life give you pleasure? I don't know exactly where he lives but could probably find out and I'd be glad to tell so I could see a liverectomy with a spork. This is NOT a good idea. There are probably several reasons no one ventured to Portage to get this - like there were several others in Anchorage to get? I wouldn't drive the RT just for one FTF and I don't know many who would. Actually, there was only one other one in Anchorage that day, and it came out about 3 hours ahead of the Portage cache. That being said, I don't think I said anything about "messing with someone else's life." The liverectomy doesn't sound very appealing though either. It doesn't sound to me like people are very favorable about my idea though, and, that being said, I will most likely continue my normal practice of logging in a timely manner after my finds. I guess many of you people just don't have much of a sense of humor. Or maybe it's just that mine is a little more twisted then yours is.

If they're a FTF Hound like me, time and gas money aren't really an issue.

OK, I imagine this thread will raise a little bit of contention within the board, but I'd like to have it anyway. I admit that I like to try and be FTF and will sometimes go to great lengths to get them. But I want to know what people think about this. First of all, a FTF race is no fun is you really aren't racing against anyone. And generally, I think people like myself slow down in going to get a cache once it has been found. That being said, I am considering in the future, NOT LOGGING my finds on caches where I am FTF until someone else has logged a find on it. This will keep "the race" alive, and get people chasing down caches a little more. Case in point: GC141T6 Portage Valley View. This cache was placed on Sunday afternoon at around 2:30 in the afternoon. It is approximately a 100 mile drive to this cache from where I live, and abour 45 miles from the area where there are a lot more cachers closer to the cache then me. When the cache was placed on Sunday afternoon, the thought occurred to me that it may be just late enough in the day that no one would make the trek to get this cache from closer town, and that I may have a shot at it. Don't get me wrong -- I'm not quite diehard enough to make a 200 mile RT just to get a FTF, but I was driving from my house to the other place that night (about a 150 mile drive) and knew that with a 5 mile detour, I could fetch the cache. When I got about 5 miles from where I would have to detour off the main path to go get the cache, I called my daughter and asked her to log in and see if the cache has logged, as I wasn't going to stop if the cache had already been logged. It hadn't, I stopped, and got the FTF at about 10:50 PM. That was 2 days ago, and the cache has not been attempted since. Or at least no one has logged a find or attempt to find. I'm thinking that if I hadn't recorded my find online yet, that it is quite likely that some of the closer FTF finds would have ventured down there on Monday to make the hunt. So my question I guess is this: Is it completely wrong and unethical to play with people's minds a little and wait to log a cache I was FTF on until someone else has logged it? Or do you think this would keep the adventure alive a little amongst people who like to race for the FTF?

As one who caches with my kids, we ignore the micros then. They like the treasures, which just can't be found in a micro. But, of course, when it comes to racing for a FTF, who cares what size it is!!!

OK, Just to add a little bit of clarification to the issue: The first of the 3 caches is named Super Sized -- GCQGNC. This is a traditional, nano cache, placed September 10, 2005. The next cache in the vicinity was placed on July 3, 2006 and is 218 feet from cache #1. This is the first point of the multi, and you basically have to get some numbers off of a post at a memorial and using some other resources, come up with the final coords. I didn't have everything I needed that night to solve the final coords, so I haven't been to the final spot, but it appears that the next point is far enough away to be within the guidelines. The 3rd cache was placed May 27, 2007, and is between cache #1 and cache #2. It is 52 feet from the first cache and 167 from the 2nd cache. Again, this is one where you have to use info at a memorial plaque to solve the final coords. I haven't been to the second leg of this one either as it was in the opposited direction of where I was going the night I hit the first point. You can go to the first cache I listed and then click on the nearby caches link on that page to see the other 2 caches in question. If you enter the coords for all 3 into google earth, you will see just how close they are. One is in the "island" where those 3 bike paths converge, one is slightly west, and the other slightly east.

I'm looking for a little bit of clarification related to the rule that caches must be placed at least 1/10 of a mile from each other as it relates to multi-caches. Does this rule only apply to the final cache location? The reason I ask is because about a week ago, I was out caching and I came across a couple of multis, both of which had starting points within 100 feet of each other. Not only that, within another 100 feet was an ACTUAL cache. I thought this was a little odd. Someone please explain. Thanks

Gramza-- When idd you las download the latest version of Palm Desktop? I saw a note on the palm webpage saying they were working on a fix, but think it is due out sometime this summer.

Once you have run your query in GSAK and are ready to export the PDB file to your SD card, just set that path as the filename to save the file to (On the SD Card). After creating the file on the SD card, it will attempt to run the install, and you can just cancel that. I have been paperless caching for about a month now, and I have Vista, and that is the workaround I found. Haven't run into any problems with it.

Looks like someone us bitter about something. How bout telling the rest of the story Sally.

You have just as much of a chance to get the FTF as any of the so called "nuts" in your area. It's just a matter of, "Do you want to put forth the effort to do it? Yes, it takes a little flexibility in your schedule at times, depending on what time caches seem to get published in your area. But really, it's just the drive to want it that matters the most I think. If someone really wants to get a FTF, they just need to put forth the effort, even if it's not on every single new cache. Doing so will eventually score them that FTF they are seeking.

To me, the race to be FTF Is what's fun -- trying to beat the other hounds. In my area, our approver seems to publish around 2 or 3 in the morning, so you often have to be a diehard to get out early to grab the FTF. I've been labelled as a FTF nut in my home area. Was recently out of town on business, and went and grabbed a couple early at 4:00 AM. Was fun to see the reaction on the logs from the normal FTF hounds in the area.

Another vote for cachemate

what he said.

I'm wondering if there are settings in GSAK that I can change to make the caches that I have loaded into GSAK will automatically update with the most recent logs, notes, etc. Or is there something I can do to manually update these AND, Is there someway then to have caches that have updated in GSAK then update in Cachemate in my palm? I've been paperless caching for a few weeks now and I'm really liking it. Just trying to get more efficient at it. I use an eTrex legend, which I still have to load manually since I refuse to pay $60 for the cable to convert to USB, and a Palm Tungsten E2. Thanks in advance for any tips and advice. I'm always willing to take pointers on any of the basics.

Still no dice. ANy other ideas?

Clew is more then just a simple misspelling of clue. the number in the first point was something like this: 1 23 456 78 9 123 456 ... 123 456 789 Those aren't the actual digits, but that's the general idea.

I've emailed the owner and googled for "clew" decoders. No luck either place. Was just wondering if anyone has seen something like this one before, and was looking for the resource so I could go solve it myself.

Here's the cache: http://www.geocaching.com/seek/cache_detai...79-6404a2d6fb72 I went to point #1. FOund a long number in there, and based on what's on the main page of the cache, I think it's come kind of "clew" coded coordinates. But I can't find anywhere online to decode it. Anyone know where I can decode this?

Does anyone here have a blackberry and do you use it for caching? How well does it work?

So, is there a way to have the GSAK file, when loaded into google earth, show the name of the cache instead of the GCXXXOOO identifier??

OK, I got it to open, but it doesn't show the cache names and icons that indicate the type of cache that it is. Just a generic marker and the GCXXX000 identifier. Am I doing something wrong?

I'm wondering if it's possible to transfer caches along a route from the PQ file into a file that I can open up in GOogle earth. Anyone know?

If you go looking for a cache and end up logging a Did Not Find, and then later you find the log, which way to you log your find? Do you: A. Go back and edit or change your old log to a FOUND IT log? B. Create a brand new log to log the find and leave the old DNF log alone. C. Something else -- please elaborate.

Did you copy it to the right folder on the SD card? It should be in \Palm\Launcher. Then in CacheMate, tap on CacheMate=>Options=>Rescan Mem Card. You may have to restart CacheMate (start another app, the CM again). OK, I moved it to this folder on the card and restarted, but still nothing. SOmeone recommended HotSyncing the pdb file to the Palm itself instead of the SD card and try again. I can't do it this way due to issues between the Palm INstaller and Windows Vista.