Use CAPTURE.EXE at you own risk.

          One of  the major problems with using software interrupts is that
          you never can tell when the interrupt vector  will be  changed by
          some other  software.   Quite often the offending software is the
          program/function that you would least suspect.

          If you are getting  the "OPUS!COMM  not responding"  message from
          Opus, then  try executing  CAPTURE just  before you execute Opus.
          You must be using X00.SYS.  CAPTURE will not work  with OPUSCOMx.
          If  you  know  the  offending  program/function,  execute CAPTURE
          immediately following the culprit.

          In fact, its not a bad idea to always execute CAPTURE just before
          you execute Opus.

          CAPTURE.EXE simply  tells the device driver X00.SYS to re-capture
          the  software  interrupt  vector(s)  (from  whoever  grabbed it).
          CAPTURE may be executed at any time.

          Revision History

          V1.00
          Added the options ON and OFF.  The default is CAPTURE ON.  If you
          enter  CAPTURE  OFF  then  X00.SYS  will   restore  the  original
          interrupt 14H  vector.   If you CAPTURE OFF then you must CAPTURE
          or CAPTURE ON before you execute Opus again.

          The advantage of the ON and OFF options is that it allows you use
          the native  driver of  SEAdog if  you want  to.   That is, if you
          enter CAPTURE OFF just before you execute SEAdog then SEAdog will
          not use  the X00.SYS  FOSSIL functions.  It will use its own comm
          drivers.  However, on my system, SEAdog V4.0 will not  work under
          MultiLink if its native drivers are used.

          V1.08
          Internal changes to work with X00 V1.07c and up.