jonib wrote:OK I figured out where the single "exe" file came from, when my updater runs "UeExtractor.exe" it has to automatically type in the correct path and the put back the "ue.exe" filename to extract, this happens very fast and works in XP, but Vista seems to miss a letter or two from "ue.exe" so when UeExtractor.exe extracted the file it had the wrong filename.
So if you check the filename before extracting everything else should work.
Should be easy to fix.
A new issue: I tested first on the D: copy. That worked fine, although I still ran from the .exe. directly so I didn't test the db path. More on this later. When I ran the updater on the S: copy, it tried to update the D: copy again. I tested this again and it did this both times.
jonib wrote:So do you want me to put the database path in the .ini and/or improve the documentation?
Do you have any other ideas/features to add as long as I'm doing a new update?
This is entirely up to you as it's your app. However, since you ask... When you first run it, you're asked for the WinRAR path and parameter. Why not also ask where the database is located for this copy and also store that in the .ini? That would cut out the need for users to remember whether or not to use quotes in the .ini or even to have to manually open, find the entry and copy/paste any paths. Possibly you could also have an option to create a shortcut. We users like apps that do everything for us and developers like to have everything polished and mature.
Ultimately, I'd like to see a directory selection dialogue on first install asking where the db is located.