At the moment the updater don't check UE.EXE version, so changing the version in the .ini file is the way to make it update.

OK.

jonib wrote:

This seems weird, the updater runs the ue.exe that is in the same directory as the updater, it does not use an absolute path only "ue.exe".

For the record, I use Vista x64. I don't know what you run/test on. Maybe there's a difference there. Hopefully we can get some others with different OSs to report back.

jonib wrote:

You should put the same thing after the UEAutoUpdater.exe as you wold ue.exe as in "UEAutoUpdater.exe PathtoDB"

I thought it must have been in the shortcut. I was running the updaters directly from my file manager. You might want to put the need for a shortcut in the readme. I was expecting an extra entry in the .ini.

For the record, I use Vista x64. I don't know what you run/test on. Maybe there's a difference there. Hopefully we can get some others with different OSs to report back.

I run XP, but I'll test in Vista 32bit, where is your ue.exe located? I know Vista does some weird stuff in some directories.

Quote:

I thought it must have been in the shortcut. I was running the updaters directly from my file manager. You might want to put the need for a shortcut in the readme. I was expecting an extra entry in the .ini.

I can put it in the .ini if you like, I assumed having the same syntax as ue.exe was the way to go

I run XP, but I'll test in Vista 32bit, where is your ue.exe located? I know Vista does some weird stuff in some directories.

My UE.exes are not in Windows directories like %Program Files% and UAC is turned off anyway so that doesn't affect anything.

jonib wrote:

I can put it in the .ini if you like, I assumed having the same syntax as ue.exe was the way to go

It's just an extra step to create the shortcut that only needs doing once. While I was testing I was using the .exe directly. It's not a problem, it just needs pointing out that it needs doing in a shortcut.

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'.

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.

Quote:

It's just an extra step to create the shortcut that only needs doing once. While I was testing I was using the .exe directly. It's not a problem, it just needs pointing out that it needs doing in a shortcut.

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?

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.

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.

I have not found why it don't update S: copy, hopefully you are up to some more testing.Could you update the S: copy by manually changing the path in UeExtractor.exe and then run my updater on the D: drive, does it update the right ue.exe?

Quote:

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.

No problem.

Quote:

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.

Do you want the icon on a silver platter? or on the desktop? no problem.

Quote:

Ultimately, I'd like to see a directory selection dialogue on first install asking where the db is located.

I have not found why it don't update S: copy, hopefully you are up to some more testing.Could you update the S: copy by manually changing the path in UeExtractor.exe and then run my updater on the D: drive, does it update the right ue.exe?

I'm always up for testing. This time it worked no problem. The only difference is that I'd rebooted a while after I tried the first time. The first thought is that anything with network shares being lost or latency - anything like that - can affect how something like this might work. On the other hand, the updater is supposed to update in whichever directory it's running in. It also ran OK in the first place, so the network share was not lost.

FYI, this computer is put to sleep regularly, e.g. overnight, but the network shares are actually TrueCrypt containers that I dismount before sleeping it then mount when I wake the computer. i.e. there are no real shares to be lost - the containers will either mount if the share is available or they won't if the share is unavailable. How about we blame this discrepancy on Windows...?

jonib wrote:

Do you want the icon on a silver platter? or on the desktop? no problem.

I'm always up for testing. This time it worked no problem. The only difference is that I'd rebooted a while after I tried the first time. The first thought is that anything with network shares being lost or latency - anything like that - can affect how something like this might work. On the other hand, the updater is supposed to update in whichever directory it's running in. It also ran OK in the first place, so the network share was not lost.

FYI, this computer is put to sleep regularly, e.g. overnight, but the network shares are actually TrueCrypt containers that I dismount before sleeping it then mount when I wake the computer. i.e. there are no real shares to be lost - the containers will either mount if the share is available or they won't if the share is unavailable. How about we blame this discrepancy on Windows...?

So this time all updated correctly? and I don't have to pull my hair out finding the problem and always blame Windows.

Josef K wrote:

jonib wrote:

Do you want the icon on a silver platter? or on the desktop? no problem.

I have released a new version 0.40, it's a beta, lots of new stuff see below.

After testing the updater in Vista I have come to the conclusion that Vista hates me and I hate Vista, basically if UAC is active Vista considers my program an "Unknown program" and ask permission to run, first time was OK but it asks everytime, and after some research I found out it is because I have the word "update" in the file name, if I rename no problems

Update: I have found a way to compile that makes Vista happy , next version hopefully works nicely in Vista.

0.40 : 2008-10-25 I consider this a beta as I have added a lot of stuff so there is higher risk for bugs, also the Updater won't check or download updates directly from UEs website. I have made the program selfinstalling, including an option to add a shortcut on the desktop. Now it doesn't unnecessarily download and install a new UE if you already have the latest version. Now it will ask if you want to use an alternative database in UE. Choosing not to install an update, won't show prompt next start. Added more error checking and optimized the code some more.

I've just run the new build on two separate instances of UE and both worked fine. The first one gave me the shortcut prompt and asked for the db location. The second did not prompt for anything. I don't remember what state they were in the last time I left them, for example, which versions were running in which locations or what was in the .ini files.

I've just run the new build on two separate instances of UE and both worked fine. The first one gave me the shortcut prompt and asked for the db location.

Great.

Quote:

The second did not prompt for anything. I don't remember what state they were in the last time I left them, for example, which versions were running in which locations or what was in the .ini files.

This is possibly less great, the program is supposed to ask the first time it is run to create a shortcut or not, could you check the .ini if there is a line "Installed=True" if it's there the program wont ask anymore, and you could remove the line and try if you get the shortcut prompt.
If you specify a DB path in the shortcut it will override the DB path in the .INI and it will not prompt for it, or if there is this line in the .ini "DBPath=" which indicates the program uses the default DB.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum