quote:
Originally posted by CookieRevised
The reason why your "ad-watcher" reports a change is because MSN Messenger is set to "run at win startup". Now, when you use Plus!, Plus! needs to be started BEFORE MSN Messenger in order to run and hook properly. Plus! ensures it is started up first by detecting and removing that key when MSN Messenger is closed. After that, Plus! will replace it by it's own key so that it can be started up first (and after that it automaticly runs MSN Messenger). Otherwise there is no way in knowning what will start up first, Plus! or Messenger. This proces is repeated every time you close MSN Messenger.
So either:
* Remove the setting in MSN Messenger "run at win startup"
* Remove Messenger Plus!
* Make your own small startup script which starts up Plus!, wait a few secs and then run MSN Messenger (and you can leave the "run at win startup" unticked in that way) and add a run-key value for the script <--- not officialy recommended and only to be used at own risk and if you have the knowledge...
Hi again CookieRevised,
I removed the MSN Messenger "run at win startup" setting and rebooted. MSN messenger did not run automatically after logging in. The hook must have worked like you said however because after starting MSN Messenger from the startmenu the problem did not occur (no notification).
I am sorry to say I do not have the skills to write my own startup script to ensure the proper start order of Messenger Plus and MSN Messnger. I know there are some programs out there that help define startorder of programs after logging in with delays if necessary.
Thanks for the tip on Ad-watch. I was not aware of the holes in its detection routine. Like you said it is just an extra add-on for Ad-Aware. I still like Ad-Aware itself though
. Will try to find an alternative to Ad-Watch.
Thanks for you help,
Thor
