Only issue I've been having with 5.57 is that when I open up another instance everything is slow. I.E. loading a stream from the net, opening up an audio file, and closing that instance. This problem happened with the beta.
Lino Morales and Louie Lab. Email and Windows Messenger : lino.morales@xxxxxxxxx For Great Internet radio, check out: www.lljfm.net On 12/20/2009 2:04 AM, Sunshine wrote:
i will have to agree with chris, here window eyes has had no problems with winamp at all and is a better choice for winamp users.----- Original Message ----- *From:* deana brown <mailto:dbrowntx@xxxxxxxxx> *To:* winamp4theblind@xxxxxxxxxxxxx <mailto:winamp4theblind@xxxxxxxxxxxxx> *Sent:* Saturday, December 19, 2009 9:23 PM *Subject:* Re: Winamp 5.57 and JAWS 11 I've been telling Fs about how I have Windows Vista Home premium 64 bit. My problem is Jaws won't tell me the names of the tracks when I hit the b key. They told me they didn't know what the problem was. I'm begginning to loose my patience with them as well. *From:* arlene <mailto:nedster6@xxxxxxxxx> *Sent:* Saturday, December 19, 2009 5:12 PM *To:* winamp4theblind@xxxxxxxxxxxxx <mailto:winamp4theblind@xxxxxxxxxxxxx> *Subject:* Re: Winamp 5.57 and JAWS 11Preach it brother! I had some problem with an earlier version of Jaws and winamp. I wrote and called Fs and told them my problem. I let them hear from my computer the problem. They fixed the problem they told me where to go in the task manager. If you don't hear from them after writing you might want to call them and let them hear it for themselves from your end!----- Original Message ----- *From:* Chris Skarstad <mailto:rascal0826@xxxxxxxxxxx> *To:* winamp4theblind@xxxxxxxxxxxxx <mailto:winamp4theblind@xxxxxxxxxxxxx> *Sent:* Saturday, December 19, 2009 2:21 PM *Subject:* Re: Winamp 5.57 and JAWS 11 This has got to be incredibly frustrating, I was able to switch to Window-eyes, and I'm very glad I did. I'm not saying that to start the old JAWS verses window-eyes debate cause haven't we been down that road more times than we care to count? Bottom line, FS needs to fix this, and many other problems with JAWS. I mean, JAWS's interaction with Winamp should not cause this type of problem, especially when other screenreaders don't exhibit the same sort of behavior. You should be able to close Winamp whenever the hell you want to, you should not have to kill it from the task manager! the average user doesn't even know what, or where the task manager is, how to kill a running process, or any other problem of that sort. Ok i'm shutting up right now because I'm not trying to cause fights on here. Just speaking my mind. I hope it's not a problem for everyone using JAWS 11. If you are experiencing this, write to FS and tell them, and don't quit until the problem is actually addressed. At 03:07 PM 12/19/2009, you wrote:Hi Folks, I do not know if this is the case with earlier versions of JAWS, but with JAWS 11 and Winamp 5.57, there is the return of the problem wherein JAWS holds elements of Winamp in memory for anywhere from several seconds to several minutes after you exit the Winamp program. The exact detailed nature of this old issue is quite complex so I won't give any detailed report in this post. It suffices to say that at least on my system and a few other people I have spoken to, that if you exit Winamp and then a few seconds to a few minutes later, you decide to load another file into Winamp by clicking on it from a folder on your hard drive, that Winamp will not load and the file will not play. You must go to the task manager and kill the Winamp process to rectify the problem. Using any other screen reader, Window-Eyes, NVDA, System Access, I do not experience this problem. "every time I say something they find hard to hear they chalk it up to my anger and never to their own fear" Ani Difranco: I'm Not A Pretty Girl 1995 __________ Information from ESET NOD32 Antivirus, version of virus signature database 4702 (20091219) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.comTo post a message to the list, send it to winamp4theblind@xxxxxxxxxxxxxx To unsubscribe from this mailing list, please send a message to: winamp4theblind-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/winamp4theblind> If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list directly. Instead, please contact the list owners at winamp4theblind-admins@xxxxxxxxxxxxxx ------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.427 / Virus Database: 270.14.114/2575 - Release Date: 12/19/09 08:33:00
