Hi! Nick,

On 11/28/2018 12:18 AM, you wrote:

 NB> I guess I'm just trying to figure out why you seem to stick with
 NB> Win98se. I mean I know the usual reasons like comfort, used to it, ease
 NB> of use, etc. But is there something there that newer Windows OSes are
 NB> lacking?

1. An overriding RAM restriction: 4Gb per host.  2.  Win98se needs only 128Mb
RAM, and the older Puppy systems only need 256-512Mb/per.  3. No income, as all
of my wealth is tied up in assets.

....outlook and scale...

 PQ>> Never updated.  They got it right the first time... well, it's
 PQ>> Puppy version 4.12 (Linux v2.5.x), and version 2.00 of the
 PQ>> particular edition (MacPuppy).

 NB> Yikes! Linux 2.5, you may even be able to setup that broken version of
 NB> Irex for Linux on there. ;)

Excuse me?  I've never run iRex for anything.  I confused you.  Sorry.

I was running Radius for a downlink using iRex/W32 who will not reset to port
24555, to catch my backup system after the primary node imploded in the vBox
update on 17 August.

Radius TRAP-ped on my web-tools server Win98se vBox, so I'm now running two
binkD servers on both ports, 24554 & 24555.  Only one is nodelisted.  (The
second binkD was always running as a LAN 'Stargate' IAC.)  Both are publically
available though only the nodelisted one will serve *all* current links.

 PQ>> the 'default' zone.  No real testing yet.

 NB> If I remember right, the default zone setting would obviously be your
 NB> default Fidonet outbound directory for zone 3. However, every other zone
 NB> should have their own directory (ie: if default zone is "fidonet", you
 NB> should have fidonet.001, fidonet.002, and fidonet.004 if links for those
 NB> zones are in your config and you've sent netmail to them). Then for any
 NB> other network you setup it would have a different directory naming
 NB> scheme, not using the "fidonet" prefix, it would use the actual name of
 NB> the network.

Yes.

 PQ>> Dude.  That's why I'm here.  I want a _good_ Linux tosser that serves
 PQ>> JAMNNTPd.  A fixed CM II 2.xx would be a wonderful winner.

 NB> Seems as though you've tried the limited options out there. Also seems
 NB> as though since CM II hasn't been touched in forever besides adding a
 NB> couple text files and moving it to sourceforge or github, it may not
 NB> ever get fixed. ;(

Yes.  :(

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0