quote:
Originally posted by ahmetgns
Maybe only Patchou can explain why his loader calls the original msnmsgr.exe file.
ah... but that's maybe because it gets its "info" from the registry where the Messenger's libraries are registered or something like that.
See
HKCR\SOFTWARE\Classes\CLSID\*
HKLM\SOFTWARE\Classes\CLSID\*
eg:
HKEY_CLASSES_ROOT\CLSID\{F81CD990-910B-4bbf-9CB3-6A77F3D697B3}
although the loader would only load when the messenger program in the same dir is executed... blah... dunno how all the hooks work and what he exactly does, so....
----------
Maybe a fairly simple solution would be to create a small batch file or WSH script which you can put in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.
Simply check who has logged in and according to that rename/copy the addon loaders to their proper name or remove them. Or set/unset some registry key. (depending on how SP and MDL hook themselfs into Messenger these days (dunno)). Such a batch or script would only be a few lines of code.
eg:
IF [%USERNAME%]=[ahmetgns] (
COPY /Y msimg32.ori msimg32.dll
) ELSE (
DEL msimg32.dll
)
will only work if you don't automatically start Messenger when you login to Windows though. Otherwise it might sometimes not work depending on what is loaded first; Messenger or the batch file.
/ 
