On 12/06/16 10:55 PM, Dennis Langton wrote:
< Deleted >
>
> I've just updated to a newer version of SM 2.48 - build ID 20161206210551.
> The
> new version solves the problem of crashes while composing an email,
Can you change the 'search engine' in this version or is it still
On 12/6/2016 9:55 PM, Dennis Langton wrote:
Dennis Langton wrote:
On 12/6/2016 2:05 PM, TCW wrote:
On Mon, 5 Dec 2016 20:15:30 -0600, S Slicer wrote:
TCW wrote:
On Sun, 4 Dec 2016 18:12:33 -0600, S Slicer wrote:
I had been using SeaMonkey 32-bit
Dennis Langton wrote:
On 12/6/2016 2:05 PM, TCW wrote:
On Mon, 5 Dec 2016 20:15:30 -0600, S Slicer wrote:
TCW wrote:
On Sun, 4 Dec 2016 18:12:33 -0600, S Slicer wrote:
I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
10 Pro
On 12/6/2016 2:05 PM, TCW wrote:
On Mon, 5 Dec 2016 20:15:30 -0600, S Slicer wrote:
TCW wrote:
On Sun, 4 Dec 2016 18:12:33 -0600, S Slicer wrote:
I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
10 Pro 64-bit, then switched to
S Slicer wrote:
I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
10 Pro 64-bit, then switched to SeaMonkey 64-bit version 2.45. Both
worked very well for me. Then while running 2.45, when I checked for an
update, there was version 2.47. I ran into e-mail problems with
TCW wrote:
On Sun, 4 Dec 2016 18:12:33 -0600, S Slicer wrote:
I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
10 Pro 64-bit, then switched to SeaMonkey 64-bit version 2.45. Both
worked very well for me. Then while running 2.45, when I checked for an
On 12/05/2016 11:02 AM, Ray_Net wrote:
NoOp wrote on 05-12-16 01:35:
Check your add-ons/extensions. Test in Safe Mode.
In the past, I received also the counsel to test in Safe Mode - AIE
After that some options of SM has been changed when I return to the
non-safe - normal version.
This
NoOp wrote on 05-12-16 01:35:
Check your add-ons/extensions. Test in Safe Mode.
In the past, I received also the counsel to test in Safe Mode - AIE
After that some options of SM has been changed when I return to the
non-safe - normal version.
This is not very "safe" ...
On 05/12/2016 02:41, TCW wrote:
> On Sun, 4 Dec 2016 18:12:33 -0600, S Slicer wrote:
>
>> I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
>> 10 Pro 64-bit, then switched to SeaMonkey 64-bit version 2.45. Both
>> worked very well for me. Then while
On 12/4/2016 4:12 PM, S Slicer wrote:
> I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
> 10 Pro 64-bit, then switched to SeaMonkey 64-bit version 2.45. Both
> worked very well for me. Then while running 2.45, when I checked for an
> update, there was version 2.47. I
On 12/4/2016 4:12 PM, S Slicer wrote:
> I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
> 10 Pro 64-bit, then switched to SeaMonkey 64-bit version 2.45. Both
> worked very well for me. Then while running 2.45, when I checked for an
> update, there was version 2.47. I
I had been using SeaMonkey 32-bit version 2.40 successfully on Windows
10 Pro 64-bit, then switched to SeaMonkey 64-bit version 2.45. Both
worked very well for me. Then while running 2.45, when I checked for an
update, there was version 2.47. I ran into e-mail problems with 2.47
12 matches
Mail list logo