jrr, on 07 March 2011 - 08:54 AM, said:
Sean2, on 06 March 2011 - 12:05 AM, said:
I'm glad I found this thread. I was going to purchase a Bushnell, but after reading what I read no thanks.
Now I'm more confused then ever. I would really like a GPS, but I may just go with a rangefinder.
I need to clarify again that Bushnell's Cs is first class as is the quality of their product. The issue is Igolf , who unfortunately, is involved with more than Bushnell in supplying software.
If you use a PC you will have no issue. If you use a Mac see message above #9 from bpark, go to the link at the bottom and the solution is there. Now what is interesting that thread is cut out of the forum threads run by Igolf. You have to wonder why??? But his great direction is working for now at least.
Contact Apple - if you want a reliable long-term solution. Write to Steve Jobs (SJobs@Apple.com) or Jeff Maranhas (Maranhas@Apple.com). If you merely "patch" or work-around the problem now, the problem may replicate when the OSX update occurs. This is both bad for Igolf and Bushnell and Apple. But since it probably is an OSX issue, then you should tell Apple. For lack of a better term - Apple sets the framework and advises software manufacturers how to geek their software to work on Apple. Sometimes the wires get crossed and OSX updates or software upgrades cause the framework to make a mistake.
I had a similar problem with a new car (that alleged it was specifically Ipod friendly) and my Iphone. The car dealer and then manufacturer and Apple both pointed the finger at each other. The problem was evidenced by several car sites. I wrote a fairly lengthy explanation to Mr. Jobs and sent an email to him. I did NOT BLAME him or anyone (as many seem to do in this thread) but simply explained the issue and who/what/where I had gone to resolve it, before bothering him. Very much to my surprise - about 2 hours after I emailed Mr. Jobs, Jeff Maranhas (who I think is a Lead Product Manager for Apple) emailed me. We began a communication trail for the next 3 months - about 10 emails and a few phone calls - and in the ensuing IOS 4.2 - the problem was resolved for me, and the several car forum members who'd had the problem. Needless to say I was amazed that a peon like me would get any response whatsoever...not to mention a full solution.
FWIW - I am not a techie - all I basically explained was that I had bought an Apple-compatible product - and it wasn't working properly. No "tech" experience required. LOL
Try it - can't hurt.
Edited by ChipDriver, 07 March 2011 - 10:25 AM.