Author Topic: New builds of Thunderbird and SeaMonkey  (Read 2077 times)

Mark Szkolnicki

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: +13/-0
    • View Profile
Re: New builds of Thunderbird and SeaMonkey
« Reply #45 on: June 14, 2022, 06:02:53 pm »

You are welcome to the rain, though it looks like it is leading to a state of emergency with the snow melt. Still grey, wet and cold here, just had to light a fire, which is almost never needed in June. At least the cold has slowed down the snowmelt here.
Good luck and hopefully no flooding

Not near me, Sir - although I live on Cooking Lake it is actually like a big slough - no inflow, no outflow, no riparian flow - all the years of drought have caused it to recede about 400 feet so we'd need metres of water coming down to m,ake a dent.

They also have the manholes in our hamlet about 2 feet above the ground, so pretty well just sewage flow - the water is still just being sucked into the soil, for which I am thankful.

As to fires - Anne and I enjoy a natural fire but because its not our primary source of heating - may have one in the fireplace today just for fun.  8)


Vincit Que Se Vincit - "He Who Conquers Self Succeeds"


  • Hero Member
  • *****
  • Posts: 649
  • Karma: +2/-0
    • View Profile
Re: New builds of Thunderbird and SeaMonkey
« Reply #46 on: June 18, 2022, 08:24:44 pm »
Well, anyways, if anyone is interested I uploaded the SM 10.3.0 build to

Glad you got this working Dave!
This version is the first that does not give me any log error, it does not close !!

I have been waiting for several days to confirm that it does not close, because on previous occasions I have given false hopes.

I was testing an idea of something that improved the previous versions a bit. And with this version has worked.

I had been thinking that you have what I think is an error in some old compiler,
or the kernel stuck when interpreting some values, mainly 16 bits,
causing the programs to fail mysteriously. Programs that are well done, failed.

What is the patch?
In changing the values in memory of the DLLS and the exes that have the value 5B for 238 (safer not to have failures during the tests)
or by 1 (everything works faster)

I understand that EXEs except that they have the same computer and load the same should erase them from my application,
and calculate you with theseus4 and the L5B.CMD program that I leave.

The way to apply the patch is to execute the three QBASIC files in three sessions of DOS-win in different windows.
I think the execution order is indistinct.

A more detailed explanation of how to use theseus4 and the L5B.cmd program I leave it in a read -.txt