Green grass and warm in WNy and no snow. Merry christmas. KB2YAA
-----Original Message-----
From: Tom Behler
Sent: Wednesday, December 24, 2014 8:56 AM
To: [log in to unmask]
Subject: Re: Off Topic: Jaws incorrect version Instalation Mystery Solved
And, a very Merry Christmas and happy new year to everyone from here in soon
to be snowy central lower Michigan!
Tom Behler: KB8TYJ
-----Original Message-----
From: For blind ham radio operators [mailto:[log in to unmask]]
On Behalf Of Ron Miller
Sent: Tuesday, December 23, 2014 11:03 PM
To: [log in to unmask]
Subject: Re: Off Topic: Jaws incorrect version Instalation Mystery Solved
Hi Tom,
You are quite welcome. It was a pleasure getting to know you during our
phon= e conversations and Tandem session.
I'll be sure to pass this on to our Technical Support staff. They truly did
t= he heavy lifting helping you get your computer squared away.=20
I hope you, and everyone on-list have a very merrn Christmas, happy New
Year= and a blessed holiday season.
73
Ron Miller
> On Dec 22, 2014, at 11:02 AM, Tom Behler <[log in to unmask]> wrote:
>=20
> Hi, everyone.
>=20
>=20
>=20
> You may remember that last week, Jaws 13 inadvertently got installed
>on my=
> new work laptop, instead of Jaws 16, which I thought would be directly
>installed from the Jaws 16 CD.
>=20
>=20
>=20
> It turns out that the fault was on this end, not with Freedom Scientific.
>=20
>=20
>=20
> Here's my analysis of what happened and why:
>=20
>=20
>=20
> Yesterday, I was nosing around on the desktop of my new work laptop, and
> found an executable file for Jaws 13. It was called j13.0.92 4 64 bit.
=
I
> checked the file properties, and the file was dated Monday: December
> 15 an=
d
> was time stamped at 10:09 a.m. This is significant, because this was
> the time when the University's I T people were in my office, and had
> transferr=
ed
> a bunch of stuff from the hard drive of my old Windows 7 desktop to
> the ne=
w
> work laptop.
>=20
>=20
>=20
> I think that what happened was this: Since I had no visual assistance
>available when it came time to install Jaws 16, I used Windows narrator
>to=
> find what I thought was the Jaws 16 instalation package on the Jaws 16
> CD,=
> and somehow ended up inadvertently choosing the Jaws 13 executable file.
>=20
>=20
>=20
> Apparently, I'm not very good at using Windows Narrator in situations
>like=
> this, although I do find Narrator to not be as verbose as I would
> like. I=
n
> addition, it also would have been nice to have visual assistance
> around, s=
o
> that I wouldn't have had to use Windows Narrator to begin with, and
>could have gotten the correct file right from the new CD.
>=20
>=20
>=20
> The really frustrating part of all of this is that, even though I
>uninstalled Jaws 13 from the new laptop, and installed Jaws 16,
>something got corrupted with the install, and I had to spend quite a
>bit of time lat=
e
> last week with FS Tech support to do a major Jaws repair.
>=20
>=20
>=20
> All and all, though, I think I'm now ok, and will certainly keep this
>in mind for the future. I also have sent a rather strongly-worded
>e-mail to our IT folks, stressing the need for visual assistance with
>new adaptive technology instalations, and also stressing the need for
>IT people to let u=
s
> know what files they are transferring onto any new computer that we
>might use.
>=20
>=20
>=20
> In closing, I want to sincerely thank Ron Miller and the folks at
>Freedom Scientific for all of their help in working through this
>issue. Ron, in particular, went above and beyond the call of duty to
>help me figure out what was going on, and that has been truly appreciated.
>=20
>=20
>=20
> Tom Behler: KB8TYJ
>=20
>=20
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4794 / Virus Database: 4253/8801 - Release Date: 12/24/14
|