Jump to content

maleki

+Charter Members
  • Posts

    378
  • Joined

  • Last visited

Everything posted by maleki

  1. With gas prices as they are, suggested parking coords would always be most appreciated. especially for caches where there might be only one legal/logical place to enter and/or park. Coords to any access point, be it road or trail, for cache areas bounded by private property are most important. Pretty much a waste of time and gas and ZERO fun trying to find access to some places. Caches in parks in most suburban neighborhoods come to mind.
  2. Still looking for a source for a bare(or wired) explorist data/power connector iif anyone has come across one. Thanks.
  3. I got on Magellan tech support several weeks ago. First for not offering support for Win 98, then also for not offering info about a workaround solution that is mentioned here(and elsewher): Explorist to Win98 info Just noticed that the link on that page to the Roadmate driver is no longer working so you'll have to search for that elsewhere I guess. I managed to get it to work and use it with GSAK, not the Magellan geocache manager software. Good luck!
  4. Anyone have a source for an Explorist connector(either naked or bare wired)?
  5. After attending the event mentioned, and checking out the impressive collection of Geocoins, they're quite cool. And of course, with the event logged, my closest caches page has returned to normal.
  6. Did 6 states in a day. Missouri, Illinois, Kentucky, Tennessee, Arkansas, and Mississippi. We'd spent the evening just south of St.Louis along I-55. The next day we meandered down towards Memphis on and off I-55. Even got a great, sort of remote, FTF along the way. The six states were not intentional for the most part - just worked out that way.
  7. Thanks for the speedy followup.
  8. All the goofy Geocoins sure mess up a cache listing page. whacked cache listing page
  9. You guys are something! I barely know what I'm doing next week much less next September. Just sign me Mr. Procrastination
  10. Had my own delightul rave out at Magellan support today about lack of 'supported' Win98 connectivity for the Explorists. After hanging up after at least 45 minutes on annoying hold I called back and left a message for a callback. Much to Thales credit I received a call back within an hour I think. Why not just answer the original call in a timely manner(I was tempted to let the phone on hold to see how long it would take bit had other things to do and recall another thread that mentioned a 5 plus hour hold I think) - I really did not expect a call back today. The newbie support person, it was quite obvious, put me on hold to check about my question. He assured me that it could not be done(although I sort of knew it could) and confirmed it with a 'support guy that had been with the company for at least 10 years'. Oh well - that set me off - poor guy... A quick google had a possible solution. I struggled a bit but managed to get things talking using a Roadmate 500 file of all things. I STILL WISH THE EXPLORIST HAD AN OPTION TO EMULATE A MERIDIAN/SPORTRAK - screen for screen as well as simple things like projections. Thanks for the listen!
  11. Sadly, a filter like this would eliminate most of the newer caches around here - the Chicago area. It would clearly make for a very slow and spread out caching day for sure.
  12. For us long time Meridian users why not just a Meridian Emualtion mode of operation. Sure would make me happy.
  13. My Explorist 100, which I thought had no probs, moves in 7 directions quite reliably and easily. Up-Right does not work. I never would have noticed because I can't see any reason I'd ever need it to move other than L-R-U-D on this basic device. I returned my new out of the box Explorist 500 last week because the up direction was terrible and unacceptable. No questions asked, just an RA# given, when I finally got thru late on a Friday afternoon. Seemed like apparently they'd heard the same call before and were not at all interested in rehashing the ugly details It's been there over a week now so anxiously waiting some word or better yet a UPS truck.
  14. Now that's gonna win big points with Magellan and help your cause.
  15. So that what I endured for awhile late last Friday afternoon when I was on hold for awhile. Yikes, that was nasty.
  16. Currently several Ebay Buy it Now currently at $ 66.95 plus $ 8 to 10. shipping. Had just looked earlier this afternoon.
  17. Aaaaagh!!!! I just spent about a half hour on a detailed reply/request for this thread then took a power hit. Gone!!! A very long story short(probably for the better). I currently, as some others have mentioned, run a set of 4 queries for ALL caches that I have not found in my state(currently about 1700 I think). I also fairly regularly run a set of 5(soon to be 6) queries for a neighboring state. While TOTAL PQ overkill it's the easiest way to keep my local data current. I dump it ALL into GSAK on the laptop when ready to go along with maybe a last minute local update(to update recent logs) if we know were headed to a very specific area and go. A MUCH easier and highly more efficient(if it's possible to program) would be a query for a WHOLE state that shows EVERYTHING that has changed status for the last week, month, whatver. The query would need to supply ANY cache that has gone from active to temp. disabled or archived and the opposite. I'd guess that the average amount of changes for the last week normally would be 100 or so caches. Maybe I'm wrong on that but certainly WAY less than 500. The alternative is to just run the current sets of queries that total near 4000 or caches as often as I can til some better query comes available. I have already voluntarily cut down the number of times I run the nearby state(which I often have to edit for 500 cache limits) and for sure do not run my home state as often as I once did. IT SURE WOULD BE NICE TO GRAB THE WHOLE STATE ONCE THEN BE ABLE TO EASILY(with much less load on the system) KEEP IT CURRENT. Please!!!
  18. I usually do not have any probs(thanks for the fine work) but queries I submitted early Monday for Monday run never processed. I resubmit them for today several hours ago and they've not run yet. Not important yet - just so I can get updated for the weekend.
  19. Hmmmm! No more film cannisters micros or magnetic key holders - what a fine idea.
  20. That is a good warning... but the first I've heard of that. I've been using my battery screw as a lanyard attachment almost since I got my GPS.. and it's never come off. So.. how is the hoop on the Meridian lanyard attached to the screw? I'd imagine it's the same technique. Anyone else have their loop come off? Jamie The heavy duty doubled loop on the Meridian Lanyard fix will NEVER pop loose. My fingers HATE that tiny loop on the Explorist. I usually just use a coin when I need to swap batteries cause I sure cant grab that loop easily. The thread on the Explorist 100 at least is the same but the captive screw that exists in the battery cover would need to be permantly removed which most would not want to do. In addition the thread length would need to be a bit greater than it is for the Meridian mount because it would need to pass thru the battery cover before engaging the threads in the case.
  21. Works for me - LOL! I really do like the solution for my trusty old Meridian too.
  22. The small nylon cable tie has been rock solid for months now. Though about doubling it up but havent yet. I'd trust it more than the battery cover loop myself. This has degenerated to off-topic so I'll leave it at this an apologize.
  23. Mr Lost, No need for an additional eyelet on the Explorist, since it already has one. Simply take the GPS and turn it around and look at the back. Jamie Yes there's a pace to hook on the battery cover screw but it hangs much better and feels better in hand when using the eyelet - IMO.
×
×
  • Create New...