Well, when I discussed my problem with local sensory solutions guys, they
said it was literally that windows 7 seems to be changing hardware
configuration during these 'changes' or something, but it didn't sound like
they had any immediate ideas on how to get around it, and they seemed to
think it was specifically an issue with windows 7 in my case of the dynamic
IP address causing this since it then seemed as if windows was then
communicating with jaws that the hardware configuration had been changed,
but they said they would be bringing it up with FS themselves, which might
help a bit more than only a customer asking about this.
Suppose it's also possible that when switching between normal power mode and
standby mode windows 7 could also render this as a hardware change, but I'm
assuming you're also experiencing this when using windows 7 on your netbook?
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
----- Original Message -----
From: "David Griffith" <[email protected]>
To: <[email protected]>
Sent: Sunday, November 08, 2009 2:24 AM
Subject: Re: [Blind-Computing] Slight issue with windows 7, and jaws 11
There is an annoying feature with some PC setups where Jaws does not
recognise its legitimacy after a computer has resumed from stand by.
Oddly
this problem may not occur immediately after you have resumed from stand
by
but eventually You get an error message saying something like
Error 6
This feature is not licensed to run on this machine.
Jaws will then sulkily go into demo mode but will not announce that this
is
what it has done. It will eventually ask you to activate. Attempting to do
this normally fails and you will eventually have to reboot.
This is the position on my Acer Netbook and I can find no way of stopping
this except by removing stand by as an option in the power settings which
may be ok for a desktop but is inconvenient for a Netbook.
I did ask tech support at sight and sound if they knew of a solution but
they had never heard of it and had no suggestions. I did discover that it
was a known problem after a Google search though.
Anybody who knows of a way of stopping this behaviour by Jaws 10 will have
my sincere gratitude.
Regards
David Griffith
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Jacob Kruger
Sent: Saturday, 07 November 2009 22:48
To: [email protected]
Subject: Re: [Blind-Computing] Slight issue with windows 7, and jaws 11
Oh well, will have to see if can find it/help FS find the other causes
then - LOL!
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
----- Original Message -----
From: "Brandon Misch" <[email protected]>
To: <[email protected]>
Sent: Saturday, November 07, 2009 7:02 AM
Subject: Re: [Blind-Computing] Slight issue with windows 7, and jaws 11
weird thing is this happens without the ip changing
On Nov 6, 2009, at 3:06 PM, Jacob Kruger wrote:
Hi there
Just noticed that since went over to windows 7 last week, that am
running jaws 11 on, it every now and then required me to re-activate/
authorise my jaws installation, and after speaking to local FS
suppliers
I think we may have figured it out.
Fact is am running on a dynamic IP address network at work, so you
generally get different IP addresses assigned to you when plugging into
a different network connection, or sometimes after one of the
computers/servers has rebooted, and it seems windows 7 might be sort of
associating/recognising this with a hardware change, which then makes
jaws want to be re-authorised/activated.
Suppose this is something microsoft could try sort out, but for now,
have asked them to try assign a static IP/network address to my machine
so this won't keep happening, but let's see, since now need to find
network configuration interface in windows 7...LOL!
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4580 (20091106) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4580 (20091106) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus
signature
database 4582 (20091107) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
__________ Information from ESET Smart Security, version of virus
signature
database 4582 (20091107) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus
signature
database 4582 (20091107) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus
signature
database 4582 (20091107) __________
The message was checked by ESET Smart Security.
http://www.eset.com
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 4582 (20091107) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4582 (20091107) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/
