Hi Stephen,

On 21 Mar 24 12:21, Stephen Walsh wrote to Wilfred van Velzen:
  about: "FMail 2.3.0.0 public beta release":

 SW>>> pkt.zip & fmailm68k.zip in your inbound.... If you want to do
 SW>>> something with M68K support... (This is after all just something
 SW>>> todo on my part!)

 WV>> Not really. ;-) I think there are more important things on the todo
 WV>> list.

 SW> That's understandable, I doubt you'd have a huge M68K user base... Mostly
 SW> a count of 1... #-)

You are not using it! So 0. ;-)

 SW>>> FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor
 SW> [...]
 SW>>> Packet is addressed to another node (256/49920); packet file:
 SW>>> /home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with
 SW>>> extension: '.wrong_destination'

 WV>> 256/49920 = 1/195, if you swap bytes. So a typical endianess
 WV>> problem...

 SW> I just looked through what andrew did to add M68K support in Talisman BBS
 SW> and it's not just a few lines of code...

Making the pkt code endianness agnostic isn't a big task. My pktviewer code does it. I wrote it decades ago, so it would compile on both the Amiga and PC. ;-)

But doing so for the three supported messagebases (msg, hudson, jam), is a huge pain in the ass, because the code for these is all over the place.


Wilfred.

--- FMail-W64 2.3.0.1-B20240319