• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Epox 8KTA+ Fast processor

Yes, the 8KTA+ will take a XP. So the XP 1900+ is the best you can get for it.

Really? Can you go into details?

It won't according to EPOX (I have one of these boards, so I have an interest in this). See EPOX support for 8KTA+. The PDF file for recommended CPU's stops at 1200Mhz Athlons (for rev 1.2), and 1100 Mhz for lower revs.

The CPU Ratio switches only go up to 12.5X, too.



 
I read the PDF also. However, I was hoping the October 2001 BIOS upgrade helped with the XP. I was thinking might have to unlock the 266fsb XP or Tbird to increase the multiplier for operating at 200mhz fsb to get rated speed or even OC; i.e. 12.5x with the XP. I read that this board, with KT133, does not like over 110mhz fsb; i.e. 133mhz fsb. I was also hoping, as an another alternative, the locked 1.4ghz Tbird @ 200mhz fsb would work even though the dip switch mulitpliers only go to 12.5x. I read somewhere that the locked 1.3ghz actually runs at 12.5x but with an automatically increased fsb to 104mhz. To run 1.4ghz with 12.5x multiplier would take 112mhz fsb. Why do this? I am looking at replacing a Duron 600@950 with the 1.4ghz Tbird or XP until I get a better board. Any experience or info would be appreciated.
 


<< Yes, the 8KTA+ will take a XP. So the XP 1900+ is the best you can get for it.

Really? Can you go into details?

It won't according to EPOX (I have one of these boards, so I have an interest in this). See EPOX support for 8KTA+. The PDF file for recommended CPU's stops at 1200Mhz Athlons (for rev 1.2), and 1100 Mhz for lower revs.

The CPU Ratio switches only go up to 12.5X, too. >>


The new bios file would have probably fixed tht.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top