On Wed, 26 Nov 2014, Bj”rn Felten wrote to Kees van Eeten:   
      
    KvE>   Put the IPv6 stuff in first it should be far easyer that    
    KvE> pulling out all the POTS stuff. Mind you, it is still a job if    
    KvE> you are no familear with it.   
      
    BF>    If only you knew how much of the code is spent on ZModem,    
    BF> Hydra(!), online chat, and dozens of more POTS only functions, you    
    BF> would say that.  :)    
      
   why do you think those are POTS only functions? i've seen them used and have   
   used them myself on TCP/IP connections... argus, radius and taurus have had no   
   problems connecting and exchanging mail with my frontdoor nodes over telnet...   
   i don't understand the problem here...   
      
    BF>    But of course, now that I got it to compile OK, the first step   
    BF> is to extend the calls to Winsock to handle IPv6. I might even use   
    BF> ready made object files from the binkd source -- no need to convert   
    BF> the C code to PAS if not needed, even if I've done it many times?   
      
   while i understand, my first reaction is to gag... perhaps i should look at   
   the taurus code mode closely and see if i missed something in its binkp   
   implementation... i'm pretty sure it is all pascal code but it had been a   
   while since i went digging and rooting about it in ;)   
      
    BF>    Oh yes, there's a lot of code in it to make it work with Win95    
    BF> and 98 too, I think I'll lose that too. After all, it *is*    
    BF> originally a relic from last century. A major clean-up is urgently    
    BF> needed, that's for sure.   
      
   i guess that means that folks running older systems for nostalgic reasons (in   
   VMs most likely) won't be able to use your new version? have you been in   
   contact with the maintainer(s) to see what they think? he is, AFAIK, still   
   active ;)   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)