Date: Mon, 25 Feb 2002 09:54:33 -0800 (PST)
From: Patrick Powell <[EMAIL PROTECTED]>
> > From [EMAIL PROTECTED] Fri Feb 22 21:47:46 2002
> > To: Patrick Powell <[EMAIL PROTECTED]>
> > Subject: Re: LPRng: HP-4100 Pagecount problem. A possible solution.
> > Date: Sat, 23 Feb 2002 16:01:13 +1100
> > From: "C. L. McAvaney" <[EMAIL PROTECTED]>
> >
>
>
> > So does that mean that the ECHO doesn't synchronise as it is documented
> > that is should do?
> >
>
> From the PJL Reference:
>
> Page 7-2
> To clear any possible unread status responses requested by the
> previous application, upon startup, an application should use
> the ECHO command...
>
> Page 7-14
> ... Since the status messages are buffered in the printer until they
> are received, the current application may receive status messages
> that were requested by a previous applciation. (This happends in
> situations where the application requests information or unsolicited
> status is enabled, and the application closes before receiving the
> status messages).
>
> Basically, what you get with this is a 'marker' in the output
> stream. It does not provide any indication that the previous
> job has completed. In fact, my observation is that if you:
>
> a) connect using TCP/IP
> b) send job
> c) disconnect
> d) send new job
> (with echo)
>
> Then:
> a) some printers refuse connection while previous job is in progress
> b) some printers accept new connection, but will not accept data
> (sigh...) while previous job is in progress
> c) some printers will accept 'no output jobs' and fake their acceptance
> d) some printers will do c), and only when there is a job with output
> will they then block all additional IO until the previous job is
> finished.
> e) some printers will do d), but also have the interesting behavior
> of reporting errors (out of paper, jam, etc) FOR THE PREVIOUS JOB
> that is in progress.
>
> Printers that do c) and d) are almost impossible to get accurate
> page counts from, as the 'initial' pagecount value is bogus.
>
> Also, I have seen a,b,c, and d on the same printer... Depending on the
> rev level of the network interface code.
>
AAAAaahhhhhh that clears things up then.
I understand more and more why you <sarcastic mode>love</sarcastic mode>
printers so much!! Oh for a standard that every follows!! ;)
Cheers,
Christopher
,,,
(. .)
/-----.oOO--(_)--OOo.-------------------------------------------------\
| Christopher McAvaney [EMAIL PROTECTED] |
| PhD Candidate [EMAIL PROTECTED] |
| [EMAIL PROTECTED] |
| phone: +61+3+52272960 [EMAIL PROTECTED] |
| fax: +61+3+52272028 http://www.cm.deakin.edu.au/~chrismc |
\---------------------------------------------------------------------/
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
