Is there a known bug with the SQUISH LINK command? Message linking doesn't work properly on my Linux armv7 build. It seems to link every message to the previous and the next, but only if there is a REPLY kludge. Looks like this in Golded:

Umsgid : 21 #
Reply : 20 #
See : 22, 0, 0, 0, 0, 0, 0, 0, 0

And this happens when I run "squish link":

[...]
Linking areas:

Linking area BINKD 0x340L25k 0---- 25---
Linking area FIDONEWS 0x245k 0-------
Linking area FIDOSOFT.HUSKY - L0x2 0----
Linking area FILE_ANNOUNCE_AMY - L0xc 0----
Linking area FSX_BBS - L0xb 0----
Linking area FSX_GEN 0x535 50L25k 0----e50 25---
Linking area FSX_HAM - L0x2 0----
Linking area FSX_MYS - L0xe 0----
Linking area FSX_NET - L0x7 0----
Linking area MYSTIC - L0xb 0----
Linking area SYNCHRONET 0x380L25k 0---- 25---
[...]

Any ideas? Does this happen on DOS, OS/2 or Windows too or is it a Linux specific bug?

---
* Origin: this message must NOT be gated to Telegram (2:280/464.47)

On 20 Jan 21 09:18:48, Oli (2:280/464.47) wrote to All:

Is there a known bug with the SQUISH LINK command? Message linking
doesn't work properly on my Linux armv7 build. It seems to link every message to the previous and the next, but only if there is a REPLY
kludge. Looks like this in Golded:

[...]

Any ideas? Does this happen on DOS, OS/2 or Windows too or is it a
Linux specific bug?

MSGID/REPLY threading worked well in the original 1.11 release on DOS & OS/2.

I can't vouch for the Linux port of Squish. I don't think it got a lot of testing. Among other things you might have C structure alignment/padding inconsistencies on ARM that weren't present on the i386 build.

I recall Bob Jones disappeared from Fido only a few years after porting Maximus (which included Squish) to Linux in 2003.

Maybe it was Scott Dudley in disguise! Probably not.

These days I think everyone using Squish bases on Linux/BSD are using Husky's HPTLINK. I vaguely recall HPTLINK is a bit more intelligent than SQUISH LINK anyway.

--- GoldED+/BSD 1.1.5-b20180707
* Origin: X (3:633/267.7)