From: B.J. Guillot
    To: Gary Kopycinski
Thread: BGFAX/2 and Binkley/2  (1/2)
  Date: 26-Apr-97, 12:31pm  (Ref# 5258)

> On the plus side, the BGFAX did append to my Faxworks log,
> and I was able to view the fax successfully.  However, I am concerned about
> the loop.  You can see from the Binkley.log below that Bink reports that COM2
> is open after the fax reception.
 
Hmm... very strange.  The only thing I can suggest is for now to
temporarily disable the printing as the faxes come in.  Perhaps calling
VIEW.EXE (a DOS program) is causing the problem.  I'm not sure why, but
that's the only thing I can think of.
 
Regards,
bgfax author


  From: Gary Kopycinski
    To: B.J. Guillot
Thread: BGFAX/2 and Binkley/2  (2/2)
  Date: 27-Apr-97, 7:43am  (Ref# 5281)

> On the plus side, the BGFAX did append to my Faxworks log,
> and I was able to view the fax successfully.  
> However, I am concerned about
> the loop.  You can see from the Binkley.log below 
 BG> that Bink reports that COM2
> is open after the fax reception.
 BG>  
 BG> Hmm... very strange.  The only thing I can suggest is for now to
 BG> temporarily disable the printing as the faxes come in.  Perhaps calling
 BG> VIEW.EXE (a DOS program) is causing the problem.  I'm not sure why, but
 BG> that's the only thing I can think of.

I don't know what to say either, except that it must have been a loop that I
caught somewhere along the line.  NOW, BGFAX operates flawlessly: faxes come
in, then print, BINK.CMD loops back to Binkley.

Go figure.

GK

--- Maximus/2 3.01
 * Origin: The Shire * (708) 755-0915 * Steger, IL (1:2222/147)