Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!spool.mu.edu!sdd.hp.com!decwrl!csus.edu!netcom.com!hasty From: hasty@netcom.com (Amancio Hasty Jr) Subject: Re: X386 and Diamond Stealth: not solution Message-ID: <l0lnhhf.hasty@netcom.com> Date: Fri, 04 Sep 92 01:45:55 GMT Organization: Netcom - Online Communication Services (408 241-9760 guest) References: <Bu04w2.2u3@immd4.informatik.uni-erlangen.de> <9460@emory.mathcs.emory.edu> Lines: 41 In article <9460@emory.mathcs.emory.edu> sb@next.neuro.emory.edu writes: >> >> I had just made up my mind to buy a Diamond Stealth when I heared about >all >> this trouble. Well, I am looking for cards from other vendors now. >> So maybe you should give them a list of people who are _not_ going to >buy a >> card from them, unless they change their policy. >> If you are doing so feel free to put my name on it. >> -- >> Andreas Klingler >> asklingl@informatik.uni-erlangen.de >> I'd love to help you out... Which way did you come in? > > > I was just about to buy a Diamond Stealth also, but not now that >I've heard about diamond's uncooperative attitudes. With the rate >that technology changes these days, you'd think that companies >couldn't afford these kinds of policies. It would help a lot if people would call up Diamond and express politly their opinion. For instance, I explained to a Diamond marketing person why I was taking my Stealth back - I can't write an X11R5 device driver to your card because you use a propieratory mechanism for setting the clock values on the Stealth. Also, be aware that future Diamonds svga cards not just the Stealth will not be supported by X386 due to their new novel way of setting the clock values. So call or write to Diamond, if you want to enjoy Diamond products. >From my view, Diamond's strategy poses a bad precedence. Amancio Hasty > > > > Steve Berger (sb@onripx.neuro.emory.edu)