Digital BW, The Print

Finally found the cause of my I/O 32 error messages, at least when
using QTR on my systems.

I always disable firewalls first when trying to troubleshoot a
software problem.  But this time things were a little different. 
Seems that Kerio Personal Firewall had recently released an update
(which I had installed on two of my three machines).  I had disabled
the firewall when troubleshooting the I/O 32 error problem. 
Apparently, disabling the firewall wasn't enough.

I finally noticed that the machine that was not giving me errors was
running Kerio version 4.1.3.  The two machines that were giving error
messages had the new version 4.2 installed.

I UN-INSTALLED Kerio Personal Firewall 4.2, and WOW, everything worked
like a charm - NO more I/O error messages when using QTR !! 
Previously disabling the firewall didn't work.  Only UN-INSTALLING
Kerio 4.2 did the trick.

There may be a new "default" setting in the Kerio 4.2 release that can
be re-configured so that it doesn't cause the error messages.  I don't
know as I haven't gotten that far yet.

If other members of this group having I/O 32 error problems are Kerio
users, you might want to check your version number, and if 4.2,
un-install it and see if it clears up the error problem.  Of course,
we still have to find a Firewall that works or find out how to
configure Kerio so that it doesn't interfere with QTR.

Apparently the suspicious Windows Update was innocent :-)

Cheers,

Tony

Great.  Thanks for tracking this down.  At least we know now to check the 
firewall for this kind of thing.  Its amazing how many little nitpicky gotcha's
there are in all this.

Roy

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Tony Bonanno" <tbonanno-
ranger2004@m...> wrote:

> Finally found the cause of my I/O 32 error messages, at least when
> using QTR on my systems.
> 
> I always disable firewalls first when trying to troubleshoot a
> software problem.  But this time things were a little different. 
> Seems that Kerio Personal Firewall had recently released an update
> (which I had installed on two of my three machines).  I had disabled
> the firewall when troubleshooting the I/O 32 error problem. 
> Apparently, disabling the firewall wasn't enough.
> 
> I finally noticed that the machine that was not giving me errors was
> running Kerio version 4.1.3.  The two machines that were giving error
> messages had the new version 4.2 installed.
> 
> I UN-INSTALLED Kerio Personal Firewall 4.2, and WOW, everything worked
> like a charm - NO more I/O error messages when using QTR !! 
> Previously disabling the firewall didn't work.  Only UN-INSTALLING
> Kerio 4.2 did the trick.
> 
> There may be a new "default" setting in the Kerio 4.2 release that can
> be re-configured so that it doesn't cause the error messages.  I don't
> know as I haven't gotten that far yet.
> 
> If other members of this group having I/O 32 error problems are Kerio
> users, you might want to check your version number, and if 4.2,
> un-install it and see if it clears up the error problem.  Of course,
> we still have to find a Firewall that works or find out how to
> configure Kerio so that it doesn't interfere with QTR.
> 
> Apparently the suspicious Windows Update was innocent :-)
> 
> Cheers,
> 
> Tony