In article <38200f8357.harriet@xxxxxxxxxxxxxxxx>,
Harriet Bazley <lists@xxxxxxxxxxxxxxxxxx> wrote:
On 8 Feb 2019 as I do recall,
Frank de Bruijn wrote:
Let's go back a bit. You wrote earlier that version 1.67 was OK until
you rebooted. So what happens when you load the module manually by
double clicking the file and then run AntiSpam?
No difference. It doesn't work until I 'load' the module from within
AntiSpam by clicking on the 'Module' button. Whereupon...
Module is: SecureSockets 1.04 (26 Nov 2005)
Yep, still same version in memory, apparently.
However, if I then do a 'Quit and restart' from AntiSpam's menu, it
registers the presence of the module correctly when it reloads. And I
don't see how it can be preserving the contents of its own memory
(unless maybe it is? Maybe it's the old bugbear of fragments of data
persisting in uninitialised Wimpslot space when a program is quit and
Also, where is the module file stored on that machine and what's its
There are several versions of the SecureSockets module within Hermes,
although I don't know for certain that this is where the module is being
loaded from: <Hermes$Dir>.Resources.Secure (v1.01),
<Hermes$Dir>.Resources.Secure32 (v1.03), and
<Hermes$Dir>.Resources.SecureG (v1.04). It was the latter that is
loaded by <Hermes$Dir>.NewSecure and which I tried double-clicking on
I can imagine that the anomalous filename may well be causing problems,
since <Hermes$Dir>.Resources.Secure is *not* going to satisfy the
conditions of an RMEnsure...
but I can't see in that case how SecureSockets 1.05 is nonetheless
getting loaded and yet not being recognised as present when AntiSpam
checks for it.