Return to BSD News archive
Xref: sserve comp.sys.ibm.pc.hardware:34597 comp.unix.bsd:7204 Newsgroups: comp.sys.ibm.pc.hardware,comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!darwin.sura.net!udel!rochester!rit!isc-newsserver!ritvax.isc.rit.edu!AJB8886 From: ajb8886@ritvax.isc.rit.edu Subject: Re: Question on Diamond Clock Synthesizer Message-ID: <1992Oct28.163555.7250@ultb.isc.rit.edu> Sender: news@ultb.isc.rit.edu (USENET News System) Nntp-Posting-Host: vaxa.isc.rit.edu Reply-To: ajb8886@ritvax.isc.rit.edu Organization: Rochester Institute of Technology References: <1992Oct24.181837.19994@Informatik.TU-Muenchen.DE> <1992Oct25.034615.5298@netcom.com> <1992Oct25.101257.13662@Informatik.TU-Muenchen.DE> <1992Oct25.222947.6164@netcom.com>,<1992Oct26.105440.21826@Informatik.TU-Muenchen.DE> Date: Wed, 28 Oct 1992 16:35:55 GMT Lines: 26 I've been reading all the arguments/complaints about Diamond keeping their dot clock programming secret. The arguments against were quite convincing, and I suspect that if a copy of this entire thread was submitted to Diamond they might begin to get a real picture of what a large user base they're abandoning and alienating by keeping this "valuable trade secret" proprietary. There will be business people in charge, and I suspect that once they determine that the advantages of releasing the dot-clock programming information outweighs the theoretical advantage keeping such information out of the hands of competitors. Indeed, it would appear from reading this thread that this policy is counterproductive, ie. sending would-be consumers to the competitors in droves. Just an obvious thought that I'm sure has already crossed everyone's mind. Since I'm not using X-free, etc and my Diamond 24X is meeting my current Windows needs nicely, I'm not going to be the one with the motivation to send this whole thread to Diamond. But just as obviously, someone should. ;D Alex