Hello,
> > I'm pretty sure that several people still use Win16 drivers,
> > as PSDRV support is still a bit weak (I never got it to run so far,
> > but didn't try too hard either).
>Given that the bug has been here for months and you are the first to
>notice, Win16 drivers do not seem to be a very demanded feature.
I'm not quite certain if my bug I reported on the newsgroup is
related, but since
it involves using a native 16-bit Lexmark printer driver, it's quite
likely.
I've attached it below - also, the referenced log might be quite
interesting:
--(quote)--
err:win32:_EnterSysLevel (0x40118974, level 1): Holding 0x40822ac0,
level 3. Expect deadlock!
CallTo16(func=03df:0faa,ds=00af,0x009f,0x046c,0x0001,0x009f,0x04e8,0x009f,0x0514,0x0000,0x0000)
ss:sp=00af:ffd0
err:win32:SYSLEVEL_CheckNotLevel (2): Holding lock of level 3!
----
Does it look like it's related?
Thanks a lot,
Yours Malte #8-)
---cut!---
Hi,
Printing with notepad and the Lexmark printer driver doesn't (yet?)
work,
and although I got a colorful test page out of my printer (so actual
printing
works with the right Ports open and under root, albeit slowly) the
spooling/rastering
does not yet function.
As Victor Schneider found out in a thread here which is now long
gone (deja),
the Lexmark printer driver works by either printing directly or by
converting PCL3 (hpdjet500)-files to files ready to feed to the
Lexmark;
the program that does this is the lx1000db.exe. I have not much luck
with that
one, it starts and does nothing until I terminate, whether I give a
filename
on the commandline or pipe the file into it. Normally ("real" Win),
this works by
piping binary copying or piping the file to LPT1 under a Win DOS
box.
Having come not much farther, I tried printing with notepad.exe; a
simple
application but it should use all important things wrt the printer
driver
(since it doesn't really output text but rasterized fonts AFAIK).
However, this one crashes after having done quite a lot with the
printer driver -
or maybe it's stuck in a loop before crashing, I dunno.
Since especially the (interesting) relay log is quite large, I've
put it up
on my webpage in case you'd like to help or have a look at the
problem:
http://wwwrzstud.rz.uni-karlsruhe.de/~uhwe/lrelay.txt.gz
for the full log and without the .gz for the normal (+winspool) log.
If you feel like it, you can also download the Lexmark 1000 Color
series
driver from www.lexmark.com/drivers and play with it; for
installation and
for everything but the printing you don't need the actual hardware!
The command line I used to invoke notepad was:
wine --debugmsg +winspool,+relay --dll commdlg,comdlg32=n
notepad.exe
since some commdlg functions in builtin are yet missing.
If you could have a look at this crash, it would be superb! ;-)
(I'm certain being able to print with the older paperweight models
from Lexmark would make quite a few people happy... and the glory is
yours for the taking :-))
If you've had enough of Lexmark printer driver woes, just tell me
and I'll shut up ;-)
CU, Yours Malte #8-)
