Xref: utzoo comp.unix.sysv386:7378 comp.unix.wizards:25166 comp.unix.internals:2645 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!rbj From: rbj@uunet.UU.NET (Root Boy Jim) Newsgroups: comp.unix.sysv386,comp.unix.wizards,comp.unix.internals Subject: Re: System V, B0, and DTR. Keywords: iNTeL SVID callback etc... Message-ID: <130476@uunet.UU.NET> Date: 26 Apr 91 19:46:52 GMT References: Followup-To: comp.unix.sysv386 Organization: UUNET Communications Services, Falls Church, VA Lines: 18 peter@ficc.ferranti.com (Peter da Silva) writes: >iNTeL says that even though it's a 2-line fix they >can't do it because it's not in the SVID... even to do a workaround for >us. The iNTeL technical people are quite helpful, and seem as frustrated >as us. If they are truly as frustrated, they will do it under the table for you. Clearly, it is so obvious that SVID forgot to mention it. >Any suggestions? (no, closing and opening the port doesn't appear to be >an option in this case) What do you people think the Right Thing to do is? You mean short of walking into the next board of directors meeting with an AK-47? The right thing to do is complain about everything else they do that isn't in the SVID. They should do anything you ask if you pay them. -- [rbj@uunet 1] stty sane unknown mode: sane