The upgrade from 1.2 to 2.0 adds the following features and fixes: * GCF-compatible keywords make CrystalFix easier to set up and more compliant with TrapToss. CrystalFix has its own section now. * FTick support. * Totally new GROUP system is a lot easier to understand and explain and is also much more readable, yet is functionally equivalent. You assign single letters to each group, instead of powers-of-two. Better yet, since I'm free of ARexx's bitand() function, I'm free of the many bugs it seems to have. This should FINALLY lick the security problem bugs that have haunted me despite repeated fixes. * COUNT command controls what counts, if any, are shown to the user at the end of queries, and can be used to greatly speed up CrystalFix's startup if you have hosts with big NA files. * Made sure the archive has the right versions of everything this time! Reply linking should work thoroughly. * Rescan now should not produce dupes to points in an area, because, instead of relying only on SEEN-BYs, it actually only rescans for the given node, by creating a temporary config file, scanning, then deleting the temp file. * Fixed a few bugs, such as the doubled MAIN lines, some security problems attaching to host areas, problems if you kept your config file on a different partition than Mail: (or if you don't have a Mail: assign), conflicts with the LOGFILE and LOGLEVEL options in other areas like TrapSched, and more. * LOGFILE command to let CrystalFix have its own private log. * Backups and working file copies of the config file are stored in the same place as the original, with a suffix added. * Control over location of CrystalFix.help The upgrade from 1.2 to 2.0 requires some significant, but not at all difficult, modifications to your config file. Here's a step-by-step guide to them. After this, we'll be GCF-compliant from now on, so there should be no need for more changes, even with new TrapToss versions. In the following, you'll see a lot of sample lines and their conversions; that is, I've used real data instead of because I thought it would be easier to read. It should be self-evident how to apply these to your own config file. 1. Add the following line to create a new section. The best place to put this is right after (or at least somewhere after) the TrapToss section. [CrystalFix] 2. Convert the line ;!FIX SYSOP Sysop Name into SYSOP "Sysop Name" (that is, take off the ;!FIX and add quotes.) Move this to the global section of your file. (Or put it in the TrapToss or CrystalFix sections if you prefer.) 3. Convert the line ;!FIX LOGLEVEL 5 into LOGLEVEL 5 and move it into the CrystalFix section. 4. Convert the line ;!FIX NEWPATH Mail:echos into NEWPATH "Mail:echos" and move it into the CrystalFix section. 5. The bits system has been completely replaced with a functionally equivalent, but easier to explain and understand and document, groups system. Every power-of-two is replaced with a single letter, and addition is replaced with concatenation. In the new system, areas, hosts, and systems are allowed to "own" one or more group letters (you decide which letter means which area), and a system can only access an area if it owns all the letters (if any) that that area owns. See the new SampleFido.cfg file for an example or two. If you need more explanation, read step 6 and 7 from the CrystalFix.doc file. Then convert your bitmasks into group letters. Plan this out and change your comments appropriately. For instance, the bitmask 2 might become the letter F, and the bitmask 4 might become T. When you would have added the bitmasks to get 6, just concatenate (in any order) the letters (as in FT). 6. Convert the line ;!FIX SYSTEM 1:325/611.1 PASSWORD 10 6 into SYSTEM 1:325/611.1 PASSWORD 10 "FT" where FT is the concatenation of the groups that correspond to the bitmasks that formed the bitmask 6. Move this line into the CrystalFix section. 7. Convert the line ;!FIX HOST 1:325/611.0 1:141/1130.0 PASSWORD 10 6 Mail:Fidonet.NA into HOST 1:325/611.0 1:141/1130.0 PASSWORD 10 "FT" "Mail:Fidonet.NA" Notice the quotes around the pathname. Move this into the CrystalFix section. 8. Convert the line ;!FIX LEVEL 10 2 A really fun area you should attach to into LEVEL 10 GROUP "F" DESCRIPTION "A really fun area you should attach to" Note the quotes and the fact that it's three separate lines now. 9. If you want CrystalFix to use a different log file, add the following line to your CrystalFix section: LOGFILE "Mail:CrystalFix.log" except use your own log file name. 10.If you want to control the location and filename of CrystalFix.help add the following line to your CrystalFix section: HELPFILE "Mail:texts/CrystalFix.help" except use your own help file pathname. 11.If you have some hosts with big NA files and you want to save some time in CrystalFix startup, or if you want to not show the user quite as much info at the end of queries, add one of the following lines before the first HOST line (if any) of your CrystalFix section: COUNT NONE COUNT ATTACH COUNT AVAIL See step 13 in the docs for more info. 12.Remove the IGNORESENT line from Fido.cfg that you added for v1.(0|1|2). Unless you like it. 13.If you want to use FTick support, edit your Tick.cfg file and add LEVEL, GROUP, and DESCRIPTION keywords under your AREA/FILEECHO blocks. You also need to add FLAGS keywords. All Tick keywords must, for the time being, be preceded by ";!". See the docs for details on these; but they all work just like the Fido.cfg equivalents. 14.If you are supporting FTick and your Tick config is not Mail:tick.cfg add its pathname to the end of your CrystalFix command line. If the Fido config pathname isn't already there, because you use the default Mail:fido.cfg, you must put Mail:fido.cfg in first. 15.If you use host autoforwarding, look at the ADDAREACMD command. Rereading the docs might be nice, but is certainly not necessary. The new SampleFido.cfg file would be a bit more useful to read. See also the new SampleTick.cfg. The whole process should be pretty simple. - Frank