PE> I'd prefer you just read the title from filearea.ctl

BL> Can you send me a sample of the format? 

See below.

BL> But I need other info
BL> for TIC anyway, like passwords and that....

That is separate from the files list.  You posted a configuration file
recently for that, which was fine.

PE> and dispensed with the graphics headers

BL> The headers are the darling part... why dispense with them?

If they're too hard to produce, which they are, then dispense with them
(for now).  Or just create a function "fancy_header", which just
does a simple printf() for now, but can be expanded later.

PE> , and got the descriptions from files.bbs (BTW, the files.bbs
PE> allows you to use wildcards, so that you can go FNEWS*.*
PE> fidonews etc). You can use patmat() from OZPD to do this. 

BL> I don't care about files.bbs and I can't read C code, but I can

You don't need to read patmat, just call it.

BL> write it okay. My code will work in UNIX which was the whoile point, I
BL> thought. I prefer to ignore files.bbs and possible errors, and use the
BL> source itself: the directory with the actual files. I got it working 

Yes, you have to use that.  But you can't ignore files.bbs, that's where I
put all the descriptions in, normally using wildcards.

Here's filearea.ctl...

Area 3
        FileAccess      Sysop

        FileInfo        BBS Related Stuff
        Download        D:\BBS\FILES\BBSSOFT\
        Upload          File\Uncheck\
End Area


Area 4
        FileAccess      Sysop

        FileInfo        Micro Emacs executables
        Download        d:\bbs\files\EMACS\
        Upload          File\Uncheck\
End Area
@EOT:

---