Hi. That's what we thought too initially, but we closed down narator
before trying the instalation again and the same exact thing happened.
So it's either just another fluke, or it's intirely possible narator may
have still been running in some way, even though we verified that it was
closed. The sighted help we had was sort of, shall we say limited?
Anyways, it still remains a mystery. We did forget to shut narator down
on our initial atempt because we were just so happy that it actually
worked, but even after we shut it down the talking installer still
crashed. Hmmm. good thoughts though!
On 1/28/2012 10:08 PM, net bat wrote:
did you turn off narrator before you ran the setup? it could be because both
voices are trying to run at the same time.
From: Chris Skarstad
Sent: Saturday, January 28, 2012 6:56 PM
To: [email protected]
Subject: installing window-eyes 7.5 on a brand new windows 7 64-bit pc
Hi folks
We Had a rather odd thing happen here, actually it's the second time
it's happened and I thought I'd quiz everyone to see if they have any
answers. It actually happened a couple weeks ago and i thought it was
just a fluke but it happened again today and my curiocity got the best
of me. Another friend of mine just got himself a brand new windows 7
64-bit pc, and we were able to get past the initial setup using
Microsoft narator. He then got his window-eyes 7.5 cd and put it in
the drive. the drive spun up and we heard the initial message inviting
us to press s to install with speech, which we did. Now here's where the
fun starts...
Aparently we got an error message, basicly saying the runtime
version of wineyes crashed, and we had to install it without speech.
It's important to add that when we were setting the pc up, we turned off
UAC,, so it most definitely wasn't keeping the program from running. So,
like I say we were able to get it installed just fine and everything is
working beautifully now, but has anyone else seen the talking install
crash on a win 7 64-bit system like this? when i was helping my GF
install it on her brand new laptop last week the exact same thing
happened, so I just wonder if we're doing something wrong?
We actually tried it twice thinking it was a fluke, but it kept
happening. Does anyone have any thoughts on why this happened and, is
there anything we can do in the future to prevent it from happening
again if we have to re-install?
Thanks guys!
Chris
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.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
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.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
