Thankfully, the registry isn't as critical as it once was when applications were heavily invested in Visual Basic, COM and Active-X controls.
Most programs written in .NET use a simple configuration file. It is usually named <program-name>.config.
Sure enough, the HomePatrolSentinel.exe file includes a companion file named HomePatrol_Sentinel.exe.config. These config files are almost always XML - which is easy enough to edit in Notepad. Examining that file in Notepad, I see the following section ...
Code:
<setting name="SentinelFolder" serializeAs="String">
<value />
</setting>
I tried an experiment which seems to work. Here's what I did ...
I copied the "HomePatrol Sentinel" folder from C:\Program Files to C:\Temp. I emphasize the word "copied" here. I'm leaving the folder under Program Files as-is.
Next, I double-clicked on C:\TEMP\HomePatrol Sentinel\HomePatrol_Sentinel.exe to make sure it was okay with running from a different folder. It does so I exit the program.
Next, I open the
C:\TEMP\HomePatrol Sentinel\HomePatrol_Sentinel.exe.config file in Notepad and edit the above section like so ...
Code:
<setting name="SentinelFolder" serializeAs="String">
<value>C:\Maybe</value>
</setting>
Note that at this point I do NOT have a folder on my C drive named "Maybe".
Again, I double-clicked on C:\TEMP\HomePatrol Sentinel\HomePatrol_Sentinel.exe. It lauches fine, making no complaints. I exit the program. Opening "C:\" in Windows Explorer I see a new folder named "C:\Maybe" has been created (with additional folders underneath). I believe I could copy the contents of "C:\ProgramData\Uniden\HomePatrol_Sentinel" to "C:\Maybe" and the C:\TEMP copy of Sentinel with the modified config file would access it just fine.
I have not gone so far as to use a thumb drive (or radio's the SD memory card for that matter) to verify this works on anything besides the C drive. However, based on a few minutes experimentation (I've spent more time typing this post), I foresee no problems.
