It behaves like it should...
some elaboration from my side
:
There is no Plus! menu when you right click the icon in your system tray, that's normal. Plus! only adds a menu in the main screen of MSN Messenger (aka: your contactlist).
So not seeing a menu when you right-click the icon doesn't mean that Plus! hasn't started up. It is running just fine, proof: open the contactlist and the Plus! menu will be there; or CTRL-AL-DEL and you'll see the process.
quote:
Originally posted by Joel
Extreme:If i use the /winstart parameter, it will not start.
Yes it will. The only "problem" is that you edited/played around in the registry and thus the "chain of events" is broken. What I mean is, when /winstart is used, Plus! will be started up, checks for another registry value and then quits. That other registry value is the value which holds the normal startup key for Messenger. Because you changed some settings (automatically startup in Messenger, or deleting startup keys) this doesn't work properly anymore.
quote:
Originally posted by Joel
But without the winstart parameter, it will start, but will not appear in the MSN window.
Proberly because Plus! is loaded after MSN Messenger. This can happend and this is exactly the reason why you shouldn't remove the parameter (or the reason why you shouldn't play around with startup options if you don't know exactly how they work and what they do
)
To fix all this:
1) Remove all the startup keys from Messenger Plus! and MSN Messenger
2) Startup Plus! manually
3) Startup MSN Messenger manually
4) Go to the MSN Messenger options:
Enable:
Tools > Options > General > Automatically run Messenger when I log on to Windows
5) Go to the Messenger Plus! options:
Enable:
Plus! > Preferences > Miscellaneous > Force Messenger Plus! to load when computer starts
6) Exit MSN Messenger completely (right-click the MSN Messenger icon and choose
Exit)
7) Now on your next reboot, Plus! and MSN Messenger will start up both together in the right order.
To know more and in detail what exactly happens with the /winstart parameter, read:
CookieRevised's reply to Startupmonitor issue
(but ignore the given workaround in that thread as it is for people who have issues with startupmonitors)
/ 
