Digital BW, The Print

Hi John,

Tried to boot in safe mode and start up just QTRgui, but couldn't
locate the file ??  Not sure what is going on.  Anyway, even went so
far as to reconstruct my install history and removed most of the
recent windows updates.. interesting thing happened.  I have QTR on
two workstations (networked).  Removing update #KB896423 actually
solved the I/O 32 error problem in one of the machines, but didn't do
a thing for my main workstation. Oh well, one of these days, we'll
figure it out.  I still suspect that the GIMP engine might have a
incompatibility with one of the recent Windows security updates, etc.
??  I don't believe anybody was experiencing this problem until
recently.  

Cheers,

Tony

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "John Moody"
<moodymz3@y...> wrote:
> Groping at straws here but try this if it was not suggested yet.
> Create the tiff file you want to print.  Reboot the machine and login
> without starting up any programs other than qtrGui.  Without doing
anything
> else try printing the file.
> 
> Best regards,
> John Moody
> 
> -----Original Message-----
> From: DigitalBlackandWhiteThePrint@yahoogroups.com
> [mailto:DigitalBlackandWhiteThePrint@yahoogroups.com]On Behalf Of Tony
> Bonanno
> Sent: Friday, August 12, 2005 5:29 PM
> To: DigitalBlackandWhiteThePrint@yahoogroups.com
> Subject: [Digital BW] Re: First Time USer Getting I/O 32 error trying to
> Print?
> 
> I've beat this one to death Alex... registry cleans, disable all
> background processes, re-installs, delete and re-install printers,
> etc. etc.  Spent hours on it over a couple of weeks and CANNOT find
> the source of what is causing it, and can't get rid of it.  I'm on
> Windows XP.
> 
> Stephen and others have made suggestions, but nothing seems to work.
> I only get the error when using QTR, both with Epson 4000 and R800
> printers.
> 
> I'm beginning to suspect that one of the Windows security patches that
> were downloaded and installed over the past couple of months might be
> responsible.  Of course, we will probably never know.  It really is
> annoying :-(  !!
> 
> Tony
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]