Newsgroup: it.comp.hardware.motherboard
Titolo: Abit KT7A e Athlon XP

Scusate se magari chiedo qualcosa di già trito e ritrito...
Ma insomma questa Abit KT7A versione precedente alla 1.3 li supporta o no
questi Athlon XP ????
Grazie..

 ha scritto nel messaggio
news:9t6eb7$jvr$1...@serv1.albacom.net...



wrote:

ma dove che non lo trovo...?
--
bye,
Enrico A.
amad...@genie.it
P.S.
Se ti interessa leggere e vedere qualche foto
sull' Egitto la mia pagina è:
http://web.genie.it/utenti/a/amadenri/index.htm

 ma dove che non lo trovo...?
Infatti nemmeno io lo trovo!  Ma siete sicuri??

 Infatti nemmeno io lo trovo!  Ma siete sicuri??
Ragazzi, e' una BANFA. Leggetevi l'apposito aggiornamento nel sito delle FAQ
su KT7 e KT7A. Probabilmente con la maggior parte degli XP i pc si
avvieranno, al limite sara' necessario qualche reset. Per questo motivo Abit
non rilascera' MAI la notizia della piena compatibilita' con gli XP, perche'
esistono incompatibilita' hardware, se pur minime.
Ciao!
Baio

 ha scritto nel messaggio
news:9t6eb7$jvr$1...@serv1.albacom.net...

leggete qui
There has been much heated discussion about the failure of early KT7A
motherboard revisions to support the AthlonXP and Duron (Morgan core)
processors. These discussions have also been confused by incorrect
statements on the ABIT (China) website, suggesting that the 64 BIOS release
provided support for these processors. This is not true, and the issue is
more complicated. The difference between the earlier Athlon processors and
the new AthlonXP processor lies in the processor boot process. You can see
the relevant boot timing diagrams on page 35, figure 10 of the Athlon Model
4 Data Sheet (for the older Athlons) and page 43, figure 12 of the Athlon
Model 6 Data Sheet (for the Athlon XP). During the boot process, the
motherboard must sample three data lines called FID(0:3) in order to
determine the CPU multiplier setting. In the new AthlonXP processor, the
timing requirements for this sampling has changed, and these lines only
become valid 100ns after the Vcore power OK (PWROK) signal is asserted.
This means that if the motherboard does not apply an extra circuit to delay
the NB_RESET# signal after the FIDs are fully valid, the motherboard may
potentially get the wrong values from the FID lines. This is the reason why
the earlier motherboard versions cannot support the AthlonXP processor.
Getting the wrong FIDs may not always result in the system being unable to
boot up - but it may result in the motherboard using the wrong parameters to
initialise the processor, causing system instabilities under certain
circumstances. On the earlier Athlon processors the FIDs are always valid
after the Vcore of the processor is valid and this is why no motherboard has
a problem supporting the highest frequency of old Athlon.
In practice, this change is very subtle. Many AthlonXP processors will work
fine on earlier motherboard revisions. Others will work fine for some
percentage of the time, but will require a hard reset during boot if this
timing assertion is violated. However, only revision 1.3 of the motherboard
contains the necessary hardware modifications to fully support AMD's revised
timing specification. This is why ABIT cannot officially support the
AthlonXP processor on earlier motherboard revisions - although if you can
live with the occasional hard reset you may be lucky. Furthermore, ABIT have
made attempts to improve the timing compatibility with the 64 BIOS release,
but still cannot officially support the processor on these revisions.
No BIOS release will allow ABIT to properly support the AthlonXP on
motherboard versions prior to v1.3. However, in practice, the timing
difference is sufficiently subtle that many processors will work fine, and
others will simply require the occasional reset during boot. Once the
processor has booted, the stability should usually be the same on all
motherboards.
In some respects ABIT are simply being more honest than other motherboard
manufacturers. In most cases the AthlonXP will appear to work OK - or have
occasional instabilities. However, rather than pretending that a simple BIOS
update can resolve the problem, ABIT are only officially claiming that the
board with the proper additional circuitry can support these new processors.