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.

Technology Stocks : AMD:News, Press Releases and Information Only! -- Ignore unavailable to you. Want to Upgrade?

To: James Yu who wrote (2156)	11/15/1997 1:27:00 AM
From: Brian Hutcheson	Read Replies (4) \| Respond to of 6843

"Weak demand for PII forces Intel to drop prices in '98" news.com Brian

To: James Yu who wrote (2156)	11/15/1997 1:30:00 AM
From: Ali Chen	Respond to of 6843

James, <F0 Fighter is available at an introductory price of $295> It sounds to me too quick to find a solution and introduce a shrink-wrapped product in just few days after the problem was published. It takes more time just to print the colored box and a two-page manual. This info is a confirmation that the problem was known for Intel for quite some time, probably a few months since Mr.Collins contacted them, as he says. This means that Intel impudently lies in their statements about this bug. Even more, look at their attitide and what they are sayng on their web site: "No memory data is corrupted and the user can perform a system reset to return to normal operation." "As a result, the system hangs and the system must be re-booted to return to normal operation. This issue does not cause data corruption or physical damage to a user's system. Any data saved to disk in the course of work..." They treat all users as total idiots: re-boot to return to "normal operation", "does not cause data corruption"! Everyone knows that reboot erases all the memory and all user processes gets killed without a message, and it is 100% true that the file system will be corrupted and will require a disk check and recovery. Regards, Ali