23 Oct 15 14:03, you wrote to me:   
      
    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   
    ml>> make a stub file with all the other lines needed from line 3 to the   
    ml>> end of the drop file... in the menu line for the door would be   
    ml>> something like   
      
    ml>>   *c /c mydoor.bat *Sd32sys   
      
   i found *R will emit the user's record number to the .bat file...   
      
    ml>> which will use the RATemplate file D32SYS.RAT in the main RA   
    ml>> directory to create a file named "D32SYS" in the node's directory...   
    ml>> D32SYS.RAT would look like this...   
      
    ml>> ===== snip =====   
    ml>> ^KR   
    ml>> RemoteAccess 2.60   
    ml>>   
    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...   
      
   see above... i found that we can get the user number on the command line but   
   figuring out how to drop it into the D32SYS or final DOOR32.SYS file is   
   another problem... looks like we might have to pass the speed and BBS name and   
   version as parameters to the BAT file so we can get the user number in   
   there... that'll change the RAT file, the menu line and the MYDOOR.BAT file...   
      
    ml>> the '1' in the next to last line /forces/ ANSI mode because we can't   
    ml>> determine which of ASCII, ANSI, Avatar or RIP is used via the macros   
    ml>> without some script processing of the values... since RA doesn't do   
    ml>> Max Graphics, we don't 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 =====   
      
   we cannot run two RAT files so building everything that we can into the one   
   D32SYS file is all we have at this point... it is going to take some serious   
   BAT magic to replace the blank line with the contents of %1 in the about   
   MYDOOR.BAT file...   
      
    DA> I don't know RA but that sounds just right. Since the BBSLink client   
    DA> for windows is based on the R&M Telnet Door, it needs the DOOR32.SYS.   
    DA> From this file, it should get the Handle and the user number.   
      
   we rarely do anything with user numbers... getting that out and into the   
   door32.sys file is going to be tough...   
      
    DA> The only thing else that's needed it the door code and that you pass   
    DA> manually as a parameter when invoking the telnet door from the RA   
    DA> menu.   
      
   yeah, that can be added in elsewhere... right now i want to try to get   
   DOOR32.SYS files being created properly... then the rest should be a   
   no-brainer ;)   
      
    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  :)   
      
   this still stands but i am kicking this through my system as a test just to   
   see if i can get a valid DOOR32.SYS to be written...   
      
   )\/(ark   
      
   ... Don't deep fry ANYTHING in the nude; bread it first.   
   ---   
    * Origin:  (1:3634/12.73)