RE: Well folks, I tried!

From: "Chip Orange" <Corange@xxxxxxxxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Date: Wed, 13 Apr 2005 12:02:22 -0400
Reports are, in general, it's as good a screen reader, and is several
hundred dollars cheaper.  They also offer a time payment plan so that
you can buy it, while using it, by paying a small amount each month.

That's a customer friendly company.

The support is also rumored to be good.



Chip Orange
Database Administrator
Florida Public Service Commission

Chip.Orange@xxxxxxxxxxxxxxx
(850) 413-6314

 =20

> -----Original Message-----
> From: jfw-bounce@xxxxxxxxxxxxx=20
> [mailto:jfw-bounce@xxxxxxxxxxxxx] On Behalf Of John McLuckie
> Sent: Tuesday, April 12, 2005 9:29 PM
> To: jfw@xxxxxxxxxxxxx
> Subject: Re: Well folks, I tried!
>=20
> I am unfamiliar with winEyes, but have seen it mentioned in=20
> various conversations on freelist.  I have been a JAWS user=20
> for many years now, and although I am no expert, I can get=20
> most things done that I need to and can usually find the help=20
> I need for most popular applications.
>=20
> I am, however, becoming very concerned about the most recent=20
> versions of JAWS, I still use 5.1.  I guess if there is going=20
> to be a breaking point, I may wish to investigate WinEyes and=20
> see how well it works as compared to my current and previous=20
> satisfaction with the JAWS product.  Does anyone on this list=20
> use winEyes?  Can anyone tell us how user friendly it is, how=20
> accessable popular software and the internet are using that=20
> product?  How much does it cost and what kind of support is=20
> available for that product?
> No use in jumping from the familiar frying pan into the=20
> unknown fire...so to speak.  thanks.
>=20
> John
>=20
> ----- Original Message -----
> From: "harry bates" <hdbates@xxxxxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Monday, April 11, 2005 10:12 AM
> Subject: Re: Well folks, I tried!
>=20
>=20
> Thanks Jerry for your efforts.  It looks like I am headed to=20
> WinEyes.  Since my 6.0 has been invalidated and there are so=20
> many complaints about 6.1, which I have downloaded, but not=20
> yet installed, I will stick to jaws 5.1, and seriously=20
> investigate the possibility of switching to WinEyes after 16=20
> years of being a jaws user.
> ----- Original Message -----
> From: "Jerry Neufeld" <jerry.neufeld@xxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Cc: <ericd@xxxxxxxxxxxxxxxxxxxxx>
> Sent: Monday, April 11, 2005 10:59 AM
> Subject: Well folks, I tried!
>=20
>=20
> > Hello everyone.
> >
> > Some weeks ago, several persons posted messages to this=20
> list in which=20
> > they complained, rather vocally, about the need for a new=20
> > authorization, validation, call it what you like, each time they=20
> > changed a bit of hardware in their computers. From the=20
> standpoint of=20
> > general principles, this issue troubled me, especially=20
> since I, among=20
> > many others on this list, like to experiment with different=20
> devices,=20
> > always looking for the optimal machine.
> > While I was entirely sympathetic with Freedom Scientific's=20
> desire to=20
> > safeguard their software, I was not very excited, shall we=20
> say, by the=20
> > possibility that, as had been claimed, each time I changed a floppy=20
> > drive, a sound card or added memory, I would have to first=20
> check that=20
> > I had a validation left to cover me, should the locking=20
> code extractor=20
> > detect the change and force an update. As I suspected,=20
> neither people=20
> > in sales nor technicians could shed any light at all on=20
> what Freedom=20
> > was going to allow us to do and not to do. So, calling upon=20
> a couple=20
> > of old friends, I contacted Sharon Spensor and Eric Damery=20
> to find out=20
> > the real story, I having promised members of this list to=20
> convey what=20
> > I learned once I had the information. Frankly, I suspected that the=20
> > situation was much less dramatic than had been represented on this=20
> > list and that I would be able to return here with=20
> substantive details=20
> > that would place our minds at rest. Well folks, for reasons about=20
> > which I can only speculate, it didn't happen, it simply=20
> didn't happen.
> >
> > Before I proceed further, even though Eric Damery has sent=20
> me nothing,=20
> > contrary to his promise, I should forward a message from=20
> him to people=20
> > on this list, something, it seems to me, he could easily have done=20
> > himself. I am to say that anyone encountering difficulties with=20
> > hardware changes and validation counts should get in=20
> contact with him.
> >
> > Friendly as both Sharon and Eric were, the latter claimed that=20
> > revealing what could and could not be changed in terms of hardware=20
> > peripherals would defeat the entire scheme, allowing hackers, as he=20
> > put it, to devise means to acquire unauthorized versions of the=20
> > software. I pointed out that, within months, enough of us who had=20
> > tried different hardware configurations would have compiled=20
> a list of=20
> > devices that could be substituted without new validations.=20
> Rather than=20
> > forcing us to generate such a list, I said, why not create=20
> some good=20
> > will and let users know what to expect. Although I did not=20
> say so, the=20
> > specter of hackers seemed just a little paranoid and=20
> self-serving to=20
> > me.
> >
> > What troubles me most about this issue is that, indirectly, Freedom=20
> > Scientific is forcing us to seek a license before we make minor=20
> > changes to our hardware, something that, in my view, is=20
> outrageously=20
> > invasive and intolerable. Unlike several other listers, I=20
> have changed=20
> > one sound card for another without the slightest problem.=20
> This may be=20
> > true for numerous other internal devices as well, in which case we=20
> > have a veritable tempest in a teapot. Eric tells me of his=20
> advice to=20
> > FS customers that, prior to making any changes to their computers,=20
> > they check to see if they have any validations left, in my=20
> language,=20
> > any licenses by FS to make the change.
> >
> > I must confess to much disappointment in FS's official attitude on=20
> > this topic, yet one more indication of the company's=20
> growing disregard=20
> > for consumer opinion. If I discover that a change in minor=20
> devices or=20
> > components like cd/dvd readers, floppy disk adaptors,=20
> memory and the=20
> > like force me to go to FS for another validation, with much, much=20
> > regret, I will give up my ability to program with the Jaws screen=20
> > reader and go to Window Eyes.
> > Prior
> > to doing this, however, I am going to forward some of the=20
> messages on=20
> > this list along with a strongly-worded letter to each=20
> member of FS's=20
> > Board with the hope that someone there will show more=20
> wisdom than that=20
> > now displayed by management.
> >
> > With much regret
> >
> >
> >
> > Jerry
> > jerry.neufeld@xxxxxxxxxx
> >
> > --
> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx To=20
> > unsubscribe from this mailing list, send a message to=20
> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=20
> subject line.
> > Archives located at: //www.freelists.org/archives/jfw
> >
> > If you have any concerns about the list, post received from=20
> the list,=20
> > or the way the list is being run, do not post them to the=20
> list. Rather=20
> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
>=20
>=20
> --
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx=20
> To unsubscribe from this mailing list, send a message to=20
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=20
> subject line.
> Archives located at: //www.freelists.org/archives/jfw
>=20
> If you have any concerns about the list, post received from=20
> the list, or the way the list is being run, do not post them=20
> to the list. Rather contact the list owner at=20
> jfw-admins@xxxxxxxxxxxxxx
>=20
>=20
>=20
> --
> To post a message to the list, send it to jfw@xxxxxxxxxxxxx=20
> To unsubscribe from this mailing list, send a message to=20
> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=20
> subject line.
> Archives located at: //www.freelists.org/archives/jfw
>=20
> If you have any concerns about the list, post received from=20
> the list, or the way the list is being run, do not post them=20
> to the list. Rather contact the list owner at=20
> jfw-admins@xxxxxxxxxxxxxx
>=20
--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to 
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw

If you have any concerns about the list, post received from the list, or the 
way the list is being run, do not post them to the list. Rather contact the 
list owner at jfw-admins@xxxxxxxxxxxxxx
RE: Well folks, I tried!

Other related posts:
