Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 -- Ignore unavailable to you. Want to Upgrade?

To: dougSF30 who wrote (118953)	7/3/2000 3:08:55 PM
From: jim kelley	Read Replies (8) \| Respond to of 1578041

Sure but these problems take time. The user does not care why the system does not work. He will blame GTW first but may switch to an Intel machine if he does not feel comfortable with the fix.

To: dougSF30 who wrote (118953)	7/3/2000 6:35:51 PM
From: Tony Viola	Read Replies (4) \| Respond to of 1578041

Doug, >Besides, I say again, how hard is this: (1) Receive flaky Gateway 1 GHz system (2) Remove 1 GHz tbird (3) Put tbird in different motherboards and systems (4) Verify no problems (5) Conclude tbird is not the problem It's not always that simple. If the T-Bird works on other mobos, it could be that those boards are more forgiving in the timing of some tight path, or paths, between the board circuitry and the microprocessor, than the board that Gateway is using. Said another way, the Gateway board could be within spec., but not give as much leeway, again in a tight path. Of course, it could be the other way around, and the Gateway board is hogging too much of the handshaking time. In any event, I would feel uneasy, whether I were Gateway or AMD, until the whole thing is fixed, which I'm sure it will be. Tony