Yes, The 64 bit Win7 CD was a very painless and short experience. Happy and
Bouncing here too, Craig R.
----- Original Message -----
From: "Keith Hinton" <[email protected]>
To: "gw-info" <[email protected]>
Sent: Tuesday, January 19, 2010 9:53 AM
Subject: Interesting Issues with the compitition, compared to the wonderful
GW Micro!
Hi all!
GW Micro has had a wonderful product as you all know.
Yesterday, to more or less dirve people to sign people to the
Braille-display petition that attempts to stop companies (witch I
won't name) from signing Braille-Display drivers, I found out through
the latest FSCast, taht some of Humanware's displays were not ready at
the time of the release of JAWS Eleven.
Freedom Scientific decided to go and, build 32-bit drivers, for 32-bit
operating systems.
But for us 64-bit users out there, (Most computers now are) guess what
they basically said?
Mr. Mosen, said: "We encourage you to contact the developers and
manufacturers to get a 64-bit driver created."
What does this prove to the blindness community?
1. That Window-Eyes is the way to go.
2. That only Window-Eyes will be the next alternitive to something
like NVDA or other programs.
3. That GW Micro always does it right, over the fact that users want
things, now!
4. That once again, GW Micro has raised the bar in this horrible
worldly market by not signing drivers that don't need to be, and
4. By allowing people like myself who cannot aford Window-Eyes
outright (partly because the VR place I work with only purchased me
JAWS) and such.) to pay for the coppy of the software through the
Window-Eyes Payment plan.
5. This continues to demonstrate, GW Micro's commitment above all
else, to customer service.
My coppy of Window-Eyes payment should be arriving soon.
What do the rest of you think?
Technical support was quick in the way that they transfered me to the
respective places instantly without hesitation!
I also like GW Micro's strong commitment to customer service. Also,
the Window-Eyes Error reporting tool..
Regardless of if an error occurs when a Demo product of Window-Eyes is
ran, etc, GW will fix it regardless.
How did you folks come up with the error-reporting tool? I'm curious
about some of the ideas behind it.
Once again, congradulations on your hard work. Hope to see some more hard
work!
This entire experience has been nothing short of amazing.
Especially, after how I was treated by some of the compitition.
Thanks for everything!
Regards, --a happy bouncy GW Micro Supporter,
--Keith
P.s.
You might consider me the bouncy ball of GW Micro. LOL
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, visit:
http://www.gwmicro.com/listserv
