K
Kim Letkeman
I was trying to establish voice contact with my father across the Internet.
We both run MSN Messenger 6.1 and it managed to connect several times this
morning. This was the first time we got a connection in a very long time.
But I could not hear him and he could not hear me. So I asked him to ask for
remote assistance so I could check his audio settings. That's when our
problems began.
As soon as he requested remote assistance, messenger told me I needed a new
version of Windows Messenger, and pointed me to the site. I went there and
installed WM 4.7, which seemed strange to me. The install had some issues,
but seemed to go ok in the end. After the restart, we were able to run
remote assistance for the first time in 6 months at least. Very promising. I
worked with him to get his USB handset all set up using his audio tuning
wizard and we were ready to establish voice connectivity again.
Only this time, it failed to connect. I tried several times and gave up. So
I shut down the remote assistance and closed down my Windows Messenger 4.7
session, then started up an MSN Messenger 6.1 session, which had worked this
morning several times. And of course it continued failing. So now my
Messenger setup can no longer do voice, which has been my problem for a year
or so.
I have once again been forced to use Yahoo voice, which never fails to
establish a connection. Ever .....
I can only wonder how MS program managers can continue having two competing
versions of Messenger that clearly do not work well together and are both
required for different operations? What are they thinking?
Anyone know why updating Windows Messenger would suddenly toast my audio,
after fixing my remote assistance?
We both run MSN Messenger 6.1 and it managed to connect several times this
morning. This was the first time we got a connection in a very long time.
But I could not hear him and he could not hear me. So I asked him to ask for
remote assistance so I could check his audio settings. That's when our
problems began.
As soon as he requested remote assistance, messenger told me I needed a new
version of Windows Messenger, and pointed me to the site. I went there and
installed WM 4.7, which seemed strange to me. The install had some issues,
but seemed to go ok in the end. After the restart, we were able to run
remote assistance for the first time in 6 months at least. Very promising. I
worked with him to get his USB handset all set up using his audio tuning
wizard and we were ready to establish voice connectivity again.
Only this time, it failed to connect. I tried several times and gave up. So
I shut down the remote assistance and closed down my Windows Messenger 4.7
session, then started up an MSN Messenger 6.1 session, which had worked this
morning several times. And of course it continued failing. So now my
Messenger setup can no longer do voice, which has been my problem for a year
or so.
I have once again been forced to use Yahoo voice, which never fails to
establish a connection. Ever .....
I can only wonder how MS program managers can continue having two competing
versions of Messenger that clearly do not work well together and are both
required for different operations? What are they thinking?
Anyone know why updating Windows Messenger would suddenly toast my audio,
after fixing my remote assistance?