Hi there,
apologies if this is a little late, and if it may be too basic a response...
When an application runs as a service, it runs in the context of the user that it is configured for. Hold this info in your head for a sec while I move to how INI files work...
INI files are not
typically accessed directly; instead they are accessed through a bunch of API calls (for example ReadProfileInt()). When these calls execute, they first look for a file in the running user's context \ Application Data.
For example, if you (John) run a program that tries to read an INI file, then the default location for this INI file is
c:\documents and settings\john\application.ini
When an application runs as a service, then it is running under a specific user contect which, almost invariably, is not you...
If you run "services.msc" you can spot your services and find out which user context it is running under (by double clicking on it and going to the Logon tab).
If the Logon Context is the local system account, then the path to it's ini file is "
C:\Documents and Settings\LocalService\Application Data
So, the first step (and bear in mind that I am talking generically here, rather than Twonky specific) is to ensure that the INI file you are editing is
this one.
OK - that was INI files 101. An application can also specify its own INI file and the easiest way to do this is to specify an INI file in the application's startup folder.
If
this is what Twonky is doing then, potential bug aside, you can still use this info to your advantage. Remember that the application (Twonky) is running in a specific user context. If it is running, for example, as the Local System Account then you know that this user "SYSTEM" should
not be allowed to overwrite your INI file.
This is actually pretty easy; find the INI file under the Twonky folder, right click on it and click on Properties and Security, then remove the security options for SYSTEM and then add a new entry for SYSTEM, allowing it Read, List Folder Contents and Read & Execute permissions.
One final fly in the ointment; you may not see a Security tab on the file properties dialog. If this is the case, refer to
http://support.microsoft.com/kb/301195 for more info.
Oh, and this may be a genuine Twonky bug and so, ITIL-speaking, the above is a workaround.
S.