Re: Discussion with Eric Damery
- From: "Gene" <guystevens@xxxxxxxxxxxxx>
- To: <jfw@xxxxxxxxxxxxx>
- Date: Mon, 18 Apr 2005 18:28:18 -0400
I have no problem at all with MSN and 6.1 and XP Home.
Thanks; Gene
On MSN and Yahoo - guystevens@xxxxxxxxxxxxx
----- Original Message -----
From: "Jarrod Jicha" <jamminjerry@xxxxxxxxx>
To: <jfw@xxxxxxxxxxxxx>
Sent: Monday, April 18, 2005 2:18 PM
Subject: Re: Discussion with Eric Damery
> all I know is in my case, the latest version of 6.1 was werse than the
> firswt 6.1 the whole msn issue was much werse, when installing the april
> 15
> version, you couldn't even read the histery window. and then when I tried
> to
> go back to 6.0, wich I knew worked? it made my 6.0 not work! I had to
> reformat anyway, so I did that, and put 6.0 on here. and am not having
> probloems. I am not going to 6.1 until I know for sure the msn 6.2 bugs
> are
> totally gone.
>
>
>
> This email has been scanned by PC Cillen Internet Sacurity 2005, and
> contains no viruses
> ----- Original Message -----
> From: "Sean McMahon" <smcmahon@xxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Monday, April 18, 2005 2:05 PM
> Subject: Re: Discussion with Eric Damery
>
>
> This is why Debian gnu/linux never gives release dates. But that's a
> whole
> different kind of market/selling strategy there
> ----- Original Message -----
> From: "Chris Skarstad" <toonhead5@xxxxxxxxxxx>
> To: <jfw@xxxxxxxxxxxxx>
> Sent: Monday, April 11, 2005 12:22 PM
> Subject: Re: Discussion with Eric Damery
>
>
> hi
> This is excellent news, but the question still must be asked, why in the
> hell didn't they just wait and release the version of the software if they
> new these bugs existed? Of ccourse, if they didn't know, then obviously we
> can't blame them. But I like the GW Micro approach to things. If it takes
> a
> little longer to release a version of the software, then that's all the
> better if it's as solid and strong as it can be.
> I'm not expecting the FS programmers to be perfectionests, and release
> absolutely bug-free software, that's not possible. But it just seems like
> a good idea to actually wait until bugs can be fixed before releasing a
> new
> version, instead of releasing a buggy version which causes people all
> kinds
> of problems, and then a week later, release a version which, in theory
> should fix those bugs. Just skip the buggy version and give me the good
> one.
>
>
>
>
>
>
>
> At 01:28 PM 4/11/2005, you wrote:
>
>>Hello list:
>>
>>I just received a phone call from Eric Damery of Freedom Scientific and he
>>asked me to pass on some information.
>>
>>1. The Access 32 issue has been identified and is now in private beta. The
>>issue was a build issue using Unicode. If you are using the ANSI version
>>of
>>Access 32 it should still run correctly. FS has repaired the problem and
>>it
>>will be available soon.
>>
>>2 The issue of replying to an HTML document and Jaws stopping on the first
>>line is tied to the MSN 6.2 problem and both are in beta now.
>>
>>3. All of these issues will be repaired and a new build of 6.1 will be
>>available in a week to 10 days.
>>
>>Note: I found him to be very helpful and concerned about these issues. I
>>think we will see some improvement very soon.
>>
>>Gene
>>
>>
>>
>>--
>>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
>
> --
> 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
>
> --
> 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
>
>
> --
> 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
>
--
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
Other related posts:
