FB> CB} It just doesn't seem to quite fit my tastes
FB>   } (doesn't support 28, 30, 33 rows, doesn't auto
FB>   } open capture file, doesn't allow multiple DL
FB>   } paths, etc.).
FB> Carey, {COMMO} does indeed support 28, 30, 33 rows (or any other
FB> text mode screen dimensions).  It will auto detect any mode when you
FB> start up and let you switch to any other mode while in the program
FB> (see the "avm" item in setup).
I had not seen that.  I guess I'm used to things being done from options
set from a menu and Commo does everything from free form files.  I'm not
sure if it would work with 28 rows or not though.  I don't think they
are actual video modes but are tricks of other VGA modes.  I'm not sure
of the details but I think for 28 you tell it to go to the 25 hardware
resolution mode and then you adjust the character height by a few pixels
and then do something else.  It's a 'trick'.  All VGA support it, but
it's a non-standard mode. (Somewhat like the popular 'X mode' in
graphics.) I don't know the details. I took a look at my video card
manual and in the SVGA section it lists 30 rows in text mode so I could
use that. In standard VGA mode though it only lists the 30 rows mode in
graphics mode.  And it doesn't list 28 or 33 at all and I know it works
because I use programs that use them. As I said, I don't know the
programming details of it.
FB> I don't know what you mean by "auto open capture file," but I'll bet
FB> it can be accomplished with a simple macro.
Well, I like to have seperate capture files for each BBS and for them to
automatically open (append) when I connect.  I'm sure it could be done
by macros, but, well, I don't like writing macros.  It's odd since I'm a
hobbiest programmer and know Pascal, C, Fortran, and even Forth.  My
dislike for writing macros may stem from some months back when I tested
more than 30 comm programs and got very fed up with them, scripts,
features, etc.
FB> Same goes for multiple DL paths.  You can easily set a separate DL
FB> path for each entry in your Dialing Directory (if that's what you're
FB> looking for).
What I would like is my QWK/REPs automatcially be sent/fetched to my
mail directory.  Gifs, PCX, etc. be sent to my picture dir, ZIPs, Arcs,
etc. be sent to my normal download dir and so on.  Just be able to
automatically route downloads to the appropriate directory
automatically.  I know I could use a simply COPY *.GIF type batch file
to take care of it, but Telemate already has this built in.  And using a
batch file wouldn't help get my REPs out my mail directory.
A macro to find the file first (using a path string indicating
appropriate extensions) would work for uploads.  Just stick the hunt
macro call in before the actual upload. And I suppose downloads could
work similarly. Just DL to a empty dir and then a macro could read that
path/extension string and copy each to the appropriate directory.
Also, I think auto upload would be nice.  Especially for REP packets.
FB> What's the "etc.?" 
I'll start at the 'top'.
I first considered commo because it was 'cute' and small compared to
other comm programs that take 500k of ram and 8 meg of HD.
The macro language seemed a bit odd compared to others, but it did seem
more powerfull than most.  It doesn't allow numeric variables so you
can't have 'for' loops etc. It seems a bit restrictive to limit it to
two macro files at a time when most others can automatically call any
number of routines in others.  (This view point may seem odd since 1:
I'm not even in the mood to do any programming, 2: two sets of 64k
worth of macros is quite a lot, 3: if you need a subroutine, all
you have to do is simply import it into the source file, 4: once you get
a startup/login macro done you don't have to mess with it anymore
anyway.)
The free form nature of the settings and fone directory and macro file
defintly take a bit of getting used to.  More than a little since I'm
used to comm programs that offer menus of options to set, dialing
directories with a fixed form and so on.  And the Commo allows comment
anywhere and brackets the items where most others bracket comments (like
/* */, { }, //, etc.)  That seems backwards.  I know it's for a reason,
but it seems backwards.  Also it being restricted to 1 line seems
restrictive.  Maybe you should add a 'continuation' indicator like
Fortran had.
My ability to get it for $30 was enticing since prices for others are
usually much higher.  (Who do you consider a 'student' to be?  Summer
break is comming up and most aren't going to be students for a while.)
The fact that the programmer is actually available is very nice.  I
probably would never report a bug, but if I did, you could fix it.
Something like that couldn't be done with Telix, Telemate, Terminate, or
most of the other popular comm programs.  (There are a few others that
might, but they generally aren't as avaialable as you are.)
I don't like writing macros.  That was one of the reasons I chose
against Telix.  Telix does have the most extensive macro language that
I've seen (sorry Fred), but I just don't like HAVING to write macros to
do things that I feel should be possible directly from the dialing dir.
Such as open seperate capture files for each BBS.  I know writing a
script/macro to do this in either Commo or Telix is no big deal, but I
don't like having to do it.
Those darn delays in {COMMO} are just so anoying... 
Commo does have fairly decent online help. (Not as extensive as some,
but decent.)  Unlike Telemate or Telix. (The telix people (Zack Jones &
Jeff Woods) were totaly baffled as to why I would want online help to be
more than just a quick key reference.)
I don't really like compiled macros.  Not so much because I actually
dislike them being compiled, but when I considered Telix, I found so
many scripts that _almost_ did what I needed but they were compiled and
I couldn't modify them.  I've got an uncompiler for Telix salt scrips
and Commo can also interpret them instead of having to have them
compiled, so I don't guess it makes too much difference anymore.
I wish Commo had a screen saver.  I sometimes do long downloads (or
multiple long downloads) and it may be DLing for an hour or more.
Normally I just turn the screen off and get up and do something else,
but it would be nice if I could leave it on so I could glance at the DL
progress.  I don't know, maybe just clear the screen and have the
transfer window slowly move around the screen.
FB> CB} I'm thinking about evaluating it again though.
FB> Please do!
I've still got 6.41 installed, although in the past three weeks I've
only used it once.  That was yesterday when I was trying out Jeff
Bishop's learn macro.
I noticed that you announce beta releases.  When you do, could you at
least tell us whats been changed so we know whether to call long
distance and get a copy?  If it's just a fix for some obscure bug that
we've never had it would be a waste of a call.
--- QScan/PCB v1.16b / 01-0162
---------------