> Yeah, but that Cyrix chip runs so much faster, you don't
>even notice the extra laps... :)
> Seriously, I don't want to flame the Cyrix guys, it's a
>sad situation how Cyrix has come close, but not close enough
>for many of us. I am upgrading my PC and was very seriously
>considering the C166+ this past month. However, the reports
>on Usenet, particularly the (continuing) incompatabilities
>with ICR2-3D have made my decision for me. I'll spend a few
>bucks more for a lowly P133, instead of a C166+. :( I want
>to thank guys like Chris for making these problems known. I
>might be spending more $ and getting less HP with the Pentium,
>but I'd be unhappy with the Cyrix incompatabilities, and its
>better to know that up front.
>Pick one or more: Model Rockets (competition-NERCB) / PCs (even Atari!) /
>Papyrus ICR-ICR2-NCR / Who needs a life when you have multiple non-lives?
Your welcome. FYI, I've had my Cyrix P166+ for 4 months now. I should
be recieving my Intel Pentium 166 this week. In four months I have
run into 4 programs that wouldn't run on my Cyrix. Granted there have
eventually been patches released to address the Cyrix problems but I
am growing tired of having to wait for patches to run the programs!
ICR2 is a prime example. I bought the Intergraph Reactor to play my
favorite sim with the 3D enhancements. Imagine my chagrin when I got
it and found out that yet again I had a program that wouldn't run on a
Cyrix. So now there is a fix for it...sort of. If you only want to
run laps it's fine, except you can only run INDYSAFE.BAT which
apparently yields about half the frame rate of INDYFAST.BAT. If you
want to run a race, well, get comfortable, it'll take you a while to
run 6 million laps (3 million if you import the NASCAR tracks) I'm
sure there will be a patch to correct this properly...eventually, I
just hope I get my Intel before the patch comes out :-)