Dean Roddey
Dean_Roddey@FIDO.qmi.mei.com
The P6's optimizations for 32-bit code are not a disadvantage. But the chip's poor performance when running 16-bit code will be a distinct disadvantage to anyone using Windows 95, Windows 3.1, DOS, or 16-bit application software. There's nothing wrong with tuning a next-generation processor for 32-bit code, but Intel could have achieved good 16-bit performance as well, and without major sacrifices. -- Tom R. Halfhill, senior editor
I am in no way distressed that Intel's P6 chip shows weakness when running 16-bit code. Intel should abandon unn
ecessary functionality and produce chips with less than 100 percent compatibility with its earlier chips. The result would be an ideal chip for workstations running Windows NT or Unix and the basis for the next generation of Intel chips -- a pure 32-bit, flat-model CPU, with binary compatibility for all Win32 and OS/2 applications.
Phil Jollans
Wolfratshausen, Germany
100275.2756@compuserve.com
While your suggestion would reduce the complexity of the P6 (Pentium Pro) and probably increase its performance, another result would be howls of protest from x86 users. Intel's best argument in favor of the x86 is its backward compatibility with existing software. If you take that away, there would be no reason to buy an x86 chip instead of a RISC chip. It will be interesting to see if Intel can maintain full x86 compatibility in the new processor it is designing with Hewlett-Packard. -- Tom R. Halfhill, senior editor