Hi, Cari. I have a related problem with a Lexmark Optra Rt+ Laser.
This is a high-end corporate-workcentre-style monochrome laser
printer with extra features such as an envelope feeder, second paper
tray, extra memory, etc.
Lexmark supply a Printer Utility software package called MarkVision 5
which communicates with the printer and allows the user to be notified
of paper jams, low toner, printer out of paper, fuser errors, cover open
and more.
This piece of software uses the bidi-communications capabilities of
the parallel LPT port to communicate printer-status between the
printer and its drivers. (This also runs through a network as well,
but in this particular case I'm running the printer standalone connected
to a single workstation through the parallel port.)
Now here's the rub:
1. If I run the MS printer drivers for this printer, there is no bidi status
update. IOW, I don't see the true memory-amount installed in the
printer, nor the state of things like the presence/absence of the
second paper tray.
2. If I run the Lexmark printer drivers for this printer along with the
bidi-communications module from Lexmark -- all works fine with
the printer drivers both in PCL5 and in Postscript2 modes.
3. However, If I run Markvision in the startup group to autostart the
printer status utility at XP startup, Markvision *cannot* find the
printer.
4. Then, with Markvision running, if I open *either* of the Lexmark
printer driver spool windows, I hear the printer start up and
deliver its status-report back to the printer drivers -- which also
then allows Markvision to detect the printer and deliver the status
updates to/from Markvision as well.
So, my problem is that the Lexmark Printer Drivers are happily
starting up Lexbce (The Lexmark bidirectional communications
engine) -- but Markvision does not, even though it is *supposed*
to...
The Markvision software and the Lexmark printer drivers *both*
work just fine under W9x -- and Markvision does what it is supposed
to under W9x. It's just that Markvision doesn't like talking to Lexbce
under XP for some reason.
I have checked the Registry entries for both Markvision and
Lexbce. I have also checked the Lexbce32 service and it is
properly set to automatic on startup -- and is running even though
Markvision is not communicating properly.
I have checked the Lexbce service dependencies and they are
set to need RPCSS and spooler. What I need is some way to
tell Markvision that it needs to "trip" Lexbce32 in the same way
the printer drivers "trip" Lexbce32 when the spooler starts up.
I have submitted the above info to Lexmark, and they've sent me
back one of their "canned" responses (aimed squarely at the
level of a retarded aardvark) telling me to check the printer cable.
Duh. Yeah, I've already done that. I even rechecked it twice
before I contacted Lexmark in the first place.
So anyway, If you could run this past one of the people at PSS
and see what they say, I'd appreciate it. I suspect this is a
compatibility issue. Lexmark seem to be extremely lazy about
supporting this older product line (either software or hardware)
even though the product is clearly capable of working properly
with the appropriate housekeeping-modifications under W2K/WXP.
Thanks for any help or info you can provide.
Bill
