Specifc questions relation to the Messenger twins (Windows and MSN) - Jonathan...?

[John S]

Hi...
Some specific questions relating to those unholy partners, aka
the Messenger family: MSN and Windows... (let's not even mention the
idiot cousin, the service...) Before you read on, I have read many of
the posts in this group and I suspect I am having a TMI syndrome (too
much information).


1) can Windows Messenger (WM) 5.xx co-exist with MSN Messenger (MM)
6.1 in a Windows 2000 Prof (wkstn) environment? I am keen to have WM
installed as it allows me access to VOIP services.

2) If so, can WM completely act in place of MSN? i.e. chat, audio,
video, access to Hotmail?

3) If not, what has to go and why

4) There is mention of an add-on for WM v4.7 that is supposed to give
it MM functionality in XP. Is this add-on needed for the environment
in (1) above? if so, why?

5) I run W2k behind ZoneAlarm Pro. I succeed in getting MSN to use
audio links by explicitly identifying the other party in my trusted
zone. For a static IP scenario, this works OK but it does mean, for
DHCP, I have to tweak ZoneAlarm every time. Question: what do I have
to do using WM? I have seen reference to opening ports 1863 and 443
TCP... (assuming the answer to question (2) above is "yes")

6) why are so many people asking - no, begging, pleading - to be told
how to uninstall WM? Is there spyware in there? adware? is it a
memory hog? is it buggy? what?

Thanks all, for your responses.

 

[Jonathan Kay [MVP]]

Greetings John,

1. No, only Windows XP can have both clients installed at the same time.

2. Windows Messenger 4.7 with the MSN Add-In will support Hotmail and other MSN services
like MSN Mobile/Profiles. Audio support will work with all clients, video support will work
with any Windows XP client (Windows Messenger or MSN Messenger) but not MSN Messenger (6) on
previous versions of Windows. Windows Messenger 5.0 does not have any Add-In functionality
and as such, the MSN (Hotmail, Profiles, etc.) Add-In is not present nor usable.

3. See above.

4. As said in 2, Windows Messenger 5 (the only version of Windows Messenger that runs on
Windows 2000) does not have Add-In support, and as such, does not have the functions
supported in the MSN Add-In.

5. It's exactly the same, although instead of the procedure you mentioned, you could just
set ZoneAlarm into the "Medium" setting, which would avoid having to explicitly put in the
IP. 1863/443 is how Windows Messenger and MSN Messenger login, this has nothing to do with
the audio connections

6. In Windows XP, it automatically starts with various applications, and at bootup time by
default. If you install MSN Messenger 6, Windows Messenger continues to start, with can
cause both clients to "battle" to login -- this is why you're seeing these requests.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

 

[John S]

Thanks Jonathan, for your helpful response.

After digesting it, I have the sense that Windows Messanger is not for
me, at least as an alternative for MSN messanger.

For VOIP applications, there are other clients out there I can use.

Thanks again.

 

[Jonathan Kay [MVP]]

Hi John,

You're very welcome =). One of the reasons why there is two clients is simply a matter of
personal choice and what features you specifically want.
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

 

[Jerry L]

It depends upon whether you want to use Microsofts' Live Communications
Server. If not, then you don't need Windows Messenger.