Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 64:25:16 |
| Calls: | 12 |
| Files: | 12,938 |
| Messages: | 99,117 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
I want to use BBSLINK (bbslink.net, doors interbbs preconfigurated).
The BBSLINK client use the DOOR32.SYS (and not anothers dropfiles).
Exist a convert for DOOR.SYS to DOOR32.SYS (or DORINFOx.DEF to
DOOR32.SYS) for execute before run the BBSLINK Client???
1. RA has no way to determine if the connection is POTS or TELNET...
2. RA has no way of knowing the socket handle number of a telnet connection...
the first two lines of door32.sys need the above in formation and
there's just no way for RA to get that information...
aside from the above, i don't know of any way of running DOOR32.SYS
doors from a RA system...
Ever will be TELNET in my case.
1. RA has no way to determine if the connection is POTS or TELNET...
Ever will be TELNET in my case.
2. RA has no way of knowing the socket handle number of a telnet
connection...
the first two lines of door32.sys need the above in formation and
there's just no way for RA to get that information...
I make manually the fist two line because are static data (ever telnet)
aside from the above, i don't know of any way of running DOOR32.SYS
doors from a RA system...
you cannot make the second line... the socket handle changes every time there's a new connection... the socket handle is not the same as the port... there's a new socket handle created for each connection no matter what port the connection is on... i don't have any active connections at the moment that i can show you what i'm talking about...
Ever will be TELNET in my case.
http://pcmicro.com/NetFoss/telsrv.html
Here's an example os RA using TelSrv 4.0. In this example, they call NetFoss (NF.BAT) and pass the handle as a command line parameter.
You just include some lines in the NF.bat to create a custom
DOOR32.SYS using this info so that when the BBSLink door runs, it can
read the custom DOOR32.SYS and let you connect.
Contact me over email and we'll discuss it further.
http://pcmicro.com/NetFoss/telsrv.html
Here's an example os RA using TelSrv 4.0. In this example, they call
NetFoss (NF.BAT) and pass the handle as a command line parameter.
socket type foreign local foreign state
port port host
socket type foreign local foreign state
port port host
How i can read the COM Socket handle??? Or is imposible?
how do they get the socket handle? oh oh oh... telsrv is running in
front? telsrv is what calls netfoss?
You just include some lines in the NF.bat to create a custom
DOOR32.SYS using this info so that when the BBSLink door runs, it
can read the custom DOOR32.SYS and let you connect.
i'll take a look too because this likely won't be the only inquiry
like this ;)
the discussion is quite welcome here... i'm sure that others are interested in doing the same type of thing with their RA systems...
i took a look and it appears that the site/page is out of date... the first thing is that the link to telsrv doesn't work when clicked... it comes back and says the file is not found when using an anonymous connection... so i went looking... it seems that mannsoft is no longer around and that telsrv was renamed to gamesrv now handled by rick parrish... a quick search for gamesrv turned up
https://www.gamesrv.ca/
and the current version available in the downloads link is
v14.08.14...
i do see now that telsrv/gamesrv is being used as the telnet server instead of having netfoss or netserial running in front... i knew that there had to be a way to grab the handle but i didn't know how one
could do that without assistance from the virtual modem software or
some way of triggering a dobbs.bat or similar so that the socket
handle might be dug out somehow...
23 Oct 15 10:21, you wrote to me:
socket type foreign local foreign state
port port host
How i can read the COM Socket handle??? Or is imposible?
in the chart i posted, that was from netstat... the telnet com socket handle would be identified by the local port of 23 if telnet is being
run on the standard telnet port... it is impossible to get the socket handle number without assistance from the telnet connection software
or from the virtual modem...
the only way i see to do it is as was pointed out by another poster... that solution is to use what is now known as gamesrv as your telnet server... gamesrv fires up netfoss via the nf.bat... the socket handle number is passed between gamesrv and netfoss via the % parameters in
the .bat... the socket number may be saved in the nf.bat file for use later...
eg: gamesrv -> nf.bat -> ra
inside nf.bat a line can be added to set the handle into an
environment variable...
eg: modified from the pcmicro page... http://pcmicro.com/NetFoss/telsrv.html
@echo off
REM NF.BAT for NetFoss
REM the next line is to capture the socket handle
set T-HANDLE=%1
shift
REM now we processing like normal
c:\telsrv\netfoss.com %1
if errorlevel 1 goto end
c:\telsrv\netcom.exe %1 %2 %3 %4 %5 %6 %7 %8 %9
c:\telsrv\netfoss.com /u
:end
and the command line in telsrv/gamesrv would be
c:\telsrv\nf.bat *H /n*N /h*H c:\ra\ra.exe -n*N -B57600
what we've done is to add the first "*H" to the nf.bat command line so that we can capture just the socket number via %1... then in nf.bat
we've added a line to set the socket number into our %variable...
finally we shift all the rest of the parameters left one place and continue nf.bat as if nothing had changed...
now when creating the door32.sys file, the value of %T-HANDLE is
available to be placed into line 2 as needed...
the tricky part is going to be creating the door32.sys but i have an
idea on that, too... it uses one of RA's template capabilities to make
a stub file with all the other lines needed from line 3 to the end of
the drop file... in the menu line for the door would be something like
*c /c mydoor.bat *Sd32sys
which will use the RATemplate file D32SYS.RAT in the main RA directory
to create a file named "D32SYS" in the node's directory... D32SYS.RAT would look like this...
===== snip =====
^KR
RemoteAccess 2.60
^Fa
^F3
^Fo
^F_
1
^KW
===== snip =====
^K is the actual ALT-011 character
^F is the actual ALT-006 character
the blank line is for the user's record number and we don't have any
way to get that via these ^K and ^F macros... the '1' in the next to
last line /forces/ ANSI mode because we can't determine which of
ASCII, ANSI, Avatar or RIP is used via the macros without some script processing of the values... since RA doesn't do Max Graphics, we don't have to worry about that one...
then in your door's bat file we would do something like this...
===== snip =====
@echo off
REM mydoor.bat
REM start with a new door32.sys and show a telnet connection
echo 2 > door32.sys
REM set socket handle in door32.sys
echo %T-HANDLE >> door32.sys
REM get the rest of the settings from the d32sys file
type d32sys >> door32.sys
REM now run our door and cross our fingers
runmydoor.exe
:end
===== snip =====
NOTE: i've not actually tested any of this... it should work or at
least be very very close to what is needed :)
the tricky part is going to be creating the door32.sys but i have an
idea on that, too... it uses one of RA's template capabilities to
make a stub file with all the other lines needed from line 3 to the
end of the drop file... in the menu line for the door would be
something like
*c /c mydoor.bat *Sd32sys
which will use the RATemplate file D32SYS.RAT in the main RA
directory to create a file named "D32SYS" in the node's directory...
D32SYS.RAT would look like this...
===== snip =====
^KR
RemoteAccess 2.60
^Fa
^F3
^Fo
^F_
1
^KW
===== snip =====
^K is the actual ALT-011 character
^F is the actual ALT-006 character
the blank line is for the user's record number and we don't have any
way to get that via these ^K and ^F macros...
the '1' in the next to last line /forces/ ANSI mode because we can't
determine which of ASCII, ANSI, Avatar or RIP is used via the macros
without some script processing of the values... since RA doesn't do
Max Graphics, we don't have to worry about that one...
then in your door's bat file we would do something like this...
===== snip =====
@echo off
REM mydoor.bat
REM start with a new door32.sys and show a telnet connection
echo 2 > door32.sys
REM set socket handle in door32.sys
echo %T-HANDLE >> door32.sys
REM get the rest of the settings from the d32sys file
type d32sys >> door32.sys
REM now run our door and cross our fingers
runmydoor.exe
:end
===== 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.
NOTE: i've not actually tested any of this... it should work or at
least be very very close to what is needed :)
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...
i found *R will emit the user's record number to the .bat file...
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...
we rarely do anything with user numbers... getting that out and into
the door32.sys file is going to be tough...
Let me know if you can achieve this.
24 Oct 15 16:03, you wrote to me:
Let me know if you can achieve this.
i have been able to do this and perform limited testing on a vista
box... i do not have RA installed on winwhatever... i do not have
telsrv or gamesrv installed, either... the testing was done by taking
the resulting d32sys file generated by RA and the .bat file over to
the vista machine... then i simply ran the .bat in a command prompt
window to generate the door32.sys file...
i had to change the way i can do it on OS/2 with 4DOS... instead it
has to be done in a very ugly way which requires changes the RAT
file... as noted previously, SOCKHAND should be set in NF.BAT using
the modified gamesrv command line and the modified NF.BAT i posted in
a previous message...
the menu command line in RA is
*c /c c:\ra\d32sys.bat *r *m
this menu option should be limited to only ANSI users and only those connected to the com ports used for telnet... users on dialup modem comports and without ANSI enabled should not see this menu option...
the RAT file is...
==== Begin "d32sys.rat" ====
LINE01=2
LINE02=%SOCKHAND
LINE03=^Kr
LINE04=RemoteAccess 2.62
LINE05=%RECNUMB
LINE06=^Fa
LINE07=^F3
LINE08=^Fo
LINE09=^F_
LINE10=1
LINE11=^Kw
==== End "d32sys.rat" ====
^F and ^K are the actual characters... generally they are entered in
DOS editors via CTRL-P CTRL-F and CTRL-P CTRL-K...
the BAT file is...
==== Begin "d32sys.bat" ====
@echo off
SETLOCAL
echo D32SYS.RAT Testing...
if not exist DOOR32.SYS then goto jump
echo deleting DOOR32.SYS
del /q door32.sys
:jump
REM SOCKHAND should already be set by NF.BAT before loading RA!
echo SOCKHAND=%SOCKHAND%
set RECNUMB=%1
echo RECNUMB=%RECNUMB%
echo:
REM doing this for windows is really nasty :(
for /f "delims=" %%x in (D32SYS.) do set %%x
echo %LINE01% >> DOOR32.SYS
echo %SOCKHAND% >> DOOR32.SYS
echo %LINE03% >> DOOR32.SYS
echo %LINE04% >> DOOR32.SYS
echo %RECNUMB% >> DOOR32.SYS
echo %LINE06% >> DOOR32.SYS
echo %LINE07% >> DOOR32.SYS
echo %LINE08% >> DOOR32.SYS
echo %LINE09% >> DOOR32.SYS
echo %LINE10% >> DOOR32.SYS
echo %LINE11% >> DOOR32.SYS
type DOOR32.SYS
echo:
echo Returning to RemoteAccess...
ENDLOCAL
==== End "d32sys.bat" ====
only three items need to be hardcoded for this to work properly... everything else is set in the RAT file so that the values are correct
for each individual user...
one possible problem may be the user's security level being passed...
some systems only allow for security levels 0 thru 255 while others,
like RA, allow for 0 through 64000... if this does cause a problem,
the only suggestion i have is to adjust one's security levels in RA to
be within 0 through 255...
the d32sys.bat can be named anything... i would continue to use the d32sys.rat file, though... the only change in d32sys.bat would be to change the "type door32.sys" line to execute the door needing door32.sys...
eg:
RA menu line
*c /c c:\ra\d32sys.bat *r lord *m
and in d32sys.bat replace the one line "type door32.sys" with
something like "c:\bbslink\bbslink.exe %2"...
if bbslink.exe needs the socket handle, pass it using %SOCKHAND% as in
c:\bbslink\bbslink.exe %2 %SOCKHAND%
now i wait for someone else to test it all together and report success
or not ;) O:)
FWIW: if someone wants to run door32.sys doors with dialup modem
nodes, some more changes will be required to fix the first line of the door32.sys file from the hardcoded value of 2 for telnet... i won't do that for now but it will take some additional .BAT magic similar to
how we set SOCKHAND before starting RA ;)
Now the hardest part. In order to help our frind Manuel Adorni, we
need to translate all this to Spanish. ;)
Excellent work man!
and in d32sys.bat replace the one line "type door32.sys" with
something like "c:\bbslink\bbslink.exe %2"...
if bbslink.exe needs the socket handle, pass it using %SOCKHAND% as in
c:\bbslink\bbslink.exe %2 %SOCKHAND%
BBSLink for Windows is based on R&M Telnet door so all it needs is to
read the DOOR32.sys and the door code.
now i wait for someone else to test it all together and report
success or not ;) O:)
Great job.
FWIW: if someone wants to run door32.sys doors with dialup modem
nodes, some more changes will be required to fix the first line of
the door32.sys file from the hardcoded value of 2 for telnet... i
won't do that for now but it will take some additional .BAT magic
similar to how we set SOCKHAND before starting RA ;)
Now the hardest part. In order to help our frind Manuel Adorni, we
need to translate all this to Spanish. ;)
the command line in GAMESRV would look like
c:\gamesrv\nf.bat *H /n*N /h*H c:\ra\ra.exe -n*N -B57600
and NF.BAT would look like this
===== begin NF.BAT =====
@echo off
REM NF.BAT for NetFoss
REM capture the socket handle to SOCKHAND
set SOCKHAND=%1
shift
REM now process as normal before the above 2 lines were
added
c:\gamesrv\netfoss.com %1
if errorlevel 1 goto end
c:\gamesrv\netcom.exe %1 %2 %3 %4 %5 %6 %7 %8 %9
c:\gamesrv\netfoss.com /u
:end
This could also be done using Net2BBS, Which is the small footprint
telnet server that comes with NetFoss. Net2BBS uses the *H macro to
pass the socket handle to NF.BAT
according to the 2000 revision 1 specification of DOOR32.SYS, three bbses supported it... Mystic, EleBBS, and Synchronet... i'm sure that others also support it these days... especially if they support telnet connections direct without needing a shim providing a virtual modem...
Re: DOOR32.SYS
according to the 2000 revision 1 specification of DOOR32.SYS, three bbses
supported it... Mystic, EleBBS, and Synchronet... i'm sure that others
also support it these days... especially if they support telnet
connections direct without needing a shim providing a virtual modem...
And WWIV 5.0