The WE 7.01 emergency removal should clean all of this up and if it
doesn't give us a call at the machine with your 7.01 cd.
At 01:43 AM 5/1/2009, you wrote:
Hi, all. You may remember that I had WE 7.01, and last Monday my
system crashed and the sound card got muted, and even after we
unmuted it, Window-Eyes couldn'tinitialize or some such thing, so we
uninstalled it. While my husband was uninstalling it (since I didn't
have speech), he saw something about Window-Eyes 5, so he
uninstalled that too. The latest CD I had was for version 6, so I
installed that, and it's been working okay, except it wanted to send
error reports for some reason.
So while I'm waiting for the 7.01 CD I ordered yesterday, I thought
I'd see if I could clean up my WE problems. I changed WE to not
start automatically, but I noticed it was still in the startup
programs. I'm almost positive that I've removed programs from the
startup that I didn't want to start automatically, so decided to try
it with WE. Big mistake! When I rebooted, I couldn't get WE to
run. My husband tried to uninstall it so I could reinstall it, but
it wouldn't uninstall. We finally thought we got it uninstalled,
but when I put in the 6.0 CD, it detected another version. It said
if I wanted to install over it, there would be no speech during the
installation, so my husband read me the prompts, and we got to a
place where it couldn't continue the installation, saying it
couldn't install version 6 over whatever I had of this mysterious
version 5 that it thought I had. We ran the emergency removal, and
it didn't work the first time for some reason, but we finally got it
removed, and I got version 6 re-installed. But apparently even the
emergency removal utility isn't removing something, because I still
got the message that Window-Eyes was already running. I still see
Window-Eyes in startup programs, even though I've told it not to
start automatically. And I took a look at the msconfig, and it's
checked to start there. When this computer was built, I think it
was version 5 that I had the builder install on it, and I've just
been installing over it with each upgrade. But I would like to
start with a truly clean slate when my 7.01 CD gets here, so that my
system knows there's really only one Window-Eyes. I'm wondering if
there's anything else we should do besides using the removal
utility, before installing 7.01 when it gets here. I just can't
figure out why my system thinks WE is already running, and why it's
suddenly making occasional comments about version 5, which I haven't
had for a million years.
Peggy
http://kernsac.livejournal.com/
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4047 (20090430) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
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.
--
Michael D. Lawler
Voice 260-489-3671
Fax 260-489-2608
Internet mailto:[email protected]
web http://www.gwmicro.com
ftp ftp://ftp.gwmicro.com
GW Micro, Inc.,
Development Liaison and Technical Support Supervisor
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.
