From: ralf@uni-koblenz.de
To: Richard Masoner <richardm@bif.cd.com>,
Bob Mende Pie <mende@piecomputer.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Challenge S question
Date: Sun, 8 Nov 1998 04:30:52 +0100 [thread overview]
Message-ID: <19981108043052.B1275@uni-koblenz.de> (raw)
In-Reply-To: <199811051627.KAA07758@bif.cd.com>; from Richard Masoner on Thu, Nov 05, 1998 at 10:27:22AM -0600
On Thu, Nov 05, 1998 at 10:27:22AM -0600, Richard Masoner wrote:
> And Bob answered:
>
> > It should.
>
> The two Challenge S's I've had, and the one I currently have, do
> not have keyboard and mouse ports.
>
> Refer to page 3-32 of the SGI Hardware Developer Handbook R2.0 for a
> diagram of what the Challenge S has.
Modern world, there things that exist but not officially. I was asking
because I had a Challenge S report in my private email that would only
make sense if the machine still has the keyboard controller.
Ralf
prev parent reply other threads:[~1998-11-09 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-04 12:20 Challenge S question ralf
1998-11-05 0:41 ` Bob Mende Pie
1998-11-05 16:27 ` Richard Masoner
1998-11-05 16:27 ` Richard Masoner
1998-11-08 3:30 ` ralf [this message]
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=19981108043052.B1275@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=mende@piecomputer.engr.sgi.com \
--cc=richardm@bif.cd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox