Page 1 of 1

Default Installing to a removed hard drive

Posted: Wed Mar 03, 2021 3:47 am
by HeadPilgrim
Clear description of the problem - try and include as much information as possible, including what button and mappings you are having problems with (if applicable).:

I removed a failing hard drive that had x-mouse button installed on it. Note, this is not the drive that has windows installed on it as that is my C drive and this was my F drive. I'm trying to install the program again and the installer always fails out because it wants to install to my F drive which no longer exists. I used a program called revo uninstaller and cleared out all of the registry files that I'm aware of but the installer still points to my F drive every time. My default ProgramFilesDir is to my C drive so I'm not sure how to fix this.

Any advice would help thanks.

Re: Default Installing to a removed hard drive

Posted: Wed Mar 03, 2021 9:55 am
by phil
Thats a new one!

The only registry key that XMBC uses is where it is installed - so maybe that's it... The XMBC config file would be on the failed drive I guess. Have a look in the registry for...
Key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Highresolution Enterprises\XMouseButtonControl
Value: InstallLocation & possibly SettingsFolder

Delete the whole key, or just the two values/valuedata and see if that fixes it. I will have to mod the installer so it handles that better - funny its never cropped up before!

NOTE: XMBC really should be installed under programfiles else it can not operate properly as a Windows Accessibility Tool due to microsoft's weird rules - and you wont be able to interact with higher elevated processes without running XMBC as admin!

Re: Default Installing to a removed hard drive

Posted: Wed Mar 03, 2021 10:44 pm
by HeadPilgrim
Thanks that fixed it! I thought I looked close enough for any related registries but I missed that one and it seems it was the culprit thanks for the help.

Re: Default Installing to a removed hard drive

Posted: Wed Mar 03, 2021 10:56 pm
by phil
Glad that fixed it - I will have to see if I can modify the installer so it handles such cases better!