From: dmanddmer <dmerchan@hiwaay.net>
To: linux@cthulhu.engr.sgi.com
Subject: [Fwd: linus.linux.sgi.com]
Date: Tue, 19 Jan 1999 17:28:23 -0600 [thread overview]
Message-ID: <36A51517.A24C2BEB@hiwaay.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Btw, I heard a rumor that the memory in the VPC is custom or unique
memory. Is this true? How much of the VPC, besides the obvious, is not
industry standard? If SGI is attempting solely to require customers to
be able to buy any upgrades ONLY from SGI, then SGI has shot itself in
the foot again. It did not work for Apple, it didn't work for Unisys,
it didn't work for Intergraph. In short, it hasn't worked for anyone.
David M.
[-- Attachment #2: Type: message/rfc822, Size: 3250 bytes --]
From: david@carrera.columbus.sgi.com (David Watters)
To: dmanddmer <dmerchan@hiwaay.net>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: linus.linux.sgi.com
Date: Tue, 19 Jan 1999 10:30:47 -0500 (EST)
Message-ID: <9901191030.ZM37783@carrera.columbus.sgi.com>
On Jan 19, 5:21am, dmanddmer wrote:
> Subject: Re: linus.linux.sgi.com
> Personally, since SGI made the questionable decision to port to NT, I
> wish they would commit to AMD's processors instead of Intels.
SGI couldn't. SGI had to replace so much of the IA/440xx chipset that there
had to be a prettty big agreement with Intel covering a lot of issues,
machines, processors, and markets to allow SGI to, for example, implement
the frontside bus in their own chipset. Don't forget all those Co'op
marketing dollars too. -dong ^dong -dong ^^dong
> Porting to NT alone is probably not enough to save the company. It
> didn't work for Intergraph.
Yeah, but Intergraph is lame so they had that working against them too. :)
--
David Watters | Silicon*Graphics
Systems Engineer | http://www.sgi.com/
Silicon Graphics, Inc.| http://reality.sgi.com/davester/ (6/13/97)
david.watters@sgi.com | 1.800.800.SGI1 (Sales) 1.800.800.4SGI (Support)
DID 1.614.844.3820 | http://www.nintendo.com/ (N64, the $130 SGI!)
WARNING: multiple messages have this Message-ID (diff)
From: dmanddmer <dmerchan@hiwaay.net>
To: linux@cthulhu.engr.sgi.com
Subject: [Fwd: linus.linux.sgi.com]
Date: Tue, 19 Jan 1999 17:28:23 -0600 [thread overview]
Message-ID: <36A51517.A24C2BEB@hiwaay.net> (raw)
Message-ID: <19990119232823.2lcHQVV3jtXRqfFEs1Qj_TzmtgnHqtP2ZEaGnxMMkLg@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Btw, I heard a rumor that the memory in the VPC is custom or unique
memory. Is this true? How much of the VPC, besides the obvious, is not
industry standard? If SGI is attempting solely to require customers to
be able to buy any upgrades ONLY from SGI, then SGI has shot itself in
the foot again. It did not work for Apple, it didn't work for Unisys,
it didn't work for Intergraph. In short, it hasn't worked for anyone.
David M.
[-- Attachment #2: Type: message/rfc822, Size: 3242 bytes --]
From: david@carrera.columbus.sgi.com (David Watters)
To: dmanddmer <dmerchan@hiwaay.net>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: linus.linux.sgi.com
Date: Tue, 19 Jan 1999 10:30:47 -0500 (EST)
Message-ID: <9901191030.ZM37783@carrera.columbus.sgi.com>
On Jan 19, 5:21am, dmanddmer wrote:
> Subject: Re: linus.linux.sgi.com
> Personally, since SGI made the questionable decision to port to NT, I
> wish they would commit to AMD's processors instead of Intels.
SGI couldn't. SGI had to replace so much of the IA/440xx chipset that there
had to be a prettty big agreement with Intel covering a lot of issues,
machines, processors, and markets to allow SGI to, for example, implement
the frontside bus in their own chipset. Don't forget all those Co'op
marketing dollars too. -dong ^dong -dong ^^dong
> Porting to NT alone is probably not enough to save the company. It
> didn't work for Intergraph.
Yeah, but Intergraph is lame so they had that working against them too. :)
--
David Watters | Silicon*Graphics
Systems Engineer | http://www.sgi.com/
Silicon Graphics, Inc.| http://reality.sgi.com/davester/ (6/13/97)
david.watters@sgi.com | 1.800.800.SGI1 (Sales) 1.800.800.4SGI (Support)
DID 1.614.844.3820 | http://www.nintendo.com/ (N64, the $130 SGI!)
next reply other threads:[~1999-01-19 23:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-19 23:28 dmanddmer [this message]
1999-01-19 23:28 ` [Fwd: linus.linux.sgi.com] dmanddmer
1999-01-20 1:29 ` Chad Carlin
1999-01-20 1:29 ` Chad Carlin
1999-01-20 2:04 ` job bogan
[not found] ` <job@piquin.uchicago.edu>
1999-01-20 2:28 ` Richard Offer
1999-01-20 2:36 ` Ken Klingman
1999-01-20 2:36 ` Ken Klingman
1999-01-20 21:18 ` David Watters
1999-01-20 21:18 ` David Watters
1999-01-20 3:01 ` job bogan
1999-01-20 3:01 ` job bogan
1999-01-20 21:29 ` David Watters
1999-01-20 21:29 ` David Watters
1999-01-20 3:08 ` Greg Chesson
1999-01-20 3:08 ` Greg Chesson
1999-01-20 3:32 ` Chad Carlin
1999-01-20 16:02 ` Eric Kimminau
1999-01-20 15:18 ` Eric Kimminau
1999-01-20 21:55 ` David Watters
1999-01-21 7:11 ` David S. Miller
1999-01-22 19:14 ` Jeffrey Watts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36A51517.A24C2BEB@hiwaay.net \
--to=dmerchan@hiwaay.net \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.