Path: utzoo!attcan!uunet!jarthur!nntp-server.caltech.edu!nntp-server.caltech.edu!andrey From: andrey@against.cs.caltech.edu (Andre T. Yew) Newsgroups: comp.sys.amiga Subject: Re: SCSI vs. ST506 vs. ESDI vs. Whatever else there is??? Message-ID: Date: 26 Sep 90 04:18:17 GMT References: <184@thor.UUCP> <1990Sep21.225835.20649@psuecl.bitnet> Sender: news@nntp-server.caltech.edu Organization: California Institute of Technology Lines: 26 In-Reply-To: lupe@alanya.Germany.Sun.COM's message of 25 Sep 90 20:57:58 GMT Nntp-Posting-Host: against.cs.caltech.edu >>>>> On 25 Sep 90 20:57:58 GMT, lupe@alanya.Germany.Sun.COM (Lupe Christoph - Sun Germany Consulting - Munich) said: L> I don't know what IPI stands for, maybe Intellegent Peripheral Interconnect. L> It is somewhat like SCSI, but faster. Haven't seen much of it myself yet. L> Sun is using it in the high-end machines. I've seen IPI used in some high-end Silicon Graphics machines (>$200K). Actually they were using IPI-2. I can't remember what IPI stands for, but I can say that it was extremely fast. One of the demos played back from the IPI disks had about 1 or 2 minutes digitized from "Batman". They were playing it back in a window the size of an overscanned NTSC picture at real-time (30 fps, not 60 fps, as some people around here think it is). So what, you say. Well, the entire sequence was not compressed. As in, they just stored each pixel as a 24 bit number or 3 bytes (I don't know which) and read it back and drew it on to the screen. According to SGI reps, the code is as simple as something just looping over the file and drawing each line or pixel (not clear) to the screen. L> -- L> | lchristoph@Sun.COM (Internet) | Disclaimer: | L> | ...!unido!sunmuc!lupe (German EUNet, "bang") | My employer has a | L> | lupe@sunmuc.UUCP (German EUNet, domain) | non-exclusive license | L> | ...!suninfo!lchristoph (Sun Germany customers) | to my opinion. | -- Andre Yew andrey@through.cs.caltech.edu (131.215.128.1)