What's this Process Monitor for? My firewall is complaining about it wanting to surf the web all the time... Not spyware or trojan-like stuff, I hope.

platina

From the Msgplus Changlog page:

quote:

---

Originally posted by http://www.msgplus.net/changelog.php
A new DLL has been added to the software, called MsgPlusLoader.dll. This DLL is now the one that will be loaded by Windows for the global hooking operations. This modification should lower considerably the impact of Messenger Plus! on older systems as this light-weight DLL doesn't allocate more than a few bytes of memory in any situation. It may also reassure some of the people who wonder why Messenger Plus! gets loaded by Windows in several other processes (this DLL contains almost no code so there can't be any risk involved).

---

It is most likly monitoring the processes waiting for messenger to be loaded.
I cant see why it will be trying to access the web, my firewall (zone alarm) doesnt metion it.
What firewall are you using.

Also Messenger plus is 100% spyware and trojan free.

quote:

---

Originally posted by Madman
It is most likly monitoring the processes waiting for messenger to be loaded.
I cant see why it will be trying to access the web, my firewall (zone alarm) doesnt metion it.
What firewall are you using.

Also Messenger plus is 100% spyware and trojan free.

---

quote:

---

Originally posted by platina
I'm using Outpost Firewall. Actually, not the DLL-file itself tries to access the internet, but when I open i.e. InternetExplorer, or Firefox or whatever, Outpost tells me that one of its components has changed, in this case MsgPlusLoader.

Also, what is it waiting for? Which processes would Messenger (or Plus) want to load?

---

quote:

---

Originally posted by Madman

This way plus doesnt have to be loaded all the time, meaning there is less load on older systems.

---

quote:

---

Originally posted by platina

quote:

---

Originally posted by Madman

This way plus doesnt have to be loaded all the time, meaning there is less load on older systems.

---

Hmm, thanks

So I can remove the MsgPlus.exe from my startup registry (MSconfig)?
Because MsgPlusLoader.dll is taking care of getting Plus to run? Or am I wrong..

And what's the difference with RichEdHook.dll, I thought this would hook up Plus with Messenger.

---

quote:

---

Originally posted by platina
So I can remove the MsgPlus.exe from my startup registry (MSconfig)?
Because MsgPlusLoader.dll is taking care of getting Plus to run?

---

quote:

---

Originally posted by WDZ

quote:

---

Originally posted by platina
So I can remove the MsgPlus.exe from my startup registry (MSconfig)?
Because MsgPlusLoader.dll is taking care of getting Plus to run?

---

I don't think so, because if MsgPlus.exe doesn't run, what will get MsgPlusLoader.dll loaded?

---

MsgPlus is the main program. The only thing it does is hooking a current loaded MSN Messenger. It loads the DLL. It will not be attached itself to each one of your processes by windows. The thing that get's attached by windows is the DLL not the EXE. Because the DLL has only a few simple functions, it takes far less resources then when the EXE should have been attached. In the earlier Plus! versions, the routines inside the DLL were part of the EXE and the whole EXE got loaded each time, now only the needed routines are loaded. That's the difference...

^^ possible some small errors in the text. But for now, that's roughly what happens. Patchou is the one that can explain you in detail what happens.

Cookie is right. Ialso want to add something: MsgPlusLoaded does NOT, under anycircumstances, connect to the internet or anythign else. Its code is extremely straightforward: when a window is created, it checks if it's a Messenger window. If it is, then it loads MsgPlusH.dll, if not, then it does nothing.

Messenger Plus! has always worked likethis, however, the window detection was previously part of MsgPlusH.dll and I thought some people may be suspicious of it (MsgPlusH.dll contains a lot of code that does a lotof stuff). By separatingthe global hook detection code from the rest, I just made sure pople withsomebasic knowledge in assembly could see that the dll does nothing in other processes.