JS> Multiple timed.cfg files, one per user. ;)
 AT> Actually, you would only need two .cfg files: one for 
 AT> you (which you use off-line) and one for the current 
 AT> user.  Just generate it on-the-fly and delete afterwards.
Let me see if I am following this correctly: instead of having a preset cfg 
for each user, you would use a method to create it each time (sort of like 
how door.sys drop files are done). Since I do not use timed but am intersted 
in this idea of another user editor, I still have a few questions even though 
this is a good idea.
From previous posts there are apparently cfg options the sysop would want to 
control (pre-can) and that would be consistent with your idea. However, are 
there user options like header/text display colours, quoting style, taglines, 
etc that would/could still be very individual? How would they get placed in 
the on-the-fly generation? How would they be stored for retrieval? That's on 
the editor.....then tagged areas, last read pointers, etc from the bbs end 
still need to be picked up, don't they?
--- Maximus 2.02
---------------