P
Patrick G.
Hey all.
Quick question.
Ok, Messenger is a bit of a hassle for me. I recently
put together a new system (Athlon XP running at 2+ghz,
512 meg of ram, yada yada yada) and put Windows XP pro on
it. I use Outlook Express as my mail client and noticed
that Messenger was opening itself whenever I used OE.
I also noticed that about half the time, Messenger
refused to let itself be closed (giving me that "some
programs are still using me!" message) even after Outlook
Express and IE were completely shut down and there were
no programs running that should have been using messenger
(IE: all that was left running was the keyboard and mouse
support software and the Antivirus scanner - which is
Symantec Antivirus Corporate Edition (2002)).
I have since done my homework and know that OE likes to
rely on the Messenger API's. I assume that this is to
speed up some processes that it otherwise has to
initialize on its own.
Anyway, Since I don't use messenger at all, I decided to
disable it (using services.msc and gpedit.msc, since it's
Win XP pro). I disabled it just fine, and like a good
little service it is staying out of my system tray, which
I like.
HOWEVER, now I've got an additional 20-30 seconds (I kid
you not, I timed it) load time just to open Outlook
Express as an application. On a 2ghz machine with half a
gigabyte of RAM, that's just silly. I am guessing that
this must be due to Outlook not being able to use the
Messenger APIs (I hadn't changed anything else on the
machine when I made this change). But honestly, when I
stop an entire extra application from running, shouldn't
that speed up the machine, rather than bogging it down
more?
Is there any way I can restore the quick load time of OE
without the hassle of having that invasive (and
pervasive) Messenger constantly in my face? Is there a
way that I can set outlook express to load up the
messenger APIs as some sort of module, so that Messenger
isn't constantly loading itself into my system memory and
slowing me down?
Quick question.
Ok, Messenger is a bit of a hassle for me. I recently
put together a new system (Athlon XP running at 2+ghz,
512 meg of ram, yada yada yada) and put Windows XP pro on
it. I use Outlook Express as my mail client and noticed
that Messenger was opening itself whenever I used OE.
I also noticed that about half the time, Messenger
refused to let itself be closed (giving me that "some
programs are still using me!" message) even after Outlook
Express and IE were completely shut down and there were
no programs running that should have been using messenger
(IE: all that was left running was the keyboard and mouse
support software and the Antivirus scanner - which is
Symantec Antivirus Corporate Edition (2002)).
I have since done my homework and know that OE likes to
rely on the Messenger API's. I assume that this is to
speed up some processes that it otherwise has to
initialize on its own.
Anyway, Since I don't use messenger at all, I decided to
disable it (using services.msc and gpedit.msc, since it's
Win XP pro). I disabled it just fine, and like a good
little service it is staying out of my system tray, which
I like.
HOWEVER, now I've got an additional 20-30 seconds (I kid
you not, I timed it) load time just to open Outlook
Express as an application. On a 2ghz machine with half a
gigabyte of RAM, that's just silly. I am guessing that
this must be due to Outlook not being able to use the
Messenger APIs (I hadn't changed anything else on the
machine when I made this change). But honestly, when I
stop an entire extra application from running, shouldn't
that speed up the machine, rather than bogging it down
more?
Is there any way I can restore the quick load time of OE
without the hassle of having that invasive (and
pervasive) Messenger constantly in my face? Is there a
way that I can set outlook express to load up the
messenger APIs as some sort of module, so that Messenger
isn't constantly loading itself into my system memory and
slowing me down?