G
George Pontis
This regards printing over TCP/IP to an HP4M+ from Windows 2000 or XP. If a print
job is sent to the printer before it is turned on it gets queued by Windows. When
the printer is powered up later, instead of printing the document an error page
comes out saying:
ERROR: timeout
OFFENDING COMMAND: timeout
STACK:
{stopped {cleartomark @ lucas eq {! exit}if }loop countdictstack ~ sub @ }
/featurecleanup
I also tried printing a short text document from a Unix system. It printed
properly, as if it waited long enough before sending the job.
Seems like there is a problem, perhaps configuration mismatch, in Windows
regarding how long it waits before sending the job. This worked at one time but I
can't say when it stopped working. Perhaps after adding some printer memory ? Any
pointers on where to look to fix this ?
Geo.
job is sent to the printer before it is turned on it gets queued by Windows. When
the printer is powered up later, instead of printing the document an error page
comes out saying:
ERROR: timeout
OFFENDING COMMAND: timeout
STACK:
{stopped {cleartomark @ lucas eq {! exit}if }loop countdictstack ~ sub @ }
/featurecleanup
I also tried printing a short text document from a Unix system. It printed
properly, as if it waited long enough before sending the job.
Seems like there is a problem, perhaps configuration mismatch, in Windows
regarding how long it waits before sending the job. This worked at one time but I
can't say when it stopped working. Perhaps after adding some printer memory ? Any
pointers on where to look to fix this ?
Geo.