TECGeoJim

My 3 PQ's failed to run (2 of them were new 10 Yr event related). I made copies of each but they have not run, yet, either.

My PQ's have not run today, either. I tried creating copys but they don't run either. I brand new query submitted as a ftesgt has not run. What's up?

Why have SOC's if anyone can log them???

I have not received the PQ's at gmail.com. Is it possible to get the number of PQ's reset? I have used up my quota of 5 for today but only received 1. I would like to try the other 4 again.

5 PQ's scheduled for today. All appear to have run at about 2:15 a.m. Hours later and only 1 received .

I think that I have narrowed down the problem -- I am not receiving emails for travel bugs or geocoins when I move them. I guess this is okay but it would have been nice to have gotten a notification that this was happening from Groundspeak.

I think that I have narrowed down the problem -- I am not receiving emails for travel bugs or geocoins when I move them. I guess this is okay but it would have been nice to have gotten a notification that this was happening from Groundspeak.

I have not been getting emails notifying me of the retrieves and drops of my geocoins. I am using a gmail account and have checked the spam folder. The emails are not going into the spam folder. I have been experiencing this problem for several weeks.

I am still not getting any notifications when many of my geocoins are retrieved or dropped. I am getting at least some of the notifications when my coins are being discovered.

I am not getting notifications of retrieval or dropping of my geocoins.

I dusted off my old Firefox browser after reading previous posts. The cache along a route pocket query worked fine.

I am getting the same error with both old routes and newly created routes. I was getting the error yesterday and again this morning. I have tried it using both IE on Vista and IE on XP.

As a former Wisconsinite, I would like to buy a set or two.

Yup! The Geocoin fairy has been to Minnesota. I found "a little something" in my Mall of America cache today. I left a 2006 Kansas geocoin in trade. I didn't realize what I had found until I did a search and came up with this thread. I was lucky enough to get #187. It will have a place of honor in my collection. Thanks Geocoin Fairy!

I received an email with a link to Mr. G Geocoins and thought maybve it was a phishing attempt. I came to this forum to see and was pleased to see the same link here. I guess I'll take a chance and order through the web site.

e-mail sent for 2.

Any updates? I would like to be added to the group for 4 coins.

I was interested in a few of these but missed my opportunity at the geocoin store. I attended both the 1960 (yes, I am an old timer) and the 1997 Jambos and plan to attend the 2010. I love to see more cpoins produced. I do have MN geocoins to trade if someone purchased extra coins.

I e-mailed my request for 2 to F&V.

e-mail sent for 5 coins.

Bloomington, MN - active as cacher a bit less thatn 2 years - usually spend my forum time at MnGCA

I received my eTrex Vista back from Garmin today. Just 9 days including 2 weekends after mailing it. They sent me back a unit with a lower serial number than what I sent in. I assume that it is a reconditioned unit and that my old one will be sent to someone else after it is repaired. They transferred my waypoints but not my maps . Maps are easy to reload. If anyone else is having a problem with the rubber coming off, I suggest contacting Garmin for an RMA and sending in your unit.

After several e-mails to Garmin tech support, they sent me an RMA number and will apparently repair my unglued rubber bumper at no charge. I sent the unit off to Garmin yesterday.

I use an eTrex Vista with TOPO maps for the field and a 60C with street map for the car. On vacation, I usually use the 60C for both rental car and field use.

The glue holding the rubber band on my 13-month old eTrex Vista turned to soup yesterday. I e-mailed Garmin tech support today. I hope to have the unit repaired/replaced since this seems to be a common problem with eTrex units. I will post updates here.