Posted by Tom Fulton on September 07, 2004 at 11:31:35:
Our "Guinea Pig" end-user that is now up on our document-imaging system makes use of Local Bar-code label printers. These printers
are configured as printer L11, Windows Printer, under the users node
name entries ( not global printers ). These printers are working
great except that the users are reporting occasional "Printer Busy"
exceptions. I thought this was curious because they are local printers and the Order Entry program closes the printer LUN, opens it,
ENTERs the CFORM program for printing the bar-code, then closes the
LUN. So I put the Exception number and the printer name in my message for display. I got my first call back and the Exception is
30! I immediately had the user go into the Printers Folder and print
a test page, which came out fine. I had the user exit Comet and re-enter Comet. Going back into the order the bar-coded label then printed OK. I believe all of these printers are USB printers. Just
out of curiosity, is there any possibility that the same code that
caused the USB Dongle disconnect problems be coming into play with USB
printers??? Thanks in advance, Tom. BTW, Comet2K4 337 at the end-user.