On Saturday, February 19, 2011 06:13:03 pm Steve Blackmore did opine:

> On Fri, 18 Feb 2011 12:19:54 -0500, you wrote:
> >You may well be right Peter.  But dragging the VIA chips into this
> >discussion reminds me of the debacles I experienced with both the VIA
> >and CYRIX chips of yore.  Very poor quality and most of the mobo's
> >died even before the Packard Bell monitors that came with that 2
> >pallets of machines we bought for the news dept. did.
> 
> I'll add another to your list of poor quality items - Gateway PC's ;)
> 
> VIA chipsets were on the "unsupported by Mach3" for a good while. Very
> erratic clock was the perceived problem but it was actually something to
> with a bug in APIC. Give VIA their due, they did a considerable amount
> of work with Art and told him how to circumvent the problem in software.
> This was December 2007, on subsequent chipsets, AFAIK they fixed the
> problem.
> 
> Steve Blackmore
> --

You know Steve, that some of this thread should go into the wiki so new 
bee's can find it don't you?  Such info, preserved in the wiki, would go a 
long ways toward smoothing the path by hopefully warning the newbies about 
certain hardware.

Ditto for the video driver issue.  If the latencies are crap, and you are 
using even the nueveau (sp?) Nvidia driver, or the flgx ati driver, the 
first thing to do is swap to the vesa driver.  Even the old nv drivers is a 
huge hit on latency.  Its a whole new ball game when you do that. (switch 
to the vesa driver)

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
<http://tinyurl.com/ddg5bz>
Our country has plenty of good five-cent cigars, but the trouble is
they charge fifteen cents for them.

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to