Hello mark,   
      
   On Fri Jan 20 2017 16:21:36, mark lewis wrote to Nicholas Boel:   
      
    NB>> If it took you two or three days to search for and find the   
    NB>> "misc" directory under HPT's (and HTICK's for that matter) root   
    NB>> directory,   
      
    ml> why would i look in there? it isn't a misc file... a document or   
    ml> config file, sure but not misc...   
      
   Sysop documentation happens to be in the "doc" subdirectory. Configuration   
   files happen to be in the "config" subdirectory. And since you've already gone   
   through both of those after install, why not check out the "misc" directory? I   
   would definitely consider areafix.hlp/filefix.hlp a miscellaneous file. It's   
   not sysop documentation so I wouldn't put it with the other sysop   
   documentation in the "doc" directory, it's a document for the user, to be   
   placed wherever you want it to be, hence a "misc" file.   
      
   And if I remember right, you have to actually specify the location of the   
   areafix.hlp/filefix.hlp in your robots sections in the main fidoconfig file,   
   which means it's not hardcoded and can be located anywhere, hence the   
   miscellaneous part. *shrug*   
      
    NB>> then I suspect PEBCAK rather than the program itself. Where would   
    NB>> you expect it to be otherwise?   
      
    ml> after running make install i would expect to find it installed along   
    ml> with the binaries and sample configs... but that's not what happened   
    ml> for either of the help files or the sample configs... i had to find a   
    ml> way to generate a config file to even get started... in that case i   
    ml> found and used fidoInst by Zano and butchered that config into my   
    ml> working copy...   
      
   I can agree with the config files. After 'make install' some default templates   
   should probably be put into a proper place, since the config directory is   
   specified in huskymak.cfg for a reason. But this doesn't happen.   
      
   The code is freely available to do whatever you want with it, though.   
      
    NB>> And now to try to bring us back to the original topic in the   
    NB>> DBRIDGE echo, It was requested that DB have a help screen for   
    NB>> users trying to access Areafix, and now it does as of the latest   
    NB>> update. I'd call that a success!   
      
    ml> it is a success... no one is disputing that :)   
      
   Instead of pointing that out, the first things mentioned after the fact was   
   what DB's areafix was lacking compared to other tosser's areafixes. Nick has   
   already stated he's not going to add in all the fluff that other tossers have   
   added in over the years, so why beat a dead horse?   
      
   Regards,   
   Nick   
      
   ... "Не знаю. Я здесь только работаю."   
   --- GoldED+/LNX 1.1.5-b20161221   
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)