Basecamp Won't load - uninstall didn't help

I'm trying to find a way of doing a completely clean reinstall of Basecamp. I had already pointed Basecamp on my laptop to a network drive for its data files and its quite happy with that.

I tried the same with Basecamp on my main PC, now it runs but then closes down. "Basecamp application has stopped working": I tried uninstalling and reinstalling. No joy. Uninstalling and removing all Basecamp data files and Registry entries, rebooting and reinstalling. But still it won't run.

Is there an .ini file somewhere I can get to to revert to default where its looking for its data files or what can I do? Driving me crazy!

Thanks.

 

Thanks. I just this minute fixed it by doing a system restore (the often lifesaving utility that Windows 10, for some reason, keeps hidden away!). Phew.

I now want to fathom out why it was not happy with the netdrive data location that my laptop was perfectly happy with!

By the way, uninstalling and reinstalling did me no good. There seems to be no simple way of doing a clean install. Unless someone knows better.....

Thanks again.

 

I found why this is happening. I had not pointed Basecamp to the "\garmin\basecamp\" folder, just the "\garmin\" folder.

To get this to work, I copied the files on my PC from here: C:\Users\my_username\AppData\Roaming\Garmin\BaseCamp to my network drive.

Then, within Basecamp, Edit, Options, General, Database Options, I gave the copied database a name "Netdrive" and browsed to the Basecamp directory on my network drive.

I did the same within Basecamp on my laptop. Although it is not possible to run both copies of Basecamp at once, it does mean that any work I do on my laptop will then be reflected within my PC copy of Basecamp, and vice versa.

Works well!

 

I tried several times, deleting all the files I could find plus entries in Registry and still it would not run. Well it ran, the splash screen referring to the help videos would load but then it would stop with the error "Basecamp has stopped working" and I'm sure it was down to the incorrect directory being set in the database options.