>Area : MIN_INFO : MicroNet: Information ----------------------------------------------------------------------------- MININFO.ZIP 17500 Micronet Information Network Infopack for Friday, 7 April 2017 (day 097). All the information you need to join Micronet, an active and friendly BBS mail network. We offer FTN, QWK and NNTP networking. For more info, please read this infopack, visit a participating BBS, or visit our webpage for more info. http://outpostbbs.net/micronet.html FREQ MININFO from 1:18/200 Orig: 618:618/1 ----------------------------------------------------------------------------- 17500 bytes in 1 file(s)
>Area : MIN_LIST : MicroNet: Nodelist ----------------------------------------------------------------------------- MICRONET.Z97 5935 Micronet Information Network nodelist for Friday, 7 April 2017 (day 097). Orig: 618:618/1 ----------------------------------------------------------------------------- 5935 bytes in 1 file(s)
>Area : NASA : Fidonet: Earth & Space Science Material ----------------------------------------------------------------------------- AP170407.ZIP 342379 NASA Astronomy Picture of the Day (plus published Report; antwrp.gsfc.nasa.gov) Orig: 1:393/68 ----------------------------------------------------------------------------- 342379 bytes in 1 file(s)
>Area : PASPOINT : PAS Pascal-Net Pointlist ----------------------------------------------------------------------------- PASPOINT.Z97 8614 Weekly Pascal-Net PointList file Orig: 115:115/15 pzpoint.z97 222 Weekly Pascal-Net PointList in new Boss format. Orig: 115:115/15 ----------------------------------------------------------------------------- 8836 bytes in 2 file(s)
>Area : PDNGOUTL : PDN:Go Utilities ----------------------------------------------------------------------------- goreprtr.zip 1685181 A Golang tool that does static analysis, unit testing, code review and generate code quality report. https://github.com/wgliang/goreporter Orig: 1:261/38 ----------------------------------------------------------------------------- 1685181 bytes in 1 file(s)
>Area : SPORINFO : SportNet InfoPak ----------------------------------------------------------------------------- sportnet.zip 21177 SportNet InfoPak for day 97, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 21177 bytes in 1 file(s)
>Area : SPORNODE : SportNet Nodelists ----------------------------------------------------------------------------- spordiff.z97 518 SportNet nodediff for day 97, 2017 Orig: 24:24/0 sportnet.txt 20875 SportNet BinkD style nodelist for day 97, 2017 Orig: 24:24/0 sportnet.z97 8194 SportNet nodelist for day 97, 2017 Orig: 24:24/0 ----------------------------------------------------------------------------- 29587 bytes in 3 file(s)
>Area : WEATHER : Fidonet: Daily Graphic Forecasts ----------------------------------------------------------------------------- DAILYWET.ZIP 750273 Daily Weather Graphics Forecasts for North America from NOAA and wisc.edu Orig: 1:393/68 ----------------------------------------------------------------------------- 750273 bytes in 1 file(s)
============================================================================= >Total 3150461 bytes in 21 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...
