Path: utzoo!attcan!uunet!peregrine!elroy!ames!ncar!tank!uxc!uxc.cso.uiuc.edu!m.cs.uiuc.edu!s.cs.uiuc.edu!carroll
From: carroll@s.cs.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: MKS BUGS
Message-ID: <213400014@s.cs.uiuc.edu>
Date: 27 Nov 88 17:10:00 GMT
References: <1361@anuck.UUCP>
Lines: 13
Nf-ID: #R:anuck.UUCP:1361:s.cs.uiuc.edu:213400014:000:686
Nf-From: s.cs.uiuc.edu!carroll    Nov 27 11:10:00 1988


/* Written  6:50 pm  Nov 25, 1988 by rac@jc3b21.UUCP in s.cs.uiuc.edu:comp.sys.ibm.pc */
[bug report], and when I sent Gerry mail about it,
he was more than cooperative. 
Roger Cornelius        uunet!pdn!jc3b21!sherpa!rac
/* End of text from s.cs.uiuc.edu:comp.sys.ibm.pc */

This is the key here, as tneff mentioned. Send bug reports to MKS. No
software is perfect, and even though I've raved to people about MKS, I'll
stand up and say 'Yes, there are bugs'. What did you expect? What makes it
acceptable is that 1. There aren't all that many, and they tend to be
minor, and 2. MKS has been very cooperative (to me) about bug reports.
So, when you find things like this, send them in.