= Сообщение: 2679 из 7125 ====================================== FTSC_PUBLIC = От : TequilaMockingbird Online 1:266/404 10 Feb 17 23:59:03 Кому : All 10 Feb 17 23:59:03 Тема : New Files Received FGHI : area://FTSC_PUBLIC?msgid=51902.2ftscpubl@1:266/404+1d049ad5 = Кодировка сообщения определена как: ASCII ================================== ============================================================================== System name: TequilaMockingbird Online Sysop: Bill McGarrity (1@tequilamockingbirdonline.net) Location: Toms River, New Jersey USA Networks: 1:266/404@fidonet 316:973/2@whispnet 618:100/24@micronet 24:24/0@sportnet 46:1/159@agoranet Telnet: bbs.tequilamockingbirdonline.net:23 Web: bbs.tequilamockingbirdonline.net:81 Running: Synchronet 3.16a Win/32 - Windows Server 2008 Enterprise Mailer: binkd/1.1a-89/win32 IPv6 Native -------------------------------------------------------------------------------
>Area : PASPOINT : PAS Pascal-Net Pointlist ----------------------------------------------------------------------------- PASPOINT.Z41 8619 Weekly Pascal-Net PointList file Orig: 115:115/15 ppoint.z41 8326 Pascal-Net Zone 115 Weekly New Fakenet Pointlist By new 5 digits numbers. Orig: 115:115/15 pzpoint.z41 10799 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 pzpoint.z41 5530 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 ----------------------------------------------------------------------------- 33274 bytes in 4 file(s)
>Area : SPORINFO : SportNet InfoPak ----------------------------------------------------------------------------- sportnet.zip 20878 SportNet InfoPak for day 41, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 20878 bytes in 1 file(s)
>Area : SPORNODE : SportNet Nodelists ----------------------------------------------------------------------------- spordiff.z41 581 SportNet nodediff for day 41, 2017 Orig: 24:24/0 sportnet.txt 20752 SportNet BinkD style nodelist for day 41, 2017 Orig: 24:24/0 sportnet.z41 8173 SportNet nodelist for day 41, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 29506 bytes in 3 file(s)
============================================================================= >Total 390835 bytes in 20 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...
[/SECOND METHOD]
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...
