WinLIRC not loading configuration

[GoogleCodeExporter]

I'm grateful for the recent inclusion of the WinLIRC package, so it's with some 
regret that I'm generating another support issue with it. I'm having trouble 
figuring out what's going on and was hoping for some help.

It seems that the new WinLIRC package installs nicely and I can set up my usual 
configuration to get it working. I do this by running WinLIRC.exe executable.
However, the next time I start the WinLIRC.exe executable, it doesn't remember 
my settings and I have to re-enter them again.

The strange thing is that this doesn't happen when I just manually unzip the 
pacakge and move the WinLIRC directory to Program files. Furthermore I'm a bit 
at a loss as to what could actually be different between installing it either 
way. There don't appear to be any registry entries involved, but I do note that 
the manual install has my user explicitly listed in the windows permissions 
(which I find impenetrable to understand). I tried my best however, to delete 
my user from the manually installed version to "break" it, but it continued to 
operate correctly.

I do find the WinLirc configuration system a little confusing though. While it 
explicitly stores the remote code data in a user specified file, it isn't at 
all clear where it stores its over-all configuration (i.e., where to actually 
find the remote config file, which plugin you use, server options, system tray 
icons). I've filed an other support request [1] asking for help understanding 
how this is supposed to work, but was wondering if there might also be some 
insights from the npackd side.

[1] https://sourceforge.net/p/winlirc/support-requests/25/

Original issue reported on code.google.com by kevmi...@gmail.com on 24 Apr 2014 at 7:41

[GoogleCodeExporter]

Ah, it looks like this information is stored in WinLIRC/plugins/WinLIRC.ini. 
When I run WinLIRC.exe (as installed by Npackd) as a regular user, this file 
does not get updated, but when I "run as administrator", it does. This seems to 
suggest that it is indeed a permissions issue and as suggested above, I'm 
hopeless at understanding the Windows permission system. I've suggested to the 
WinLIRC people, that %appdata%/WinLIRC would be a better place to store 
configuration data (it would also work better with upgrades).

Original comment by kevmi...@gmail.com on 25 Apr 2014 at 2:08

[GoogleCodeExporter]

Ok, well after a fresh install into the C:\Npackd directory, I don't even need 
root access to set it up initially. So go ahead and close this. If anyone else 
has a similar problem, they should try runing as administrator for the initial 
setup.

Original comment by kevmi...@gmail.com on 25 Apr 2014 at 11:22

[GoogleCodeExporter]

I added a warning to the package description.

Original comment by tim.lebe...@gmail.com on 25 Apr 2014 at 7:00

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 25 Apr 2014 at 7:00

• Changed state: WontFix