17 Mar 12 11:49, Michiel van der Vlist wrote to Roy Witt:   
      
    MvdV>>> 1) It occasionally crashes when a specific node or some   
    MvdV>>> specific nodes call in. Roy can confirm that, as his system   
    MvdV>>> used to crash when I called him.   
      
    RW>> I think that was an earlier version, since it hasn't happened since   
    RW>> the time your log-in here crashed the system.   
      
    MvdV> My main Fido system hads been running the latest official release   
    MvdV> which is 2.29. That version is over a decade old.   
      
   Yes, and that was the version that crashed here.   
      
    MvdV> It still occasionally crashes on this side. I use the following   
    MvdV> workaround:   
      
    MvdV> === Cut ===   
      
    MvdV> :loop   
    MvdV> del \sema\*.0   
    MvdV> rexw -daemon   
    MvdV> choice /C:yn /T:n,5 Quit Rex   
    MvdV> if errorlevel 2 goto loop   
      
    MvdV> === Cut ===   
      
   That's probably a nice workaround for you. However, 'Choice' isn't   
   recognized by W2k as an internal or external command or operable program.   
      
   I did something similar to that, but it required a manual restart, which   
   used 'if', 'else' and 'goto' to wipe out the *.0 semaphore and restarts   
   Rex.   
      
   I can probably dupe yours with 'if, else, goto, errorlevel' which are   
   recognized commands by W2k...   
      
    MvdV> So whe Irex terminates, normally or abnormally, it restarts in 5   
    MvdV> seconds, unless I push the "y" key.   
      
    MvdV> When I gave up hope that it will ever be fixed, I have stopped   
    MvdV> keeping track of when and how it happens, but I know that it still   
    MvdV> crashes now and then.   
      
   I haven't seen it crash like it used to, but I've seen it lock up and   
   not respond to keyboard input, but keep on doing mail transfers, etc..   
      
    MvdV>>> 2) When entering a new node in the node manager it reads the   
    MvdV>>> nodelist, But it only finds the host name if it is in the   
    MvdV>>> system name field. It does not find it when the host name is a   
    MvdV>>> parameter after the protocol flag or the INA flag.   
      
    RW>> Correct.   
      
    MvdV> I have also created a work around for that, but it is less of an   
    MvdV> annoyance, as I do not enter new nodes in the node manager any   
    MvdV> more. Actually, removing a node that left FidoNet happens more   
    MvdV> often...   
      
   Starting with the August event of 2011, I began to add new nodes to Rex   
   node-manager as they came online here. I'm also attempting to get Fidonet   
   back to San Antonio and have added a new node to net387 just a few weeks   
   ago. There's an older node in San Marcos, just 14 miles up the road from   
   here that is listed in the Austin network, but he lives closer to me.   
      
    MvdV>>> 3) A parameter after a protocol flag is always interpreted as a   
    MvdV>>> port number. Even if it clearly is not.   
      
    MvdV>>> 4) When no host name is in the system name field, it will try   
    MvdV>>> the f.n.z.fidonet.net method. This is not overridable and the   
    MvdV>>> domain is not configurable.   
      
    RW>> It can be user (sysop) written in binkp to use anything but the   
    RW>> fnz.fidonet.net addressing system.   
      
    MvdV> I know. But not Irex...   
      
    MvdV>>> 8) No IPv6   
      
    RW>> [Version update]   
      
    MvdV>>> I have been waiting for a decade, my patience has run out.   
      
    RW>> Same here.   
      
    MvdV> With the next major system upgrade I will switch to binkd I think.   
      
   The same here...maybe D'B if it can quote properly by the time I get to   
   use it.   
      
      
                   R\%/itt   
      
      
     ... Only those who will risk going too far can possibly   
     ... find out how far one can go ~ TS Eliot   
      
      
   --- Twit(t) Filter v2.1 (C) 2000-10   
    * Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)