I of course cannot say for sure, without seeing the machine, but quite honestly, this does not sound like a window-eyes problem. Window-eyes, is not going to interfere with the video intercept for Jaws for Windows. What you have here is a failing Windows operating system. Please remember that the screen reader hooks into the operating system in ways that other programs do not. Some problems that manifest themselves while the Screen reader is loaded, have absolutely nothing to do with the Screen reader itself. it has to do with an unstable operating system. As for Aaron failing to take a report. You have no reports to file. you have no error log. So this cannot be used for debugging purposes. you have no directions for reproducing the problem on a consistent basis. So they cannot reproduce the problem in house to generate an error report to do that debugging. So Aaron was not rude and refused to take your error report. You had no error report to offer. Now my personal recommendation is this. get an unattended xp cd, or get your friendly technician back over to your home. reinstall Windows reinstall window-eyes 6.1, And then reinstalled window-eyes 7.0 beta 1. You will find your experience much more pleasurable, after you do these things. Please note, you will probably encounter other problems with that operating system. As time goes by, and the operating system becomes more and more unstable.
-----Original Message----- From: Pam Drake [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 11:21 PM To: [email protected] Subject: FW: My experiences with the beta thus far. Long Post I am forwarding this message from Dave, who would like to hear any thoughts on the issues he has discussed. His address is listed below. It also serves as a follow-up to my cross post of last night concerning the strange problem he was having when attempting to reboot after returning home to find the computer unable to process a web page. I may add a comment or two here, and will so indicate. -----Original Message----- From: Dave McElroy [EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 6:45 PM To: 'Pam Drake' Subject: My experiences with the beta thus far. Please forgive the forward, as I've asked Pam to send this along since she is on the list and I am not as of yet. I am a relatively new Window-Eyes purchaser, having bought 6.1 at the beginning of the year. Therefore, I have downloaded V7 beta and installed it on a desktop PC, 512 MB ram with tripppletalk outboard speech, the PCI card. Initially, I seemed to have no problems. However, yesterday afternoon after some time away from the PC I seemed to be unable to navigate away from the web page I'd been using previously. As no keyboard command seemed to work, I gave the system a hard reboot. At the time the musical intro started, the whole system froze and the last chord of the intro just kept repeating like an endless loop. I attempted to reboot several times throughout the evening, believing that there might be some kind of a heat issue, but had the same result every time. With the help of a friend by phone, I managed to get the system into safe mode and then out again; I believe he hoped that running it in safe mode and then closing it might clear up whatever the issue was; it did not. Today, I had a sighted friend come in and he advised me that upon hearing the music, a failure notice appeared on the PC, talking about failure, a memory "dump" and indicating some problem with win32. We next went back into safe mode and uninstalled Window-Eyes 7.0, which was the most recent program I'd installed. The PC booted up without a hitch. Now not having Window-Eyes on the PC, I went into Jaws and I now get a video intercept error which I cannot correct. That is to say, I have taken the steps to reinstall the video intercept and it simply does not reinstall. I'll check this one out with FS tomorrow. As a final note, I attempted to report this situation to GW Micro this PM and was rather rudely advised by someone named Aron that unless I could reproduce the problem he was not going to accept the report as valid. I advised him that not having sighted assistance in this home on a regular basis does not incline me to attempt to reproduce this problem which I was unable to correct without sighted assistance. Now perhapse Aron thought that I was calling to lodge a complaint. What I was calling him for was nothing more than to offer an advisory and to advise him of the actions I'd taken to that point to address the issue. To be fair, arron did ask about the synthesizer, and did state that there *might* be a problem with the driver and its interaction with Window-eyes. This is something, however, which has not come up with version 6.1 and, until this time, I've been able to freely use both Jaws and Window-Eyes interchangeably with no problem. So in review, here is where we now stand. I have uninstalled Window-Eyes from my desktop intending to at the very least reinstall version 6.1 at some future date. However, as Jaws is now also mis-behaving, I believe it most prudent to address that video chaining issue prior to any reinstall of 6.1. For now, it might be wise for anyone operating an older Trippletalk to be aware of this potential. BTW, I'm open to any suggestions regarding the video chaining issue as well. Much thanks. David McElroy Pam's comments: Perhaps it would have been helpful if our friend Bill had dictated the exact text of the on-screen error message to Dave so he could repeat it word for word to Aaron. I had left the house for a dental appointment shortly after Bill arrived, so was not able to mention this at the time. Also, Bill had only a few moments to spare so Dave was trying to get the most work done in the shortest amount of time. This, indeed, is why he was reluctant to attempt to duplicate the error. Bill was not able to come to our home until some 20 hours after Dave telephoned him, and he is the closest person to our location who knows enough about computers to attempt to troubleshoot our issues when they occur. He is a computer technician recently retired from our County employment. As for duplication, the error occurred several times last night as Dave attempted to restart the computer, only to find the process reverting to a loop at the exact point in the boot sequence. So the error was in fact duplicated, but Dave lacked the empirical data to fully report it. I have assured Dave that the seeming lack of interest or concern he inferred from Aaron's failure to take a report is not the typical way in which the GW-Micro Staff respond to customer issues. Indeed, Aaron himself may not have realized how his response would be interpreted. It was fifteen minutes to closing time in Fort Wayne, but three hours earlier here in Visalia, California. Perhaps Aaron believed the Triple Talk issue was going to be researched, so there was no need to take a report. Dave believed he was providing valuable info to the testers, while Aaron was looking for supportive data which didn't exist. As Dave pointed out, he has only recently purchased Window-Eyes, and perhaps I have said too much about Staff's positive responsiveness, totally forgetting about the fact that everyone is human, especially at a quarter to closing time. <smile> Also, Dave has set Window-Eyes, and JAWS prior to his purchase of W/E, to load at startup. I have not installed the beta, but I do not use the load at startup option. I wonder what might have happened if he were to re-install the beta and load it manually. I may suggest he try this, but first he will contact Freedom Scientific for help in solving the video issue. I plan to check to see whether there have been any updates to the Triple Talk PCI software. In conclusion, I am sure the issue will be resolved, and trust Dave will continue to use and become more familiar with Window-Eyes as time goes on. I do believe this experience may have pointed out some issues needing examination, especially if the installation and subsequent of the beta may have interfered with the video dcm issues which are now so rare we've almost forgotten them. We would appreciate any thoughts anyone may have on these matters. I will forward any replies I receive to Dave, but please feel free to send me copies of any responses sent to him if you would like. Thanks for bearing with this very long post. Pam Drake If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [EMAIL PROTECTED] and include leave gw-info in the body of the message. If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search form at the bottom of the page. If you wish to unsubscribe from this list, send a message to [EMAIL PROTECTED] and include leave gw-info in the body of the message.
