Keith,
I think it's safe to say you have some sort of corrupted install. If
your experience were the norm, we wouldn't have shipped our 64-bit
support. I would recommend uninstalling both JAWS and Window-Eyes, using
the Window-Eyes Emergency Removal Utility
(http://www.gwmicro.com/Support/Downloads/?fileNo=1114) to remove all
traces of Window-Eyes, and then run the Window-Eyes install again. Let's
see where that takes you.
I'm fully aware of SecureCRT, and as far as I know, we have other users
using it successfully. Perhaps one of them could chime in with their
experience. Personally, I use PuTTY for SSH access with minimal
problems. I believe Raul uses it too. Knowing exactly what problems
you're having, again, would be useful. Of course, using the mouse
hotkeys would allow you to navigate potentially any terminal emulation app.
Finally, in response to your blatant, contentious accusation that the
Skype scripts "suck," I have but two words for you: I agree. I wish I
had the time and resources to work on them, but I don't. That's why I've
asked for anyone else to take them over and maintain them. As is often
the case with the passing of open source code, however, my request
remains unanswered. So, until I get some other projects finalized, Skype
will have to continue to suck more than usual with the Skype script running.
Aaron
On 8/13/2009 12:58 PM, Keith Hinton wrote:
Alright. I'll happily explain
I downloaded the 30 minute demonstration of Window-Eyes.:
I installed it onto my Windows Vista 64-bit machine (wich I use as a
testing machine for this new technologey access.)
The first message DecTalk said when running the setup was:
"Window-Eyes cannot communicate with the Window-Eyes display driver.
It may be disabled, or" whatever the rest of the message was..forgot.
Then, I removed JAWS.
Not surprisingly, Window-Eyes installed just fine, or at least I
thought it had..
That wasn't the case.
Window-Eyes did not install just fine at all.
First sign of this was not finding "Window-Eyes" in programs in
features under Vista.
Second sign I had was when at one random point I whent to reboot due
to the timeout.
The box would not launch Window-Eyes after the login process, and when
I checked with NVDA, turned out that "Weproxy.exe" had crashed or
something, this wasn't an Window-Eyes error report specifically, as
Window-Eyes in turn, would not even launch. I then reran the
installation, restarting my PC in the process.
It installed just fine. After this, I removed Window-Eyes,
reinstalling JAWS afterword, because of another problem. While this is
not 64-bit specific, it does upset me greatly.
The specific problem Arron, that Im' unhappy about (no) I don't have
time to write a script) and writing scripts for this application are
impossible, from what I have heard..Have you ever tried writing
scripts for an SSH terminal, Arron?
In fact, have you ever had any luck with an SSH program called
SecureCRT? Do you even know what SecureCRT is, as far as how it was
written?
Another thing that one of my sources, Tyler Spivey, told me is that
your Skype scripts suck. They rely upon the Skype extra's manager,
(SkypePM.exe) and that things break with WinAmp the faster he loads
tracks.
Sometimes, he says Window-Eyes stops reading instant messages at random.
If you wish to contact me on Skype, add skypedude1234 to your Skype accounts.
Regards, --Keith
P.S.
How responsive is Eloquence for WE when compared to the compitition? I
have heard from my "source" that Eloquence in Window-Eyes is
practically unuseable.
I therefore am having trouble deciding if Window-Eyes or JAWS is the
right thing for me.
While I know how screen-reading programs work better with applications
over another etc, I still cannot make an informed decision.
An example:
GW Micro says Window-Eyes was the first to support flash.
Then Freedom comes along, and reports that they were the first.
Similar to the adoption of Adobie PDFS.
Window-Eyes claims to be the first (says so on the window-Eyes page)
and JAWS claims they were the first.
Anotehr thing:
JAWS has had a scripting language that has existed for years. It
though scripting, works with SecureCRT (I use it) to ssh into a web
provider that I have (for webpages and box security) etc.
Is there a chance out of a million one day that Window-Eyes can speak
with SecureCRT, (perhaps this functionality exists) but I would like
to see WIndow-Eyes read all text (not highlighted) on the screen and
yet provide a hotkey (control-shift-alt-R to turn off and on this
function.
How possible is it to do this in Window-Eyes even if you are
interfacing to a non-standard non-com automation supported
Application?
I hear SecureCRT doesn't support com automation.
If your scripts only use Com automation and it is not possible to hack
hack and I mean sync the drill down into the applications in question
(despite com automation or no)
existing or not) then...what good pray tell, are scripts for
something like an SSH client anyhow?
How will Window-Eyes hold up int he work place where folks log into
computers remotely via SSH and not over RDP like most PCs?
Sorry for my rant, but I need some wonderful feedback.
Google for SecureCRT if you don't knno what that is. :)
Regards, --keith
On 8/13/09, Aaron Smith<[email protected]> wrote:
On 8/12/2009 9:13 PM, Keith Hinton wrote:
It is my official understanding that 7.1 of Window-EYes contains lots
of 64-bit issues, etc.
Can anyone from GW-Micro confirm or deny this?
I'll happily deny this. Using Window-Eyes under 64-bit is no different
than using Window-Eyes under 32-bit.
Can anyone explain why issues with the compitition, and now GW-Micro
are happening? Why can things not work exactly perfectly in 64-bit
just like in 32?
I can't explain why they're having problems (although I have quite a few
suggestions that I can't share publicly). The only issue I know of
regarding Window-Eyes and 64-bit operating systems has to do with
creating some objects through scripting, and that will be resolved soon.
64-bit is a completely different architecture, and despite the few
blatherskites who claim that migrating from 32-bit code to 64-bit code
ought to be easy peasy, there is a tremendous amount of work that has to
be done to move millions of lines of code from one to the other. Anyone
who claims otherwise doesn't have any real experience of doing the
update with a major software product. In the process, there are lots of
regressions, new problems to deal with, and what not. Through our
private and public beta cycles, we've nailed down pretty much all known
64-bit issues with Window-Eyes.
My experience with Window-Eyes 64-bit (as I have no choice but to use
it) has been horrible at best, and that's just the 30 minute demo.
How about providing some specifics? I've been using Window-Eyes under
64-bit Vista and 64-bit Windows 7 for some time now with no issues. Nor
have we heard from others about 64-bit specific problems.
Aaron
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support& Web Development
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.
--
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
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.
