SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 2 Jan 2002 13:22:19 PST7
From:	"J. R. Fox" <jr_fox@pacbell.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Minor annoyance with Xerox C-20

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Hi Sheridan --

I was going to take this up with Tony, but since you mentioned
that you have a Xerox
C-20 connected in your setup, I thought I'd try you. I like this
printer a lot, and it is a big
improvement over the LexMark Optra 40 it recently replaced. (For
those who may not know,
the C-20, internally, happens to be an Optra 45, big brother to
the aforementioned LexMark.)
The photo repro isn't going to challenge the Epsons, but
otherwise it is very good, quieter and
faster than the inkjet models I've previously tried. I
transferred the max. printer memory I
had added to the Optra 40, and continued using the drivers that
had been installed for that
printer: the PS driver (noticeably slower), and a PCL driver
LexMark Tech. Support had
put me onto a while back. These seem to be working fine. I did
not bother with the PS
driver on the Xerox cd. It looks rather generic, and was a
couple years older than the others.
I also did not bother with the cartridge control utility from the
LexMark, as the front panel
controls on the Xerox -- which are rather well done, a la the
older HP lasers -- make this
unnecessary.

There is one minor annoyance, though. At the end of most print
jobs, after the last page
has emerged, the printer remains in a "Busy" state, per the front
panel. I have to manually
"cancel" the job, even though it has completed, in order to
return the printer to the "Ready"
state. I'd say the Optra never did this, but since it had no
front panel, there's no way to know.
It does not matter if the print job was initiated by an OS/2, a
DOS, or a Win-OS/2 app.
I suppose this could be a driver issue, but isn't a CTRL-E
(printer Reset) a pretty standard
function at the conclusion of a print job, for *any* printer ?

If you ran into this issue, and corrected it, I would definitely
like to know what you did.

Jordan

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 02 | January | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.