Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 1725  |
|  Wilfred van Velzen to Vincent Coen  |
|  Re: Issues with running makenl for a reg  |
|  04 Mar 25 19:13:51  |
 TID: FMail-lnx64 2.3.2.4-B20240523 RFC-X-No-Archive: Yes TZUTC: 0100 CHRS: CP850 2 PID: GED+LNX 1.1.5-b20240306 MSGID: 2:280/464 67c742e1 REPLY: 2:250/1@fidonet 67c73aed * Originally in FTSC_PUBLIC * Crossposted in MAKENL_NG Hi Vincent, On 2025-03-04 17:23:04, you wrote to All: VC> I use makenl 3.5.1 under Linux and the o/p file region25.nnn has a VC> binary value at the end of file that Ward (2:0) cannot handle in his VC> Dos environment. Sure he can. Every "normal" nodelist or segment ends with that character, and always has! It's even documented in: http://ftsc.org/docs/fts-0005.003 The Z2 nodelists I get from Ward also end with that character... So I think something else is going on. VC> Does any one have a fix for it as I have tried using unix2dos and VC> cannot find setting to omit it. There is no need to. VC> Out of interest it is 1a hex that is just after hex 0d oa i.e., VC> 0000930 7265 2e73 656e 2c74 4249 0d4e 1a0a VC> Above from hexdump VC> Short of hacking the makenl code (assuming I find the code). There is no need to. Bye, Wilfred. --- FMail-lnx64 2.3.2.4-B20240523 * Origin: FMail development HQ (2:280/464) SEEN-BY: 1/19 16/0 19/37 103/705 105/81 106/201 123/130 124/5016 128/187 SEEN-BY: 129/305 132/174 142/104 153/757 7715 154/10 30 110 203/0 SEEN-BY: 218/700 221/0 226/30 227/114 229/110 114 206 317 426 428 SEEN-BY: 229/470 664 700 705 240/1120 2100 5411 5832 5853 5890 266/512 SEEN-BY: 280/464 5003 5555 291/111 292/854 8125 301/1 310/31 320/119 SEEN-BY: 320/219 319 2119 322/757 762 341/66 234 342/200 396/45 423/120 SEEN-BY: 460/58 467/888 633/280 712/848 770/1 902/26 2454/119 5020/400 SEEN-BY: 5075/35 PATH: 280/464 240/5832 320/219 229/426 |
[ << oldest | < older | list | newer > | newest >> ]