Digital BW, The Print

Hi Roy,

I've been working on it a bit more this morning.  I'm still baffled as
uninstalling KB896423 update on one machine definitely seems to have
solved the problem, but not on the other machine ??? 

Machine #1.  This particular machine is, unfortunately, my backup and
"business records" computer, not my main image processor machine. 
Anyway, the Epson 4000 is accessed by this machine through a local
network.  After installing the above update, I would consistently get
an I/O 32 error almost immediately and the printer would not print the
image. QTR was not usable at all.  After uninstalling KB896423 update,
I have not had any further problem.  I've printed several images, etc.
and everything is just fine.

Machine #2.  My image processing computer, a newer fairly state of the
art P4 with all the goodies.  Beginning a few weeks ago, I'd print
using QTRgui and after the file apparently loaded (spooled, etc.), I
would get the I/O 32 error message, BUT the file DID print fine.  The
error message was just annoying.  It did this EVERY time I tried to
print.  No matter what the settings.  After deleting the windows
KB896423 update, things changed somewhat.  Frequently, the first print
with QTR would be fine with NO error message.  Unfortunately, almost
every subsequent print though would display the same annoying error
message after the file was processed and the printing began. 
Basically, exactly the same behavior as before deleting the update,
except that the "first" print would often go through without the error
message.

I did an inventory of updates on both computers to see if there was
still an update on machine #2 that wasn't on #1, that might possibly
still be causing a problem, but currently it appears that both
machines have exactly the same update configuration.  

OH, I almost forgot, I went in and tried every combination of
spooler setting, sharing settings, etc. that I could think of.  Didn't
seem to help.  Also, I have tried re-installing earlier versions of
QTR and the problem still occurred.  I should also mention, that this
problem NEVER occurred until a few weeks ago.  At the time, I was
still using 2.2.4, and later updated to 2.3.  I don't think it has
anything to do with the version.  It seems to have "suddenly"
developed quietly.  Apparently, whatever is causing it has affected
several other users too.  The windows update scenario sure seems
suspicious, especially since it seems to have been the solution on one
of my machines.

Back to the salt mine :-)

Tony




--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Roy Harrington"
<roy@h...> wrote:
> 
> Hi Tony,
> 
> This is an interesting discovery.  I'm not much of a Windows expert
> but I looked up that update# and lo and behold this is a security
fix
> for the Printer Spooler Service -- something about buffer overflow
possibility,
> shared printers and anonymous connections to the spooler.
> 
> QTR does write to the print spooler so this is highly suspicious. 
You might
> check things like Sharing and Spooler setup parameters.  Do you
always get
> this error?  Does it print anyway?  I know you've already spent more
time
> than you want on this.  I'd like to see if I can duplicate this.
>