Hi..
 CB> I'm not sure if that would work with externals doing downloads
 CB> though.  Because they don't tell the comm program what was
 CB> downloaded (either during or after) and the only way Commo would
 CB> know what was downloaded would be to check the transfer log, if
 CB> the protocol even made one, and then copy the files to the
 CB> appropriate directory.
What I have in mind would be to capture the file extension when the
transfer first starts.  The filename/extension is passed in the
protocol's first header packet.  Fred already knows how to grab it since
he uses it in the status screen.  Once the extension is known, the d/l
path could be set "on the fly".  There would be no need to check any
transfer logs, etc., since the file would have been routed to the
correct directory automatically.
This is probably much easier done with the internal protocols than
external.
 CB> I suppose some enterprising person could try it with a macro
Not currently do-able, except after-the-fact.  IOW, the only way is to
move files (to directories based on extension) after they've been
d/l'ed.  *That* can be easily be automated with a macro.
Jim
--- Maximus/2 2.02
---------------