Just so we're clear. Live essentials and security essentials are different. Yes yes, they both have the same name you say, but we all know by now that Microsoft can't brand something to save their life. It's like Steven King and endings to novels, or Dan Brown and actual content, or Pinky and the Brain and escaping from the lab. It's just a fact of life, *smile*. Accept, move on, pass go and collect 200 dollars. Take care, Sina -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Saturday, October 23, 2010 1:15 PM To: programmingblind@xxxxxxxxxxxxx Subject: RE: fix for the windows live messenger issue. Email's like this are very funny. First off if it was not for Essentials some of the viruses I have run into both at work and home would not have been caught and that includes all the most used nod32 Norton and mcfee. Second if people did stuff like this in the past we would have dumped Microsoft when IE 6 came out and none of us could use it. I will give Jaws till 12 to fix it then I will scrap windows live messenger but there is no way I will drop essentials. Oh one more thing. You could have unchecked the box at update time that said update all windows live programs. Then you could have chosen to only update essentials or others but not windows live. I actually updated all to see if it was still accessible. I have skype till it is fixed and there is no reason to blow a gasket. Welcome to accessibility lag. The screen readers cannot keep up not even Mac screen reader keeps up. I know cause I have the beta on the IPhone and let's just say I have found 4 accessibility lags there maybe just maybe if some of us were beta testing the windows live and working on the scripts this would not have been a problem. Windows live messenger is accessible the scripts just need a bit of tweaking maybe if the scripts are open enough I will go see what is erroring. Ken -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Øyvind Lode Sent: Saturday, October 23, 2010 8:06 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: fix for the windows live messenger issue. I have killed Live Messenger and all additional tools installed by the Live Essentials package. I will never install a M$ Live crap program again. I would like to try Miranda but as Tyler said it seems hard to get up and running. I can't find any up to date JAWS scripts either. I've seen a lot of frustration towards Apple on this list recently. But in my opinion M$ is even worse. On 23.10.2010 00:35, Tyler Littlefield wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I thought about Miranda, but getting it going seems to be a pain. a > plugin here, a plugin there, a script here... and google shows lots of > them that are old and outdated (running on jaws 4.0)... Is there a > good source for a nice clean accessible miranda? > On 10/22/2010 4:15 PM, Jared Wright wrote: >> I just use aggragate clients--Miranda on Windows, Pidgin on Linux. >> All those branded IM clients have far greater problems than their >> substandard accessibility implementations. >> On 10/22/2010 04:56 PM, Ken Perry wrote: >>> I just joined the teeny boppers and use skype till its fixed. >>> >>> Ken >>> >>> -----Original Message----- >>> From: programmingblind-bounce@xxxxxxxxxxxxx >>> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Tyler >>> Littlefield >>> Sent: Friday, October 22, 2010 1:35 AM >>> To: programmingblind@xxxxxxxxxxxxx >>> Subject: fix for the windows live messenger issue. >>> >> Hello all, >> I just remembered my friend had this same problem. Good news: There >> is a copy of windows live that still works: at oldversion.com, it's >> called msn messenger. it says beta in the title, but hell, it works >> until fs finds a fix and decides to charge you another SMA, then you can >> upgrade. >> Enjoy! >> -- Thanks, >> Tyler Littlefield > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind >>> > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind >>> > >> __________ >> View the list's information and change your settings at >> //www.freelists.org/list/programmingblind > > > > > - -- > Thanks, > Tyler Littlefield > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJMwhGjAAoJELDPyrppriJPtmcH/2/q2jduwVxbgQmXOQjIKvnp > b/c/1X039moDzu/Xv+19DoLW703v95WElUK8bKuL03AJ36aXPORNlrcZHTwOeKbg > fJaN4FMdx4hqSX44j8+7DQKIsu7M1zMwY76dq0ulNEfOIF12YsK7xmnjNkC4K9ND > /WXv9S0c+Yx2qyyUV7igUoA7IixKoqztwwloP8UCWxAvQlk7blY5Y47bo5lCfU8M > nbZlij4ULYe52garFzcsW/K8Tk+APM+xVyDr4al4WcDAD7X4m6B5V22Afs2d/Xrt > oX3Q2IiHbAMuUgEKNsZs/I/BaSeYkmGKmxzbFey/pYW/Ih2tNQI+8RdzYKnpfPU= > =b49F > -----END PGP SIGNATURE----- > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind