Steve Kemp
December 5th 03, 02:31 PM
Now this is why I like newsgroups... Keith, that was exactly the problem! I
was going through my head the changes between noticing the problem and the
last time it worked.... I remembered the driver update and even had my mouse
on the roll back option and thought "Nahhh couldn't be, a driver problem
would affect more than just messenger".
So for the record my motherboard has an on-board NIC "Intel(R) PRO/100+
Server Adapter (PILA8470B)". Installing the "Intel network software update
released on March 04 2003" from the Drivers Update section of WindowsUpdate
caused the one-way only communication problem with Windows Messenger. I
didn't write down the updated driver version before rolling back, however
the old, and now working driver version is 6.1.3.0 dated 2002-Feb-02.
"Keith Jack" > wrote in message
...
> Mine quit working when I updated the networking driver from Intel. Rolled
it
> back, and works fine again.
>
>
>
> "richard" > wrote in message
> ...
> > Well I am running the software on two different brand new
> > machines. They only difference between the one that
> > works and the one that doesn't is that the one that works
> > is an AMD with an Asus motherboard and the one that
> > doesn't work is an intel motherboard and processor. The
> > intel board is brand new and is running at 800 mhz bus
> > speed. The processor is using hyperthreading. The
> > machines have the same video card which are both geforce
> > 5600. They both an running office and Norton antivirus.
> > I thought the problem was the sound card perhaps so I
> > disabled the onboard card and installed a soundblaster x
> > gamer but it did the same thing even with the mic plugged
> > into the xgamer card instead of the on board sound. So
> > its not the sound card that is the problem.
> > >-----Original Message-----
> > >Now that is really interesting.... Not that I know what
> > it means. My STRONG
> > >suspicion is that this is a recently introduced bug that
> > only affects some
> > >computers. I noticed that we snagged a MS Messenger
> > developer a few postings
> > >back. So now I guess we wait until they find a solution.
> > Hopefully our
> > >discussion has shed some light on it.
> > >
> > >In the meantime I'll answer any questions about my
> > configuration that they
> > >have (HINT HINT). Resolving this is important to me
> > because one of the
> > >computers that I cannot "voice" communicate with is
> > VPNing into our network.
> > >Using Messenger is a lot cheaper than phoning Arizona
> > from Ontario!
> > >
> > >
> > >"richard" > wrote in message
> > ...
> > >> My messenger acts the same as yours in both
> > >> circumstances. It gives me that error message even
> > when
> > >> none of the referenced programs are running and I got
> > >> into the task manager and shut them down if they are
> > >> running in the background but it still won;t shut down
> > as
> > >> you say. But if I do the setting you mentioned it then
> > >> immediately quits when you sign out.
> > >> >-----Original Message-----
> > >> >Richard: On your afflected computer, can you exit
> > >> messenger?
> > >> >
> > >> >When I attempt to shut down messenger on my affected
> > >> machine it complains
> > >> >that "There are other applications currently using
> > >> features provided by
> > >> >Windows Messenger... " This is also recently new
> > >> behaviour. I don't know if
> > >> >the two are connected... However they could be. The
> > >> unaffected computer do
> > >> >not have this problem.
> > >> >
> > >> >What is really interesting is if I turn off the "Allow
> > >> this program to run
> > >> >in the background option" then I can exit messenger
> > >> (i.e. it exits instead
> > >> >of hiding the window when I click the X icon in the
> > >> window).
> > >> >
> > >
> > >
> > >.
> > >
>
>
was going through my head the changes between noticing the problem and the
last time it worked.... I remembered the driver update and even had my mouse
on the roll back option and thought "Nahhh couldn't be, a driver problem
would affect more than just messenger".
So for the record my motherboard has an on-board NIC "Intel(R) PRO/100+
Server Adapter (PILA8470B)". Installing the "Intel network software update
released on March 04 2003" from the Drivers Update section of WindowsUpdate
caused the one-way only communication problem with Windows Messenger. I
didn't write down the updated driver version before rolling back, however
the old, and now working driver version is 6.1.3.0 dated 2002-Feb-02.
"Keith Jack" > wrote in message
...
> Mine quit working when I updated the networking driver from Intel. Rolled
it
> back, and works fine again.
>
>
>
> "richard" > wrote in message
> ...
> > Well I am running the software on two different brand new
> > machines. They only difference between the one that
> > works and the one that doesn't is that the one that works
> > is an AMD with an Asus motherboard and the one that
> > doesn't work is an intel motherboard and processor. The
> > intel board is brand new and is running at 800 mhz bus
> > speed. The processor is using hyperthreading. The
> > machines have the same video card which are both geforce
> > 5600. They both an running office and Norton antivirus.
> > I thought the problem was the sound card perhaps so I
> > disabled the onboard card and installed a soundblaster x
> > gamer but it did the same thing even with the mic plugged
> > into the xgamer card instead of the on board sound. So
> > its not the sound card that is the problem.
> > >-----Original Message-----
> > >Now that is really interesting.... Not that I know what
> > it means. My STRONG
> > >suspicion is that this is a recently introduced bug that
> > only affects some
> > >computers. I noticed that we snagged a MS Messenger
> > developer a few postings
> > >back. So now I guess we wait until they find a solution.
> > Hopefully our
> > >discussion has shed some light on it.
> > >
> > >In the meantime I'll answer any questions about my
> > configuration that they
> > >have (HINT HINT). Resolving this is important to me
> > because one of the
> > >computers that I cannot "voice" communicate with is
> > VPNing into our network.
> > >Using Messenger is a lot cheaper than phoning Arizona
> > from Ontario!
> > >
> > >
> > >"richard" > wrote in message
> > ...
> > >> My messenger acts the same as yours in both
> > >> circumstances. It gives me that error message even
> > when
> > >> none of the referenced programs are running and I got
> > >> into the task manager and shut them down if they are
> > >> running in the background but it still won;t shut down
> > as
> > >> you say. But if I do the setting you mentioned it then
> > >> immediately quits when you sign out.
> > >> >-----Original Message-----
> > >> >Richard: On your afflected computer, can you exit
> > >> messenger?
> > >> >
> > >> >When I attempt to shut down messenger on my affected
> > >> machine it complains
> > >> >that "There are other applications currently using
> > >> features provided by
> > >> >Windows Messenger... " This is also recently new
> > >> behaviour. I don't know if
> > >> >the two are connected... However they could be. The
> > >> unaffected computer do
> > >> >not have this problem.
> > >> >
> > >> >What is really interesting is if I turn off the "Allow
> > >> this program to run
> > >> >in the background option" then I can exit messenger
> > >> (i.e. it exits instead
> > >> >of hiding the window when I click the X icon in the
> > >> window).
> > >> >
> > >
> > >
> > >.
> > >
>
>