= Сообщение: 2626 из 7125 ====================================== FTSC_PUBLIC = От : TequilaMockingbird Online 1:266/404 13 Oct 17 23:59:03 Кому : All 13 Oct 17 23:59:03 Тема : New Files Received FGHI : area://FTSC_PUBLIC?msgid=57188.2ftscpubl@1:266/404+1e47a0eb = Кодировка сообщения определена как: EUC-JP ================================= ============================================================================== System name: TequilaMockingbird Online Sysop: Bill McGarrity Location: The Badlands of New Jersey USA Networks: 1:266/404@fidonet 316:973/2@whispnet 618:100/24@micronet 24:24/0@sportnet 46:1/159@agoranet 10:3/68@league10 801:1/13@rdwxnet Telnet: tequilamockingbirdonline.net Web: bbs.tequilamockingbirdonline.net FTP: ftp.tequilamockingbirdonline.net:2121 Running: Synchronet 3.17a Win/32 - Windows Server 2008 Enterprise Mailer: binkd/1.1a-95/win32 IPv6 Native
>Area : FILES2HQ : Oddball Files to HQ ----------------------------------------------------------------------------- sportnet.zip 1463466 SportNet InfoPak for day 286, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 1463466 bytes in 1 file(s)
>Area : NASA : Fidonet: Earth & Space Science Material ----------------------------------------------------------------------------- AP171013.ZIP 187507 NASA Astronomy Picture of the Day (plus published Report; antwrp.gsfc.nasa.gov) Orig: 1:393/68 ----------------------------------------------------------------------------- 187507 bytes in 1 file(s)
>Area : SPORINFO : SportNet InfoPak ----------------------------------------------------------------------------- sportnet.zip 1463466 SportNet InfoPak for day 286, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 1463466 bytes in 1 file(s)
>Area : SPORNODE : SportNet Nodelists ----------------------------------------------------------------------------- spordiff.z86 440 SportNet nodediff for day 286, 2017 Orig: 24:24/0 sportnet.txt 21041 SportNet BinkD style nodelist for day 286, 2017 Orig: 24:24/0 sportnet.z86 8277 SportNet nodelist for day 286, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 29758 bytes in 3 file(s)
>Area : WEATHER : Fidonet: Daily Graphic Forecasts ----------------------------------------------------------------------------- DAILYWET.ZIP 743903 Daily Weather Graphics Forecasts for North America from NOAA and wisc.edu Orig: 1:393/68 ----------------------------------------------------------------------------- 743903 bytes in 1 file(s)
============================================================================= >Total 4063671 bytes in 16 file(s)
2. Rename the file using the hex of my net and node... each must be padded with leading zeros to make four places... Net: 266 Node: 404
266 == 010a 404 == 0194
ren WPUSA.REQ 010a0194.req
3. Move the REQ file to your proper outbound directory for zone 1 since I'm in zone 1... in my case, this is just the .../outbound folder you have configured in binkd... for others it would be .../outbound.001 if zone 1 is not their primary zone...
move 010a0194.req .../outbound/010a0194.req
4. Create a poll file of the same name in the same directory to trigger binkd to connect to the remote system... a REQ file by itself will not trigger the poll... a ?LO file is required...
echo.>> .../outbound/010a0194.clo
5. sit back and watch binkd send the request and pick up the files and/or response messages...
╔═════════════╗ ║/First Method║ ╚═════════════╝
╔═════════════╗ ║Second Method║ ╚═════════════╝
1. Create a file containing the magic or actual file name(s) of the desired file(s)... i'll use my master files list and the fido history archive in this example... both of these are magic names on my system...
2. Move the REQ file to your proper outbound directory for zone 1 since i'm in zone 1... in my case, this is just the /outbound folder you have configured in binkd... for others it would be /outbound.001 if zone 1 is not their primary zone...
move WPUSA.REQ /.../outbound/wpusa.req
[ yes i renamed the REQ file to all lower case in the move to show that one can move and rename at the same time ;) ]
3. Create a poll file containing a pointer to the REQ file in the outbound directory... the poll file must be the hex net and node as shown in the example above... a REQ file by itself will not trigger the poll... a ?LO file is required...
The '^' in the above tells binkd to delete the req file after it has been sent... the full path to the REQ file is needed... it may reside anywhere and is not required to be in the outbound with using this method...
4. Sit back and watch binkd send the request and pick up the files and/or response messages...
I just tested both of these and they worked properly If one is using fileboxes for a system they want to FREQ from, i would imagine that just placing the REQ file in the filebox would work without the need to create the ?LO file or mess with the hex format naming stuff... as long as the file has the REQ extension it should work...
