On 09/27/2016 11:14 AM, mark lewis -> rick christian wrote:   
      
    ml> that must have been before Ray Gwinn (yes, the x00 fossil author)   
    ml> released SIO for OS/2...   
      
      
   Ummm.. I left in late '99 due to job relocation and some other things...   
      
    ml> yup... AFAIK SIO on OS/2 is the only way one can use the vmodem   
   protocol...   
      
   Well that probably is part of why I never really paid much attention I didn't   
   do OS2! I was dragged kicking and screaming from my DOS world heavily   
   customized with 4DOS and FANSI-CONSOLE to winstupper...in the ~ 5 years or so   
   from that to eXtremely stuPidows.. then I moved to Linux full time via Knoppix   
   with KDE 3 right before that one went down the Linux Holy Roller route ie: "It   
   must be open! ! ! "   
      
    ml> to avoid the scanner bots on port 23, choose any other port... you can   
    ml> use 3141 if you like... i was just pointing out that vmodem normally   
    ml> runs on that port...   
      
   Well I was thinking that putting it there might be "correct" since this is   
   some sort of "VMODEM" but from what it appears this is probably not the same   
   protocol.   
      
   And dosxbox would need to be run as root to get below 1024! And that ain't   
   happening!   
      
   I get plenty of scans on stuff... but since SSH and a select few are the only   
   ones passed through.. they get bubckious... I chose to leave SSH v. something   
   else in the off chance I run into things blocking non standard ports which I   
   have with some VPN services and LAN's.   
      
    ml> so they say ;)   
      
   I spend alot of time using them... If I blow up a VM.. no biggie... I go back   
   to the base image, and go on from there after I triage what went wrong..   
      
   Thats why I despise compiling since it takes 3-4-5-x-x- times to try get it   
   work when the instructions mostly leave out the key things, namely   
   dependencies..   
      
   I don't install anything till I read, read, read, read, then read read read   
   again, and thats for a DEB!   
      
   I need to know what it is going to do to things that could potentially muck up   
   things.   
      
   Once I get things to a stable level, then I will install to physical hardware   
   if applicable or create a VM and repeat installs from my notes to get error   
   free operations.   
      
    ml> hahahaha... i'd probably fall back to QEMU from quarterdeck because i   
    ml> know it... no clue if it would even work with today's stuff, though...   
      
   I am not sure if you need it as DOSbox I think tries to provide a lot of   
   this...like EMS/XMS etc..there is a lack of info, or info at the level I   
   prefer on setup and use.   
      
   I used QEMU for a long time then TLB came along.. and it ran rings around   
   QEMU. I got more memory, I think because one of the newer units I built had   
   one of the needed chipsets that would do some of the extra magic that QEMU   
   couldn't I was getting like 760K free DOS or something silly and thats with   
   FANSI-CONSOLE loaded, 4DOS etc...   
      
   I think it and Terminate were about the only thing at that time I actually   
   paid registrations for.. the rest was shareware and lived with its limits like   
   Silver Xpress and SLMR.   
      
    ml> joho was very forward thinking... frontdoor was the first to offer this   
    ml> capability...   
      
   That definitely happened after '99 then... or if not I didn't pay attention to   
   it in the updates.. I used uucp to get news and mail till then..  relocation   
   brought ISDN, and then finally cable based internet.   
      
      
    ml> #filegate.net   
    ml> #74.167.111.188   
    ml> Vquinnspost.nodelist.net   
    ml> 000-192.168.99.23   
      
    ml> frontdoor development stopped before the nodelist INA flag was put into   
    ml> use so a lot of stuff has to be done manually instead of reading from   
    ml> the nodelist unless someone wants to write a tool to convert the   
    ml> distributed nodelist to the form that frontdoor can read directly... it   
    ml> is easy enough to do   
      
      
   Is there something that outlines what conversions need to be done for FD.. I   
   think I've found 2.26 and a 2.12 SL's or basically read in the domain names in   
   the one field and move them to the phone # location in the nodelist sort of   
   like a FDNODE.txt similar to the binkd list that its little script makes from   
   the raw nodelist.   
      
   I can possibly write a BASH or python script to take nodelist.999 in and spit   
   out something for FD to read... maybe even PHP as an option..   
      
    ml> and there are still examples using '000-' as their   
    ml> areacode to signal that the following numbers are an IPv4 number...   
      
   Yeah.. I read that in reading the nodelist notes...but I see mostly   
   "unpublished" for nearly 90+% of things.. so this conversion would need to be   
   done.   
      
   That clue probably saved me from dropping the experiment when it barfed on the   
   node list...   
      
    ml> IPv6  is different and requires additional conversions... SIO doesn't do   
   IPv6   
      
   I don't do IPv6 either... that is proof that engineers should not be allowed   
   to set standards without supervision! :) ;)   
      
   And honestly does EVERYTHING on the planet need an IP???? ;)   
      
    * Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)