What does the "Force Messenger Plus! to load when computer starts" option really do? (Besides setting HKEY_LOCAL_MACHINE\SOFTWARE\Patchou\MsgPlus2\ForceLoad = 1).

Sometimes plus! won't load before MSN, don't ask me why . And this makes sure, it always loads before MSN.

That's all I know

What I mean is how does that work, how does it ensure Plus will load before Messenger?

That's something I don't know

Well, I asked this because I want to add a checkbox to my AppLoader program so you can easily enable/disable MsgPlus autorun at Windows startup (and open it whenever you want from AppLoader), and I didn't want to break anything. I guess just removing MsgPlus' key from the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run) will work (it seems to be set by the installer).

As you know, when you select "Automaticly run Messenger when I log on to Windows" in MSN Messenger, MSN Messenger adds a key to the registry:
=> HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
=> msnmsgr := "C:\Program Files\MSN Messenger\msnmsgr.exe" /background
This will make that MSN Messenger starts up when you start up Windows...
(note: this key is added each time Messenger starts up.*)

Also, when you've selected that "autorun"-option from Messenger, Messenger Plus! will delete the "msnmsgr"-key again and add its own key there when Messenger is closed:
=> MessengerPlus3 := "C:\Program Files\Messenger Plus! 3\MsgPlus.exe" /WinStart
(note: this key is added/replaced each time the process of Messenger ends (and Plus! is still running of course).*)

/WinStart makes that Messenger Plus! initialize first (like always) and then that it automaticly starts up MSN Messenger itself and hooks it.

If you don't use /WinStart, then Plus! wont start Messenger automaticly. But due the way that Windows handles the startup items, there is no way in making sure that Plus! is started before Messenger in that case.
In many situations this isn't realy a problem because most startup processes don't take long and Plus! will have enough time to hook into Messenger, even when it is started up after Messenger. But this is only true if there is a fraction of time between the two processes starting up, otherwise Plus! will give a "timeout" in the form of the recovery window.

Now, to make sure that Plus! tries to hook Messenger longer and more agressively (with more tries then normal), you can select the option "Force Plus! to load when computer starts" in Messenger Plus!.

This will set that registry key: ForceLoad := 1. Whenever Plus! is started up, it reads out that key and when it is true, it performs the "more agressive" method for hooking...



* because of this beheviour, you'll get a popup with a tool like StartupMonitor each time that Messenger starts (like every time you log into Windows) because it can find its key in to run-section (because plus! replaced it) and adds it again. And you'll get also a popup each time that Messenger quits because then Plus! removes the entry again... (given this, there is a workaround to this problem: just unselect the "autostartup"-option in Messenger and leave the Plus! entry (with /WinStart) in the run-section...)


EDIT: I hope, I've edited out the mistakes now

Hum... you should edit your pot Cookie because you're not exactly right.

What you're describing with /Winstart is true, however, this behavuiour always occurs by default and has nothign to do with the recovery window. The /winstart method ensures Plus! is always loaded before Messenger when Windows starts (Plus! loads Messenger itself when it detects everything has been prepared).

The force option is here only in case of software malfunction. Some programs that are using hooks are not written properly and prevent other similar programs (like Plus!) to work properly. This happens if such program is loaded after Plus! is loaded and as Plus! tries its best to load as fast as possible, if you have such a defective program installed on your computer, you can be almost sure you'll get the problem.

The "force load" option tried to fix this problem by doing somethign very uncommon: it starts a timer and recreates its global hook every 5 seconds for a minute or so. That way, if another software hooks the syste unproperly while windows is starting, Plus! rehooks over it and the problem is solved. However, some systems may not like Plus! doing this kind of stuff and that'S why the force load option should be used only when it's necessary, it's not a toy to play with.

Hope it helps you,
Patchou

Plus loads on my computer even when i have Diagnostic Startup selected.  Plus is the only program to start.

quote:

---

Originally posted by Patchou
Hum... you should edit your pot Cookie because you're not exactly right.

---

What's wrong is that the Messenger key is always deleted and replaced wy a /WinStart Plus! one. It has nothing to do with the force load option .

oh I see, yeah... hmm... I drasticly edited my post now... I hope it's correct this time

Thank you guys, it's very clear now

However, I've been doing some tests under a virtual machine with a clean Windows XP and noticed something:

I installed MSN Messenger 6.2 and then Plus. MSN Messenger set itself at startup in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Plus set itself at startup in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.

I closed MSN Messenger but Plus didn't replace the MSN Messenger startup key with the Plus one with "/WinStart" as expected.

I checked the registry, in HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger, AppSettings was = 62 00 00 80 (autorun disabled), but in the Options window it was enabled!


When I clicked OK there, then it changed to 62 02 00 80 (autorun enabled) and when I closed MSN Messenger, Plus did what I expected it to do in the first place.



