Hi Dave: Yup, having an idea of how the sausage is made gives you a better insight into what may be going on indeed. I too have sat through meetings both hot and snoozy and found the same things. It is likely, in AI Squareds case, they want to fix the problem but it is either too deeply embedded in the code base or it is the result of a complex combinations of factors and not easily correctible. Think of if it it is the whole senario of using a single threaded app and vbScript as a primary mechanism and if the very methodology is not very compatible with newer technologies - not saying this is the actual problem folks, no indication of that just an example of something that would require such a quantum change in the fundemental design that it would not be considered possible without almost a complete rewrite of the entire platform and likely beyond the cost capabilities of a smaller software house in any reasonable timeframe. Other situations exist less significant that could also cause meetings to get hot as Dave mentioned. Anyway, Dave, it is good to know someone else out there has been there and done that and has an understanding that working on a software team and trying to fix problems with a major piece of software is not like just typing a few lines of code and Bam! The problem is fixed. I think there is plenty of noise on this list and spilling over into other arenas which is hammering the WindowEyes reputation and they are indeed very interested in this problem. That said, like you, I am very interested in the results of that person who sent his, her, laptop into AISquared. That was going well beyond the normal role of a software client user and I too have never heard the results of that endevor from anyone - what was the problem and how did they fix it or, are we talking a worst case, perhaps extinction, senario here as mentioned above? Inquiring minds want to know - not to mention a large number of WindowEyes clients having these problems on a daily basis. Rick USA
-----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, September 30, 2015 8:00 PM To: Rick Thomas <[email protected]>; Window-Eyes Discussion List <[email protected]> Subject: Re: the on going saga of losing speech Hi Rick I worked for many years as a Software Tech for a Company that produced their own Software. So I am a little bit familiar with what goes on behind the Curtain, and it isn't always pretty. I wish I knew more about how the new 9.X version worked, and how the New Browse Mode handles the information it is to relay to the speech out put part of Window Eyes. If I did, perhaps I might be able to make better observations, and suggest things closer to the target. I am sure the guys at A I Squared are aware they have a per centage of their users who are suffering from these random failures. the problem is that they only have a small number of systems in their offices where they can test 9.X. And if all of those systems are set up correctly, version 9 might run like a Champ. And A I Squared can not duplicate the problem plaguing so many others. The other extreme is the problem is known, but the glitch in the code would require such a deep level over haul, it is impossible to fix for this edition of series 9. A fix like this might have to be suffered by the unfortunate few until edition 10 comes along. Then there are the Ugly Meetings, which I have been a part of far more than I wished. And this is where the Big Boss is told of the problem, and the cost in resources it will take to fix this known problem. He swears and yells and has a fit, and asked stupid questions like, How did this get into the Program? And of course no one says a word, and we all just sit there waiting for the Big Boss to Cool down before any of us dare speak. finally the Big Boss asks, How many of our customers are affected by this problem? Someone gives an estimate, and the Big Boss then says, he is not going to fix this problem until the next edition. Too few are expereincing the problem to put the needed resources into fixing it. the meeting comes to an end, and you feel like a Shit Heal when the next customer calls in with the Big Problem, and you have to fake like you are doing everything you can to fix the issue, when you know there is no fix, and won't be until maybe a year or two later. I am not saying that A I Squared has had one of these Meetings, but I will say, these types of Meetings do take place. I did ask in an earlier post what was the result of the one guy sending in their Lap Top for A I Squared to figure out the problem. have yet to hear from either A I Squared, or from the guy who sent in the lap top. It is quite possible that A I Sqaured has no system where this problem occurs. Anyway, like everyone else on this list, who suffers from the Random failures, I too will help where I can, and hope a fix is coming sooner rather than much later. Dave -- Dave <[email protected]> _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
