When running as a Windows Service, any changes I make to the configuration don take effect. Whats wrong?
This is normal. The nature of this problem is that when you run the program while the Windows Service instance of AUTAPF is running, there are technically two instances running, in which case the later one (AUTAPF started manually) will probably not be able to listen on the ports – since they’re being listened on by the service instance of AUTAPF. This would be indicated by Error starting in the Status field of AUTAPF when run manually in this case for those ports which are already being listened on by the service instance of AUTAPF. When logged-on to Windows through Terminal Services and running AUTAPF as a Windows Service, you may not see the AUTAPF icon in the System Tray, even though AUTAPF is running (as a Windows Service). To be able to configure AUTAPF in this case, you would need to either log-in to the machine via another means (not Terminal Services) and configure AUTAPF, or you would need to stop the AUTAPF service, start the program manually and configure it, then preferabl
