Basecamp does not see my Dakota 20

I also did remove all USB drivrs (as suggested by Sussamb). Still no luck.
The funny thing is that the Dakoto works okay on another computer.
Also, when the Dakota is attached while running Basecamp and I disconnect the device (e.g. by removing the cable) Basecamp shows the device for a second or so and gives an error related to each individual track on the device.

So this is what I have narrowed it down to:

On my Windows 8.1 tablet Basecamp CANNOT see:

* My Oregon 450;
* USB memory devices plugged into any of the three USB ports available;
* microSD cards that I put into the microSD port.

HOWEVER, Basecamp CAN see and properly interacts with my eTrex Vista HCx! I figure that's because the Vista is not a Mass Storage Device; it cannot be assigned a drive letter because Windows does not see it as a mass storage device. All others devices (Oregon 450, USB memory devices and SD cards) are considered mass storage devices. I think this is where the issue is, but I don't know what is causing it. I still have to do more research online to see if I can find anything related to that.

As another test, I temporarily installed Basecamp on my wife's work laptop and I had no issues with the Oregon 450 on it. It interacted properly with Basecamp, as did USB memory devices and SD cards that I ran tests with as well.

My guess is that it might be something with .NET on my tablet. I haven't gotten around to reinstalling it yet but I will try at some point (when I have time).

HOWEVER, Basecamp CAN see and properly interacts with my eTrex Vista HCx!

That's because, like your Oregon 450 in Spanner mode, the Garmin USB communications protocol is used.

My guess is that it might be something with .NET on my tablet.

Agreed. I think Microsoft released some .NET updates recently.

PS: Garmin software/units use the following methods of communicating.

Garmin serial protocol (obsolete for the most part but used by older models). BC doesn't support this but MapSource does.

Garmin USB protocol (the above serial protocol but over USB). Basecamp/Mapsource support this.

Mass Storage mode. Basecamp/Mapsource support this.

MTP (Media Transfer Protocol). BaseCamp supports this but MapSource doesn't.

Depending upon the age and type of unit(s) one or more of the above are available. For example my 76CSx supports serial/USB (it's mass storage mode is not used for data transfer). My 1490T only supports mass storage mode. Newer model nuvi's default to MTP and many can be put into mass storage mode. The Monterra (Android based) only supports MTP as I recall.

The bottom line is that these methods are different.

Eureka! I solved my issue!!

The short answer: I have various map products (totalling over 10,000 .img files) installed on a 32GB microSD card (D: drive). I do that because the tablet SSD C: drive is limited in space and I didn't want to use it up with the .img files of all the map products I have. Upon startup, Basecamp was trying to read each *.img individually when the files were located in various sub-folders under a Garmin folder (at the root). After renaming the base folder to GarminMaps and making all necessary changes to the registry entries for all related installed map products, Basecamp now sees the D: drive instantly on startup, which in turn leads to seeing the Oregon 450 mass storage devices (E: and F: drives) and other USB memory devices. Basically, it's not that Basecamp wasn't seeing the other USB memory devices or the Oregon 450 that was really occurring. What was happening is that Basecamp was trying to get through all 10,000+ .img files first before moving on to other devices. It would have taken hours, if not longer, to get through all of those files (each time I started up Basecamp).

The longer answer: After much troubleshooting and noticing in Task Manager (under Processes) that after startup Basecamp was using 25% CPU (one full core of a Quad-core processor) non-stop, I started trying to figure out what it was doing. I eventually got around to renaming the Garmin directory on the microSD card to GarminX and then suddenly Basecamp immediately saw the Oregon 450 and other USB memory devices! The map products no longer worked, until I modified the registry entries to point to the new folder name; I eventually called it GarminMaps and pointed the registry entries to it. Before Basecamp was upgraded to 4.3.5 a couple of weeks ago, I don't know what version of Basecamp I had but it was at least one year old. I don't remember it doing that (i.e. trying to read all .img files under a Garmin directory upon startup). Maybe it did and I don't remember that, and I didn't have many map products installed on my tablet at the time. I do know that I hadn't tried to connect my Oregon 450 directly to the tablet since before I had installed the various Garmin map products many, many months ago. Until a couple of weeks ago, I was using a laptop to manage Basecamp and my Oregon 450, and all files were located under the C:\Garmin drive\folder (i.e. on the hard drive) on the laptop. I would then simply make a Basecamp backup from the laptop and restore it onto the tablet when I wanted to use Basecamp on my tablet. Unfortunately, I no longer have that laptop and now have to use my tablet, which is what led me to run into this issue.

Thanks to all who offered ideas and links. Your help was much appreciated!

The short answer: I have various map products (totalling over 10,000 .img files) installed on a 32GB microSD card (D: drive).

Whoa!!!!

You do know IMG files can be combined (into larger ones) right?

GMapTool

I didn't know about that tool. I will check it out this weekend. Thanks for the tip!

F_E_T_U_S,

I'm glad you found a solution for your problem. Unfortunately, it didn't work out in my case.