Path: utzoo!utgpu!watmath!clyde!att!rutgers!deimos!uxc!tank!mimsy!haven!decuac!felix!info-ultrix From: cetron@wasatch.UUCP (Edward J Cetron) Newsgroups: comp.unix.ultrix Subject: Re: Ultrix killed by a resetting X server (Help wanted) Message-ID: <73125@felix.UUCP> Date: 3 Dec 88 16:00:05 GMT References: <68510@felix.UUCP> <71189@felix.UUCP> Sender: info-ultrix@felix.UUCP Reply-To: cetron@wasatch.UUCP (Edward J Cetron) Organization: Morrison-Knudsen, Industrial Buildings Division, SLC, UT Lines: 18 Approved: zemon@felix.UUCP Reply-Path: Reply-to: cetron@wasatch.UUCP (Edward J Cetron) In article <71189@felix.UUCP> yba@sabre.bellcore.com (Mark Levine) writes: >Reply-to: yba@sabre.bellcore.com (Mark Levine) >I despair of getting email to your domain -- when another writer in >comp.windows.x complained of this problem and I echoed same, we both >received a mailed copy of a new Qdss driver from someone at DEC that >fixes the problem. I have a copy, but am not sure how to help you -- >contacting DEC is probably best. I trust the repaired driver will be >included with Ultrix 3.0. Actually, the X11R2 driver is fine WHEN ALL PATCHES ARE APPLIED. What IS needed from DEC is the new qd.c/qd.o which is messed up.. also I remember someone saying something about changing DMA_bufsize to 10 from 3 * 1024. It should be 10* 1024... -ed (who used to have the same problem) cetron@wasatch.utah.edu