ConfigFReq User Manual version 3.1 1. Introduction Use ConfigFReq to setup a correct environment for FReq to work properly. With ConfigFReq you can specify several directories and values needed by FReq as well as some default preferences. 2. Usage You can call ConfigFReq with two arguments of which the second is optional. The first argument must be the name of the configfile you wish to edit or create for that matter. The second argument is the name of the destination configfile. Specify this name if you do not want to overwrite the source configfile. ConfigFReq will read from the source configfile and write to the destination configfile. If no destination configfile was specified, the source configfile will be used as such. ConfigFReq will open a window with several gadgets. Change anything you like and click on the SAVE gadget when you are ready. The closegadget can be used to discard any changes, that is, to not save them to disk. The same can be archieved by pressing the right mousebutton with the ConfigFReq window still active. If a non-existing sourcefile was specified, i.e. the name of a configfile you wish to create, ConfigFReq will fill all gadgets with hardwired defaults. These are equal to the ones used by FReq at the absence of a configfile. You can immediately select SAVE to create a configfile using these defaults or apply some changes first. 3. The gadgets This section will describe the meaning of all gadgets in detail. 3.1. TrapDoor commandline template This gadget contains a template for the commandline used by FReq to call TrapDoor. Just type a commandline like you would use it from your CLI or shell. You may use three patterns in this commandline which will be replaced with proper values at runtime. These patterns are: ›3m%›1mn ›0mwill be replaced with the node address for the node to call. ›3m%›1mp ›0mwill be replaced with the phonenumber of the node to call. ›3m%›1mw ›0mwill be replaced with the session password for the node to call. Do not put quotes around this pattern since this will result in failing handshakes (the quotes will become part of the actual password). If FReq encounters an empty password Page 1 ConfigFReq User Manual version 3.1 at runtime, quotes will automatically be used (PASSWORD ''). 3.2. TrapTell commandline template When TrapDoor is yet running at the moment when FReq attempts to address it, the TrapTell command will be used instead of the TrapDoor command. The normal procedure is to copy the TrapDoor commandline template to this gadget, replace 'TrapDoor' with 'TrapTell' and put all of its arguments between quotes. As with the TrapDoor commandline template you should not include quotes with a %w pattern as FReq will generate these if necessary. Take a look at the default configuration which appears if you create a new configfile. This will give you an idea as to what a typical FReq configuration should look like. 3.3. Custom nodelistfile This gadget should contain the full path of FReq's custom nodelistfile, usually "MAIL:FReq.NOD". 3.4. Official nodelist directory The directory in which FReq can find the official nodelistfiles should appear in this gadget. This directory harbours files like "NODELIST.???", "fidonet.index" and "fidonet.extra". Refer to the manual of TrapList for more information on these files. 3.5. Outbound directory Specify your outbound directory in this gadget. This is the directory where FReq will store all requestfiles and checkfiles. 3.6. Inbound directory This gadget must contain the name of your inbound directory which will be looked for by FReq each time you select the CALL NODE or CHECK INBOUND switches. 3.7. TrapDoor's ARexx port This gadget should contain the name of the ARexx port as you have specified it in your TrapDoor configfile. Usually this would be "TrapDoor". FReq uses this name to determine if TrapDoor is active, i.e. in ANSWER mode. 3.8. Default zone Two dimensional requestfilenames do not feature a zone specification. Since this is required for nodelist operations however, a default zone must be specified in this gadget which will be used if a two dimensional filename is encountered. Normally you would use your own zone number here. Page 2 ConfigFReq User Manual version 3.1 3.9. Create checkfile With this item checked, FReq will create checkfiles along with every created requestfile by default. Refer to section 4.6.3 of FReq.DOC for more information on checkfiles. 3.10. 4D reqfilename If this item is checked, FReq will use four dimensional filenames by default when creating requestfiles. Refer to section 4.6.4 of FReq.DOC for more information on this. 3.11. Use official nodelist By default, FReq will use the official nodelist in addition to its custom nodelist when this item is checked. Refer to section 4.6.5 of FReq.DOC for more information on this. 3.12. Add file comments FReq adds filecomments to checked inbound files by default when this item is checked. Refer to sections 4.5.3 and 4.6.6 of FReq.DOC for more information on inbound checking and filenotes. 3.13. Auto load listfile If this item is checked and a listfile is specified in the nodelist entry belonging to the current node, FReq will automatically load this file if the filelist browser is activated. Refer to section 4.6.7 of FReq.DOC for more information on this topic. 3.14. Auto check inbound If a checkfile exists for a selected node, FReq will automatically perform an inbound check for that node if this item is checked. Refer to sections 4.5.3, 4.6.3 and 4.6.8 of FReq.DOC for more information about checkfiles and inbound checking. 4. Policy ConfigFReq is a part of the FReq version 3.1 distribution archive and therefore subject to FReq's rules and regulations. Refer to FReq.DOC to learn about FReq's policy. Page 3 ConfigFReq User Manual version 3.1 Index 1. Introduction ...................................... 1 2. Usage ............................................. 1 3. The gadgets ....................................... 1 3.1. TrapDoor commandline template ..................... 1 3.2. TrapTell commandline template ..................... 2 3.3. Custom nodelistfile ............................... 2 3.4. Official nodelist directory ....................... 2 3.5. Outbound directory ................................ 2 3.6. Inbound directory ................................. 2 3.7. TrapDoor's ARexx port ............................. 2 3.8. Default zone ...................................... 2 3.9. Create checkfile .................................. 2 3.10. 4D reqfilename .................................... 2 3.11. Use official nodelist ............................. 3 3.12. Add file comments ................................. 3 3.13. Auto load listfile ................................ 3 3.14. Auto check inbound ................................ 3 4. Policy ............................................ 3 Page 4