False Devices

I reported this a while ago and got a very nice reply saying they plan in a future BC version to allow user selection of devices.

https://forums.garmin.com//showthread.php?t=22659

-dan

when I start the application it thinks two Hard Drives (HD), iDisk and Time Machine, are Garmin devices and puts them in the list, and then every 10-15 minutes pops up a window staying the device is busy.

Is your OS popping up these "busy device" prompts or is BaseCamp? BaseCamp typically won't care about mass storage devices like your hard drive being busy unless it's trying to eject them.

Support for hiding volumes will be included in a future BaseCamp release.

Is your OS popping up these "busy device" prompts or is BaseCamp? BaseCamp typically won't care about mass storage devices like your hard drive being busy unless it's trying to eject them.

Support for hiding volumes will be included in a future BaseCamp release.

BaseCamp is popping up the warning window it can't eject the HD, which lists two of them, the mobile me iDisk and Time Machine HD's, which are obviously not used with BaseCamp. I'd like to know if this bug has been known for awhile, why can't Garmin bring out a patch or an interim update to resolve this?

I'd like to know if this bug has been known for awhile, why can't Garmin bring out a patch or an interim update to resolve this?

They've known about it for quite some time, at least one release. Why it's not been fixed yet? It's probably not a priority.

BaseCamp is popping up the warning window it can't eject the HD, which lists two of them, the mobile me iDisk and Time Machine HD's, which are obviously not used with BaseCamp. I'd like to know if this bug has been known for awhile, why can't Garmin bring out a patch or an interim update to resolve this?

What does that dialog say? The only such dialog I've found in BaseCamp is one that only says "Failed to eject", "The device could not be ejected. The device may be busy. If so, please try again later." without listing any specific volume.

If you're referring to the eject message in your bug inquiry, that's not something I've been able to reproduce here. In general, things like Time Machine drives don't show up, so I'd be interested in knowing if there are specific conditions where these eject warnings show up (e.g. do they only show if you start up with a Garmin device or SD card inserted already?).

Displaying tons of different volumes as potential send locations isn't a bug, though. Not all drives are detected and displayed in that manner. The drives that are shown are the ones we couldn't differentiate from SD cards. The manual hiding option is our planned fix for that.

In general, things like Time Machine drives don't show up, so I'd be interested in knowing if there are specific conditions where these eject warnings show up (e.g. do they only show if you start up with a Garmin device or SD card inserted already?).

Interesting. My Time Machine drive and Mobileme local drive do show up but my usb data drive that used to show up doesn't anymore. The data drive would be handy. ;)

What does that dialog say? The only such dialog I've found in BaseCamp is one that only says "Failed to eject", "The device could not be ejected. The device may be busy. If so, please try again later." without listing any specific volume.

If you're referring to the eject message in your bug inquiry, that's not something I've been able to reproduce here. In general, things like Time Machine drives don't show up, so I'd be interested in knowing if there are specific conditions where these eject warnings show up (e.g. do they only show if you start up with a Garmin device or SD card inserted already?).

Displaying tons of different volumes as potential send locations isn't a bug, though. Not all drives are detected and displayed in that manner. The drives that are shown are the ones we couldn't differentiate from SD cards. The manual hiding option is our planned fix for that.

My Time Machine disk shows up every time it is called upon to mount for backup and I have verified that it does not matter if a Garmin device is mounted at the time or not. As long as BaseCamp is running, when the TM disk mounts it appears in the upper left pane and when TM tries to "put away" the disk, BC throws the error message you quote above.

I am using a shared USB hard drive plugged into an Airport Extreme Base Station for TM backups, meaning it uses a sparse bundle which automatically mounts for each TM backup and then un-mounts, so this is not quite the same thing as a TM disk which always lives on the desktop.

Hope this helps,

-dan

My Time Machine disk shows up every time it is called upon to mount for backup and I have verified that it does not matter if a Garmin device is mounted at the time or not. As long as BaseCamp is running, when the TM disk mounts it appears in the upper left pane and when TM tries to "put away" the disk, BC throws the error message you quote above.

I am using a shared USB hard drive plugged into an Airport Extreme Base Station for TM backups, meaning it uses a sparse bundle which automatically mounts for each TM backup and then un-mounts, so this is not quite the same thing as a TM disk which always lives on the desktop.

Hope this helps,

-dan

Are you sure that the warning appears when the drive mounts, and not when it unmounts at the end of the backup operation? It would still be a bug, but I can see that auto-eject potentially confusing our own eject handling.

Are you sure that the warning appears when the drive mounts, and not when it unmounts at the end of the backup operation? It would still be a bug, but I can see that auto-eject potentially confusing our own eject handling.

It adds the HD when TC mounts and pops the error when it unmounts, but it also occasionally pops the error with the iDisk HD which it adds when you open the app.