Subject: | 2/2 - SBBS & MS-Kermit
| Date: | Wed, 23 Jul 2003 00:50:47 GMT
| From: | "Digital Man" <digital.man@vert.synchro.net.remove-120u-this>
| Newsgroups: | alt.bbs.synchronet
|
To: Michel Samson
Re: 2/2 - SBBS & MS-Kermit
By: Michel Samson to Mohamed Nishath on Tue Jul 22 2003 09:00 pm
> The batch-files will be useless if you don't pass the parameters to
> them from the command-line, the three command-lines would go as follows:
>
> Fake1.BAT %A %B %C %F %G %I %J %K %N
> Fake2.BAT %O %P %Q %R %S %T %U %W %Z
> Fake3.BAT %! %# %* %$ %1 %2
The only specifiers I see being of any use to Kermit (or any external transfer
protocol, for that matter), are:
%f the path/filename to transfer for single-file transfers, or
the filelist for batch transfers
%s the paths/filenames of all files to transfer (for batch transfers)
and if it's a socket based program:
%h the active socket descriptor
For 16-bit FOSSIL programs (like FDSZ), the FOSSIL port used by the program is
irrelevant, as the Synchronet FOSSIL driver automatically directs the I/O to
the correct node.
I can't imagine any of the other command-line specifiers being of any use to
the external transfer protocol (Kermit or otherwise), but of course, they are
documented in Appendix A of the sysop manual, and you can look at the stock
FDSZ command-lines as examples.
digital man
Snapple "Real Fact" #133:
Honeybees navigate by using the sun as a compass.
--- Synchronet 3.11a-Win32 NewsLink 1.64
* Vertrauen - Fullerton, California - telnet://vert.synchro.net
|