textfiles.com: /programming/procomm2
             Part 2 of PROCOMM - OUTSTANDING TELECOM by Merv Adrian
 
DOS Gateway :  This is a fairly standard feature.  Owing to the size of the code 
used for ProComm,  you must be selective with respect to  the  applications  you 
choose to use.  
 
Saving Screens and Sessions : Disk logging of a screen (with Alt-G) or a session 
(with Alt-F1) is possible.  In the case of session logs,  you are not stuck with 
the default file you established;  you are prompted for another new name if  you 
wish  to  specify  one.  This  is  very useful for those special needs you don't 
anticipate and want to keep separate from your general  log  file.  I  once  was 
pleasantly  interrupted by a SYSOP in CHAT mode and I would have loved to keep a 
separate log of that conversation on disk.  
 
Printed Log Files :  Printer logging is another feature  which  I  usually  find 
annoying  but  has its place,  especially when running unattended command files.  
ProComm supports it with the Alt-L toggle  interactively  and  with  appropriate 
commands.  

Editing  Files  :  Use your own editor!  Doesn't sound too revolutionary,  but I 
consider it a Godsend not to be stuck with either the  program's  editor  (a  la 
RELAY,  an otherwise excellent product),  or worse, EDLIN.  I've grown very fond 
of KEDIT (you see, I DO buy some commercial programs), so that's what I use.  

Personalized communications...  
 
Sound : Sound effects may be set on or off by default on the configuration menu, 
but they may also be overridden at startup time with  the  "/S"  switch  on  the 
command line.  
 
Color  :  Color  may be set for the program screens individually for foreground, 
background,  and highlighted text.  The program  will  also  display  any  color 
information passed to it by a BBS you are connected to.  
 
Relationship to DOS : You may tell ProComm to be "well-behaved", that is, to use 
BIOS calls rather than direct screen writes,  which makes it easier to use under 
multitasking systems.  This may be set up by default or through the "/M"  option 
on the command line.  
 
Environment  Support  :  Environment  support  (SET  PROCOMM  =  pathname)  is a 
substantial topic.  Someone really should cover it but in the meantime read your 
DOS manual, I'm busy enough as it is.  

The requirements to use ProComm are: 1. 128K 2. IBM Compatible 3. MS-DOS 
 
Documentation :  The manual is one of the  best  I've  ever  seen.  It  includes 
thorough  details  on  each  of  the  terminal emulation settings in appendices, 
discusses character translation at length (in case you  ever  wondered  how  the 
program  can  tell  the difference between receiving a carriage return and being 
asked to send a carriage return,  for example),  and provides a well-thought out 
introduction  to  all  the  features  of  the product.  I've never seen a better 
discussion of XON/XOFF;  this one tells you what you need to know about it, what 
you  might  want to do about it in a tricky situation,  and doesn't give you any 
unnecessary  technical  information  (at  least  at  this  point,  it  would  be 
unnecessary).  

Summing Up :  I hoped to keep this brief;  I could have gone on because there is 
so much to say about ProComm.  I'm a believer,  my check is in the mail already. 
Try it, and support another great piece of software. 
Procomm - Outstanding telecom by merv adrian                
review: Procomm- outstanding telecom a review by merv adrian describing features of procomm review: PROCOMM - OUTSTANDING TELECOM by Merv Adrian


<FOLDER>
        <NAME> 1.2 The World According to Pro-Comm
      <AUTHOR> [ProComm Users' Part Two Of "Procomm - Outstanding Telecommunication"
DOS Gateway
Saving Screens and Sessions
Printed Log Files
Editing  Files

Personalized communications...
Sound
Color
Relationship to DOS
Environment Support
The requirements to