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 : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: Yiren Huang who wrote (40099)	11/13/1997 1:43:00 AM
From: Petz	Respond to of 186894

Yiren, re:If you can access DEBUG.EXE try this on any X86 based CPU systems: 1. open a DOS window, 2. type DEBUG 3. type F 0:0 FFFF 00 DOS, and any other OS designed for the pre-286 Intel CPU does not have any protection against bad opcodes. Try your memory fill "bug" in a DOS Window under Windows 3.1 or later, though, and your DEBUG sequence won't affect other tasks. But try the F0 0F ... sequence and it will kill all tasks on an Intel Pentium. BTW, I heard they found 7 more 32 bit opcodes that will do the same thing. The only vulnerability an isolated user might have is in browsing web pages with Active-X controls embedded in them. I haven't come across one of these yet, but I see Java all over the place. The code might also start showing up in viruses which don't destroy data but just prevent you from using your computer until innoculation. Petz