home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   IREX      Internet Rex (FTN <=> Internet) Public S      1,458 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 407 of 1,458   
   Michiel van der Vlist to Roy Witt   
   Bug report   
   17 Mar 12 11:49:11   
   
   Hello Roy,   
      
   On Friday March 16 2012 03:55, you wrote to me:   
      
    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.   
      
   My main Fido system hads been running the latest official release which is   
   2.29. That version is over a decade old.   
      
   It still occasionally crashes on this side. I use the following workaround:   
      
   === Cut ===   
      
   :loop   
   del \sema\*.0   
   rexw -daemon   
   choice /C:yn /T:n,5 Quit Rex   
   if errorlevel 2 goto loop   
      
   === Cut ===   
      
   So whe Irex terminates, normally or abnormally, it restarts in 5 seconds,   
   unless I push the "y" key.   
      
   When I gave up hope that it will ever be fixed, I have stopped keeping track   
   of when and how it happens, but I know that it still crashes now and then.   
      
    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.   
      
   I have also created a work around for that, but it is less of an annoyance, as   
   I do not enter new nodes in the node manager any more. Actually, removing a   
   node that left FidoNet happens more often...   
      
    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.   
      
   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.   
      
   With the next major system upgrade I will switch to binkd I think.   
      
      
   Cheers, Michiel   
      
   --- GoldED+/W32-MINGW 1.1.5-b20110320   
    * Origin: http://www.vlist.org (2:280/5555)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca