Newsgroups: comp.os.minix
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!flatlin!ptavv!ralf
From: ralf@ptavv.ka.sub.org (Ralf Wenk)
Subject: Re: Minix ST 1.5 printer driver problems
Message-ID: <1991Apr23.205255.00931@ptavv.ka.sub.org>
Date: Tue, 23 Apr 1991 20:52:55 GMT
References: <meulenbr.672319161@cstw168>
Lines: 27

In article <meulenbr.672319161@cstw168>
meulenbr@cst.prl.philips.nl (Frans Meulenbroeks) writes:
> I've seen reports about bad printer problems before. 
> Since I don't have a parallel printer, I cannot test these.
> However someone reported that this is due to the fact that the
> winchester task uses op to much stack.
> Try to change the definition of WINCH_STACK to
> #define WINCH_STACK     (3*SMALL_STACK/2)
> 
> Please let me know if that helps.

If the winchester task uses up to much stack the system will crash
immediately when trying to print anything. But this bug was introduced
with patch 2 and fixed with patch 3.

I saw the problem mentioned in the original artikle too. I got a lot
of garbage and "printer still busy" messages when trying to print
graphic data on a 24 needle printer. After changing back to my old
9 needle printer I did not got any still-busy message and less often
the data was corrupted. When bypassing the printer driver and using
cat data >/dev/lp instead I got no data error any more. I can not
explain it, but it seems to have nothing to do with the stack of the
winchester task.

-- 
-- 
Ralf Wenk -- ralf@ptavv.ka.sub.org