So, my question is how does Plus read the AppSettings value to determine if MSN Messenger should start when Windows starts? Its value depends on many options (it's not always "62 00 00 80" for autorun disabled like in my case, it depends on the other options aswell).
Hope I was clear

quote:

---

Originally posted by lopardo
So, my question is how does Plus read the AppSettings value to determine if MSN Messenger should start when Windows starts?

---

EDIT (3hours later):

quote:

---

Originally posted by lopardo
So, my question is how does Plus read the AppSettings value to determine if MSN Messenger should start when Windows starts?

---

quote:

---

Originally posted by lopardo
I installed MSN Messenger 6.2 and then Plus. MSN Messenger set itself at startup in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Plus set itself at startup in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.

---

lol... you're right, here is the code . I think you found out pretty much everythign anyway. As for "HandleMessengerStart" it's just here as a user setting (how did you know about it? I don't remember giving this information publicly . I added it in case someone wouldn't want Plus! to create it's own /Winstart key for some obscure technical reason.

code:

---

//
///////////////////////////////////////////////////////////////
void CMsgPlusUtilWnd:reventAutoMessengerStart()
{
    try
    {
        TRACE("CMsgPlusUtilWnd:reventAutoMessengerStart - called");

        //Removes Messenger from Windows starts and remember the command lines
        CRegKey reg;
        if(reg.Open(HKEY_CURRENT_USER, _T("Software\\Microsoft\\Windows\\CurrentVersion\\Run")) == ERROR_SUCCESS)
        {
            TCHAR sPath[1024]; sPath[0] = '\0';
            ULONG nSize = 1024;
            reg.QueryStringValue(CPreferences::GetMessengerVersion() < 5 ? _T("MSMSGS") : _T("msnmsgr"), sPath, &nSize);
            reg.DeleteValue(_T("MessengerPlus2")); //Delete the old value

            CRegKey regMP;
            regMP.Create(HKEY_CURRENT_USER, _T("Software\\Patchou\\MsgPlus2"));
           
            DWORD nEnable = 1;
            regMP.QueryDWORDValue(_T("HandleMessengerStart"), nEnable);
            if(nEnable)
            {
                //First, check if we can do something here
                regMP.QueryDWORDValue(_T("HandleMessengerStart"), nEnable);
                if(sPath[0] == '\0')
                {
                    TCHAR sMPPath[1024]; sMPPath[0] = '\0';
                    DWORD nSize = 1024;
                    regMP.QueryStringValue(CPreferences::GetMessengerVersion() < 5 ? _T("AutoMsg4Start") : _T("AutoMsg5Start"), sMPPath, &nSize);
                    if(sMPPath[0] == '\0')
                        return;
                }

                //Check if Messenger is set to start automatically
                bool bMessengerStart = false;

                CRegKey regAdmin;
                DWORD nNotAdminMode = FALSE;
                if(regAdmin.Open(HKEY_CURRENT_USER, _T("Software\\Patchou\\MsgPlus2"), KEY_READ) == ERROR_SUCCESS)
                {
                    regAdmin.QueryDWORDValue(_T("NotAdminMode"), nNotAdminMode);
                    regAdmin.Close();
                }

                if(!nNotAdminMode)
                {
                    if(CPreferences::GetMessengerVersion() < 5)
                    {
                        CRegKey reg;
                        if(reg.Open(HKEY_CURRENT_USER, _T("Software\\Microsoft\\MessengerService")) == ERROR_SUCCESS)
                        {
                            DWORD nAppSettings = 0;
                            reg.QueryDWORDValue(_T("AppSettings"), nAppSettings);
                            if(nAppSettings & 0x200)
                                bMessengerStart = true;
                        }
                    }
                    else
                    {
                        CRegKey reg;
                        if(reg.Open(HKEY_CURRENT_USER, _T("Software\\Microsoft\\MSNMessenger")) == ERROR_SUCCESS)
                        {
                            DWORD nAppSettings = 0;
                            reg.QueryDWORDValue(_T("AppSettings"), nAppSettings);
                            if(nAppSettings & 0x200)
                                bMessengerStart = true;
                        }
                    }
                }

                //Add or remove our MP start value?
                if(bMessengerStart)
                {
                    //Add a special Messenger Plus! command line
                    string sMPCmdLine = _T("\"");
                    sMPCmdLine += CPreferences::GetMessengerPlusBinDir();
                    sMPCmdLine += _T("\\");
                    sMPCmdLine += CPreferences::GetMsgPlusExeName();
                    sMPCmdLine += _T("\" /WinStart");
                    reg.SetStringValue(_T("MessengerPlus3"), sMPCmdLine);

                    //Remember the path
                    if(sPath[0] != '\0')
                        regMP.SetStringValue(CPreferences::GetMessengerVersion() < 5 ? _T("AutoMsg4Start") : _T("AutoMsg5Start"), sPath);
                    reg.DeleteValue(CPreferences::GetMessengerVersion() < 5 ? _T("MSMSGS") : _T("msnmsgr"));
                }
                else
                    regMP.DeleteValue(CPreferences::GetMessengerVersion() < 5 ? _T("AutoMsg4Start") : _T("AutoMsg5Start"));
            }
            else
                reg.DeleteValue(_T("MessengerPlus3"));
        }
        TRACE("CMsgPlusUtilWnd:reventAutoMessengerStart - exited");
    }
    catch(...)
    {
        TRACE("An exception was thrown in CMsgPlusUtilWnd:reventAutoMessengerStart");
    }
}

---

Plus! source!

quote:

---

Originally posted by Patchou
As for "HandleMessengerStart" it's just here as a user setting (how did you know about it?

---

quote:

---

Originally posted by CookieRevised
these things can be found out with programs like Registry Monitor...

---

quote:

---

Originally posted by Dempsey
Plus! source!

---

Great! Now I understand

This is for Delphi:
function IsMessengerAutostartEnabled: Boolean;
var
  reg: TRegistry;
  Buffer: DWORD;
begin
  Result := False;

  reg := TRegistry.Create;
  try
    reg.RootKey := HKEY_CURRENT_USER;

    if (reg.OpenKey('\Software\Microsoft\MSNMessenger',False)) then
    begin
      try
        if (reg.ReadBinaryData('AppSettings',Buffer,SizeOf(Buffer)) = 4) then
        begin
          Result := (Buffer and $0200 <> 0);
        end;
      except
      end;
    end;
  finally
    reg.Free;
  end;
end;

One last thing though, how did you know that option was 0x200?

That's the easy part...

Select the option in Messenger, press ok, check the value in the registry...
Unselect the option in Messenger, press ok, check the value in the registry...
Compare the two....