- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
It's a well-known issue between Windows 7 and Garmin Forerunner. Garmin company says it's a compatibility issue concerning the USB connection between the computer and the device and usually they recommend to be an Intel Chipset. Try to download and install using the latest drivers available on their site on WIN 7 and Forerunner 305.m You have them ALL here and the USB driver was released this year and it's the last one on that list.
I've just experienced a similar issue for the first time since owning my Garmin 305 Forerunner. Slight difference in my circumstance is that the device itself doesn't show the activity in its history, despite having displayed apparently accurate readings during the activity iteself. Bizarre isuee, and although it's my first issue with this otherwise great device, it does destroy your faith in the unit.
The problem is probably not with the USB cable if the GPS wont even turn on. The older firmware of the Forerunner 205 and 305 have a problem with locking up. This causes the Forerunner to look completely dead. There is a reset procedure: push the mode and reset button at the same time and then let go and hit the power on button. If it powers on that is the problem. Go to the Garmin site and load the newest rev. of firmware into the Forerunner. Fixed mine and a few friends with the same problem.
I do however have a cable problem. Sometimes my PC will come up with unrecognized USB device and my 305 wont talk to the PC, it does charge. It is the cable or dock for sure, because I have tried a different cable/dock and the 305 has no problem. This is the reason I ended up here. I hope the lock fix works for those with the above problem.