Return to BSD News archive
Xref: sserve comp.sys.ibm.pc.hardware:33358 comp.unix.bsd:6491 comp.org.eff.talk:9471 Path: sserve!manuel.anu.edu.au!munnari.oz.au!constellation!mimbres.cs.unm.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!sdd.hp.com!spool.mu.edu!agate!curtis From: curtis@cs.berkeley.edu (Curtis Yarvin) Newsgroups: comp.sys.ibm.pc.hardware,comp.unix.bsd,comp.org.eff.talk Subject: Re: Question on Diamond Clock Synthesizer Date: 13 Oct 1992 18:25:41 GMT Organization: CS Dept. Snakepit - Do Not Feed. Lines: 11 Distribution: inet Message-ID: <1bf4b5INNh4n@agate.berkeley.edu> References: <1b9hudINNmv1@agate.berkeley.edu> <1992Oct12.044838.15514@fcom.cc.utah.edu> <1992Oct12.061220.17620@netcom.com> NNTP-Posting-Host: cobra.cs.berkeley.edu In article <1992Oct12.061220.17620@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes: > >Why bother with Diamond, >When you can buy an Orchid's F1280 or Artix's GraphicsEngine. Because if Diamond's clocks were truly programmable, you could use a Diamond card to drive a fixed-sync monitor, like a used Sun gray-scale. This would be a hefty boon, as there don't seem to be large mono monitors available for PCs. c