Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2143  |
|  Stephen Walsh to Wilfred van Velzen  |
|  FMail 2.3.0.0 public beta release  |
|  21 Mar 24 12:21:52  |
 REPLY: 2:280/464.112 65f93be2 MSGID: 3:633/280 65fb8c80 CHRS: CP437 2 TZUTC: 1100 TID: hpt/lnx 1.9 2024-03-02 Hello Wilfred! 19 Mar 24 08:09, you wrote to me: 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. That's understandable, I doubt you'd have a huge M68K user base... Mostly a count of 1... #-) SW>> FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor [...] 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... I just looked through what andrew did to add M68K support in Talisman BBS and it's not just a few lines of code... https://gitlab.com/apamment/talisman/-/commits/master?search=endian I still have it running, but only as a point in FSXNet... Stephen --- GoldED+/LNX 1.1.5-b20240302 * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280) SEEN-BY: 15/0 90/1 105/81 106/201 128/260 129/305 135/225 153/7715 SEEN-BY: 218/700 226/30 227/114 229/110 112 113 206 307 317 426 428 SEEN-BY: 229/470 550 664 700 266/512 280/464 282/1038 291/111 292/854 SEEN-BY: 320/219 322/757 342/200 396/45 460/58 633/267 280 412 418 SEEN-BY: 633/509 2744 712/848 770/1 PATH: 633/280 229/426 |
[ << oldest | < older | list | newer > | newest >> ]