SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Politics : Formerly About Advanced Micro Devices

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Ali Chen who wrote (43342)12/14/1998 1:39:00 PM
From: Paul Engel  Read Replies (1) of 1572629
 
Ail - Re: "Intel could have same timing problem as AMD"

You selectively edited out the last part of that article which explains that this IS NOT THE AMD PROBLEM - but a simple set-up problem with newer chip sets unrecognized by the older Windows 95.

Here is the part you left out, "Ail brain":

theregister.co.uk

" But a senior architect, who declined to be named, said the patches were unrelated.

He said: "Not that it's not entirely possible that the same timing loop problem in Win95 affects Intel (and maybe Cyrix too) CPUs ...but the PIIX4 patch that I've seen fixes a different problem, one having to do with chipset IDE ports.

"Briefly, Win32 uses keyed info in INF files as tokenized how-to info on accessing system resources. The Intel 430 HX and TX chipsets, with the PIIX3 and PIIX4 chips before, were released after Win95, so the OS doesn't recognize the chips with their secret signatures, assumes that there's default hardware on its motherboard, and
misbehaves.

"The patch consists largely of updated INF files describing the newer chipset hardware. Abit has also provided this info for their customers, and Intel still has the update on their website."

{=============================}
Paul
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext