JohaViss wrote:I would like to see the following additions to the SI software:
Option to remove an application from the list.
Option to 'lock' an application. (Never look for updated version)
Connection through a proxy.
Printable list of applications.
Update based on a timer. (Once a day, once a week, on every reboot, etc..)
At this moment, the SI application is not very usefull. There are a lot of wrong versions. It is not clear where SI is looking for the version number. I haven a number of applications that store in the regisrty the first installed version, the actual installed version can be retreived from the exe.
Sometimes the supplier is the wrong one. Some applications from different suppliers have the same name.
Regards Johan Visser
I'd ike to share some of what I know about updaters with you:
The problem isn't reading the registry. The main issue with all updaters is how to interpret (correctly) the dated information contained in Windows vast dynamic libraries. Most of the configuration files contain dated information, but any updater will not be able to tell what file is the lates build. This is mostly due to developers writing the files incorrectly, making them low priority, or putting the version information in a txt file instead of an ini or dll. Most updaters avoid (wisely) scanning exe files, depending on how intrusive their scanning protocol, as they may errantly activate an executable file.
I'm new to SI, but from what I've seen so far, it deals with Windows pretty well. The only tried and true, 100% effective method for updating is for software and driver developers to email every user to let them know an update is available. Out of the updaters I've tried, I'd rank this one as number two. The number one on the list doesn't scan every installed program, so that makes this one a really close second. Good luck!