🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.ibm.pc.games.action
Article #6630

Re: Intel names P6 "Pentium Pro", not "Pentium2"

#6630
From: dav... Dave Glue
Date: Thu, 21 Sep 1995 00:00
28 lines
1683 bytes
nobody <nob...@csufresno.edu> wrote:


>  This is not a good news for PC gamers, since P6 will not improve the 
>excution speed of DOS and Windows95 games over similarly clocked P5.   

This is not news- it has been discussed here over a month ago and been
known several months before that.

First off, the P6's price is out of reach for most gamers- you won't
even seen them in quantity until mid 96.  Secondly, most DOS games are
32-bit, DOS is just used as a loader.  And the P6 does help in 95,
just not as much as NT- it depends on the application.  We won't have
accurate benchmarks until we see modern 32-bit apps on 95 with the P6-
the first ones still have a lot of 16-bit code.

As well, competitors NexGen, AMD and Cyrix have their
faster-than-Pentium clones coming, and apparently don't have the
problems with 32-bit code that the P6 does.

All of this is moot, as the P6 is hardly relevant for gamers.  The
Pentium is by far fast enough for most games, the problem is the lack
of supporting hardware-3D and 2D processors.  And that is changing,
which we have also been discussing in this forum with 3D cards from
Diamond and Creative Labs, and 95's support of these.  PC gaming news
is getting better, the P6 is irrelevant.

 
Technical Details
Message-ID: <43qf8l$8j6@steel.interlog.com>
Path: mbox-mo1.pugleaf.net!unknown!not-for-mail
References: <1995Sep20.172827.2783@titan.sfasu.edu>

Show Full Headers
Complete Article Headers
From: dav...@interlog.com (Dave Glue)
Subject: Re: Intel names P6 "Pentium Pro", not "Pentium2"
Date: 1995/09/21
Message-ID: <43qf8l$8j6@steel.interlog.com>
X-Deja-AN: 110446395
references: <1995Sep20.172827.2783@titan.sfasu.edu>
organization: InterLog Internet Services
newsgroups: comp.sys.ibm.pc.games.action
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit