I finally had time to check this out properly. I tried it as soon as I saw this but it needed further investigation which I didn't have time for.
Running it today (copy on D:), it ran through as it should. When it ran UE.exe, the previous version (2.2.1) was loaded. There was a new file in that directory, called just 'exe'. I figured out that UAAutoUpdater was passing the pathname as 'D:\Apps\Usenet ExplorerUE.exe' rather than 'D:\Apps\Usenet Explorer\UE.exe', so it needs to include the extra backslash.
When I run it again, UAAutoUpdater does not detect that it is still the previous version and so just runs UE. Deleting the .ini or changing the .ini file version will correct this.
Running the updater on the NAS copy (S:\Usenet Explorer\UE.exe), there was no full pathname passed to it. Where the local copy on D: had the pathname 'D:\Apps\Usenet ExplorerUE.exe' (minus the backslash), the NAS copy on S: had only 'UE.exe' in the filename box. This allowed the update to happen as expected. On a second run, it passed the path, minus the last backslash so it would have happened as it did with the copy on D:.
UEAUReadme.txt wrote:
0.25 : 2008-10-20
Now you can send a parameter to UE to open a specific database.
Upon running UE on the NAS, the local database was still loaded. I'm not sure where the database path is to be entered.