TZUTC: -0500   
   MSGID: 227.fido-bbscarni@1:3634/12 22af3c8f   
   REPLY: 1:229/426 AD4DBEB0   
   PID: Synchronet 3.17c-Linux  Feb 14 2020 GCC 7.4.0   
   TID: SBBSecho 3.10-Linux r3.151 Feb 14 2020 GCC 7.4.0   
   CHRS: ASCII 1   
   NOTE: FSEditor.js v1.103   
     Re: NTVDM project update   
     By: Nick Andre to All on Thu Feb 06 2020 01:03:40   
      
    Hi Nick,   
      
    > I received a very detailed email from the author of Net2BBS/NETFOSS, which   
    > is  a Telnet server for Windows.   
      
   Here's an update on getting NetFoss to work with the NTVDMx64 port by   
   Leecher1337:   
      
   I'm now able to get NETFOSS.DLL to load into this environment, though it took   
   a lot more work then I had expected. I actually created a separate version of   
   NetFoss due to major changes in order to work around all the compatibility   
   isues I encountered, so I'm calling NetFoss64. Beta 1 is now available by   
   request, but it currently only works in "COM port mode", so it is functional   
   with the 64-bit version of NetSerial. However when I try to use it in normal   
   "Telnet mode", it fails to recognize the socket that Net2BBS passes to it as a   
   valid socket, which means there is an issue with the socket inheritance.   
   Another issue I found is that batch files abort as soon as any DOS program   
   loads as a TSR, so programs like ANSI.COM and NETFOSS.COM for example cause   
   the batch file to abort as soon as it executes the TSR program. I found a   
   workaround for that by using a DOS program called "BatLite" which compiles a   
   batch file into a .com executable file, which does not cause the abort.   
   As for the socket inheritance issue, I think I can work around that issue by   
   changing the sequence of what gets loaded first. Currently Net2BBS spawns   
   NF.BAT, which loads NetFoss, and then loads NetCom (The Telnet Communication   
   Engine), which in turn launches the BBS Program (or door). It appears that   
   when a DOS program gets loaded (such as NetFoss.com which is the DOS stub of   
   the fossil driver that communicates with the Windows DLL) this causes NTVDMx64   
   to secretly replace the Command processor from x64 to x86, and this appears to   
   be what kills the socket inheritance. I did a test to see if NetCOM.exe can   
   send data to the socket if NetFoss.com is not loaded, and it can indeed which   
   means it should be possible to make everything work in "Telnet Mode" by having   
   NetCOM.EXE load NetFoss after it has inherited the socket, and then NetFoss   
   will be able to then launch the BBS software. I'll let you know in a few days   
   if that works out.   
      
   By the way, I see that Leecher1337 used to run a telnet bbs at h   
   tp://dose.0wnz.at :-)   
      
   Regards, Mike   
   PCMicro dot com   
   --- SBBSecho 3.10-Linux   
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)   
   SEEN-BY: 1/120 123 18/0 200 90/1 103/705 116/116 123/0 25 50 115 150   
   SEEN-BY: 123/170 755 129/215 135/300 153/7715 154/10 30 40 700 203/0   
   SEEN-BY: 221/0 6 227/114 400 229/426 452 1014 240/5832 249/206 317   
   SEEN-BY: 249/400 261/38 280/464 5003 300/4 317/3 322/757 342/200 396/45   
   SEEN-BY: 633/280 2452/250 3634/0 12 15 27 50 119   
   PATH: 3634/12 154/10 280/464 229/426