Hello mark!   
      
   23 Oct 15 11:16, you wrote to Manuel Adorni:   
      
      
    ml> 23 Oct 15 10:21, you wrote to me:   
      
    ml>>> socket   type   foreign   local     foreign         state   
    ml>>>                  port      port       host   
      
    MA>> How i can read the COM Socket handle??? Or is imposible?   
      
    ml> in the chart i posted, that was from netstat... the telnet com socket   
    ml> handle would be identified by the local port of 23 if telnet is being   
    ml> run on the standard telnet port... it is impossible to get the socket   
    ml> handle number without assistance from the telnet connection software   
    ml> or from the virtual modem...   
      
   True   
      
    ml> the only way i see to do it is as was pointed out by another poster...   
    ml> that solution is to use what is now known as gamesrv as your telnet   
    ml> server... gamesrv fires up netfoss via the nf.bat... the socket handle   
    ml> number is passed between gamesrv and netfoss via the % parameters in   
    ml> the .bat... the socket number may be saved in the nf.bat file for use   
    ml> later...   
      
    ml> eg: gamesrv -> nf.bat -> ra   
      
    ml> inside nf.bat a line can be added to set the handle into an   
    ml> environment variable...   
      
   Exactly.   
      
    ml> eg: modified from the pcmicro page...   
    ml> http://pcmicro.com/NetFoss/telsrv.html   
      
    ml>       @echo off   
    ml>       REM NF.BAT for NetFoss   
    ml>       REM the next line is to capture the socket handle   
    ml>       set T-HANDLE=%1   
    ml>       shift   
    ml>       REM now we processing like normal   
    ml>       c:\telsrv\netfoss.com %1   
    ml>       if errorlevel 1 goto end   
    ml>       c:\telsrv\netcom.exe %1 %2 %3 %4 %5 %6 %7 %8 %9   
    ml>       c:\telsrv\netfoss.com /u   
    ml>       :end   
      
      
    ml> and the command line in telsrv/gamesrv would be   
      
    ml>   c:\telsrv\nf.bat *H /n*N /h*H c:\ra\ra.exe -n*N -B57600   
      
      
    ml> what we've done is to add the first "*H" to the nf.bat command line so   
    ml> that we can capture just the socket number via %1... then in nf.bat   
    ml> we've added a line to set the socket number into our %variable...   
    ml> finally we shift all the rest of the parameters left one place and   
    ml> continue nf.bat as if nothing had changed...   
      
    ml> now when creating the door32.sys file, the value of %T-HANDLE is   
    ml> available to be placed into line 2 as needed...   
      
      
    ml> the tricky part is going to be creating the door32.sys but i have an   
    ml> idea on that, too... it uses one of RA's template capabilities to make   
    ml> a stub file with all the other lines needed from line 3 to the end of   
    ml> the drop file... in the menu line for the door would be something like   
      
    ml>   *c /c mydoor.bat *Sd32sys   
      
    ml> which will use the RATemplate file D32SYS.RAT in the main RA directory   
    ml> to create a file named "D32SYS" in the node's directory... D32SYS.RAT   
    ml> would look like this...   
      
    ml> ===== snip =====   
    ml> ^KR   
    ml> RemoteAccess 2.60   
      
    ml> ^Fa   
    ml> ^F3   
    ml> ^Fo   
    ml> ^F_   
    ml> 1   
    ml> ^KW   
    ml> ===== snip =====   
      
    ml> ^K is the actual ALT-011 character   
    ml> ^F is the actual ALT-006 character   
      
    ml> the blank line is for the user's record number and we don't have any   
    ml> way to get that via these ^K and ^F macros... the '1' in the next to   
    ml> last line /forces/ ANSI mode because we can't determine which of   
    ml> ASCII, ANSI, Avatar or RIP is used via the macros without some script   
    ml> processing of the values... since RA doesn't do Max Graphics, we don't   
    ml> have to worry about that one...   
      
    ml> then in your door's bat file we would do something like this...   
      
    ml> ===== snip =====   
    ml> @echo off   
    ml> REM mydoor.bat   
    ml> REM start with a new door32.sys and show a telnet connection   
    ml> echo 2 > door32.sys   
      
    ml> REM set socket handle in door32.sys   
    ml> echo %T-HANDLE >> door32.sys   
      
    ml> REM get the rest of the settings from the d32sys file   
    ml> type d32sys >> door32.sys   
      
    ml> REM now run our door and cross our fingers   
    ml> runmydoor.exe   
    ml> :end   
    ml> ===== snip =====   
      
   I don't know RA but that sounds just right. Since the BBSLink client for   
   windows is based on the R&M Telnet Door, it needs the DOOR32.SYS. From this   
   file, it should get the Handle and the user number. The only thing else that's   
   needed it the door code and that you pass manually as a parameter when   
   invoking the telnet door from the RA menu.   
      
      
    ml> NOTE: i've not actually tested any of this... it should work or at   
    ml> least be very very close to what is needed  :)   
      
      
   Dennis   
      
      
   --- GoldED+/LNX 1.1.5-b20150715   
    * Origin: The Wall Caribbean & Central American Hub (1:135/301)