chris f

I've been unable to get my 60c to work also. The device is detected and Windows loads the driver but neither Mapsource nor firmware updaters find it.

My 60c did the same thing not long ago, directing me on a 40 mile loop for what normally should be a 10 mile trip from home to office. I did a full reset and that resolved the issue. This was with firmware 4.1, I think, or the last beta of 4.06. I was using City Select NA v. 7.

Can't load maps without using Mapsource- Windows only.

I'd like to bring this question up again. Are you sure?? There is no mention of needing to have the latest version to upgrade on Garmin's site. I upgraded without issue from v5 to v7. I will make one suggestion: if you do not find that the new version has roads you were missing with v5, I'd stick with that. I find that the autorouting with v7 on my 60c in many cases fails to generate either the shortest or fastest route- a problem which was much less common in v5 and often results in a very circuitous route which I've noted has been as much as approximately 20% longer than a v5 generated route.

VPC will connect to the 60C/60CS via USB if you are running OS 9. It's not especially fast but it does work. Of course, this is only an option if you are still running a Mac which supports OS 9 booting- Classic does not work with VPC. One of the supposed enhancements for VPC 7, due out this fall, is for improved USB support so there is hope that it may work again in OS X.

USB only works in OS 9. For some reason, you won't be able to use OS X to connect via USB. Let's hope that's fixed in VPC 7. Chris

USB 1 is 12Mb/sec. The 60c/cs is not USB2. Chris

I have similar problems with the Garmin cable. On my cable, the computer end isn't too tight, but the GPS end is definitely too loose- the computer and GPS will lose connection if I wiggle the cable. I've been using the USB cable from my Canon camera and it has none of these problems. Chris