15-Jul-86 23:38:41-PDT,782;000000000001 Mail-From: SCHMIDT created at 15-Jul-86 23:38:41 Date: Tue 15 Jul 86 23:38:41-PDT From: Christopher Schmidt Subject: Iris DL? To: WorkS@Rutgers.ARPA Message-ID: <12223060865.12.SCHMIDT@SUMEX-AIM.ARPA> Is there a mailing list for users of Silicon Graphics Iris workstations? If not, would others be interested in forming one? We have the feeling that we're learning a lot of things the hard way that would be "common knowledge" if a discussion list existed. For starters: 1.) Has anyone ported EMACS? 2.) How do you compile a program to be downloaded from an "Iris Workstation" to an "Iris Terminal"? We have one "Workstation" and one "Terminal." Please answer directly, as I don't read WorkS regularly. --Christopher ------- 10-Jul-86 17:06:14-PDT,781;000000000011 Return-Path: Received: from IUS2.CS.CMU.EDU by SUMEX-AIM.ARPA with TCP; Thu 10 Jul 86 17:06:06-PDT Date: Thu, 10 Jul 1986 20:03-EDT From: Ralph.Hyre@ius2.cs.cmu.edu To: SCHMIDT@SUMEX-AIM.ARPA Subject: Re: SGI Iris DL? Message-ID: <521424204/Ralph.Hyre@ius2.cs.cmu.edu> In-Reply-To: <12220944026.16.SCHMIDT@SUMEX-AIM.ARPA> SGI is trying to get one started, they called me 2 months ago, but I didn't want to deal with paperwork, etc. Bring it up pulicly at SIGGRAPH? -- - Ralph W. Hyre, Jr. Internet: ralphw@c.cs.cmu.edu [most reliable] Phone: (412) 268-2847 [CMU-BUGS] Amateur Radio: KA3PLY (c/o W3VC, CMU Radio Club) [packet mailbox coming soon!] Fido: Ralph Hyre at Pitt-Net [may change soon, when I put up a BBS of my own!] 11-Jul-86 09:57:50-PDT,804;000000000001 Return-Path: Received: from hydra.ARPA ([128.102.64.2].#Internet) by SUMEX-AIM.ARPA with TCP; Fri 11 Jul 86 09:57:47-PDT Date: Fri, 11 Jul 86 09:12:33 pdt From: Jim Houston Message-Id: <8607111612.AA00561@hydra.ARPA> Received: by hydra.ARPA (4.12/4.01) Fri, 11 Jul 86 09:12:33 pdt To: SCHMIDT@SUMEX-AIM.ARPA Subject: RE: SGI Iris Cc: jim@RIACS.ARPA I'm not aware of a particular mailing list for the Iris. SGI supplies a version of UniPress Emacs as an optional software package. I wouldn't be surprised if someone has ported GNU Emacs, since it is in the public domain. 2) I'm not aware that any seperate compilation is necessary between a "workstation" and a non-disk "terminal". jim@riacs.arpa RIACS/Nasa Ames, Moffett Field, CA 11-Jul-86 16:36:05-PDT,1231;000000000001 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Fri 11 Jul 86 16:35:58-PDT Received: by ucbvax.Berkeley.EDU (5.52/1.14) id AA18579; Fri, 11 Jul 86 16:35:54 PDT Received: by cad.berkeley.edu (5.5/5.6) id AA19349; Fri, 11 Jul 86 16:36:03 PDT Received: Fri, 11 Jul 86 16:30:28 PDT by titan.arc.nasa.gov (5.45/1.2) Received: by uw-beaver.arpa (5.45/5.3) id AA12211; Thu, 10 Jul 86 16:47:07 PDT Received: by ssc-vax (4.12/4.7) id AA00933; Thu, 10 Jul 86 15:49:05 pdt Message-Id: <8607102249.AA00933@ssc-vax> Date: Thu, 10 Jul 86 08:54:19 pdt From: nike!uw-beaver!ssc-vax!voodoo!zombie@ucbvax.Berkeley.EDU (Mike York) To: ssc-vax!SUMEX-AIM.ARPA Subject: Re: SGI Iris DL? In-Reply-To: your article <12220944026.16.SCHMIDT@SUMEX-AIM.ARPA> Yes! We're interested in talking with other Iris users. We've got two 2400 Turbos. We have just porte Gnu Emacs over to the Turbos. I suspect that you'll be receiving mail from the guy who did the port, Jim Tolefson. If you don't hear from him, let me know and I'll get the details to you. Mike York Boeing Computer Services (206) 656-5446 uw-beaver!ssc-vax!voodoo!zombie 12-Jul-86 08:20:00-PDT,1499;000000000001 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Sat 12 Jul 86 08:19:56-PDT Received: by ucbvax.Berkeley.EDU (5.52/1.14) id AA00133; Sat, 12 Jul 86 08:20:08 PDT Date: Sat, 12 Jul 86 08:20:08 PDT From: ihnp4!utzoo!dciem!tim@ucbvax.berkeley.edu Message-Id: <8607121520.AA00133@ucbvax.Berkeley.EDU> Received: by ihnp4.ATT.COM id AA19390; 10 Jul 86 21:09:51 CDT (Thu) To: SCHMIDT@SUMEX-AIM.ARPA Subject: Re: SGI Iris DL > Is there a mailing list for users of Silicon Graphics Iris > workstations? > If not, would others be interested in forming one? > We have the feeling that we're learning a lot of things the > hard way that would be "common knowledge" if a discussion list > existed. > For starters: > 1.) Has anyone ported EMACS? > 2.) How do you compile a program to be downloaded from an "Iris > Workstation" to an "Iris Terminal"? > We have one "Workstation" and one "Terminal." > Please answer directly, as I don't read WorkS regularly. Consider this 1 vote FOR the formation of an IRIS mailing-list. I think that it would be very helpful and informative. I hope that your mailer will be able to find me way out here on the UUCP net... Tim Pointing, DCIEM !ihnp4!utzoo!dciem!tim [...!dciem!isis!tim is our IRIS] P.S. FYI - We have 2 IRIS 2400's, running the TCP/IP kernel, which are on the UUCP net, through site dciem. 12-Jul-86 19:08:03-PDT,884;000000000001 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Sat 12 Jul 86 19:07:58-PDT Received: by ucbvax.Berkeley.EDU (5.52/1.14) id AA07518; Sat, 12 Jul 86 19:08:09 PDT From: ulysses!allegra!phri!cooper!cooper!chris@ucbvax.berkeley.edu Received: by ulysses.UUCP; Sat, 12 Jul 86 21:45:54 edt Received: by phri.uucp (4.12/SMI-3.0DEV3) id AA26757; Sat, 12 Jul 86 18:06:26 edt Date: Sat, 12 Jul 86 18:06:26 edt Message-Id: <8607122206.AA26757@phri.uucp> To: phri!SUMEX-AIM.ARPA!SCHMIDT Subject: Re: SGI Iris DL? In-Reply-To: your article <12220944026.16.SCHMIDT@SUMEX-AIM.ARPA> I don't know of a e-mailing list but we have an IRIS 1000 hooked up over a serial line (we're waiting for Ethernet for the systems). You want to start one? Chris Lent ihnp4!allegra!phri!cooper!chris 16-Jul-86 17:13:21-PDT,1653;000000000000 Mail-From: BRUGGE created at 16-Jul-86 17:13:06 Date: Wed 16 Jul 86 17:13:06-PDT From: John Brugge Subject: SGI DL has been created! To: info-iris@SUMEX-AIM.ARPA Message-ID: <12223252817.35.BRUGGE@SUMEX-AIM.ARPA> From the interest expressed in the replies to the query on an IRIS mailing list, it seems like a worthwhile thing to set up. There is an awful lot of capability in these machines, but they can be mysterious too, so I hope that this list can be a venue to help alleviate that. Those receiving this were the original respondents to the query, and have been placed on the distribution list. Following is a brief description of the focus of the list, as well as directions for requests/bugs/questions/other administrivia: Info-Iris@SUMEX-AIM.Stanford.edu This discussion list focuses on Silicon Graphics Iris workstations and software. Its purpose is to stimulate communication and sharing between computer science research groups that are using or are interested in these machines. An archive of messages is kept on SUMEX-AIM in the file: INFO-IRIS.TXT Requests to be added to or deleted from these lists, problems, questions, etc. should be sent to Info-Iris-Request@SUMEX-AIM or Bug-1100-Request@SUMEX-AIM. Contributors who wish never to see error messages from the TOPS-20 mailer should specify one of these addresses as the return-path: of their messages. Coordinator: John Brugge Welcome aboard! John Brugge Knowledge Systems Laboratory Stanford University (415) 725-3850 ------- 17-Jul-86 10:32:05-PDT,2376;000000000000 Mail-From: BRUGGE created at 17-Jul-86 10:30:47 Date: Thu 17 Jul 86 10:30:47-PDT From: John Brugge Subject: Introductions: what are you doing? To: info-iris@SUMEX-AIM.ARPA Message-ID: <12223441721.49.BRUGGE@SUMEX-AIM.ARPA> To start things out, I think it would be useful to know just what type of environment people are working in with their IRISes: - what type of configuration (terminal, workstation, turbo workstation; Ethernet, serial line; number of users; etc) - what type of application/intended application This may sound like an old summer-camp trick to get to know everyone, but I think it will provide the group with a base, and perhaps help guide some communication if there are other people with similar situations. Here at the Knowledge Systems Lab, we have an IRIS 1200 terminal and a 3020 workstation. The terminal is connected to the Stanford network, through which it talks to a VAX (running Unix 4.2) to run applications. The workstation has just arrived, and has presented problems with connecting it to the Ethernet (which we're trying to iron out with SGI). Our application area is that of a tool for displaying the results of an expert system (PROTEAN) to determine the three-dimensional structure of proteins in solution. It differs from molecular modeling in that (1) we are currently working at a higher level of abstraction than the atomic level, and are representing sections of the protein as cylinders, spheres, and rectangular solids, and (2) we need to display multiple conformations of the protein, since that is the output of PROTEAN, rather than a single structure, such as derived from x-ray crystallography. The code for the display program was written in C and resides on the VAX. We have just brought it over to the workstation, but found a few changes needed due to the changes in the graphics library. We are also considering using MIDAS and/or MMS to supplement our display tools, and would be interested in hearing of others experience using them. I'm sure there are myriads of other applications being used or contemplated, so feel free to let others know what you're doing (if you're allowed to), or what you'd like to do--maybe someone's already done it. John Brugge KSL, Stanford University brugge@sumex-aim.stanford.edu (415) 725-3850 ------- 17-Jul-86 10:37:32-PDT,612;000000000000 Mail-From: BRUGGE created at 17-Jul-86 10:37:25 Date: Thu 17 Jul 86 10:37:25-PDT From: John Brugge Subject: Error in first message To: info-iris@SUMEX-AIM.ARPA Message-ID: <12223442928.49.BRUGGE@SUMEX-AIM.ARPA> In the introductory message sent out to the first group of respondents, it stated that list additions, deletions, problems, etc could be addressed to Info-Iris-Request@SUMEX-AIM *or* Bug-1100-Request@SUMEX-AIM. Since Bug-1100-Request@SUMEX-AIM has nothing to do with IRISes, please cross it out. It was included by accident. John Brugge, Coordinator ------- 21-Jul-86 12:08:57-PDT,419;000000000000 Return-Path: Received: from ames-nas.ARPA by SUMEX-AIM.ARPA with TCP; Mon 21 Jul 86 12:08:35-PDT Message-Id: <8607211913.AA21736@ames-nas.ARPA> Received: from localhost by ames-nas.ARPA; Mon, 21 Jul 86 12:13:21 pdt To: info-iris@sumex-aim.stanford.edu Subject: please add me Date: 21 Jul 86 12:13:15 PDT (Mon) From: raible@AMES-NAS.ARPA raible@ames-nas.arpa thanks... ---------- 22-Jul-86 08:31:30-PDT,2789;000000000000 Mail-From: BRUGGE created at 22-Jul-86 08:31:07 Date: Tue 22 Jul 86 08:31:07-PDT From: John Brugge Subject: Introductions: what are you doing? To: info-iris@SUMEX-AIM.ARPA 17-Jul-86 10:31:45-PDT,2376;000000000001 Mail-From: BRUGGE created at 17-Jul-86 10:30:47 Date: Thu 17 Jul 86 10:30:47-PDT From: John Brugge Message-ID: <12224730656.20.BRUGGE@SUMEX-AIM.ARPA> A number of people have joined the discussion list since this message was first sent, so it is being resent for those who missed it. To start things out, I think it would be useful to know just what type of environment people are working in with their IRISes: - what type of configuration (terminal, workstation, turbo workstation; Ethernet, serial line; number of users; etc) - what type of application/intended application This may sound like an old summer-camp trick to get to know everyone, but I think it will provide the group with a base, and perhaps help guide some communication if there are other people with similar situations. Here at the Knowledge Systems Lab, we have an IRIS 1200 terminal and a 3020 workstation. The terminal is connected to a serial line, through which it talks to a VAX (running Unix 4.2) to run applications. It is also connected to the ethernet, through which it can communicate with Xerox 1100 series Lisp machines that have the Iris library routines loaded. The workstation has just recently arrived, and is now running the TCP/IP kernel to speak with other hosts. Our application area is that of creating a tool for displaying the results of an AI system (PROTEAN) to determine the three-dimensional structure of proteins in solution. It differs from molecular modeling in that (1) we are currently working at a higher level of abstraction than the atomic level, and are representing sections of the protein as cylinders, spheres, and rectangular solids, and (2) we need to display multiple conformations of the protein (the output of PROTEAN), rather than a single structure, such as derived from x-ray crystallography. The code for the display program was written in C and resides on the VAX. We have just brought it over to the workstation, but found a few changes needed due to the changes in the graphics library. We are also considering using MIDAS and/or MMS to supplement our display tools, and would be interested in hearing of others experience using them. I'm sure there are myriads of other applications being used or contemplated, so feel free to let others know what you're doing (if you're allowed to), or what you'd like to do--maybe someone's already done it. John Brugge KSL, Stanford University brugge@sumex-aim.stanford.edu (415) 725-3850 ------- 22-Jul-86 11:11:16-PDT,1735;000000000000 Return-Path: Received: from CSNET-RELAY.ARPA by SUMEX-AIM.ARPA with TCP; Tue 22 Jul 86 11:10:51-PDT Received: from omnitor.arpa by CSNET-RELAY.ARPA id aa07762; 22 Jul 86 13:44 EDT Received: by omnitor.ARPA id AA03946 at Tue, 22 Jul 86 13:28:55 edt Date: Tue, 22 Jul 86 13:28:55 edt From: Kevin Tureski Full-Name: Kevin Tureski Message-Id: <8607221728.AA03946@omnitor.ARPA> To: info-iris%sumex-aim.arpa@CSNET-RELAY.ARPA Subject: Omnibus is doing this ... Omnibus Computer Graphics Inc presently uses 3 2400 workstations and 1 2400 Turbo primarilly for motion development, digitizing/inspecting data, and rendering. To quote from a recent press release: OMNIBUS has facilities in Toronto, New York City and Hollywood serving the advertising, television and film industries. Its software is also licensed on an exclusive basis in the U.K., Australia and Japan. Each facility has 1 2400; Toronto also has the Turbo. At each site, there is at least a Vax 780 running 4.2BSD to which the Irises are ether'ed via XNS. The 780's are in turn connected to each other via CSNET. The purchase of more Turbos (preferably 3030's) is anticipated, though not certain. We are investigating the adaptation of our current software from a Vax4.2 - Adage RDS 3000 based environment to the Iris. Kevin M Tureski Systems Administrator Omnibus Computer Graphics Inc. 2180 Yonge St. Toronto, Ontario, Canada M4S 2B9 UUCP: {allegra,decvax,ihnp4,utcsri}!watmath!omnitor!ktureski CSNET: ktureski@omnitor.csnet ARPA: ktureski%omnitor.csnet@csnet-relay.arpa (ktureski@omnilax.arpa works below the 49'th parallel) 22-Jul-86 14:38:56-PDT,650;000000000000 Mail-From: BRUGGE created at 22-Jul-86 14:38:35 Date: Tue 22 Jul 86 14:38:33-PDT From: John Brugge Subject: Common Lisp interface to the Iris To: info-iris@SUMEX-AIM.ARPA Message-ID: <12224797547.20.BRUGGE@SUMEX-AIM.ARPA> I have heard that Common Lisp is, or soon will be, released for the Iris from Franz, Inc. and was wondering if anyone knows what the interface is/ will be like? That is, although it must surely have hooks to the graphics library, does it also have a flavors environment for windowing operations, so that code written on a TI Explorer or Symbolics would run on it? Thanks, John ------- 23-Jul-86 07:52:26-PDT,1778;000000000000 Return-Path: Received: from BBN-PROPHET.ARPA by SUMEX-AIM.ARPA with TCP; Wed 23 Jul 86 07:51:58-PDT To: John Brugge cc: info-iris@sumex-aim.ARPA, hbaig@BBN-PROPHET.ARPA Subject: Re: Introductions: what are you doing? In-reply-to: Your message of Tue 22 Jul 86 08:31:07-PDT Thu 17 Jul 86 10:30:47-PDT. <12224730656.20.BRUGGE@SUMEX-AIM.ARPA> Date: 23 Jul 86 10:54:09 EDT (Wed) From: hbaig@BBN-PROPHET.ARPA We have recently acquired an Iris 3020, on which we are developing the ProphetII system. ProphetII is the second generation of Prophet, a program which has been in existence since 1970, under the sponsorship of the National Institutes of Health. The system is designed to the meet the computational and analysis needs of the biomedical research community, and includes extensive, graphically-oriented capabilities for data management and presentation, statistical analysis, and molecular modeling. Among the salient improvements in ProphetII are a distributed, open architecture, a multiple window environment, more dynamic graphics (particularly for visualization of three-dimensional molecular structures), and an enhanced user interface. The SGI workstation has an Ethernet interface with TCP/IP, connected to a VAX 785 (our development host machine, running Ultrix) and a Sun 3/160C. It also has the Weitek FPA. The primary language we use is C, with some Fortran. We are interested in hearing about others' experiences with the SGI hardware and software, particularly in the areas of graphics (any suitable standards on the horizon?), window systems (X?), networking, and molecular modeling packages (MMS, Midas, etc.). Hank Baig BBN Laboratories Cambridge, Mass. 23-Jul-86 12:44:51-PDT,1089;000000000000 Return-Path: Received: from omnilax.ARPA by SUMEX-AIM.ARPA with TCP; Wed 23 Jul 86 12:44:30-PDT Received: by omnilax.ARPA id AA26298 at Tue, 22 Jul 86 15:45:26 pdt Date: Tue, 22 Jul 86 15:45:26 pdt From: jisdale@omnilax (Jerry Isdale) Full-Name: Jerry Isdale Message-Id: <8607222245.AA26298@omnilax.ARPA> To: info-iris@sumex-aim.ARPA Subject: X on the Iris I asked about this in the xpert news list, but it might be worth a shot here: Has anyone tried/started porting the X windowing system to the Iris? This system is free from MIT but is designed for BSD4.2 using sockets. Supposively, the Iris Unix has/will have some implementation of sockets that might be used. Does anyone have any subjective evaluation of X vs the menu stuff supplied by SGI for the Iris? (i.e. is the SGI stuff good enough to forego the X port?) Does anyone have any other menu/window packages for the Iris? Thanks, Jerry Isdale, Omnibus Computer Graphics 5555 Melrose Ave, Hollywood CA CSNET/ARPA: jisdale@omnilax.arpa omnilax%jisdale@csnet-relay.arpa 23-Jul-86 13:02:25-PDT,833;000000000000 Mail-From: CORNELIUS created at 23-Jul-86 13:02:11 Date: Wed 23 Jul 86 13:02:11-PDT From: Craig Cornelius Subject: Debug for Graphics Mode? To: info-iris@SUMEX-AIM.ARPA Message-ID: <12225042146.41.CORNELIUS@SUMEX-AIM.ARPA> Are there any tools for debugging programs that operate in graphics mode on the IRIS? I have used dbx, but it is not very handy while trying to debug a graphics routine, and using queued keyboard buttons is almost impossible in dbx. I feel certain that there should be a debug routine that would: a. open a separate window for debug commands b. allow query of the state of the graphics system c. allow interactive call of graphics routines to manually change the display. Any hints or relevant experience, especially in C? Craig Cornelius ------- 23-Jul-86 15:53:25-PDT,1264;000000000000 Return-Path: Received: from CSNET-RELAY.ARPA by SUMEX-AIM.ARPA with TCP; Wed 23 Jul 86 15:52:51-PDT Received: from omnitor.arpa by CSNET-RELAY.ARPA id aa06138; 23 Jul 86 18:55 EDT Received: by omnitor.ARPA id AA03565 at Wed, 23 Jul 86 18:47:05 edt Date: Wed, 23 Jul 86 18:47:05 edt From: Kevin Tureski Full-Name: Kevin Tureski Message-Id: <8607232247.AA03565@omnitor.ARPA> To: info-iris%sumex-aim.arpa@CSNET-RELAY.ARPA Subject: GL2.0-W3.4 Flight Simulator Brain Damage (with adb patch) The 3.4 release for (at least) the 2400T has some pretty damaging code in it. We happened to notice that after the flight simulator was run, /dev/ttyd3 was rendered useless. For example: echo >/dev/ttyd3 /dev/ttyd3: No such device or address SGI hotline provided the following patches for flight and dog, which work: cd /usr/people/demos adb -w flight 1192?ia [ should read "bsr 0x44D2" ] 1194?x [ should read "0x333E" ] ?w2 [ should read "0x333E=0x2" ] 1192?ia [ should read "bsr 0x1196" ] $q adb -w dog 1196?ia [ should read "bsr 0x45D8" ] 1198?x [ should read "0x3440" ] ?w2 [ should read "0x3440=0x2" ] 1196?ia [ should read "bsr 0x119A" ] $q 23-Jul-86 22:05:26-PDT,506;000000000000 Return-Path: Received: from ames-nasb.arpa ([128.102.4.2].#Internet) by SUMEX-AIM.ARPA with TCP; Wed 23 Jul 86 22:05:07-PDT Received: Wed, 23 Jul 86 22:10:34 PDT by ames-nasb.arpa (5.28/1.2) Message-Id: <8607240510.AA04386@ames-nasb.arpa> To: Info-Iris@SUMEX-AIM.Stanford.edu Subject: yet another Date: 23 Jul 86 22:10:33 PDT (Wed) From: raible@ames-nasb.arpa So could you add creon@ames-nas to the list too? Or do you want him to request this? - Eric ---------- 24-Jul-86 05:05:21-PDT,2406;000000000000 Return-Path: Received: from uw-beaver.arpa by SUMEX-AIM.ARPA with TCP; Thu 24 Jul 86 05:05:10-PDT Received: by uw-beaver.arpa (5.45/5.3) id AA25119; Thu, 24 Jul 86 05:14:48 PDT Return-Path: Received: by ssc-vax (4.12/4.7) id AA15848; Wed, 23 Jul 86 19:46:30 pdt Message-Id: <8607240246.AA15848@ssc-vax> To: ssc-vax!uw-beaver!info-iris@sumex-aim.arpa Date: Wed, 23 Jul 86 18:07:33 PDT From: ssc-vax!voodoo!zombie@uw-beaver.arpa (Mike York) Subject: One thing that Boeing is doing Reply-To: Mike York X-Mailer: ELM [version 1.2] We currently have two 2400 Turbos. They currently are standalone workstations, but will eventually be linked via ethernet to a VAX-11/750 running Ultrix. We are developing a technical illustration system to be used in the preparation of maintenance, flight, operating and training manuals for Boeing commercial airplanes. The new system will replace the current system that consists of 14 PDP-15's, two PDP-11/40's and a DEC-10. "Vintage" hardware to say the least. Our application is an extremely interactive one, lots of picking and dragging (that's why we selected SGI). One disappointment we had was not being able to inquire about the drawing commands that make up an object that's in the display list, an absolute necessity for our application. After looking at the alternatives, we decided to write our own display list handler. We have written a "toy" display list handler (no editing capabilities yet) and it runs quite fast (however, it does not yet handle text which will be implemented as graphical objects). We would be interested in hearing from others who have implemented their own display list handler. We are particularly interested in how others have handled text and editing objects in the display list. We have had some problems with one Turbos. We have lost the disk drive on it twice in four months. Is this a common problem? We also had the monitor quit on us one day. It happened to be when the air conditioning was out in our building and the temperature was around 80. Is there a thermal cutoff in the monitor? The SGI service rep wasn't sure. Al McPherson uw-beaver!ssc-vax!voodoo!bhagwan (206) 342-1442 Mike York uw-beaver!ssc-vax!voodoo!zombie (206) 656-5446 28-Jul-86 10:27:58-PDT,2457;000000000000 Return-Path: Received: from cgl.ucsf.edu ([128.32.140.1].#Internet) by SUMEX-AIM.ARPA with TCP; Mon 28 Jul 86 10:27:32-PDT Received: from socrates.ucsf.edu by cgl.ucsf.edu (4.46/GSC4.0) id AA13090; Mon, 28 Jul 86 10:20:10 PDT Received: by socrates.ucsf.edu (4.46/GSC4.0) id AA07949; Mon, 28 Jul 86 10:26:47 PDT Date: Mon, 28 Jul 86 10:26:47 PDT From: rl@cgl.ucsf.edu Message-Id: <8607281726.AA07949@socrates.ucsf.edu> To: info-iris@sumex.stanford.edu Subject: UCSF Computer Graphics Laboratory Cc: rl@cgl.ucsf.edu In response to the request from John Brugge: The Computer Graphics Laboratory at the University of California, San Francisco, has two SGI Iris 3030s as part of a molecular graphics lab that includes E&S PS2 and PS3XXs. The lab is a National Research Resource of the NIH (National Institutes of Health) which began at Princeton in 1970 with an E&S LDS-1 system interfaced to a PDP-10 (KA- 10). The lab moved to UCSF in 1976. where we standardised on UNIX and installed first a PDP-11/70, and then a series of Vaxen (now 8600 + 750's + micros). We also have two Symbolics 36XXs. All ethernetted. We also make heavy use of the Cray XMP-48 at the SDSCC for molecular dynamics calculations. Our main research interests are in drug design and protein and nucleic acid structures and interactions. Software developed here includes Midas (Molecular Interactive Display And Simulation) which developed from our earlier work here and at Princeton, and is specifically designed for efficient display and mani- pulation of very large molecules. Midas was originally written for the PS2, and ported to the IRIS when it first came out. We are also working on protein structure prediction (PROEM: PROtein Experimental Modeler) and drug design (KARMA: Kee Assisted Receptor Map- ping Analysis). The lab will be moving to considerably increased space in 1987 and a new grant from DARPA for protein structure work will begin in late 1986. We will be expanding our personnel, and are interested in applications from potential graduate students, programmers or postdocs. Bob Langridge rl@cgl.ucsf.edu (ARPANET) Computer Graphics Laboratory ...ucbvax!ucsfcgl!rl (USENET) University of California rl@ucsfcgl (BITNET) San Francisco CA 94143-0446 +1 415 476-2630, -1540, -5128 28-Jul-86 11:39:42-PDT,495;000000000000 Return-Path: Received: from WISCVM.ARPA by SUMEX-AIM.ARPA with TCP; Mon 28 Jul 86 11:39:04-PDT Received: from (VMMAIL)PUCC.BITNET by WISCVM.ARPA on 07/28/86 at 13:39:42 CDT Received: by PUCC (Mailer X1.23) id 9355; Mon, 28 Jul 86 13:23:28 EDT Date: Mon, 28 Jul 1986 13:23:12 EDT From: Kirk D. Alexander To: Info-Iris@SUMEX-AIM.Stanford.edu Please include me on the new Iris Workstation mailing list. Kirk 30-Jul-86 10:57:45-PDT,421;000000000000 Return-Path: Received: from BBN-PROPHET.ARPA by SUMEX-AIM.ARPA with TCP; Wed 30 Jul 86 10:57:19-PDT To: info-iris@sumex-aim.ARPA Subject: GNU Emacs Date: 30 Jul 86 13:51:11 EDT (Wed) From: hbaig@BBN-PROPHET.ARPA Does anyone have any experience porting GNU Emacs to the SGI machines? If so, we would appreciate the opportunity to ask some questions. Thanks in advance, >Hank Baig 31-Jul-86 09:31:32-PDT,1942;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.ARPA with TCP; Thu 31 Jul 86 09:31:07-PDT Date: Thu 31 Jul 86 09:33:27-PDT From: Lloyd La Comb Subject: Iris questions and answers To: Info-Iris@SUMEX-AIM.Stanford.EDU cc: lacomb@Sierra.Stanford.EDU Message-ID: <12227101299.15.LACOMB@Sierra.Stanford.EDU> We have two 2400 turbos here in the Applied Physics Dept. Stanford University. Both are connected to the S(tanford)U(niversity)NET (tcp/ip) which is connected to the arpa net. I can ftp and telnet to other machines on the net but can't use mail since the Iris does not support send mail. We are conducting reseach in acoustic and tunnelling microscopy using the Irises for imaging processing, manipulation, and display. We do most of the work in C with some in FROTRAN when I can steal some good code. I can answer a few of the question posed by some of the other users. I have Unipress emacs, it is o.k. at best, I've given up on it and now use the AME editor by Software System in San Jose (408-995-0689), it costs about $800 about works just the MacWrite editor but a little more sophistocated. They may still be giving out one-month samples if you send them a tape. I also have a copy of Midas up and running on one of the Turbos, and you guys over at the med center are welcome to come over and take a look at it. The developers at UCSF sent out a memo a couple of months ago about an update, but I haven't gotten mine yet so I don't know if there are any major changes forthcoming. I also have some experinece with the IEEE-488 option on the Iris if there are any other users that had problems getting that up an running. I would like to be on the mailing list here is my information: Lloyd La Comb Dept of Applied Physics Stanford University Stanford Ca 94305 (415) 723-1810 lacomb@su-sierra.arpa ------- 31-Jul-86 13:32:30-PDT,816;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Thu 31 Jul 86 13:31:35-PDT Date: Thu, 31 Jul 86 13:51 EDT From: PEPKE%FSU.MFENET@LLL-MFE.ARPA Subject: IRIS, Wollengong TCP/IP, and DI-3000 To: INFO-IRIS@SUMEX-AIM.ARPA We are interested in running an IRIS 3020 from a VMS VAX using the TCP/IP version of the IRIS terminal software and remote graphics library through the Wollengong group TCP/IP code for VMS. We will be using the library both by itself and as part of a device driver for DI-3000. Any words of advice, especially about the terminal software to Wollengong TCP/IP link would be appreciated. Eric Pepke Supercomputer Computations Research Institute Florida State University Tallahassee, Florida 32304-4052 pepke@fsu.mfenet 31-Jul-86 16:53:06-PDT,3407;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Thu 31 Jul 86 16:51:17-PDT Date: Thu, 31 Jul 86 16:53:17 pst From: michael zyda Message-Id: <8608010053.AA08840@nps-cs> To: info-iris@sumex-aim Subject: NPS's IRIS Activities... I am a Professor of Computer Science at the Naval Postgraduate School in Monterey, California. We have a Turbo 2400 and an IRIS-2400. We have two additional IRISes on order this fiscal year and two in next year's budget. We use the IRISes to teach beginning computer graphics and as a vehicle for our research into special architectures for graphics applications algorithms. We also use them for autonomous vehicle route planning and walking machine animation. My students have generated a number of videogames and other useful software as part of the beginning IRIS class. Our most successful program to date is a figure illustrator (ozdraw), which is available in source form for anyone who sends us a cartridge tape. We have a number of text fonts for the IRIS that we swiped from our laser printer, for those of you who like large (24 x 24 fonts). We have Common LISP installed now and will shortly begin using it. We have had IRISes since October 1984 and have gone through the entire product line. Part of my consulting is to offer an Iris course onsite to people needing to get off the ground in a hurry. I've given the course to Nasa/Edwards AFB and to about 12 different companies in Japan. The course can be given in 5 days if anyone is interested... Reliability is a very sticky point for the IRISes. They do not like heat (over 80 degrees in the room). If the room is 80F, the cabinet temp is about 120F. We blow a 72MB disk drive every 6 months. This happens more often at sites where the IRIS is turned on/off every night. If you can afford maintenance, buy it. Otherwise, save money for the downs. We had 25 service calls for two IRISes last year! Maintenance is very expensive on the IRIS. Mr. Daniels of SGI thinks that you ought to pay 12 percent of the ORIGINAL purchase price of your system for maintenance, even though that may now be half of the cost of replacing the entire system today! My maintenance bill for the last year averaged 25 percent of replacement value, double the industry standard. By the way, having had a number of other high-performance graphics systems, SGI's hardware reliability is about the same as experienced for E+S equipment (at least for my experience). It may be a bit worse but on the whole, I think its worth it... By the way, there is a User's Group meeting being set up by SGI for SIGGRAPH in Dallas. It will be from 3pm to 6pm on the 20th of August. They haven't sent any announcements yet as to where... Current student projects... (a) a two-dimensional fractals tutorial (b) a study on interworkstation communication and real-time graphics capabilities over the net (c) lighting and shading computable quickly on the IRIS Michael J. Zyda Naval Postgraduate School Code 52, Dept. of Computer Science Monterey, California 93943 (408) 646-2305 Arpanet: zyda@nps-cs UUCP: ucbvax!dual!lll-crg!nps-cs!zyda ucbvax!olympus!nps-cs!zyda ihnp4!seismo!lll-crg!nps-cs!zyda 1-Aug-86 10:45:41-PDT,2868;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Fri 1 Aug 86 10:44:24-PDT Date: Fri, 1 Aug 86 10:46:07 pst From: michael zyda Message-Id: <8608011846.AA14962@nps-cs> To: info-iris@sumex-aim Subject: IRIS Window Manager (mex)... Mex and X Windows... The current state of the Window Manager and its future is evidently under considerable controversy at SGI. X Windows is being promulgated by some who are pushing the IRIS towards 4.3 Unix. There is tremendous support for Mex too. My experience in the consulting world is that very few CAD/CAM companies are building their software around mex. Almost all of them express an interest in mex but do not yet know how to build systems around such capabilities. This question will be out for a long time. I show mex and several sample programs to every IRIS class I teach on the road but when I check in later, the IRIS is being used standalone, without mex. A lot of the resistence to Mex is its low amount of documentation. The current manual is too short and the examples not real clear. There is also no intelligent discussion of WHY one wants to use a Window Manager. We do this here in our advanced graphics class. SGI is trying to remedy this by writing a Tutorial document for the IRIS graphics package based around writing programs for mex. This document goes to the printers shortly. Its pretty well-written and quite good. (I reviewed it for SGI...) Mex uses a lot of IRIS resources. If you have a Turbo with 4MB of memory, the overhead from mex will make your demos look quite disappointing. I am currently teaching an Advanced Graphics course at NPS in which one of the longer topics is Window Management in general and mex and X Windows in particular. Maybe we will be able to say something a bit later on down the road. I have built several programs using mex and find it quite easy. Now that SGI has distributed Popup menu support with mex, I believe more people will be willing to use it. By the way, the author of mex is Paul Haeberli at SGI. If you ever stop in and talk to him, he gives a wonderful demo with mex. He has a very nice development environment and set of useful programs under mex. These programs never make the SGI releases because Paul won't document them and no one else understands them. The stuff you get under 'mextools' is only a small part of what Paul has up and running. It is not even the best part. He has a nice movement recording system that is neat! SGI may turn to Unix 4.3 soon. I think this is going to be the end of System V for them. For the short run, you might want to avoid using anything System V dependent... If they do you will have X windows as its part of 4.3... Michael Zyda Naval Postgraduate School 1-Aug-86 23:58:10-PDT,2726;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Fri 1 Aug 86 23:57:50-PDT Date: Sat, 2 Aug 86 2:57:01 EDT From: Mike Muuss To: michael zyda cc: info-iris@sumex-aim.arpa, SWillson@nrtc.arpa Subject: Re: IRIS Window Manager (mex)... Message-ID: <8608020257.aa01138@SEM.BRL.ARPA> I have no reason to believe that SGI will deviate from it's "System V Uber Alles" course of action, due to stiff SysV requirements from several large customers. However, they seem to understand the importance of all the good things Berkeley has done. Things are not so grim. For example, the wonderful people at NASA Ames have installed 4.2 networking into their SGI kernel, finally offering an end to the horrid Excelan TCP. The X window system has some interesting ideas. It is not yet clear that it's "Bit-BLIT pixels across the net" philosophy makes so much sense when the display is 24 or 32 bits deep -- it's pretty demanding on an Ethernet doing 1Kx1Kx1 bit transfers. It's also not clear that the X philosophy of viewing the screen as an array of pixels allows much use of the graphics pipeline. These comments notwithstanding, X is a very nice window system, and Jim Gettys and the rest of MIT Project Athena deserve a lot of credit for doing a nice job, and avoiding design religion. In some future letter I will discuss BRL's solid modeling package and Raytracer. While it has been run on SGIs, we don't have any yet, so the packaging isn't perfect. More later. And, while I'm writing, how many of you didn't know that in release 3.3.??, the compiler folds "double" into a "float", and now mis-interprets the declaration "long float" as what "double" OUGHT to be. Horrid. Also, beware of the library routine hypot() -- it will trash the stack frame, causing core dumps some random time later. A reasonable (but not great) workaround is: double hypot(a,b) double a,b; { return( sqrt(a*a+b*b) ); } And the best bug of all: how many of you knew that typing ^S (ctl/S) on one of the async lines stalls ALL the output to ALL terminals, including the console? I happen to like the SGI hardware quite a lot -- the graphics pipeline is extremely well designed. (Amazingly enough, it's actually quite nice to program directly (which I do, for performance)). However, abortions like "long float" are not appreciated. You should call Tech Support and express your feelings. (I've already ranted at everybody I could find, including Chief Scientist, Marketing, and Tech Support, but more people ranting will help get proper attention focused on fixing it). Best, -Mike 5-Aug-86 00:25:59-PDT,465;000000000000 Return-Path: Received: from OZ.AI.MIT.EDU (MC.LCS.MIT.EDU.#Internet) by SUMEX-AIM.ARPA with TCP; Tue 5 Aug 86 00:25:44-PDT Date: Tue, 5 Aug 1986 03:25 EDT Message-ID: Sender: GZT.TDF%OZ.AI.MIT.EDU@XX.LCS.MIT.EDU From: "David D. Story" To: Info-Iris@SUMEX-AIM.ARPA Subject: Please add me to the list Phase-Of-The-Moon: NM+4H.32M.57S. FTD@MIT-OZ 6-Aug-86 13:03:27-PDT,815;000000000000 Mail-From: BRUGGE created at 6-Aug-86 13:03:07 Date: Wed 6 Aug 86 13:03:07-PDT From: John Brugge Subject: re: GNU Emacs To: info-iris@SUMEX-AIM.ARPA Message-ID: <12228712332.37.BRUGGE@SUMEX-AIM.ARPA> We just got a copy of GNU Emacs the other day that had already been configured for the IRIS, so it was up and running in an afternoon. The only changes that seem to have been necessary were a couple of header files describing the peculiarities of the machine and system. The only disappointment has been that System V doesn't support inferior shells in a buffer, so that you need to suspend or kill Emacs to get to the system. Otherwise, it feels much the same, only faster than on a Vax, and with a few new changes/features (such as a smarter C mode). John ------- 6-Aug-86 17:49:42-PDT,1409;000000000000 Return-Path: Received: from sdcsvax.ucsd.edu by SUMEX-AIM.ARPA with TCP; Wed 6 Aug 86 17:47:45-PDT Received: by sdcsvax.ucsd.edu (5.31/4.42) id AA29540; Wed, 6 Aug 86 17:45:48 PDT hops=0 Received: by sdchema.chem.ucsd.edu (5.44) id AA21357; Wed, 6 Aug 86 17:45:31 PDT Received: by sdchemf.chem.ucsd.arpa (4.12) id AA06632; Wed, 6 Aug 86 17:49:32 pdt Date: Wed, 6 Aug 86 17:49:32 pdt From: sd%chem@sdcsvax.ucsd.edu (Steve Dempsey) Message-Id: <8608070049.AA06632@sdchemf.chem.ucsd.arpa> To: Info-Iris@sumex-aim.arpa Subject: Greetings Here in the Dept. of Chemistry Computer Facility at UCSD we have an IRIS 2400T running the TCP/IP kernel. The IRIS sits on a local network with VAXes running 4.2BSD and 4.3 BSD, and Celerity 1260D's running 4.2BSD. Our IRIS is used for the study and determination of the three-dimensional structure of macromolecules (molecular modeling) and the dynamics of molecular systems. I am the author of the UCSD Molecular Modeling System (MMS) which we are currently distributing. One of our main interests is the development of stereo viewing systems for the IRIS. We would be very interested in hearing of similar efforts by others. We are currently investigating the Tektronix Liquid Crystal Shutter system. Steve Dempsey Chemistry Dept., B-014 Univ. of Calif., San Diego La Jolla, CA 92093 (619) 534-0208 6-Aug-86 19:41:39-PDT,1269;000000000000 Return-Path: Received: from uw-beaver.arpa by SUMEX-AIM.ARPA with TCP; Wed 6 Aug 86 19:41:18-PDT Received: by uw-beaver.arpa (5.45/5.5) id AA17945; Wed, 6 Aug 86 19:44:47 PDT Return-Path: Received: by ssc-vax (4.12/4.7) id AA20718; Wed, 6 Aug 86 17:48:13 pdt Message-Id: <8608070048.AA20718@ssc-vax> To: ssc-vax!uw-beaver!info-iris@sumex-aim.arpa Date: Wed, 6 Aug 86 15:39:16 PDT From: ssc-vax!voodoo!bhagwan@uw-beaver.arpa (A. L. McPherson) Subject: no subject (file transmission) X-Mailer: ELM [version 1.2] Help! I bought XNS (4.2bsd) software and Interlan card for my 750 from SGI. We run Ultrix 1.2 and cannot config a new kernel with SGI's XNS stuff in it. They're saying that it wont work under Ultrix, yet I was led to believe that Ultrix is compatable with 4.2bsd. Anybody know what gives? Anybody have a fix? Anybody have the same problem (maybe we can gang up on them). Thanks for the help. -------------------------------------------------------------------------- Al McPherson Voodoo Graphics Project (soon to be BoGART) Boeing Computer Services ....uw-beaver!ssc-vax!voodoo!bhagwan Everett, Washington (206) 342-1442 7-Aug-86 09:40:41-PDT,2772;000000000000 Return-Path: <@MCC.COM:nong%loverly.hi.mcc.com@mcc.com> Received: from MCC.COM by SUMEX-AIM.ARPA with TCP; Thu 7 Aug 86 09:39:53-PDT Received: from loverly.hi.mcc.com by MCC.COM with TCP; Thu 7 Aug 86 11:39:03-CDT Date: Thu, 7 Aug 86 07:43:35 cdt From: Nong Tarlton Posted-Date: Thu, 7 Aug 86 07:43:35 cdt Message-Id: <8608071243.AA07845@loverly.hi.mcc.com> Received: by loverly.hi.mcc.com (4.24/STP) id AA07845; Thu, 7 Aug 86 07:43:35 cdt To: Info-Iris@SUMEX-AIM.ARPA Subject: Common Lisp I just joined the group, and thought I would introduce myself. My name is Nong Tarlton, and I am with Human Interface Program at MCC (Microelectronics and Computer Technology Corporation). We have a 2400T that connects to Ethernet using TCP/LP, and we have a 2300 connected to LMI Lambda Lisp Machine via a multibus interface. In response to the question about Common Lisp for the IRIS. Franz does have a Common Lisp that runs on the IRIS. When we talked to them. about a month ago, they were working on the documentation. They do have hooks to the graphics library, but I don't know whether they implemented the flavors system or not. As far as the user interface goes, I assume that it is like the Lisp Listener on the lisp machines. Prices are: $7,000 for the first copy, $3,500 for subsequent copies, and $250 for a 30 day evaluation copy. We are also looking into Kyoto Common Lisp (KCL), which was developed at the Research Institute for Mathematical Sciences, Kyoto university. It is available from IBUKI. Currently, they do not have a version that will run on the IRIS, however, they do have a version that runs on the SUN (68020) and a version that runs on an AT&T system under System V. They said it would be straight forward to modify it to run on the IRIS (maximum of a week of one person's time), since most of KCl is written in C and Common Lisp itself. There are about 20 to 30 lines of assembly code. One nice thing about KCL is that programs can be compiled into C. And, the price is right. You can get the source and all for only $1,400. Is anyone out there interested in porting it? If you are interested in object-oriented lisp dialects, Object Lisp can be run on either Franz or Kyoto Common Lisp. It is available from LMI, at the cost of shipping and media (approximately $200) for the first copy, and you may make susequent copies without obligation to LMI. IBUKI 399 Main Street Los Altos, CA 94022 phone: (415) 949-1126 LMI Marketing Dept., 6 Technology Dr., Bldg. #4 Andover, MA 01810 phone: (617) 682-0500 Franz Inc. 1141 Harbor Bay Parkway Suite 270 Alameda, CA 94501 phone: (415) 769-5656 Nong 11-Aug-86 17:08:09-PDT,4968;000000000000 Return-Path: Received: from ames-nasb.arpa by SUMEX-AIM.ARPA with TCP; Mon 11 Aug 86 17:07:39-PDT Received: Mon, 11 Aug 86 16:17:07 PDT by ames-nasb.arpa (5.28/1.2) Message-Id: <8608112317.AA05867@ames-nasb.arpa> To: info-iris@SUMEX-AIM.ARPA Cc: wksteam@ames-nasb.arpa Subject: An interesting IRIS site report. Date: 11 Aug 86 16:17:05 PDT (Mon) From: creon@ames-nasb.arpa This is a site report destined for the info-iris mailing list. We are NASA's Numerical Aerodynamic Simulation (NAS) facility. We are a national center for computational fluid dynamics research located at NASA Ames Research Center in Mountain View, California. The main number crunching engine at our site is a Cray 2 (4 CPUs, 4nsec cycle, 256 Million 64-bit words of RAM). It does "flow simulation" and some amount of grid generation (preprocessing) and postprocessing in cooperation with the Silicon Graphics IRIS's. It runs unix (Cray's UNICOS), including 4.2bsd-like tcp/ip over NSC hyperchannel. We also have a Cray XMP-48 and a four-pipe CDC cyber 205 here. For mass storage and non-numeric cycles we use a dual processor Amdahl 5840 (24 Mbytes RAM and 200 Gbytes disk). Our Silicon Graphics IRIS environment is unique. We were SGI's first big customer - we are only about half a mile away from them - and Jim Clark worked here for several years, before forming SGI. Currently, we have about 30 IRIS's. Most of them are 2500's (GL2, non-turbos, 400 Mbyte Fujitsu eagles). About five of them are turbos (2500T's). They are all being upgraded tu 2500T's and 3030's over the next few weeks. On the non-turbos, we run our own operating system. It is SGI 2.3, but with their networking code ripped out and our own put in. Our networking code is real 4.2bsd sockets, with multiple interfaces real IP, select, and 4.3 bug fixes. A major feature for us is that it talks tcp/ip over both ethernet and hyperchannel, so our iris's can talk directly to our Crays, with no gateways. We also have a hyperchannel driver on the IRIS accessible through /dev/hyxx for diagnostics and communication to non-tcp/ip machines (such as the Cray XMP running COS). We can simultaneously run tcp/ip to the Cray 2 and the COS station package to the XMP in seperate windows. This networking software was done for us by Sterling Software Inc., and we may distribute it if there is sufficient demand. We (a friend here at NASA, a fellow from SGI, and I) are currently working together putting hyperchannel support into a prerelease of SGI's 3.5 operating system on the turbos. The idea is that it will be supported by SGI in 3.5.1. 3.5 is largely like 3.4, but with some significant 4.3bsd enhancements and even some SVR3 thrown in. It has mkdir(2), rmdir(2), rename(2) (though still SVR2 directory structures), a new compiler, SUN's NFS, and most importantly (for us), it has 4.3bsd sockets and 4.3bsd tcp/ip, with multiple interfaces. However, be warned that what I have been working with is a pre-release. Backwards compatibilty with 3.4 is excellent. Another very interesting thing that we have done here is enhancements to the SGI remote graphics library (RGL). This has been largely done by Diana Choi (choi@ames-nas). RGL has been rewritten to run under sockets and tcp/ip, and has been ported to the Cray 2. The iris side of it (wsiris) has been chenged from a program into a subroutine. We routinely run programs that do iris graphics calls on the Cray, to, say, build an object (makeobj(), move(), draw(), ...,endobj()). Control is then passed back to the iris where the object can be locally transformed. Points in 3d are picked, and control is passed back to the cray, where a new object is made, etc. It is like having a dual processor IRIS where one of them can go at hudreds of Mflops, sort of... We have developed an animation system here for 3d scientific animation of vector fields, scalar fields, and solids. It is called GAS. It drives a Dunn movie camera or Lyon Lamb box. We are working on interfacing it to a Abekas disk-based video system. It is public domain and can be seen at the SGI booth at SIGRAPH '87. We also have a general pupose 2-d & 3-d scientific graphics package (PLOT3D), oriented towards fluid dynamics. (So it does vorticity contours of vector fields, and many things like that). It interfaces to the animation system mentioned above. It can also We have enhanced the window manager so that you can select text and background colors for the currently active window to be different from those in other windows. It is a nice hack, one that greatly decreases the frequency of typing into the wrong window. All in all, an interesting place. Creon Levit NASA Ames Research Center Moffett Field, California 94035 (415)-694-6410 creon@ames-nas (ARPAnet) ihnp4!ames!amelia!creon (uucpnet) ---------- 12-Aug-86 09:58:04-PDT,1496;000000000000 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Tue 12 Aug 86 09:57:38-PDT Received: by ucbvax.Berkeley.EDU (5.53/1.16) id AA12208; Tue, 12 Aug 86 09:36:29 PDT Received: by olympus.SGI (5.15/5.6) id AA05112; Mon, 11 Aug 86 16:21:32 PDT Date: Mon, 11 Aug 86 13:38:16 pst From: michael zyda Message-Id: <8608112138.AA11895@nps-cs> To: olympus!sumex-aim.arpa!info-iris Subject: IRIS User's Group Meeting IRIS USERS GROUP MEETING AT SIGGRAPH IN DALLAS ***** First Annual Meeting IRIS User Group SIGGRAPH '86 Dallas Convention Center, Room N230 Wednesday, August 20, 1986 4-6 p.m. Be in on the ground floor of establishing the IRIS User Group. Contact other IRIS users. Exchange software. Bring your software and show it at the IRIS User Software Forum. Meet Silicon Graphics' executive, engineering and marketing staff. Look into the future of the IRIS. Program Highlights Meeting of IRIS Users Feedback To Silicon Graphics Executives IRIS Application Talk - Solid Modeler & Ray Tracer Research on IRIS User Interface Silicon Graphics Future Directions, Dr. James Clark, Founder, Chairman of the Board IRIS User Software Forum & Cocktail Party Demo of IRIS 3-D Exploratorium To reserve a machine for the IRIS Software Forum, or for additional information, please call Zsuzsanna Molnar at Silicon Graphics, 415- 960-1980 ext 698. 12-Aug-86 12:19:19-PDT,1250;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Tue 12 Aug 86 12:18:57-PDT Date: Mon, 11 Aug 86 13:33:14 pst From: michael zyda Message-Id: <8608112133.AA11857@nps-cs> To: info-iris@sumex-aim Subject: IRIS User's Group Meeting... IRIS USERS GROUP MEETING AT SIGGRAPH IN DALLAS ***** First Annual Meeting IRIS User Group SIGGRAPH '86 Dallas Convention Center, Room N230 Wednesday, August 20, 1986 4-6 p.m. Be in on the ground floor of establishing the IRIS User Group. Contact other IRIS users. Exchange software. Bring your software and show it at the IRIS User Software Forum. Meet Silicon Graphics' executive, engineering and marketing staff. Look into the future of the IRIS. Program Highlights Meeting of IRIS Users Feedback To Silicon Graphics Executives IRIS Application Talk - Solid Modeler & Ray Tracer Research on IRIS User Interface Silicon Graphics Future Directions, Dr. James Clark, Founder, Chairman of the Board IRIS User Software Forum & Cocktail Party Demo of IRIS 3-D Exploratorium To reserve a machine for the IRIS Software Forum, or for additional information, please call Zsuzsanna Molnar at Silicon Graphics, 415- 960-1980 ext 698. 12-Aug-86 16:48:47-PDT,980;000000000000 Return-Path: Received: from diablo.stanford.edu by SUMEX-AIM.ARPA with TCP; Tue 12 Aug 86 16:48:17-PDT Received: by diablo.stanford.edu with Sendmail; Tue, 12 Aug 86 16:48:53 pdt Date: Tue, 12 Aug 86 16:48:53 pdt From: Bruce Duncan Subject: TCP/IP To: info-iris@sumex Greetings, IRIS users. Here at Stanford I'm trying to write some network code using TCP-IP so that the IRIS can talk to our XEROX lisp machines. I'm having some problems using the "accept" routine which accepts network connections. In 4.2bsd UNIX, the accept routine returns a NEW socket for use by child processes. On the IRIS this doesn't seem to happen. Does anyone know how to get the child process connected to the original request thus leaving the parent process free to service new requests? The 4.2bsd implementation is so simple. I hope the IRIS implementation isn't too complicated. Bruce Duncan duncan@sumex-aim bsd@diablo 12-Aug-86 16:51:47-PDT,301;000000000000 Return-Path: Received: from diablo.stanford.edu by SUMEX-AIM.ARPA with TCP; Tue 12 Aug 86 16:51:01-PDT Received: by diablo.stanford.edu with Sendmail; Tue, 12 Aug 86 16:51:39 pdt Date: Tue, 12 Aug 86 16:51:39 pdt From: Bruce Duncan To: info-iris@sumex 14-Aug-86 13:24:30-PDT,707;000000000000 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Thu 14 Aug 86 13:23:53-PDT Received: by ucbvax.Berkeley.EDU (5.53/1.16) id AA00915; Thu, 14 Aug 86 13:22:11 PDT Received: by olympus.SGI (5.15/5.6) id AA07535; Thu, 14 Aug 86 13:17:52 PDT Date: Wed, 13 Aug 86 22:18:25 pst From: michael zyda Message-Id: <8608140618.AA10024@nps-cs> To: olympus!sumex-aim.arpa!info-iris Subject: IRIS Polygon fill... Does anyone have a nice routine that decomposes concave polygons into convex ones the IRIS can fill? zyda@nps-cs.arpa ucbvax!olympus!nps-cs!zyda Michael Zyda 15-Aug-86 13:04:00-PDT,1347;000000000000 Return-Path: Received: from USNA.ARPA by SUMEX-AIM.ARPA with TCP; Fri 15 Aug 86 13:03:37-PDT Date: Fri, 15 Aug 86 13:59:58 EDT From: Dfr@USNA.ARPA To: Info-Iris@sumex-aim.ARPA cc: dfr@USNA.ARPA Subject: 3.4 Installation Funny and games: The installation instructions that come with 3.4 are both wrong and incomplete. Wrong -- You cannot complete an installation in multi-user mode if you have the tcp option. Incomplete -- There is a tacit assumption that you are using the C-shell. The installation doesnot work correctly if you are using a Bourne shell. The following finally worked for me. Make the following changes/additions to the installation document before starting. No guarentees for your installation. page 3 item 1. Make sure the system is in single-user mode. page 3 item 2 Make sure you are in the root directory cd / pwd page 4 item 6. Before the set path command make sure you are using the csh. If any doubt, type csh Now set the path as specified Make sure that usr is mounted. /etc/mount /dev/md0c /usr page 6 item 13. After Verify make sure you exit the C-shell. Type exit 15-Aug-86 14:39:41-PDT,918;000000000000 Return-Path: Received: from CSNET-RELAY.ARPA by SUMEX-AIM.ARPA with TCP; Fri 15 Aug 86 14:39:10-PDT Received: from omnitor.arpa by CSNET-RELAY.ARPA id aa02720; 15 Aug 86 16:45 EDT Received: by omnitor.ARPA id AA10068 at Fri, 15 Aug 86 16:38:48 edt Date: Fri, 15 Aug 86 16:38:48 edt From: Kevin Tureski Full-Name: Kevin Tureski Message-Id: <8608152038.AA10068@omnitor.ARPA> To: Info-Iris <@CSNET-RELAY.ARPA:Info-Iris@SUMEX-AIM.ARPA> Subject: Re: 3.4 Installation Tcp, multi-user and Bourne shell aside, I had a rough time installing 3.4 on our 2400T. As I recall, it did a complete MAKEDEV, and copied the old /dev to /tmp. It also copied shared text executables into /usr/tmp. Nor was I very impressed with the default /etc/bcheckrc and the rest of the /etc/*rc* files. Be careful and take a peek around afterwards. 19-Aug-86 02:41:24-PDT,532;000000000000 Return-Path: Received: from WISCVM.WISC.EDU by SUMEX-AIM.ARPA with TCP; Tue 19 Aug 86 02:41:06-PDT Received: from (MAILER)CRNLIMAP.BITNET by WISCVM.WISC.EDU on 08/18/86 at 09:51:00 CDT Received: by CRNLIMAP (Mailer X1.23b) id 1816; Mon, 18 Aug 86 08:34:13 EDT Date: Mon, 18 Aug 1986 08:33 EDT From: BILL MARTIN To: Please put me on your IRIS mailing list. Thanks -- Bill Martin 20-Aug-86 14:28:20-PDT,998;000000000000 Return-Path: Received: from sdcsvax.ucsd.edu by SUMEX-AIM.ARPA with TCP; Wed 20 Aug 86 14:24:36-PDT Received: by sdcsvax.ucsd.edu (5.31/4.42) id AA00258; Mon, 18 Aug 86 21:03:30 PDT hops=0 Received: by sdchema.chem.ucsd.edu (5.44) id AA05010; Mon, 18 Aug 86 15:24:02 PDT Received: by sdchemf.chem.ucsd.arpa (4.12) id AA13766; Mon, 18 Aug 86 15:19:57 pdt Date: Mon, 18 Aug 86 15:19:57 pdt From: sd%chem@sdcsvax.ucsd.edu (Steve Dempsey) Message-Id: <8608182219.AA13766@sdchemf.chem.ucsd.arpa> To: Info-Iris@sumex-aim.arpa Subject: bug in 3.4 version of swapinterval A new bug has been introduced in the 3.4 distribution with regards to the swapinterval, i.e., the minimum number of times a given buffer is refreshed between calls to 'swapbuffers()'. You now get one more refresh than you ask for. The default is now two refreshes, which you get from invoking swapinterval(1). You can get the maximum swapping rate by invoking swapinterval(0). 24-Aug-86 22:25:35-PDT,97178;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Sun 24 Aug 86 22:23:32-PDT Date: Sun, 24 Aug 86 22:23:47 pst From: michael zyda Message-Id: <8608250623.AA03158@nps-cs> To: info-iris@sumex-aim Subject: Help with Iris fonts... Several people have asked me how to put up special fonts on the Iris. Here are some sample routines and fonts you may find helpful... zyda@nps-cs.arpa ucbvax!olympus!nps-cs!zyda The following software is a way of getting new fonts up on the Iris... Files: -rw-r--r-- 1 zyda 6597 Oct 18 1985 fontdef.c -rw-r--r-- 1 zyda 1746 Oct 18 1985 fontdef.extern -rw-r--r-- 1 zyda 1692 Oct 18 1985 fontdef.h -rw-r--r-- 1 zyda 11953 Oct 18 1985 fontedit.c -rw-r--r-- 1 zyda 1654 Oct 18 1985 fonttest.c Font files: r610.iris means Roman (r) 6 lines per inch, 10 chars per inch. s610.iris means Sans Serif t610.iris means Typewriter I have all of the following fonts. I am only attaching a few samples. You want the rest, send me an electronic address and I will forward the appropriate ones... Note: the files can be edited and characters cut out. -rw-r--r-- 1 zyda 22794 Oct 18 1985 la610.iris -rw-r--r-- 1 zyda 22465 Oct 18 1985 la612.iris -rw-r--r-- 1 zyda 26309 Oct 18 1985 mo610.iris -rw-r--r-- 1 zyda 25686 Oct 18 1985 mo612.iris -rw-r--r-- 1 zyda 23656 Oct 18 1985 mt610.iris -rw-r--r-- 1 zyda 22266 Oct 18 1985 mt612.iris -rw-r--r-- 1 zyda 85130 Jun 27 1985 r35.iris -rw-r--r-- 1 zyda 25393 Oct 18 1985 r610.iris -rw-r--r-- 1 zyda 25280 Oct 18 1985 r612.iris -rw-r--r-- 1 zyda 19487 Oct 18 1985 r810.iris -rw-r--r-- 1 zyda 19472 Oct 18 1985 r812.iris -rw-r--r-- 1 zyda 25547 Oct 18 1985 rb610.iris -rw-r--r-- 1 zyda 25362 Oct 18 1985 rb612.iris -rw-r--r-- 1 zyda 19650 Oct 18 1985 rb810.iris -rw-r--r-- 1 zyda 19570 Oct 18 1985 rb812.iris -rw-r--r-- 1 zyda 28704 Oct 18 1985 rs610.iris -rw-r--r-- 1 zyda 26553 Oct 18 1985 rs612.iris -rw-r--r-- 1 zyda 20353 Oct 18 1985 rs810.iris -rw-r--r-- 1 zyda 20015 Oct 18 1985 rs812.iris -rw-r--r-- 1 zyda 52464 Oct 18 1985 ru610.iris -rw-r--r-- 1 zyda 37384 Oct 18 1985 ru612.iris -rw-r--r-- 1 zyda 28879 Oct 18 1985 ru810.iris -rw-r--r-- 1 zyda 28800 Oct 18 1985 ru812.iris -rw-r--r-- 1 zyda 8773 Jul 11 12:58 s1225.iris -rw-r--r-- 1 zyda 81005 Jun 27 1985 s35.iris -rw-r--r-- 1 zyda 25458 Oct 18 1985 s610.iris -rw-r--r-- 1 zyda 25459 Oct 18 1985 s612.iris -rw-r--r-- 1 zyda 19514 Oct 18 1985 s810.iris -rw-r--r-- 1 zyda 19080 Oct 18 1985 s812.iris -rw-r--r-- 1 zyda 12166 Jul 11 12:57 s825.iris -rw-r--r-- 1 zyda 25902 Oct 18 1985 sb610.iris -rw-r--r-- 1 zyda 25600 Oct 18 1985 sb612.iris -rw-r--r-- 1 zyda 19669 Oct 18 1985 sb810.iris -rw-r--r-- 1 zyda 19617 Oct 18 1985 sb812.iris -rw-r--r-- 1 zyda 13012 Jul 11 12:59 sb822.iris -rw-r--r-- 1 zyda 27964 Oct 18 1985 si610.iris -rw-r--r-- 1 zyda 26521 Oct 18 1985 si612.iris -rw-r--r-- 1 zyda 20305 Oct 18 1985 si810.iris -rw-r--r-- 1 zyda 20282 Oct 18 1985 si812.iris -rw-r--r-- 1 zyda 28180 Oct 18 1985 ss610.iris -rw-r--r-- 1 zyda 26216 Oct 18 1985 ss612.iris -rw-r--r-- 1 zyda 20077 Oct 18 1985 ss810.iris -rw-r--r-- 1 zyda 19957 Oct 18 1985 ss812.iris -rw-r--r-- 1 zyda 53820 Oct 18 1985 su610.iris -rw-r--r-- 1 zyda 44299 Oct 18 1985 su612.iris -rw-r--r-- 1 zyda 33869 Oct 18 1985 su810.iris -rw-r--r-- 1 zyda 30160 Oct 18 1985 su812.iris -rw-r--r-- 1 zyda 85119 Jun 27 1985 t35.iris -rw-r--r-- 1 zyda 25619 Oct 18 1985 t610.iris -rw-r--r-- 1 zyda 25567 Oct 18 1985 t612.iris -rw-r--r-- 1 zyda 19877 Oct 18 1985 t810.iris -rw-r--r-- 1 zyda 19835 Oct 18 1985 t812.iris -rw-r--r-- 1 zyda 25992 Oct 18 1985 tb610.iris -rw-r--r-- 1 zyda 25703 Oct 18 1985 tb612.iris -rw-r--r-- 1 zyda 21242 Oct 18 1985 tb810.iris -rw-r--r-- 1 zyda 19985 Oct 18 1985 tb812.iris -rw-r--r-- 1 zyda 29217 Oct 18 1985 ts610.iris -rw-r--r-- 1 zyda 26628 Oct 18 1985 ts612.iris -rw-r--r-- 1 zyda 20865 Oct 18 1985 ts810.iris -rw-r--r-- 1 zyda 20341 Oct 18 1985 ts812.iris -rw-r--r-- 1 zyda 46761 Oct 18 1985 tu610.iris -rw-r--r-- 1 zyda 33300 Oct 18 1985 tu612.iris -rw-r--r-- 1 zyda 35095 Oct 18 1985 tu810.iris -rw-r--r-- 1 zyda 25303 Oct 18 1985 tu812.iris ************** file fontdef.c ********** /* this is an IRIS-2400 program */ /* this is file fontdef.c It defines a new raster character font. It reads a specified font from a font file. */ #include #include "gl.h" #include "fontdef.h" /* get the declarations for the font */ fontdef(fontnum,filename) long fontnum; /* you select the number you want to call this guy */ char filename[];/* passed in file name */ { long i,j,k; /* temp loop index */ long jj; /* temp loop variable */ FILE *rfp; /* file pointer for the font file */ char charval; /* temp char value */ long width,height; /* size of this bitmap (real size) */ long xoffset,yoffset;/* xoffset and yoffset for the char*/ long skipwidth; /* amount to skip after this char is in */ char tmp[150]; /* temp char array */ long words; /* number of words per row */ long icnt; /* temp counter to read in the bitmaps */ /* clear the char table... */ for(i=0; i < 128; i=i+1) { chars[i].offset=0; /* no space for this char def */ chars[i].w=0; /* bitmap is zero in width */ chars[i].h=0; /* bitmap is zero in height */ chars[i].xoff=0; /* no x offset */ chars[i].yoff=0; /* no y offset */ chars[i].width=0; /* no skip width */ chardefined[i] = FALSE; } /* clear the raster array */ for(i=0; i < MAXRASTER; i=i+1) { raster[i]=0; } /* no max width yet... */ maxwidth=0; /* open the named font file */ rfp=fopen(filename,"r"); if(rfp == NULL) { printf("FONTDEF: cannot open file %s!\n",filename); exit(1); } /* read the max height in pixels */ fscanf(rfp,"%d",&maxheight); /* scan past the end of the line */ fgets(tmp,150,rfp); /* say that we havent used any raster space yet */ rptr = -1; /* read until we run out of file */ while(TRUE) { /* get a char def line */ i=fscanf(rfp,"%c %d %d %d %d %d",&charval,&width,&height, &xoffset,&yoffset,&skipwidth); /* scan past the end of the line */ fgets(tmp,150,rfp); if(i <= 0) { /* eof */ break; } /* we have a character def... */ /* do we have a new max width? */ if(width > maxwidth) { maxwidth=width; } /* we have a character def */ j=charval; /* say the char spot is defined */ chardefined[j]= TRUE; chars[j].offset=rptr+1; /* start of this bit map */ chars[j].w=width; /* width of this bitmap */ chars[j].h=height; /* height of this bit map */ chars[j].xoff=xoffset; /* x offset for the char */ chars[j].yoff=yoffset; /* y offset for the char */ chars[j].width=skipwidth; /* skip this many pixels after you draw the char */ /* we need to read 'height' rows of data. the first row we read is the last one to go into array raster. */ /* compute number of words per row */ words = ((width-1)/16)+1; /* the total space we need is i times height */ i=words*height; /* read each row... */ icnt = -1; for(k=0; k < height; k=k+1) { icnt=icnt+1; /* we read across the row but its backwards... */ for(jj=1; jj <= words; jj=jj+1) { fscanf(rfp,"%4x",&temp[icnt+words-jj]); } icnt=icnt+words-1; /* skip past end of line */ fgets(tmp,150,rfp); } /* reverse the values in the temp array */ for(k=i-1; k >= 0; k=k-1) { rptr=rptr+1; raster[rptr]=temp[k]; } } /* end while there are char defs in the file */ /* check to see if we wrote past the end of raster... */ if(rptr >= MAXRASTER) { printf("FONTDEF: We have written beyond the end of array raster!\n"); exit(1); } /* call routine to set up raster font definition */ /* fontnum = the font number to use to call up this font. maxheight = the max height in pixels of characters in this font. 128 = the number of characters in this font. chars = the character table. rptr+1 = the number of words in array raster. raster = the bit maps for the chars. */ defrasterfont(fontnum,maxheight,128,chars,rptr+1,raster); fclose(rfp); } /* this is file fontdefout.c it writes out the font in array raster */ fontdefout(filename) char filename[];/* passed in file name */ { long i,j,k; /* temp loop index */ long jj; /* temp loop variable */ FILE *wfp; /* file pointer for the font file */ long charval; /* temp char value */ long words; /* number of words per row */ long icnt; /* temp counter to read in the bitmaps */ /* open the named font file */ wfp=fopen(filename,"w"); if(wfp == NULL) { printf("FONTDEFOUT: cannot open file %s!\n",filename); exit(1); } /* write the max height in pixels */ fprintf(wfp,"%d\n",maxheight); /* for all possible chars...*/ for(charval=0; charval < 128; charval=charval+1) { /* is the char defined ? */ if(!chardefined[charval]) { continue; /* skip this guy */ } /* we have a character def... */ /* output the table values to the file */ fprintf(wfp,"%c %d %d %d %d %d\n", charval,chars[charval].w,chars[charval].h, chars[charval].xoff,chars[charval].yoff, chars[charval].width); /* we need to read 'height' rows of data. the first row we read is the last one to go into array raster. */ /* compute number of words per row */ words = ((chars[charval].w -1)/16)+1; /* the total space we need is i times height */ i=words*chars[charval].h; /* read the words from raster and put into temp reversed */ icnt=chars[charval].offset -1; for(k=i-1; k >=0; k=k-1) { icnt=icnt+1; temp[k]=raster[icnt]; } /* write out each row */ icnt = -1; for(k=0; k < chars[charval].h; k=k+1) { icnt=icnt+1; /* we read across the row but its backwards... */ for(jj=1; jj <= words; jj=jj+1) { fprintf(wfp,"%04x",temp[icnt+words-jj]); } fprintf(wfp,"\n"); icnt=icnt+words-1; } } /* endfor all chars... */ fclose(wfp); } ********** end of file fontdef.c ********** ********** start of file fontdef.extern ********** /* this is an IRIS-2400 Program. This is file fontdef.extern It contains the external declarations for routine fontdef so that other functions can access the font definition data arrays. */ #define MAXRASTER 16384 /* max number of raster words available */ /* We compute this value in the following fashion: The maxwidth of each char is computed in 16 bit words. That value is multiplied by the maxheight. That value is then multiplied by 128 chars in the set. For example, 48 bit by 48 bit chars need 18432 raster spots. 64 bit by 64 bit chars need 32768 raster spots. */ /* Al Casarez of SGI says there are only 16K words available... */ extern Fontchar chars[128]; /* the Font table */ extern unsigned short raster[MAXRASTER]; /* the raster defs for this font */ extern long maxheight; /* the max pixel height for this font */ extern long maxwidth; /* the max pixel width for this font */ extern long chardefined[128]; /* TRUE if the char is defined, FALSE otherwise */ extern long rptr; /* the last written spot in array raster */ extern unsigned long temp[1000]; /* this array is used to reverse the char defs. It must equal maxwidth in 16 bit words times maxheight. 256 is good for max 64 by 64 chars. */ ********** end of file fontdef.extern ********** ********** start of file fontdef.h ********* /* this is an IRIS-2400 Program. This is file fontdef.h It contains the external declarations for routine fontdef so that other functions can access the font definition data arrays. */ #define MAXRASTER 16384 /* max number of raster words available */ /* We compute this value in the following fashion: The maxwidth of each char is computed in 16 bit words. That value is multiplied by the maxheight. That value is then multiplied by 128 chars in the set. For example, 48 bit by 48 bit chars need 18432 raster spots. 64 bit by 64 bit chars need 32768 raster spots. */ /* Al Casarez of SGI says there are only 16K words available... */ Fontchar chars[128]; /* the Font table */ unsigned short raster[MAXRASTER]; /* the raster defs for this font */ long maxheight; /* the max pixel height for this font */ long maxwidth; /* the max pixel width for this font */ long chardefined[128]; /* TRUE if the char is defined, FALSE otherwise */ long rptr; /* the last written spot in array raster */ unsigned long temp[1000]; /* this array is used to reverse the char defs. It must equal maxwidth in 16 bit words times maxheight. 256 is good for max 64 by 64 chars. */ ********** end of file fontdef.h ********* ********** start of file fontedit.c ********** /* this is an IRIS-2400 program */ /* this is file fontedit.c Its purpose is to edit any char in any font file. The mouse button is then used to set and unset the bits of that map. It puts up any previous character definition associated with the specified correspondence character... */ #include "gl.h" #include "device.h" #include #include "fontdef.extern" #define LIFTROW 2 #define LIFTCOL 2 #define MAXROWS 64 #define MAXCOLS 64 long on[MAXCOLS][MAXROWS]; /* array indicating which spots are on */ Tag tag[MAXCOLS][MAXROWS]; /* tags for the color spots */ main() { Object pixelobj; /* the object that has the pixel description */ Object smallchar; /* actual size view of the char */ Colorindex wmask; /* the standard writemask guy */ long i,j; /* temp loop vars */ char tchar; /* the character this definition will correspond to */ float xtmp,ytmp; /* loc. of the mouse device */ char filename[100]; /* temp array for the filename */ long realwidth; /* width of char plus (a boundary of 2) */ long realheight; /* height of char plus a boundary of 2 */ float orthowidth,orthoheight; /* values passed to ortho2 */ long device; /* returned device from the event queue */ short value; /* value returned from the event queue */ /* get the character we are defining from the terminal */ /* when the font that uses this definition is selected, and this character is passed by way of 'charstr', the new definition is what will appear...*/ printf("Enter the correspondence character: "); scanf("%c",&tchar); /* ask for the font file */ printf("Enter font filename: "); scanf("%s",filename); /* init graphics */ ginit(); /* read in the font file */ fontdef(1,filename); /* get this chars bitmap out of the array */ getthebitmap(tchar,&realwidth,&realheight,&orthowidth,&orthoheight); /* put into doublebuffer mode */ doublebuffer(); /* configure the iris */ gconfig(); /* writemask... */ wmask=(1<> position; /* mask out the high bits */ temp=temp & 0x0001; return(temp); } /* set bits in a short word */ bset(shrt,position) short *shrt; long position; { unsigned short temp; temp=1; temp= temp << position; /* shift left the bit */ *shrt = *shrt | temp; } /* getthebitmap.c The purpose of this routine is to pull the bitmap out of the raster array and put it into array on. */ getthebitmap(tchar,realwidth,realheight,orthowidth,orthoheight) char tchar; /* the character we are examining */ long *realwidth; /* the returned width of the displayed bitmap*/ long *realheight; /* the returned height of the displayed bitmap */ float *orthowidth; /* the value used for the ortho call */ float *orthoheight;/* the value used for the ortho call */ { long i,j,k; /* temp loop variables */ long icnt; /* a temp loop variable */ long words; /* how many words across the row is */ long btest(); /* bit test function */ /* clear out the bitmap before we use it... */ for(j=0; j < MAXROWS; j=j+1) { for(i=0; i < MAXCOLS; i=i+1) { on[i][j]=0; } } /* if the char is not defined... */ if(!chardefined[tchar]) { /* stick in some values into the table */ chars[tchar].w=chars[' '].w; chars[tchar].h=chars[' '].h; chars[tchar].xoff=0; chars[tchar].yoff=0; chars[tchar].width=chars[' '].width; chars[tchar].offset=rptr+1; chardefined[tchar]=TRUE; } /* peel out the bits from raster corresponding to tchar */ /* get the number of words in the bitmap */ words=((chars[tchar].w -1)/16)+1; /* get starting loc of the bitmap minus 1 */ icnt=chars[tchar].offset -1; /* for all the rows of the bitmap */ for(j=0; j < chars[tchar].h; j=j+1) { for(k=0; k < words; k=k+1) { icnt=icnt+1; /* get next raster word */ for(i=k*16; i < chars[tchar].w && i < ((k*16)+16); i=i+1) { on[i+LIFTCOL][j+LIFTROW]=btest(raster[icnt],((k*16)+15-i)); } } } /* compute the width and height plus a boundary of 2 */ *realwidth=chars[tchar].w+4; *realheight=chars[tchar].h+4; if(maxheight >= maxwidth) { *orthoheight=maxheight+4; *orthowidth= *orthoheight/0.75; } else { *orthowidth=maxwidth+4; *orthoheight= *orthowidth*0.75; } } /* putthebitmap.c This routine puts out the drawn bitmap into array raster */ putthebitmap(tchar,realwidth,realheight) char tchar; /* the current char */ long realwidth; /* the actual width of the bitmap */ long realheight; /* the actual height of the bitmap*/ { long mincol,maxcol,minrow,maxrow; /* the bounds of the bitmap */ long i,j,k; /* temp loop variables */ long newwidth,newheight; /* new dimensioans of the bitmap */ long words; /* the width of the bitmap in words */ /* find the chars bits in the array */ mincol = MAXCOLS; minrow = MAXROWS; maxcol = -1; maxrow = -1; /* find the boundary of the bitmap */ for(i=0; i < realwidth; i=i+1) { for(j=0; j < realheight; j=j+1) { if(on[i][j] == 1) { if(i > maxcol) { maxcol=i; } if(i < mincol) { mincol=i; } if(j > maxrow) { maxrow=j; } if(j < minrow) { minrow=j; } } } /* endfor j */ } /* endfor i */ /* compute newwidth and height */ newwidth=maxcol-mincol+1; newheight=maxrow-minrow+1; /* put new bitmap into raster */ /* save first write spot */ chars[tchar].offset=rptr+1; /* compute number of words required */ words=((newwidth -1)/16)+1; /* for all the rows of the bitmap */ for(j=0; j < newheight; j=j+1) { for(k=0; k < words; k=k+1) { /* get next raster word */ rptr=rptr+1; raster[rptr]=0; for(i=k*16; i < newwidth && i < ((k*16)+16); i=i+1) { if(on[i+mincol][j+minrow] == 1) { /* set the bit in the raster word */ bset(&raster[rptr],((k*16)+15-i)); } } /* endfor i... */ } /* endfor k ... */ } /* endfor j... */ /* put rest of data into chars table */ chars[tchar].w=newwidth; chars[tchar].h=newheight; } ********** end of file fontedit.c ********** *********** start of file fonttest.c ********** /* this is an IRIS-2400 program */ /* this is file fonttest.c It tests the font defined in routine fontdef (file fontdef.c) */ #include "gl.h" #include "device.h" main() { Object textobj; /* the text to display is in this object */ Colorindex wmask; /* write mask variable */ char filename[100]; /* input filename holding a font def */ printf("Enter font filename: "); scanf("%s",filename); /* init the graphics system */ ginit(); /* put in doublebuffer mode */ doublebuffer(); /* configure the iris */ gconfig(); /* writemask... */ wmask=((1< 22 33 4 -4 30 e0000000 f0000000 fc000000 7e000000 3f000000 0f800000 07e00000 03f00000 01f80000 007e0000 003f0000 001f8000 0007c000 0003f000 0001f800 0000fc00 00003c00 0000fc00 0001f800 0003f000 0007c000 001f8000 003f0000 007e0000 01f80000 03f00000 07e00000 0f800000 3f000000 7e000000 fc000000 f0000000 e0000000 ? 21 34 4 0 30 07fe0000 3fffc000 7ffff000 fe07f000 fc00f800 fc007800 fc007800 fc007800 7800f800 0000f800 0003f000 003fe000 00ffc000 01ff8000 01f00000 01c00000 01c00000 01c00000 01c00000 01c00000 01c00000 01c00000 01c00000 01c00000 00000000 00000000 00000000 00000000 01e00000 03f00000 03f00000 03f00000 03f00000 01e00000 @ 26 34 2 0 30 007f8000 01ffe000 03fff000 07e1f800 0f807c00 1f003e00 3e3f1f00 3c7f8f00 78ffc780 79f3e780 73e1fb80 f3c0fbc0 f7807bc0 e78079c0 e70039c0 e70039c0 e70039c0 e70039c0 e70039c0 e70039c0 e78079c0 f7807bc0 f3c0fbc0 73e1fb80 79f3ff80 78ffff80 3c7f9f00 3e3f1f00 1f0001c0 0f8007c0 07e07fc0 03ffff80 01fffe00 007fe000 A 32 33 0 0 30 0003c000 0003c000 0003c000 0007c000 0007e000 0007e000 000fe000 000ff000 000ff000 001ff000 001ef800 001cf800 003cf800 003c7c00 00387c00 00787c00 00783e00 00703e00 00f03e00 00f01f00 01ffff00 01ffff80 01ffff80 03c00f80 03c007c0 038007c0 078007c0 078003e0 0f0003e0 1f0003f0 ffe01fff ffe01fff ffe01fff B 28 33 1 0 30 fffff800 fffffe00 ffffff00 0f803f80 0f800fc0 0f8007c0 0f8007e0 0f8003e0 0f8003e0 0f8003e0 0f8003e0 0f8007e0 0f8007c0 0f800fc0 0f803f80 0fffff00 0fffff00 0fffff80 0f801fc0 0f8007e0 0f8003e0 0f8003f0 0f8001f0 0f8001f0 0f8001f0 0f8001f0 0f8003f0 0f8003e0 0f8007e0 0f801fc0 ffffff80 ffffff00 fffffc00 C 26 33 2 0 30 001fe1c0 00fff1c0 01fffdc0 07f87fc0 0fe03fc0 0fc00fc0 1f800fc0 3f0007c0 3e0007c0 7e0003c0 7c0003c0 7c0001c0 fc0001c0 f80001c0 f8000000 f8000000 f8000000 f8000000 f8000000 f80001c0 fc0001c0 7c0001c0 7c0003c0 7e0003c0 3e000780 3f000780 1f800f00 0fc00f00 0fe03e00 07f87e00 01fffc00 00fff000 001fe000 D 28 33 0 0 30 ffff8000 fffff000 fffff800 0f81fe00 0f807f00 0f803f00 0f801f80 0f800fc0 0f8007c0 0f8007e0 0f8003e0 0f8003e0 0f8003f0 0f8001f0 0f8001f0 0f8001f0 0f8001f0 0f8001f0 0f8001f0 0f8001f0 0f8003f0 0f8003e0 0f8003e0 0f8007e0 0f8007c0 0f800fc0 0f801f80 0f803f00 0f807f00 0f81fe00 fffff800 fffff000 ffff8000 E 27 33 1 0 30 ffffff80 ffffff80 ffffff80 0f803f80 0f800780 0f8007c0 0f8003c0 0f8003c0 0f80e3c0 0f80e1c0 0f80e1c0 0f80e1c0 0f81e000 0f81e000 0fffe000 0fffe000 0fffe000 0f81e000 0f81e000 0f80e0e0 0f80e0e0 0f80e0e0 0f80e1e0 0f8001e0 0f8001e0 0f8001e0 0f8003e0 0f8003c0 0f8007c0 0f803fc0 ffffffc0 ffffffc0 ffffffc0 F 27 33 0 0 30 ffffffc0 ffffffc0 ffffffc0 07c01fc0 07c003c0 07c003e0 07c001e0 07c001e0 07c001e0 07c070e0 07c070e0 07c070e0 07c07000 07c0f000 07c0f000 07fff000 07fff000 07fff000 07c0f000 07c0f000 07c07000 07c07000 07c07000 07c07000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 fffe0000 fffe0000 fffe0000 G 27 33 2 0 30 003f8700 00ffe700 03fff700 07f1ff00 0fc07f00 1f803f00 1f001f00 3f001f00 7e000f00 7e000f00 7c000f00 fc000700 fc000700 f8000700 f8000000 f8000000 f8000000 f8000000 f8000000 f803ffe0 fc03ffe0 fc03ffe0 7c001f00 7e001f00 7e001f00 3f001f00 1f001f00 1f801f00 0fc03f00 07f0ff00 03ffff00 00ffff00 003fc700 H 30 33 0 0 30 fff87ffc fff87ffc fff87ffc 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0fffffc0 0fffffc0 0fffffc0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 fff87ffc fff87ffc fff87ffc I 25 33 3 0 30 ffffff80 ffffff80 ffffff80 007f0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 003e0000 007f0000 ffffff80 ffffff80 ffffff80 J 26 33 4 0 30 007fffc0 007fffc0 007fffc0 0003f800 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 0001f000 7801f000 fc01f000 fc01f000 fc03f000 fc07f000 fe1fe000 7fffc000 3fff8000 0ffe0000 K 30 33 0 0 30 fff83ff8 fff83ff8 fff83ff8 0f801fc0 0f801f00 0f803e00 0f807c00 0f80f800 0f81f000 0f83e000 0f83c000 0f878000 0f8f8000 0f9f0000 0fbf0000 0fff8000 0fffc000 0ff7c000 0ff3e000 0fe3e000 0fc1f000 0f81f000 0f80f800 0f80f800 0f807c00 0f803e00 0f803e00 0f801f00 0f801f80 0f800fc0 fff87ffc fff87ffc fff87ffc L 28 33 0 0 30 fffe0000 fffe0000 fffe0000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00000 07c00070 07c00070 07c00070 07c000f0 07c000f0 07c000f0 07c000f0 07c001f0 07c001e0 07c007e0 07c01fe0 ffffffe0 ffffffe0 ffffffe0 M 28 33 1 0 30 fe0007f0 fe0007f0 ff000ff0 1f000f80 1f000f80 1f800f80 1f801f80 1f801f80 1f801f80 1fc03f80 1fc03f80 1fc03f80 1fe07f80 1fe07f80 1de07780 1df07780 1df0f780 1cf0f780 1cf0e780 1cf9e780 1cf9e780 1c79c780 1c7fc780 1c7fc780 1c3f8780 1c3f8780 1c3f8780 1c1f8780 1c1f0780 3e1f0780 ff9f3ff0 ff8e3ff0 ff8e3ff0 N 29 33 1 0 30 ff003ff8 ff803ff8 ffc03ff8 0fc007c0 0fe00380 0fe00380 0ff00380 0ef80380 0ef80380 0e7c0380 0e7c0380 0e3e0380 0e1f0380 0e1f0380 0e0f8380 0e0f8380 0e07c380 0e03e380 0e03e380 0e01f380 0e01f380 0e00fb80 0e007f80 0e007f80 0e003f80 0e003f80 0e001f80 0e000f80 0e000f80 1f000780 ffe00780 ffe00380 ffe00380 O 24 33 3 0 30 03ffc000 1ffff800 3ffffc00 7f81fe00 7c003e00 7c003e00 7c003e00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 7c003e00 7c003e00 7c003e00 7f81fe00 3ffffc00 1ffff800 03ffc000 P 27 33 1 0 30 fffff800 fffffe00 ffffff00 0f803f80 0f800fc0 0f8007c0 0f8007e0 0f8003e0 0f8003e0 0f8003e0 0f8003e0 0f8007e0 0f8007c0 0f800fc0 0f803f80 0fffff00 0ffffe00 0ffff800 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 0f800000 fff80000 fff80000 fff80000 Q 26 42 3 -9 30 03ffc000 1ffff800 3ffffc00 7f81fe00 7c003e00 7c003e00 7c003e00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8001f00 f8ff1f00 f9ff9f00 f9ff9f00 fbc3df00 7fc3fe00 7f81fe00 7f83fe00 7f83fe00 3ffffc00 1ffff800 03ffc1c0 000381c0 000781c0 000783c0 000783c0 0007c7c0 0003ff80 0003ff80 0001ff00 0000fe00 R 29 33 0 0 30 ffffe000 fffff800 fffffe00 0f80ff00 0f803f80 0f801f80 0f800fc0 0f8007c0 0f8007c0 0f8007c0 0f8007c0 0f800fc0 0f801f80 0f803f80 0f80ff00 0ffffe00 0ffff800 0ffff000 0f81f800 0f80fc00 0f807c00 0f803c00 0f803e00 0f803e00 0f803e00 0f803e00 0f803e38 0f803e38 0f803f38 0f803f78 fff81ff8 fff80ff0 fff807e0 S 24 33 3 0 30 03fe0e00 0fffce00 1fffee00 3f07fe00 7c00fe00 f8007e00 f8003e00 f0001e00 f0001e00 f8000e00 f8000e00 fe000e00 7f800000 7ffc0000 3fffc000 1ffff000 0ffff800 01fffc00 000ffe00 0000fe00 00003f00 e0001f00 e0001f00 e0000f00 f0000f00 f0000f00 f8001f00 fc001e00 ff007e00 ffe1fc00 effff800 e3fff000 e07fc000 T 27 33 2 0 30 7fffffc0 7fffffc0 7fffffc0 7f9f3fc0 7e1f0fc0 fc1f07e0 f81f03e0 f81f03e0 f01f01e0 f01f01e0 e01f00e0 e01f00e0 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 003f8000 07fffc00 07fffc00 07fffc00 U 32 33 0 0 30 fff807ff fff807ff fff807ff 0f8000f8 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f800070 0f8000f0 0fc000f0 07c000e0 07e001e0 03f003e0 03f807c0 01fe1f80 00ffff00 003ffe00 000ff800 V 32 33 0 0 30 fff807ff fff807ff fff807ff 0fc000f8 07c000f0 07c001e0 03e001e0 03e001c0 03e003c0 01f003c0 01f00380 00f80780 00f80780 00f80f00 007c0f00 007c0e00 007c1e00 003e1e00 003e1c00 003e3c00 001f3c00 001f3800 001f7800 000ff800 000ff000 000ff000 0007f000 0007e000 0007e000 0003e000 0003c000 0003c000 0003c000 W 30 33 0 0 30 fe0fc3fc fe0fc3fc fe0fc3fc 3e07c0f0 3e07c0f0 1e07c0e0 1e07c0e0 1e07c0e0 1f0fe1e0 1f0fe1e0 0f0fe1c0 0f0fe1c0 0f0fe1c0 0f9ff3c0 0f9ff3c0 079cf380 079cf380 079cf380 07fcff80 07fcff80 03f87f00 03f87f00 03f87f00 03f87f00 03f87f00 01f03e00 01f03e00 01f03e00 01f03e00 01f03e00 00e01c00 00e01c00 00e01c00 X 32 33 0 0 30 fff81fff fff81fff fff81fff 0fc003f0 07e007c0 01f00780 01f00f00 00f80f00 00f81e00 007c3e00 003e3c00 003e7800 001ff800 000ff000 000fe000 0007e000 0003e000 0007e000 0007f000 000ff000 001ff800 001e7c00 003c7c00 007c3e00 00781f00 00f01f00 00f00f80 01e00f80 03e007e0 0fc003f0 fff81fff fff81fff fff81fff Y 32 33 0 0 30 fff807ff fff807ff fff807ff 0fc001f8 07e001e0 01f003c0 01f003c0 00f80780 00f80f80 007c0f00 003e1e00 003e1e00 001f3c00 000fbc00 001ff000 000ff000 0007e000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 007ffc00 007ffc00 007ffc00 Z 24 33 3 0 30 3ffffe00 3fffff00 3ffffe00 3f803e00 3e007c00 7c00f800 7800f800 7801f000 7801f000 7003e000 7007c000 7007c000 000f8000 001f0000 001f0000 003e0000 007c0000 007c0000 00f80000 00f80700 01f00700 03e00700 03e00f00 07c00f00 0f800f00 0f800f00 1f001f00 1f001e00 3e003e00 7c01fe00 7ffffe00 fffffe00 7ffffe00 [ 13 44 14 -9 30 fff8 fff8 fff8 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 fff8 fff8 fff8 \ 24 45 3 -10 30 e0000000 e0000000 f0000000 f0000000 78000000 78000000 3c000000 3c000000 1e000000 1e000000 0f000000 0f000000 07800000 07800000 03c00000 03c00000 01e00000 01e00000 00f00000 00f00000 00780000 00780000 003c0000 003c0000 001e0000 001e0000 000f0000 000f0000 00078000 00078000 0003c000 0003c000 0001e000 0001e000 0000f000 0000f000 00007800 00007800 00003c00 00003c00 00001e00 00001e00 00000f00 00000f00 00000700 ] 13 44 4 -9 30 fff8 fff8 fff8 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 fff8 fff8 fff8 ^ 18 9 6 25 30 01e00000 03f00000 07f80000 0ffc0000 1ffe0000 7f3f8000 fc0fc000 f807c000 f003c000 _ 33 3 -1 -12 30 ffffffff8000 ffffffff8000 ffffffff8000 ` 8 16 10 18 30 0700 0f00 1f00 3e00 7c00 7800 f000 f000 e000 e000 fe00 ff00 ff00 7f00 7f00 3e00 a 27 21 3 0 30 07fe0000 3fff8000 7fffc000 7e07e000 7e03f000 7e01f000 3c00f000 0000f000 001ff000 01fff000 0ffff000 1ff8f000 3f80f000 7e00f0e0 f800f0e0 f000f0e0 f803f1e0 fc1ff9e0 7fffffc0 7fff7fc0 1ff83f80 b 25 34 2 0 30 1f000000 ff000000 ff000000 ff000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f1fc000 0f7ff000 0ffffc00 0ff8fe00 0fe03e00 0fc01f00 0f800f00 0f000f80 0f000780 0f000780 0f000780 0f000780 0f000780 0f000f80 0f800f00 0fc01f00 0fe03e00 0ff8fe00 0ffffc00 0e7ff000 0e1fc000 c 24 21 4 0 30 00ffc000 03fff800 0ffffc00 1fc0fc00 3f00fc00 7e00fc00 7c007800 f8000000 f8000000 f0000000 f0000000 f0000000 f8000000 f8000000 7c000700 7e000700 3f001f00 1fc07f00 0ffffe00 03fff800 00ffe000 d 25 34 3 0 30 0000f800 0007f800 0007f800 0007f800 00007800 00007800 00007800 00007800 00007800 00007800 00007800 00007800 00007800 01fc7800 07ff7800 1ffff800 3f8ff800 3e03f800 7c01f800 7800f800 f8007800 f0007800 f0007800 f0007800 f0007800 f0007800 f8007800 7800f800 7c01f800 3e03f800 3f8ff800 1fffff80 07ff7f80 01fc7f80 e 22 21 4 0 30 01ff0000 07ffc000 1fffe000 3f87f000 3e00f800 7c007800 78007c00 f8003c00 fffffc00 fffffc00 fffffc00 f0000000 f8000000 f8000000 7c001c00 7e001c00 3f003c00 1fc1fc00 0ffff800 03fff000 00ff8000 f 21 34 4 0 30 001fc000 007fe000 00fff000 00f8f800 01f1f800 01e1f800 01e1f800 01e1f800 01e0f000 01e00000 01e00000 01e00000 01e00000 ffffc000 ffffc000 ffffc000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 03f00000 ffffc000 ffffc000 ffffc000 g 27 30 2 -9 30 03fe7fc0 0fffffe0 1fffffe0 3f8fe3e0 7e03f1c0 7c01f000 7800f000 7800f000 7800f000 7c01f000 7e03f000 3f8fe000 3fffc000 7fff8000 7bfe0000 70000000 7c000000 7ffff000 3ffffe00 3fffff00 7fffff80 fc003fc0 f80007c0 f00003c0 f80007c0 fc000fc0 7f80ff80 3fffff00 1ffffe00 03ffe000 h 26 34 2 0 30 1f000000 ff000000 ff000000 ff000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f7fc000 0ffff000 0ffff800 0fe0fc00 0fc07c00 0f803c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 fff3ffc0 fff3ffc0 fff3ffc0 i 20 33 5 0 30 01c00000 03e00000 07f00000 07f00000 07f00000 03e00000 01c00000 00000000 00000000 00000000 00000000 00000000 07f00000 fff00000 fff00000 fff00000 01f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 01f80000 fffff000 fffff000 fffff000 j 14 42 5 -9 30 0070 00f8 01fc 01fc 01fc 00f8 0070 0000 0000 0000 0000 0000 00fc 1ffc 1ffc 1ffc 007c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 783c fc7c fc7c fcf8 fff0 7fe0 1fc0 k 26 34 2 0 30 1f000000 ff000000 ff000000 ff000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 0f03ffc0 0f03ffc0 0f03ffc0 0f01fe00 0f07f000 0f0fc000 0f1f8000 0f7e0000 0ffc0000 0ffe0000 0fff0000 0fdf8000 0f8f8000 0f07c000 0f07e000 0f03f000 0f01f000 0f00fc00 ffe1ffc0 ffe1ffc0 ffe1ffc0 l 20 34 5 0 30 07f00000 fff00000 fff00000 fff00000 01f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 00f00000 01f80000 fffff000 fffff000 fffff000 m 30 21 0 0 30 1ffc7f00 fffeff80 ffffffc0 ff9fe7e0 1f0fc3e0 1f07c1e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 1e0781e0 fffffffc fffffffc fffffffc n 26 21 2 0 30 1f7fc000 fffff000 fffff800 ffe0fc00 0fc07c00 0f803c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 fff3ffc0 fff3ffc0 fff3ffc0 o 26 21 2 0 30 00ffc000 03fff000 0ffffc00 1fe1fe00 3f003f00 7e001f80 7c000f80 f80007c0 f80007c0 f00003c0 f00003c0 f00003c0 f80007c0 f80007c0 7c000f80 7e001f80 3f003f00 1fe1fe00 0ffffc00 03fff000 00ffc000 p 25 30 2 -9 30 1f1fc000 ff7ff000 fffffc00 fff8fe00 0fe03e00 0fc01f00 0f800f00 0f000f80 0f000780 0f000780 0f000780 0f000780 0f000780 0f000f80 0f800f00 0fc01f00 0fe03e00 0ff8fe00 0ffffc00 0f7ff000 0f1fc000 0f000000 0f000000 0f000000 0f000000 0f000000 0f000000 fff00000 fff00000 fff00000 q 28 30 3 -9 30 01ff0700 07ffc700 0fffff00 1fc3ff00 3f00ff00 7c003f00 7c001f00 f8001f00 f8000f00 f0000f00 f0000f00 f0000f00 f8000f00 f8001f00 7c001f00 7c003f00 3f00ff00 1fc3ff00 0fffff00 07ffcf00 01ff0f00 00000f00 00000f00 00000f00 00000f00 00000f00 00000f00 0000fff0 0000fff0 0000fff0 r 24 21 3 0 30 0fc3fc00 ffcffe00 ffffff00 ffff3f00 07fc3f00 03f03f00 03e01e00 03e00000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00000 07e00000 ffff0000 ffff0000 ffff0000 s 22 21 4 0 30 03ff9c00 1ffffc00 7ffffc00 ff01fc00 f8003c00 f0001c00 f8001c00 ff801c00 7fff0000 3fffe000 1ffff000 01fff800 e003fc00 e000fc00 e0003c00 e0003c00 f8007c00 ff03f800 fffff000 ffffe000 e3ff0000 t 25 30 3 0 30 01c00000 01c00000 01c00000 01c00000 03c00000 03c00000 07c00000 0fc00000 1fc00000 fffff000 fffff000 fffff000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00000 03c00380 03c00380 03c00380 03c00780 03c00780 03e00f00 03f01f00 01fc7e00 00fffc00 007ff800 001fe000 u 26 21 2 0 30 1f007c00 ff03fc00 ff03fc00 ff03fc00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f003c00 0f007c00 0f80fc00 07e1fc00 03ffffc0 01ffffc0 007fbfc0 v 27 21 1 0 30 fff0ffe0 fff0ffe0 fff0ffe0 0f801f00 07c03c00 07c03c00 03e07800 03e07800 01f0f000 01f0f000 00f0e000 00f9e000 00f9e000 007fc000 007fc000 003f8000 003f8000 001f0000 001f0000 000e0000 000e0000 w 30 21 0 0 30 ff8ff3fc ff8ff3fc ff8ff3fc 1e07c0f0 0e07c0e0 0f0fe1e0 0f0fe1e0 070ee1c0 070ee1c0 079ef3c0 079ef3c0 039c7380 03fc7f80 03fc7f80 01f83f00 01f83f00 01f83f00 00f01e00 00f01e00 00f01e00 00f01e00 x 28 21 1 0 30 ffe0ffe0 ffe0ffe0 ffe0ffe0 0fc07f00 07e0fc00 03f0f000 01f9e000 00ffe000 007fc000 003f8000 001f8000 003fc000 007fe000 00fbf000 00f1f800 01e0fc00 07e07e00 1fc03f00 ffe07ff0 ffe07ff0 ffe07ff0 y 27 30 1 -9 30 fff0ffe0 fff0ffe0 fff0ffe0 0f801f00 07c03c00 07c03c00 03e07800 03e07800 01f0f000 01f0f000 00f0e000 00f9e000 00f9e000 007fc000 007fc000 003f8000 003f8000 001f0000 001f0000 000e0000 001e0000 001e0000 003c0000 3c7c0000 7e780000 7ef00000 7ff00000 7fe00000 3fc00000 1f800000 z 22 21 4 0 30 7ffffc00 7ffffc00 7ffffc00 7e01f800 f803f000 f007e000 f00fc000 e01f8000 e03f0000 e07e0000 00fc1c00 01f81c00 03f01c00 07e03c00 0fc03c00 1f807c00 3f007c00 7e01f800 fffff800 fffff800 fffff800 { 22 45 4 -10 30 00007c00 0003fc00 000ffc00 001fe000 003f0000 007e0000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 01f80000 03f00000 1fe00000 ffc00000 ff000000 ffc00000 1fe00000 03f00000 01f80000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 007e0000 003f0000 001fe000 000ffc00 0003fc00 00007c00 | 3 45 14 -10 30 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 } 22 45 4 -10 30 f8000000 ff000000 ffc00000 1fe00000 03f00000 01f80000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 007e0000 003f0000 001fe000 000ffc00 0003fc00 000ffc00 001fe000 003f0000 007e0000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 00780000 01f80000 03f00000 1fe00000 ffc00000 ff000000 f8000000 ~ 20 6 5 28 30 3fc07000 7fe07000 fffdf000 f0fff000 e07fe000 000f8000  24 32 4 1 30 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 ffffff00 file s610.iris (sample font file) 48 1 1 0 1 30 0000 ! 5 33 12 1 30 7000 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 f800 7000 0000 0000 0000 0000 7000 f800 f800 f800 " 16 19 7 15 30 781e fc3f fc3f fc3f fc3f fc3f fc3f fc3f fc3f fc3f fc3f 781e 781e 781e 781e 781e 781e 781e 300c # 26 43 2 -9 30 00601800 00F03C00 00F03C00 00F03C00 00F03C00 00F03C00 00F03C00 01F07C00 01E07800 01E07800 01E07800 01E07800 01E07800 01E07800 7FFFFF80 FFFFFFC0 FFFFFFC0 7FFFFF80 03C0F000 03C0F000 03C0F000 03C0F000 03C0F000 03C0F000 7FFFFF80 FFFFFFC0 FFFFFFC0 7FFFFF80 0781E000 0781E000 0781E000 0781E000 0781E000 0781E000 0781E000 0F83E000 0F03C000 0F03C000 0F03C000 0F03C000 0F03C000 0F03C000 06018000 $ 24 36 3 -1 30 00180000 00FF0000 07FFE000 0FFFF000 1FFFF800 3FBDFC00 7C3C3E00 F83C1F00 F03C0F00 F03C1F00 F03C1F00 F03C1F00 F83C0E00 7C3C0000 3FBC0000 1FFC0000 0FFF8000 07FFE000 00FFF000 003FF800 003CFC00 003C3E00 003C1F00 703C0F00 F83C0F00 F83C0F00 F83C0F00 F83C1F00 783C1E00 7E3C7E00 3FBDFC00 1FFFF800 0FFFF000 03FFC000 00FF0000 00180000 % 27 36 2 -1 30 078000c0 0fc001e0 1fe003e0 3ff00fc0 7dffffc0 79ffff80 f9ffff00 f1fffe00 f1e03e00 f1e07c00 f1e07800 f3e0f800 f3c1f000 f7c1e000 ff83e000 7f07c000 7e078000 3c0f8000 001f0f00 003e1f80 003c3f80 007c7fc0 00f8fbc0 00f0f3c0 01f1f3c0 03e1e3c0 03c1e3c0 07c1e3c0 0f81e3c0 0f01e7c0 1f01e780 3e01ef80 7c01ff00 7800fe00 7800fc00 30007800 & 27 34 2 0 30 007C0000 00FE0000 01FF0000 03FF8000 03C78000 07C7C000 0783C000 0783C000 0783C000 0783C000 0787C000 07C78000 03CF8600 03DF0F00 03FE0F00 03FC1F00 01F81E00 03F01E00 07F03E00 0FF03C00 1FF07C00 3EF8F800 7C78F000 787DF000 F83FE000 F03FC0C0 F01FC1E0 F01F81E0 F03F01E0 F0FF83E0 FFFFFFC0 7FFBFF80 3FE1FF00 1F80FE00 ' 9 16 12 18 30 3C00 7E00 7F00 7F80 3F80 0780 0780 0780 0F80 0F00 1F00 3E00 7E00 FC00 F800 6000 ( 15 45 12 -10 30 000C 003E 007E 00FC 01F8 03E0 07C0 0780 0F80 1F00 1E00 3E00 3C00 7C00 7800 7800 7800 F800 F000 F000 F000 F000 F000 F000 F000 F000 F000 F800 7800 7800 7800 7C00 3C00 3E00 1E00 1F00 0F80 0780 07C0 03E0 01F8 00FC 007E 003E 000C ) 15 45 3 -10 30 6000 F800 FC00 7E00 3F00 0F80 07C0 03C0 03E0 01F0 00F0 00F8 0078 007C 003C 003C 003C 003E 001E 001E 001E 001E 001E 001E 001E 001E 001E 003E 003C 003C 003C 007C 0078 00F8 00F0 01F0 03E0 03C0 07C0 0F80 3F00 7E00 FC00 F800 6000 * 22 22 4 2 30 00300000 00780000 00780000 00780000 60781800 F8787C00 FE79FC00 FF7BFC00 7FFFF800 1FFFE000 07FF8000 07FF8000 1FFFE000 7FFFF800 FF7BFC00 FE79FC00 F8787C00 00780000 00780000 00780000 00780000 00300000 + 24 23 3 1 30 00180000 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 7ffffe00 ffffff00 ffffff00 7ffffe00 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 003c0000 00180000 , 8 15 10 -9 30 1E00 3F00 3F00 3F00 3F00 1F00 0F00 1F00 1E00 3E00 3C00 7C00 F800 F000 6000 - 24 4 3 11 30 7FFFFE00 FFFFFF00 FFFFFF00 7FFFFE00 . 6 6 12 0 30 7800 FC00 FC00 FC00 FC00 7800 / 24 45 3 -10 30 00000600 00000F00 00000F00 00001F00 00001E00 00003E00 00003C00 00007C00 00007800 0000F800 0000F000 0001F000 0001E000 0003E000 0003C000 0007C000 00078000 000F8000 000F0000 001F0000 001E0000 003E0000 003C0000 007C0000 00780000 00F80000 00F00000 01F00000 01E00000 03E00000 03C00000 07C00000 07800000 0F800000 0F000000 1F000000 1E000000 3E000000 3C000000 7C000000 78000000 F8000000 F0000000 F0000000 60000000 0 26 32 2 0 30 003F0000 00FFC000 03FFF000 07FFF800 0FE1FC00 1F807E00 1F003E00 3E001F00 7E001F80 7C000F80 7C000F80 FC000FC0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 FC000FC0 7C000F80 7C000F80 7E001F80 3E001F00 1F003E00 1F807E00 0FE1FC00 07FFF800 03FFF000 00FFC000 003F0000 1 20 31 5 1 30 00300000 00780000 03f80000 7ff80000 fff80000 fff80000 7ef80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 3fffe000 7ffff000 7ffff000 2 24 32 3 0 30 01FF0000 07FFE000 0FFFF800 1FFFFC00 3F01FE00 7C007E00 78003F00 F8001F00 FC001F00 FC001F00 FC001F00 FC003F00 78003E00 00007E00 00007C00 0000F800 0001F000 0007E000 000FC000 001F8000 003F0000 00FE0000 01F80000 03F00000 07E00000 0F800000 1F000000 3E000000 7FFFFE00 FFFFFF00 FFFFFF00 7FFFFE00 3 26 32 2 0 30 00FF8000 03FFF000 0FFFF800 1FFFFC00 3F80FE00 3E003F00 3E001F00 3E001F00 1C001F00 00003F00 00007E00 0001FC00 000FF800 00FFF000 01FFF000 01FFF800 00FFFE00 0000FF00 00003F80 00000F80 00000FC0 000007C0 780007C0 FC0007C0 FC000FC0 FC000F80 FC003F80 7F80FF00 3FFFFE00 1FFFFC00 07FFF000 00FF8000 4 26 32 2 0 30 0000E000 0001F000 0003F000 0007F000 0007F000 000FF000 001FF000 003FF000 003DF000 007DF000 00F9F000 01F1F000 01E1F000 03E1F000 07C1F000 0F81F000 0F01F000 1F01F000 3E01F000 7C01F000 7FFFFF80 FFFFFFC0 FFFFFFC0 7FFFFF80 0001F000 0001F000 0001F000 0001F000 0001F000 0001F000 0001F000 0000E000 5 24 32 3 0 30 1C001C00 3FFFFE00 3FFFFE00 3FFFFC00 3FFFF000 3C000000 3C000000 3C000000 3C000000 3C000000 3C000000 3C000000 3CFF0000 3FFFC000 3FFFF000 3FFFF800 3F81FC00 3C007E00 18003E00 00003F00 00001F00 00001F00 70001F00 F8001F00 F8003F00 F8003E00 FC00FE00 7F03FC00 3FFFF800 1FFFF000 07FFC000 01FE0000 6 25 32 3 0 30 007FC000 01FFF000 03FFF800 07FFF800 0FC07C00 1F007C00 3E007C00 3C003800 7C000000 78000000 78000000 78FF0000 FBFFE000 F7FFF000 FFFFF800 FF81FC00 FE007E00 FC003F00 F8001F00 F0000F80 F0000F80 F0000F80 F0000F80 F0000F80 F0001F00 F8003F00 7E007E00 3F81FC00 1FFFF800 0FFFF000 03FFE000 00FF0000 7 26 32 2 0 30 7FFFFF80 FFFFFFC0 FFFFFFC0 7FFFFF80 00001F00 00003E00 00003C00 00007C00 0000F800 0000F000 0001F000 0003E000 0003C000 0007C000 00078000 000F8000 001F0000 001E0000 003E0000 003C0000 003C0000 007C0000 00780000 00F80000 00F00000 00F00000 00F00000 00F00000 01F00000 01F00000 01F00000 00E00000 8 26 32 2 0 30 007F8000 03FFF000 07FFF800 0FFFFC00 1FC0FE00 3E001F00 7C000F80 78000780 78000780 78000780 7C000F80 3E001F00 3F807F00 1FFFFE00 0FFFFC00 07FFF800 1FFFFE00 3FF3FF00 3F003F00 7C000F80 F80007C0 F00003C0 F00003C0 F00003C0 F80007C0 78000780 7E001F80 3F807F00 1FFFFE00 0FFFFC00 03FFF000 00FFC000 9 26 32 2 0 30 007F8000 03FFE000 07FFF800 0FFFFC00 1FC0FE00 3F003F00 7E000F00 7C000F80 FC000780 F8000780 F80007C0 F80007C0 F8000780 FC000F80 7C000F80 7E001F80 3F003F80 1FC0FF80 0FFFFF80 07FFF780 03FFEF80 007F8F00 00000F00 00001F00 0E001E00 1F003E00 1F007C00 1F81F800 0FFFF000 07FFE000 03FFC000 00FF0000 : 6 22 12 0 30 7800 FC00 FC00 FC00 FC00 7800 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 7800 FC00 FC00 FC00 FC00 7800 ; 8 31 10 -9 30 1E00 3F00 3F00 3F00 3F00 1E00 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 1E00 3F00 3F00 3F00 3F00 1F00 0F00 1F00 1E00 3E00 3C00 7C00 F800 F000 6000 < 22 34 4 -4 30 00001800 00003C00 00007C00 0001F800 0003F000 0007E000 000FC000 001F0000 007E0000 00FC0000 01F80000 03F00000 07C00000 1F800000 3F000000 7E000000 FC000000 F8000000 7E000000 3F000000 1F800000 0FC00000 03E00000 01F80000 00FC0000 007E0000 003F0000 000F8000 0007E000 0003F000 0001F800 0000FC00 00003C00 00001800 = 26 14 2 6 30 7FFFFF80 FFFFFFC0 FFFFFFC0 7FFFFF80 00000000 00000000 00000000 00000000 00000000 00000000 7FFFFF80 FFFFFFC0 FFFFFFC0 7FFFFF80 > 22 34 4 -4 30 60000000 F0000000 F8000000 7E000000 3F000000 1F800000 0FC00000 03E00000 01F80000 00FC0000 007E0000 003F0000 000F8000 0007E000 0003F000 0001F800 0000FC00 00007C00 0001F800 0003F000 0007E000 000FC000 001F0000 007E0000 00FC0000 01F80000 03F00000 07C00000 1F800000 3F000000 7E000000 FC000000 F0000000 60000000 ? 21 34 4 0 30 07FE0000 1FFFC000 3FFFE000 7FFFF000 FC03F800 F8007800 F8007800 F8007800 70007800 0000F800 0000F000 0003F000 003FE000 007FC000 00FF8000 01FE0000 01E00000 01E00000 01E00000 01E00000 01E00000 01E00000 01E00000 01E00000 00C00000 00000000 00000000 00000000 00000000 00E00000 01F00000 01F00000 01F00000 00E00000 @ 26 34 2 0 30 003F0000 00FFC000 03FFF000 07FFF800 0FE1FC00 0F807C00 1F1E3E00 3E7F9F00 3CFFCF00 7DFFEF80 79F3F780 7BE1FF80 FBC0FFC0 F7C0FBC0 F7807BC0 F7807BC0 F7807BC0 F7807BC0 F7807BC0 F7807BC0 F7C0FBC0 FBC0FBC0 7BE1FFC0 79F3FF80 7DFFFF80 3CFFFF00 3E7FBF00 1F1E1F80 0F8007C0 0FE03FC0 07FFFF80 03FFFF00 00FFFC00 003FE000 A 27 34 1 0 30 000E0000 001F0000 001F0000 003F8000 003F8000 003F8000 007FC000 007FC000 00FFE000 00F3E000 00F3E000 01F3F000 01E1F000 01E1F000 03E1F800 03C0F800 07C0FC00 07807C00 07807C00 0F807E00 0FFFFE00 0FFFFE00 1FFFFF00 1FFFFF00 1E001F00 3E001F80 3C000F80 7C000FC0 780007C0 780007C0 F80007E0 F00003E0 F00003E0 600001C0 B 27 34 2 0 30 7FFFC000 FFFFF000 FFFFF800 FFFFFC00 F8007E00 F8003F00 F8001F00 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8001F00 F8003F00 F8007E00 FFFFFC00 FFFFFC00 FFFFFE00 FFFFFF00 F8003F80 F8000FC0 F80007C0 F80003E0 F80003E0 F80003E0 F80003E0 F80003E0 F80007C0 F8000FC0 F8003F80 FFFFFF00 FFFFFE00 FFFFFC00 7FFFE000 C 24 34 3 0 30 001FC000 007FF000 01FFFC00 03FFFE00 07F07F00 0FC01F00 1F800600 1F000000 3E000000 7E000000 7C000000 7C000000 FC000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 FC000000 7C000000 7C000000 7E000000 3E000000 1F000000 1F800600 0FC01F00 07F07F00 03FFFE00 01FFFC00 007FF000 001FC000 D 26 34 3 0 30 7FF80000 FFFF0000 FFFFC000 FFFFE000 F80FF000 F801F800 F800FC00 F8007E00 F8003F00 F8001F00 F8001F80 F8000F80 F8000F80 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F80007C0 F8000F80 F8000F80 F8001F80 F8001F00 F8003F00 F8007E00 F800FC00 F801F800 F80FF000 FFFFE000 FFFFC000 FFFF0000 7FF80000 E 26 33 3 1 30 7fffff00 ffffff80 ffffff80 ffffff00 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 fffff800 fffffc00 fffffc00 fffff800 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 ffffff80 ffffffc0 ffffffc0 F 26 33 3 1 30 7fffff80 ffffffc0 ffffffc0 ffffff80 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 fffffc00 fffffe00 fffffe00 fffffc00 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 G 26 34 2 0 30 001FC000 007FF000 01FFF800 03FFFC00 07F87E00 0FC01F00 1F800F00 1F000F80 3E000780 3E000780 7C0007C0 7C0003C0 FC0003C0 F8000180 F8000000 F8000000 F8000000 F8000000 F8000000 F8007F80 F800FFC0 FC00FFC0 7C007FC0 7C0007C0 3E0007C0 3E0007C0 1F0007C0 1F8007C0 0FC007C0 07F81FC0 03FFFFC0 01FFFFC0 007FFFC0 001FF180 H 25 34 2 0 30 70000700 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 FFFFFF80 FFFFFF80 FFFFFF80 FFFFFF80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 70000700 I 21 33 5 1 30 7ffff000 fffff800 fffff800 7ffff000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 00f80000 7ffff000 fffff800 fffff800 J 21 33 6 1 30 00007000 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 0000f800 7000f800 f800f800 f800f800 f801f800 fe07f000 7fffe000 3fffc000 1fff8000 K 25 34 3 0 30 70000600 F8000F00 F8001F00 F8003E00 F8007C00 F800F800 F801F000 F803E000 F807C000 F80F8000 F81F0000 F83E0000 F83C0000 F87C0000 F8FC0000 F9FC0000 FBFE0000 FFFF0000 FF9F0000 FF1F8000 FE0FC000 FC07C000 F807E000 F803F000 F801F000 F801F800 F800FC00 F8007C00 F8007E00 F8003F00 F8001F00 F8001F80 F8000F80 70000700 L 27 33 3 1 30 70000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 f8000000 ffffffc0 ffffffe0 ffffffe0 M 26 34 2 0 30 70000380 f80007c0 f80007c0 fc000fc0 fc000fc0 fc000fc0 fe001fc0 fe001fc0 fe001fc0 ff003fc0 ff003fc0 ff003fc0 ff807fc0 f7807bc0 f7807bc0 f7c0fbc0 f3c0f3c0 f3c0f3c0 f3e1f3c0 f1e1e3c0 f1e1e3c0 f1f3e3c0 f0f3c3c0 f0f3c3c0 f0ffc3c0 f07f83c0 f07f83c0 f07f83c0 f03f03c0 f03f03c0 f03f03c0 f01e03c0 f01e03c0 600c0180 N 25 34 3 0 30 78000300 fc000780 fe000780 fe000780 ff000780 ff800780 ff800780 ffc00780 f7c00780 f7e00780 f3f00780 f1f00780 f1f80780 f0fc0780 f07c0780 f07e0780 f03f0780 f01f0780 f01f8780 f00f8780 f00fc780 f007e780 f003e780 f003f780 f001ff80 f000ff80 f000ff80 f0007f80 f0007f80 f0003f80 f0001f80 f0001f80 f0000f80 60000700 O 24 34 3 0 30 01FF8000 0FFFF000 1FFFF800 3FFFFC00 7F00FE00 7C003E00 7C003E00 7C003E00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 7C003E00 7C003E00 7C003E00 7F00FE00 3FFFFC00 1FFFF800 0FFFF000 01FF8000 P 25 34 2 0 30 7FFFC000 FFFFF000 FFFFF800 FFFFFC00 F8007E00 F8003F00 F8001F00 F8000F80 F8000F80 F8000F80 F8000F80 F8000F80 F8001F00 F8003F00 F8007E00 FFFFFC00 FFFFF800 FFFFF000 FFFFC000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 F8000000 70000000 Q 26 41 3 -7 30 01FF8000 0FFFF000 1FFFF800 3FFFFC00 7F00FE00 7C003E00 7C003E00 7C003E00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8001F00 F8181F00 F83C1F00 F83E1F00 F81F1F00 F80F1F00 7C0FBE00 7C07FE00 7C03FE00 7F01FE00 3FFFFC00 1FFFF800 0FFFFC00 01FFBC00 00003E00 00001F00 00000F80 00000780 000007C0 000003C0 00000180 R 26 34 2 0 30 7FFFC000 FFFFF000 FFFFFC00 FFFFFE00 F800FF00 F8001F80 F8000F80 F8000FC0 F80007C0 F80007C0 F80007C0 F8000FC0 F8000F80 F8001F80 F800FF00 FFFFFE00 FFFFFC00 FFFFF000 FFFFC000 F80FC000 F807C000 F807E000 F803F000 F801F000 F801F800 F800F800 F800FC00 F8007E00 F8003E00 F8003F00 F8001F00 F8001F80 F8000F80 70000700 S 25 34 2 0 30 007F8000 03FFF000 07FFFC00 0FFFFE00 1FC0FF00 3E001F80 7C000780 78000300 78000000 78000000 78000000 7C000000 3F000000 1FC00000 0FFC0000 07FFC000 01FFF000 007FF800 0007FC00 00007E00 00001F00 00000F00 00000F80 00000780 00000780 60000780 F0000F80 F8000F00 7E003F00 3FC0FE00 1FFFFC00 0FFFF800 03FFE000 007F8000 T 31 33 0 1 30 7ffffffc fffffffe fffffffe 7ffffffc 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 0007c000 U 27 34 1 0 30 700000C0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 F80001E0 FC0003E0 7C0003C0 7E0007C0 3E000780 1F801F80 1FE07F00 0FFFFE00 03FFFC00 01FFF000 003FC000 V 27 34 1 0 30 700000C0 F80001E0 F80001E0 FC0003E0 7C0003C0 7C0003C0 7E0007C0 3E000780 3F000F80 1F000F00 1F000F00 1F801F00 0F801E00 0F801E00 0FC03E00 07C03C00 07E03C00 03E07C00 03E07800 03F0F800 01F0F000 01F0F000 01F9F000 00F9E000 00F9E000 00FFE000 007FC000 007FC000 003F8000 003F8000 003F8000 001F0000 001F0000 000E0000 W 28 34 1 0 30 60060060 f00f00f0 f00f00f0 f00f00f0 f81f81f0 781f81e0 781f81e0 781f81e0 781f81e0 781f81e0 7c3fc3e0 3c3fc3c0 3c3fc3c0 3c3fc3c0 3c3fc3c0 3e7fe7c0 1e79e780 1e79e780 1e79e780 1e79e780 1e79e780 1ff9ff80 0ff0ff00 0ff0ff00 0ff0ff00 0ff0ff00 0ff0ff00 07e07e00 07e07e00 07e07e00 07e07e00 07e07e00 07e07e00 03c03c00 X 27 34 1 0 30 700000C0 F80001E0 FC0003E0 7C0007C0 7E000F80 3F000F00 1F801F00 0F803E00 0FC07C00 07E07800 03F0F800 01F1F000 01FBE000 00FFC000 007FC000 003F8000 003F0000 001F8000 003F8000 007FC000 007FE000 00FBF000 01F1F000 03E1F800 03C0FC00 07C07E00 0F803E00 1F003F00 1E001F80 3E000FC0 7C0007C0 780007E0 780003E0 300001C0 Y 27 33 1 1 30 700000c0 f80001e0 fc0003e0 7c0003c0 7e0007c0 3f000f80 1f801f00 0f801e00 0fc03e00 07e07c00 03e07800 03f0f800 01f9f000 00f9e000 00ffe000 007fc000 003f8000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 001f0000 Z 24 34 3 0 30 3FFFFE00 7FFFFF00 7FFFFF00 3FFFFE00 00007E00 0000FC00 0000F800 0001F800 0001F000 0003F000 0007E000 0007C000 000FC000 001F8000 001F0000 003F0000 007E0000 007C0000 00FC0000 00F80000 01F80000 03F00000 03E00000 07E00000 0FC00000 0F800000 1F800000 1F000000 3F000000 7E000000 7FFFFE00 FFFFFF00 FFFFFF00 7FFFFE00 [ 14 44 13 -9 30 7ff8 fffc fffc fff8 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 fff8 fffc fffc 7ff8 \ 24 45 3 -10 30 60000000 F0000000 F0000000 F8000000 78000000 7C000000 3C000000 3E000000 1E000000 1F000000 0F000000 0F800000 07800000 07C00000 03C00000 03E00000 01E00000 01F00000 00F00000 00F80000 00780000 007C0000 003C0000 003E0000 001E0000 001F0000 000F0000 000F8000 00078000 0007C000 0003C000 0003E000 0001E000 0001F000 0000F000 0000F800 00007800 00007C00 00003C00 00003E00 00001E00 00001F00 00000F00 00000F00 00000600 ] 14 44 3 -9 30 7ff8 fffc fffc 7ffc 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 003c 7ffc fffc fffc 7ff8 ^ 18 9 6 25 30 00C00000 01E00000 07F80000 0FFC0000 1FFE0000 7F3F8000 FC0FC000 F807C000 70038000 _ 34 4 -2 -12 30 7fffffff8000 ffffffffc000 ffffffffc000 7fffffff8000 ` 9 16 10 18 30 0300 0F80 1F80 3F00 3E00 7C00 7800 F800 F000 F000 F000 FE00 FF00 7F00 3F00 1E00 a 21 22 4 0 30 07FE0000 3FFF8000 7FFFC000 FFFFE000 FC03F000 F800F800 70007800 00007800 000FF800 00FFF800 07FFF800 1FFFF800 3FF87800 7F807800 FC007800 F0007800 F000F800 F80FF800 7FFFF800 3FFFF800 1FFFF800 0FF83000 b 23 34 4 0 30 60000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0FE0000 F3FF8000 FFFFE000 FFFFF000 FF83F800 FE00F800 FC007C00 F8003C00 F8003E00 F0001E00 F0001E00 F0001E00 F0001E00 F8003E00 F8003C00 FC007C00 FE00F800 FF83F800 FFFFF000 FFFFE000 F3FF8000 60FE0000 c 22 22 4 0 30 007FC000 03FFF000 07FFF800 0FFFFC00 1FC07C00 3E007C00 7C003800 78000000 F8000000 F0000000 F0000000 F0000000 F0000000 F8000000 78000000 7C000000 3E003800 1FC0FC00 0FFFFC00 07FFF800 03FFE000 007F8000 d 23 34 3 0 30 00000C00 00001E00 00001E00 00001E00 00001E00 00001E00 00001E00 00001E00 00001E00 00001E00 00001E00 00001E00 00FE1E00 03FF9E00 0FFFFE00 1FFFFE00 3F83FE00 3E00FE00 7C007E00 78003E00 F8003E00 F0001E00 F0001E00 F0001E00 F0001E00 F8003E00 78003E00 7C007E00 3E00FE00 3F83FE00 1FFFFE00 0FFFFE00 03FF9E00 00FE0C00 e 22 22 4 0 30 00FE0000 03FF8000 0FFFE000 1FFFF000 3F83F000 3E00F800 7C007C00 78003C00 FFFFFC00 FFFFFC00 FFFFFC00 FFFFF800 F0000000 F8000000 78001800 7C003C00 3E007C00 1FC1FC00 0FFFF800 07FFF000 03FFC000 007F0000 f 21 33 4 1 30 001f8000 003fe000 007ff000 00fff800 01f0f800 01e0f800 01e07000 01e00000 01e00000 01e00000 01e00000 01e00000 7fff8000 ffffc000 ffffc000 7fff8000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 01e00000 g 24 31 3 -9 30 00FF0600 03FFCF00 07FFEF00 0FFFFF00 1F81FF00 3E007F00 7C003F00 78001F00 F8001F00 F0000F00 F0000F00 F0000F00 F0000F00 F8001F00 78001F00 7C003F00 3E007F00 1F81FF00 0FFFFF00 07FFEF00 03FFCF00 00FF0F00 00000F00 00000F00 70001F00 F8003E00 FC01FC00 FFFFF800 7FFFF000 3FFFE000 07FF0000 h 20 34 5 0 30 60000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F3FE0000 FFFF8000 FFFFC000 FFFFE000 FE03F000 F800F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 60006000 i 6 33 11 1 30 7800 fc00 fc00 fc00 fc00 7800 0000 0000 0000 0000 0000 0000 1800 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 3c00 j 16 43 2 -9 30 001E 003F 003F 003F 003F 001E 0000 0000 0000 0000 0000 0000 0006 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 701F F83E FFFC FFF8 7FF0 1FE0 k 20 34 5 0 30 60000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0006000 F001F000 F003F000 F00FE000 F01FC000 F07F0000 F0FE0000 F3F80000 F7F00000 FFE00000 FFF00000 FEF80000 FC7C0000 F83E0000 F01F0000 F00F0000 F00F8000 F007C000 F003E000 F001F000 F000F000 60006000 l 4 33 13 1 30 6000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 m 24 22 3 0 30 6FC3F000 FFF7FC00 FFFFFE00 FFFFFE00 F87E1F00 F83E0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 F03C0F00 60180600 n 20 22 5 0 30 63FE0000 FFFF8000 FFFFC000 FFFFE000 FE03F000 F800F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 60006000 o 26 22 2 0 30 007F8000 03FFF000 07FFF800 0FFFFC00 1FC0FE00 3E001F00 7C000F80 78000780 F80007C0 F00003C0 F00003C0 F00003C0 F00003C0 F80007C0 78000780 7C000F80 3E001F00 1FC0FE00 0FFFFC00 07FFF800 03FFF000 007F8000 p 23 31 4 -9 30 60FE0000 F3FF8000 FFFFE000 FFFFF000 FF83F800 FE00F800 FC007C00 F8003C00 F8003E00 F0001E00 F0001E00 F0001E00 F0001E00 F8003E00 F8003C00 FC007C00 FE00F800 FF83F800 FFFFF000 FFFFE000 F3FF8000 F0FE0000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 F0000000 60000000 q 24 31 3 -9 30 00FF0600 03FFCF00 07FFEF00 0FFFFF00 1F81FF00 3E007F00 7C003F00 78001F00 F8001F00 F0000F00 F0000F00 F0000F00 F0000F00 F8001F00 78001F00 7C003F00 3E007F00 1F81FF00 0FFFFF00 07FFEF00 03FFCF00 00FF0F00 00000F00 00000F00 00000F00 00000F00 00000F00 00000F00 00000F00 00000F00 00000600 r 19 21 8 1 30 60ff0000 f3ffc000 ffffe000 ffffe000 ff83e000 fe01c000 f8000000 f8000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 f0000000 s 25 22 2 0 30 00FFC000 03FFF800 0FFFFE00 1FFFFF00 3F807F00 3E000E00 3C000000 3F000000 1FF80000 0FFFE000 07FFF800 01FFFE00 000FFF00 00003F00 00000F80 60000780 F8000F80 FF007F00 7FFFFE00 3FFFFC00 0FFFF800 01FFC000 t 25 31 3 0 30 01800000 03C00000 03C00000 03C00000 03C00000 03C00000 03C00000 03C00000 03C00000 7FFFE000 FFFFF000 FFFFF000 7FFFE000 03C00000 03C00000 03C00000 03C00000 03C00000 03C00000 03C00300 03C00780 03C00780 03C00780 03C00780 03C00F80 03E01F00 01F83E00 00FFFE00 007FFC00 003FF000 000FE000 u 20 22 5 0 30 60006000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F000F000 F801F000 7E07F000 3FFFF000 1FFFF000 0FFFF000 03FC6000 v 21 22 5 0 30 60003000 F0007800 F0007800 F800F800 7800F000 7C01F000 3C01E000 3E03E000 1E03C000 1F07C000 0F078000 0F078000 0F8F8000 078F0000 07DF0000 03DE0000 03FE0000 01FC0000 01FC0000 00F80000 00F80000 00700000 w 26 22 2 0 30 600c0180 f01e03c0 f01e03c0 f83f07c0 783f0780 783f0780 783f0780 7c7f8f80 3c7f8f00 3c7f8f00 3e7fcf00 1efbdf00 1ef3de00 1ef3de00 1ff3fe00 0fe1fc00 0fe1fc00 0fe1fc00 0fe1fc00 07c0f800 07c0f800 03807000 x 21 22 5 0 30 60006000 F000F000 F801F000 7C03E000 3E07C000 1F0F8000 0F8F0000 07DF0000 03FE0000 01FC0000 00F80000 01F80000 03FC0000 07FE0000 0F9F0000 0F0F8000 1F07C000 3E03E000 7C01F000 F800F800 F0007800 60003000 y 25 31 1 -9 30 06000300 0F000780 0F000780 0F800F80 07800F00 07C01F00 03C01E00 03E03E00 01E03C00 01F07C00 00F07800 00F8F800 0078F000 007DF000 003DE000 003DE000 003FE000 001FC000 001FC000 000F8000 000F8000 000F0000 001F0000 001E0000 003E0000 707C0000 F9F80000 FFF00000 FFE00000 7FC00000 3F000000 z 22 22 4 0 30 7FFFF800 FFFFFC00 FFFFFC00 7FFFF800 0001F000 0003E000 0007C000 000F8000 001F0000 003E0000 007C0000 00F80000 01F00000 03E00000 07C00000 0F800000 1F000000 3E000000 7FFFF800 FFFFFC00 FFFFFC00 7FFFF800 { 24 44 3 -9 30 00001E00 0000FF00 0003FF00 000FFE00 001FF000 003F8000 003E0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 007C0000 01FC0000 0FF80000 7FF00000 FFC00000 FFC00000 7FF00000 0FF80000 01FC0000 007C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003E0000 003F8000 001FF000 000FFE00 0003FF00 0000FF00 00001E00 | 4 44 13 -9 30 6000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 f000 } 24 44 3 -9 30 78000000 FF000000 FFC00000 7FF00000 0FF80000 01FC0000 007C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003E0000 003F8000 001FF000 000FFE00 0003FF00 0003FF00 000FFE00 001FF000 003F8000 003E0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 003C0000 007C0000 01FC0000 0FF80000 7FF00000 FFC00000 FF000000 78000000 ~ 22 7 4 27 30 0FC01000 1FE03800 3FFFFC00 7FFFFC00 FFFFF800 703FF000 201FC000  23 33 4 1 30 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 fffffe00 file s1225.iris (sample font file) 23 1 1 0 1 13 0000 ! 3 18 5 1 13 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 e000 0000 0000 e000 e000 e000 " 6 10 3 9 13 fc00 fc00 fc00 fc00 fc00 fc00 fc00 fc00 fc00 fc00 # 10 23 1 -4 13 1980 1B80 1B00 1B00 1B00 1B00 3B00 3300 FFC0 FFC0 3300 3300 3300 FFC0 FFC0 3300 3700 3600 3600 3600 3600 7600 6600 $ 10 18 1 1 13 1E00 7F80 FFC0 CDC0 CDC0 CDC0 EC00 7C00 3F00 0F80 0DC0 ECC0 ECC0 ECC0 EDC0 7F80 7F80 1E00 % 11 18 1 1 13 3060 7DE0 FFC0 DF80 DB80 DB00 FF00 F600 6E00 0CC0 1DE0 1BE0 3B60 3360 7360 63E0 E3C0 C180 & 11 18 1 1 13 1C00 3E00 3600 3600 3600 3600 3E00 3CC0 19C0 3980 7B80 7B00 FF00 CF60 CE60 DE60 FFE0 73C0 ' 4 9 5 10 13 E000 F000 F000 3000 3000 7000 6000 E000 C000 ( 6 23 5 -4 13 0C00 1C00 3800 7000 6000 6000 E000 C000 C000 C000 C000 C000 C000 C000 C000 C000 E000 6000 6000 7000 3800 1C00 0C00 ) 6 23 1 -4 13 C000 E000 7000 3800 1800 1800 1C00 0C00 0C00 0C00 0C00 0C00 0C00 0C00 0C00 0C00 1C00 1800 1800 3800 7000 E000 C000 * 10 11 1 2 13 0C00 0C00 CCC0 FFC0 7F80 1E00 7F80 FFC0 CCC0 0C00 0C00 + 10 9 1 3 13 0C00 0C00 0C00 FFC0 FFC0 0C00 0C00 0C00 0C00 , 4 7 4 -3 13 7000 7000 7000 3000 7000 E000 C000 - 10 2 1 7 13 ffc0 ffc0 . 3 3 5 1 13 e000 e000 e000 / 10 23 1 -4 13 00C0 00C0 01C0 0180 0380 0300 0300 0700 0600 0600 0E00 0C00 1C00 1800 1800 3800 3000 3000 7000 6000 E000 C000 C000 0 10 17 1 1 13 1E00 3F00 7380 6180 E1C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 E1C0 6180 7380 3F00 1E00 1 8 17 2 1 13 1800 3800 F800 F800 1800 1800 1800 1800 1800 1800 1800 1800 1800 1800 1800 FF00 FF00 2 10 17 1 1 13 1E00 7F80 73C0 E0C0 E0C0 E0C0 E1C0 0180 0380 0700 0E00 1C00 3800 7000 6000 FFC0 FFC0 3 10 17 1 1 13 1E00 3F00 7380 7180 7180 0380 0700 3E00 3F80 0380 01C0 E0C0 E0C0 E1C0 E380 7F80 3E00 4 10 17 1 1 13 0300 0700 0700 0F00 0F00 1F00 1B00 3B00 3300 7300 6300 FFC0 FFC0 0300 0300 0300 0300 5 10 17 1 1 13 7F80 7F80 6000 6000 6000 6000 7E00 7F80 7380 61C0 00C0 00C0 C0C0 C1C0 E380 7F00 3E00 6 10 17 1 1 13 1F00 3F80 7180 6180 6000 E000 DE00 FF80 F380 E1C0 C0C0 C0C0 C0C0 E1C0 7380 7F80 1E00 7 10 17 1 1 13 FFC0 FFC0 0180 0380 0300 0700 0600 0600 0E00 0C00 1C00 1800 1800 1800 3800 3800 3800 8 10 17 1 1 13 3F00 7F80 E1C0 C0C0 C0C0 C0C0 E1C0 7F80 7F80 7380 E1C0 C0C0 C0C0 E1C0 7380 7F80 1E00 9 10 17 1 1 13 1E00 3F00 7380 E1C0 C0C0 C0C0 C0C0 C0C0 E1C0 73C0 3FC0 1FC0 0180 0180 0380 0F00 0E00 : 3 11 5 1 13 e000 e000 e000 0000 0000 0000 0000 0000 e000 e000 e000 ; 4 15 4 -3 13 7000 7000 7000 0000 0000 0000 0000 0000 7000 7000 7000 3000 7000 E000 C000 < 8 16 2 0 13 0300 0700 0E00 1C00 1800 3800 7000 E000 E000 7000 3800 1800 1C00 0E00 0700 0300 = 10 7 1 4 13 ffc0 ffc0 0000 0000 0000 ffc0 ffc0 > 8 16 2 0 13 C000 E000 7000 3800 1800 1C00 0E00 0700 0700 0E00 1C00 1800 3800 7000 E000 C000 ? 8 18 2 1 13 7C00 FE00 E700 E300 E300 0700 1E00 3C00 3000 3000 3000 3000 3000 0000 0000 3800 3800 3800 @ 10 18 1 1 13 1E00 3F00 7380 6D80 7F80 FFC0 F3C0 F3C0 F3C0 F3C0 F3C0 F3C0 FFC0 7FC0 6DC0 73C0 3F80 1E00 A 11 17 1 1 13 0E00 0E00 0E00 0E00 1F00 1B00 1B00 3B80 3180 3180 7FC0 7FC0 60C0 60C0 E0E0 C060 C060 B 11 17 1 1 13 FF00 FF80 C1C0 C0C0 C0C0 C0C0 C1C0 FF80 FFC0 C1C0 C0E0 C060 C060 C0E0 C1C0 FFC0 FF00 C 10 17 1 1 13 0F00 3F80 39C0 70C0 6000 E000 C000 C000 C000 C000 C000 E000 6000 70C0 39C0 3F80 0F00 D 10 17 1 1 13 FC00 FE00 C700 C380 C180 C1C0 C0C0 C0C0 C0C0 C0C0 C0C0 C1C0 C180 C380 C700 FE00 FC00 E 12 17 1 1 13 FFE0 FFE0 C000 C000 C000 C000 C000 FFC0 FFC0 C000 C000 C000 C000 C000 C000 FFF0 FFF0 F 11 17 1 1 13 FFE0 FFE0 C000 C000 C000 C000 C000 FFC0 FFC0 C000 C000 C000 C000 C000 C000 C000 C000 G 10 17 1 1 13 0F00 3F00 3B80 71C0 60C0 E0C0 C0C0 C000 C000 C000 C3C0 E3C0 60C0 71C0 39C0 3FC0 0FC0 H 10 17 1 1 13 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 FFC0 FFC0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 I 8 17 2 1 13 ff00 ff00 1800 1800 1800 1800 1800 1800 1800 1800 1800 1800 1800 1800 1800 ff00 ff00 J 8 17 2 1 13 0300 0300 0300 0300 0300 0300 0300 0300 0300 0300 0300 0300 E300 E300 E700 FE00 3C00 K 10 17 1 1 13 C0C0 C1C0 C380 C300 C700 CE00 DC00 FC00 FC00 FE00 E600 C700 C300 C380 C180 C1C0 C0C0 L 12 17 1 1 13 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 fff0 fff0 M 10 17 1 1 13 C0C0 C0C0 E1C0 E1C0 F3C0 F3C0 FFC0 DEC0 DEC0 DEC0 CCC0 CCC0 C0C0 C0C0 C0C0 C0C0 C0C0 N 10 17 1 1 13 c0c0 e0c0 e0c0 f0c0 f0c0 f8c0 d8c0 dcc0 ccc0 cec0 c6c0 c7c0 c3c0 c3c0 c1c0 c1c0 c0c0 O 10 17 1 1 13 3F00 7F80 E1C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 E1C0 7F80 3F00 P 10 17 1 1 13 FF00 FF80 C1C0 C0C0 C0C0 C0C0 C1C0 FF80 FF00 C000 C000 C000 C000 C000 C000 C000 C000 Q 11 20 1 -2 13 3F00 7F80 E1C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 C0C0 CCC0 CEC0 C6C0 E7C0 7F80 3F80 01C0 00E0 0060 R 10 17 1 1 13 FF00 FF80 C1C0 C0C0 C0C0 C0C0 C1C0 FF80 FF00 C600 C700 C300 C380 C180 C1C0 C0C0 C0C0 S 10 17 1 1 13 3F00 7F80 E1C0 C0C0 C000 C000 F000 7C00 1F00 0780 01C0 00C0 C0C0 C0C0 F3C0 7F80 1E00 T 10 17 2 1 13 ffc0 ffc0 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 U 11 17 1 1 13 C060 C060 C060 C060 C060 C060 C060 C060 C060 C060 C060 C060 C060 E0E0 71C0 3F80 1F00 V 11 17 1 1 13 C060 C060 E0E0 60C0 60C0 70C0 31C0 3180 3180 3B80 1B00 1B00 1F00 0E00 0E00 0E00 0E00 W 12 17 0 1 13 C030 C030 C030 E030 6070 6660 6660 6660 6F60 7F60 3FE0 3FC0 3FC0 39C0 39C0 39C0 39C0 X 11 17 1 1 13 C060 E0E0 60C0 71C0 3180 3B80 1F00 0E00 0E00 0E00 1F00 3B80 3180 71C0 60C0 E0E0 C060 Y 11 17 1 1 13 C060 E0E0 60C0 71C0 3980 1B80 1F00 0F00 0E00 0600 0600 0600 0600 0600 0600 0600 0600 Z 10 17 1 1 13 7FC0 7FC0 0180 0380 0300 0700 0600 0E00 0C00 1C00 1800 3800 3000 7000 6000 FFC0 FFC0 [ 6 23 5 -4 13 fc00 fc00 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 fc00 fc00 \ 10 23 1 -4 13 C000 C000 E000 6000 7000 3000 3000 3800 1800 1800 1C00 0C00 0E00 0600 0600 0700 0300 0300 0380 0180 01C0 00C0 00C0 ] 6 23 1 -4 13 fc00 fc00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 0c00 fc00 fc00 ^ 8 5 2 14 13 1800 3C00 7E00 E700 C300 _ 13 2 -1 -4 13 fff8 fff8 ` 4 9 4 10 13 3000 7000 6000 E000 C000 C000 F000 F000 7000 a 8 11 2 1 13 FC00 FE00 E700 0300 1F00 7F00 F300 C300 C700 FF00 7F00 b 9 18 2 1 13 C000 C000 C000 C000 C000 C000 C000 FC00 FF00 E700 E380 C180 C180 C180 E380 E700 FF00 FC00 c 9 11 2 1 13 1F80 7F80 7380 E000 C000 C000 C180 E180 7380 7F00 1E00 d 10 18 1 1 13 00C0 00C0 00C0 00C0 00C0 00C0 00C0 1EC0 7FC0 73C0 E1C0 C0C0 C0C0 C0C0 E1C0 73C0 7FC0 1EC0 e 8 11 2 1 13 3C00 7E00 6700 E300 FF00 FF00 C000 E300 7700 7E00 1C00 f 9 18 1 1 13 0F00 0F80 1F80 1B80 1800 1800 1800 FF00 FF00 1800 1800 1800 1800 1800 1800 1800 1800 1800 g 10 15 1 -3 13 1EC0 7FC0 73C0 E1C0 C0C0 C0C0 C0C0 E1C0 73C0 7FC0 1EC0 C0C0 E1C0 7F80 3F00 h 8 18 2 1 13 C000 C000 C000 C000 C000 C000 C000 FE00 FF00 E300 C300 C300 C300 C300 C300 C300 C300 C300 i 3 18 5 1 13 e000 e000 e000 0000 0000 0000 0000 6000 6000 6000 6000 6000 6000 6000 6000 6000 6000 6000 j 7 22 1 -3 13 0E00 0E00 0E00 0000 0000 0000 0000 0600 0600 0600 0600 0600 0600 0600 0600 0600 0600 0600 0600 EE00 FC00 F800 k 8 18 2 1 13 C000 C000 C000 C000 C000 C000 C000 C300 C700 CE00 DC00 F800 F800 DC00 CE00 C600 C700 C300 l 2 18 6 1 13 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 m 10 11 2 1 13 FF80 FFC0 CCC0 CCC0 CCC0 CCC0 CCC0 CCC0 CCC0 CCC0 CCC0 n 8 11 2 1 13 FE00 FF00 E300 C300 C300 C300 C300 C300 C300 C300 C300 o 10 11 1 1 13 1E00 7F80 7380 E1C0 C0C0 C0C0 C0C0 E1C0 7380 7F80 1E00 p 9 15 2 -3 13 FC00 FF00 E700 E380 C180 C180 C180 E380 E700 FF00 FC00 C000 C000 C000 C000 q 10 15 1 -3 13 1EC0 7FC0 73C0 E1C0 C0C0 C0C0 C0C0 E1C0 73C0 7FC0 1EC0 00C0 00C0 00C0 00C0 r 8 11 3 1 13 DF00 FF00 F700 E000 C000 C000 C000 C000 C000 C000 C000 s 10 11 1 1 13 3F00 7FC0 E1C0 E000 FE00 3F80 03C0 C0C0 E1C0 7F80 3F00 t 10 16 1 1 13 3000 3000 3000 3000 3000 FF00 FF00 3000 3000 3000 30C0 30C0 30C0 39C0 1F80 0F00 u 8 11 2 1 13 C300 C300 C300 C300 C300 C300 C300 C300 E700 7F00 3F00 v 9 11 2 1 13 C180 C180 E380 6300 7700 3600 3600 3E00 1C00 1C00 1C00 w 10 11 1 1 13 CCC0 CCC0 CCC0 FFC0 7F80 7F80 7F80 7F80 3300 3300 3300 x 8 11 2 1 13 C300 E700 6600 7E00 3C00 1800 3C00 7E00 6600 E700 C300 y 11 15 0 -3 13 3060 3060 38E0 18C0 1DC0 0D80 0D80 0F80 0700 0700 0600 0E00 EC00 FC00 F800 z 10 11 1 1 13 7FC0 7FC0 0380 0700 0E00 0C00 1C00 3800 7000 FF80 FF80 { 10 22 1 -3 13 01C0 07C0 0F00 0C00 0C00 0C00 0C00 0C00 0C00 3C00 F800 F800 3C00 0C00 0C00 0C00 0C00 0C00 0C00 0F00 07C0 01C0 | 2 23 5 -4 13 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 c000 } 10 22 1 -3 13 E000 F800 3C00 0C00 0C00 0C00 0C00 0C00 0C00 0F00 07C0 07C0 0F00 0C00 0C00 0C00 0C00 0C00 0C00 3C00 F800 E000 ~ 10 4 1 15 13 3880 7FC0 FF80 4700  8 16 2 2 13 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 ff00 25-Aug-86 13:54:23-PDT,1014;000000000000 Return-Path: Received: from aplvax.ARPA by SUMEX-AIM.ARPA with TCP; Mon 25 Aug 86 13:53:47-PDT Received: by aplvax.ARPA (4.12/4.7) id AA07707; Mon, 25 Aug 86 16:53:11 edt Date: Mon, 25 Aug 86 16:53:11 edt From: marc@aplvax (Marcus H. Gates) Message-Id: <8608252053.AA07707@aplvax.ARPA> To: info-iris@sumex-aim Subject: Berkeley Font Catalog I have written a program to convert the fonts in the Berkeley font catalog into compilable C code which can then be displayed on our 2400T. I also have written a test program for use in displaying the fonts. If there is enough interest I could provide samples. The Berkeley font catalog comes with 4.?BSD unixes and was designed for use with a Versatec printer/plotter. For the larger fonts (point size > 20) the whole font cannot be loaded at one time so it is necessary to use some subset at that level. I don't know if the fonts are in the public domain, unless I can verify that they are, I can't distribute the actual fonts. 25-Aug-86 14:32:11-PDT,592;000000000000 Return-Path: Received: from Sushi.Stanford.EDU by SUMEX-AIM.ARPA with TCP; Mon 25 Aug 86 14:30:26-PDT Date: Mon 25 Aug 86 14:22:24-PDT From: Tomas G. Rokicki Subject: TeX previewer To: info-iris@SUMEX-AIM.Stanford.EDU Message-ID: <12233707502.23.ROKICKI@Sushi.Stanford.EDU> I wrote a TeX screen previewer for the IRIS workstations, if anyone is interested. It's not public domain, but is fairly cheap. (I also have TeX running, of course.) Mail me if you're interested. -tom rokicki (ROKICKI@SU-SUSHI.ARPA) ------- 25-Aug-86 19:50:15-PDT,800;000000000000 Return-Path: Received: from hera.CS.UCLA.EDU ([128.97.2.20].#Internet) by SUMEX-AIM.ARPA with TCP; Mon 25 Aug 86 19:49:46-PDT Received: by hera.CS.UCLA.EDU (Sendmail 5.45/5.14) id AA19458; Mon, 25 Aug 86 16:28:28 PDT Message-Id: <8608252328.AA19458@hera.CS.UCLA.EDU> To: marc@aplvax.arpa (Marcus H. Gates) Cc: info-iris@sumex-aim.arpa, trainor@CS.UCLA.EDU Subject: Re: Berkeley Font Catalog In-Reply-To: Your message of Mon, 25 Aug 86 16:53:11 -0400. <8608252053.AA07707@aplvax.ARPA> Date: Mon, 25 Aug 86 16:28:26 PDT From: Douglas J. Trainor Can you say public domain. They don't like to admit it, but due to the funding intricacies they can't actually do anything to you. They might whine a lot though... Douglas 29-Aug-86 08:27:32-PDT,607;000000000000 Mail-From: BRUGGE created at 29-Aug-86 08:27:03 Date: Fri 29 Aug 86 08:27:03-PDT From: John Brugge Subject: Iris SIGGRAPH meeting To: info-iris@SUMEX-AIM.ARPA Message-ID: <12234691389.11.BRUGGE@SUMEX-AIM.ARPA> I didn't make it to SIGGRAPH, but would be interested in hearing about the Iris Users Group meeting held there. Would someone who attended be willing to post a summary of what was presented? And was there mention of future Users Group meetings (especially in the Bay Area)? It sounded like they had an interesting program planned. Thanks, John ------- 29-Aug-86 10:25:51-PDT,6565;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Fri 29 Aug 86 10:24:51-PDT Date: Fri, 29 Aug 86 10:24:54 pst From: michael zyda Message-Id: <8608291824.AA13993@nps-cs> To: info-iris@sumex-aim Subject: SIGGRAPH and the IRIS User's Group Meeting... SIGGRAPH and the IRIS User's Group Meeting There are several pieces of information I have col- lected from my visit to SIGGRAPH in Dallas with respect to the IRIS that you may find useful. There is now a very nice stereo system available for the IRIS. It is a system produced by a company called Stereographics. I saw the system demonstrated and was quite impressed. The graphics monitor needs to be modified on the IRIS ($2000), a display controller needs to be added ($7000), and a set of visors purchased ($3000 for one). Most customers purchase two visors so for about $15,000 a very nice stereo image can be had. The visors go over the head like a welding mask so that people who wear glasses can use it. The light transmission is much better than the pre- vious systems. I have run across a three-dimensional digitizer camera that looks nice. The camera is produced by a small company 5 minutes in Pacific Grove, California. The company is called Cyberware Laboratories. The camera travels around the object to be digitized and produces a set of points on the surface of the object. The camera can digitize objects 14 inches cubic, which though small, is useful for models. The camera samples 512 lines in a cylindrical path around the object, each line being composed of 512 points. The data can be used to drive an NC controlled machine for pur- poses of milling a copy. I have received several sets of data digitized by this camera and have been playing with producing a filled polygon view of the objects. I put in a point source of light in the IRIS display and the models looked quite nice. The camera is priced at around $40,000. At the SIGGRAPH conference, Silicon Graphics had a User's Group Meeting. The purpose of this meeting was to provide a forum for IRIS users to ask questions and for SGI to discuss future products and software changes. There were a number of things that will have a strong impact. The most important item of note is that SGI is making TCP/IP the standard networking software as opposed to the XNS software they formerly supported. This change will occur with release 3.5 of the IRIS software. With this change, SGI will switch from supporting System V Unix to Berkeley 4.3 Unix. This is a major change. Any networking software using System V sockets will probably have to be rewritten. The use of 'sockets' under 4.3 Unix is very different from that under System V Unix. There are bound to be a number of other changes that will affect the System V embedded people. Another thing to be aware of is that SGI will soon sup- port the product Network File System (NFS). NFS is a facil- ity for sharing files in a heterogeneous computing environ- ment, i.e. between workstations and remote computers. August 29, 1986 - 2 - Remote files will be able to be accessed in a transparent fashion. I understand that this is under test currently at SGI headquarters. Part of the IRIS user's group meeting was a talk by Paul Haeberli on the future of the Window Manager. He stated that changes will be forthcoming in the next six months in the Window Manager. I hope they are additions and not major changes. Paul seemed unable to discuss the per- formance limitations of the Connection Manager he showed off there. He also gave me the feeling that I better not use the IRIS Window Manager because it is not yet in a stable form. The SGI future directions section was a bit disappoint- ing. Jim Clark really did not say much that was new. The user's group will be producing a newsletter answer- ing questions brought up that could not be answered at the meeting. There was some fairly harsh questioning of Ed McCracken with respect to the IRIS product in its many forms. There were several people whose software would run on the 2400 and not on the Turbo/3020 series. There were people whose 3020 systems ran slower than their 2400 ver- sions of the same product. There were requests for asyn- chronous I/O for disk drives so that the IRIS could perform like a real-time system. There were evidently many ques- tions that people still had about the IRIS that did not get answered as the time ran out. Zsuzsa Molnar collected some of those questions and will attempt to get answers for them. These answers should comprise the User's Group Newsletter. I am hoping that part of this newsletter will be a list of the people who attended the User's Group Meeting and their addresses... I didn't get time to ask some of my favorite questions at the User's Group Meeting because of the shortness of time. One of mine is why are maintenance costs so high? The Full Support Maintenance for my Turbo system next year is $11,940 or 20.3% of the replacement cost of the machine. The Full Support Maintenance for my 2400 is $9,060 or 31% of the replacement cost of the machine. The person in charge of Maintenance for the IRIS, Mr. Daniels, charges you based on the original price you purchased the IRIS for, in effect penalizing long time users of the IRIS. Let's hope that this changes!!! My other request was can we get the Popup Menu routines to work in standalone, non-Window Manager mode. Since Mr. Haeberli has not yet finished with changing the Window Manager, I feel it would be nice to provide standalone Popup Menu support LIKE ALL THE REST OF THE ROUTINES IN GL2. That is about all I have for the moment of the User' August 29, 1986 - 3 - Group Meeting. I would like to hear other people's opinions on that meeting. Michael J. Zyda zyda@nps-cs.arpa ucbvax!olympus!nps-cs!zyda August 29, 1986 4-Sep-86 14:39:31-PDT,488;000000000000 Return-Path: Received: from IUS2.CS.CMU.EDU by SUMEX-AIM.ARPA with TCP; Thu 4 Sep 86 14:38:27-PDT Date: 4 Sep 1986 17:33-EDT From: Ralph.Hyre@ius2.cs.cmu.edu To: info-iris@sumex-aim Cc: michael zyda Subject: Re: SIGGRAPH and the IRIS User's Group Meeting... Message-Id: <526253604/ralphw@ius2.cs.cmu.edu> Now that SGI's switching from XNS to TCP/IP, will the dogfight and flight programs be rewritten to use the 'supported' protocols? 4-Sep-86 14:47:25-PDT,883;000000000000 Mail-From: CORNELIUS created at 4-Sep-86 14:46:23 Date: Thu 4 Sep 86 14:46:19-PDT From: Craig Cornelius Subject: IRIS WS and Terminal To: info-iris@SUMEX-AIM.ARPA Message-ID: <12236333296.29.CORNELIUS@SUMEX-AIM.ARPA> We have an old IRIS 1200 terminal and a new 3020 IRIS workstation. We'd like to use the 1200 as a graphics terminal with the 3020, but all graphics commands issued from a terminal (we are using Telnet to connect over the TCP network connection) cause the graphics to be drawn on the workstation CONSOLE, not the remote 1200 terminal. Is there anyone out there who knows how to (if it's possible) configure the workstation so that graphics commands are sent over the serial line to a direct connected graphics terminal, or over a net connection to a terminal. Thanks for any suggestions. Craig Cornelius ------- 4-Sep-86 14:49:46-PDT,721;000000000000 Mail-From: CORNELIUS created at 4-Sep-86 14:49:09 Date: Thu 4 Sep 86 14:49:09-PDT From: Craig Cornelius Subject: Console - base unit To: info-iris@SUMEX-AIM.ARPA Message-ID: <12236333813.29.CORNELIUS@SUMEX-AIM.ARPA> Does anyone know how far the CPU/disk/graphics controller of a 3020 workstation can be situated from the console/keyboard/dials-and-buttons of the same machine? We'd like to put our noisy base unit in a separate room, at some distance from the console site. Are there any specs? Has anyone tried making cables to separate the units further than that allowed by SGI supplied cables? Again, I appreciate any pointers or suggestions. Craig Cornelius ------- 4-Sep-86 15:38:50-PDT,505;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Thu 4 Sep 86 15:36:54-PDT Date: Thu, 4 Sep 86 15:03:45 pst From: michael zyda Message-Id: <8609042303.AA04292@nps-cs> To: info-iris@sumex-aim Subject: Dogfight and flight under TCP/IP... Dogfight and flight have already been rewritten to use TCP/IP. I believe this was done by Al Casarez at SGI at the insistence of a major SGI customer. I don't know why they don't distribute it... Michael Zyda 4-Sep-86 20:52:24-PDT,763;000000000000 Return-Path: Received: from ames-nasb.arpa by SUMEX-AIM.ARPA with TCP; Thu 4 Sep 86 20:52:02-PDT Received: Thu, 4 Sep 86 20:52:33 PDT by ames-nasb.arpa (5.28/1.2) Message-Id: <8609050352.AA00397@ames-nasb.arpa> To: Craig Cornelius Cc: info-iris@SUMEX-AIM.ARPA Subject: Re: Console - base unit In-Reply-To: Your message of Thu 4 Sep 86 14:49:09-PDT. <12236333813.29.CORNELIUS@SUMEX-AIM.ARPA> Date: 04 Sep 86 20:52:32 PDT (Thu) From: creon@ames-nasb.arpa We have cables that go hundreds of feet, and through a patch panel. If the patch panel connectors get dirty then sharp edges start to streak on the console, but other than that long cables seem to work pretty well. ---------- 11-Sep-86 10:13:04-PDT,1107;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.ARPA with TCP; Thu 11 Sep 86 10:12:17-PDT Date: Thu 11 Sep 86 10:12:27-PDT From: Lloyd La Comb Subject: IRIS tutorial To: Info-Iris@SUMEX-AIM.Stanford.EDU cc: lacomb@Sierra.Stanford.EDU Message-ID: <12238118448.10.LACOMB@Sierra.Stanford.EDU> I was out a Silicon Graphics the other day, and got a look at a new tutorial system they have developed. The tutorial system shows the workings of almost all of the graphics commands (viewport, lookat, scale, etc) in an interactive enviroment. The user selects a parameter within the command and then can use the mouse the change the value of that parameter and the results appear instantly on the screen. I sure this will be really useful not only for people just starting to learn the system, but also those with considerable experience. It is supposed to come out with the 3.5 release in the next few months. Lloyd La Comb lacomb@su-sierra.arpa ------- 11-Sep-86 12:12:22-PDT,620;000000000000 Mail-From: BRUGGE created at 11-Sep-86 12:10:46 Date: Thu 11 Sep 86 12:10:45-PDT From: John Brugge Subject: Re: IRIS tutorial To: info-iris@SUMEX-AIM.ARPA Message-ID: <12238139983.82.BRUGGE@SUMEX-AIM.ARPA> That sounds like a wonderful program! Even after working with an IRIS for a year I would still like to have a more intuitive feel for what some of the transformations do, and just how the parameters affect them. Having the source code for that would help too, to see how the commands are put together. Another reason to look forward to the next release... John ------- 18-Sep-86 08:44:45-PDT,928;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Thu 18 Sep 86 08:44:24-PDT Date: Thu, 18 Sep 86 11:42 EDT From: MCCALPIN%FSU.MFENET@LLL-MFE.ARPA Subject: Serial Communications ??? To: info-iris@sumex-aim.arpa We recently installed an IRIS 3030, and would like to run more serial ports. They seem to be cheaper than TCP/IP terminal servers by a factor of 2 or so. We are talking to the people at MicroBar, who sell a generic MultiBus board, but the UNIX termio software they provide is unsupported. Is anyone out there running dumb terminals/modems on an MultiBus serial port controller ??? If so, do you have any advice or suggestions ??? Thanks, John D. McCalpin mccalpin%fsu.mfenet@lll-mfe.arpa mcalpin@fsuesr.bitnet 18-Sep-86 09:11:03-PDT,1398;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Thu 18 Sep 86 09:10:38-PDT Date: Thu, 18 Sep 86 11:29 EDT From: MCCALPIN%FSU.MFENET@LLL-MFE.ARPA Subject: New Installation To: INFO-IRIS@SUMEX-AIM.ARPA We have just installed an IRIS 3030 with 2 170 MB drives, 1/2" tape, and lots of other goodies at the Mesoscale Air-Sea Interaction Group at Florida State University. We do numerical simulations of the large-scale, wind-driven ocean circulation and animate the results on the IRIS. So far, all the graphics calculations are done on the mainframe (a Cyber 205), and downloaded via tape or phone lines to our machine (no E-net installed yet). For archives and presentations, we run the video through an RGB/NTSC encoder then to VHS format videotape. The IRIS software consists of a graphics metacode translator, and an animation control program which lets us look at the 'movies' in many different ways (change order of frames, look at every n'th frame, change colors, turn on/off objects/overlays, etc). John D. McCalpin Control Data Corp. PACER Fellow Dept. of Oceanography, FSU (904) 644-6532 mccalpin%fsu.mfenet@lll-mfe.arpa mcalpin@fsuesr.bitnet 23-Sep-86 08:16:39-PDT,1860;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Tue 23 Sep 86 08:14:14-PDT Date: Tue, 23 Sep 86 11:13 EDT From: MCCALPIN%FSU.MFENET@LLL-MFE.ARPA Subject: IRIS 3030 Benchmarks To: INFO-IRIS@SUMEX-AIM.ARPA I just ran the LINPACK benchmarks on our new IRIS 3030 and came up with some puzzling results. Jack Dongarra at Argonne National Labs publishes the results of benchmarks on many machines. These are posted on his bulletin board (netlib@anl-mcs.arpa), along with the benchmark codes (in fortran). The only IRIS listed is the 2400 Turbo. I got the codes and ran the tests with the FPA and my results are noticeably slower than the IRIS 2400 Turbo. Specifically: LINPACK test IRIS 3030 IRIS 2400T 2400T coded -------------------------------------------------------------------- 64 bit reals .206 Mflops .24 Mflops .34 Mflops 32 bit reals .310 Mflops .40 Mflops .53 Mflops -------------------------------------------------------------------- These results are for systems of linear equations on order 100. The last column reports test results for the LINPACK tests with hand- coded (assembly language) Basic Linear Algebra Subroutines (BLAS), with noticeably improved results. I would guess that someone at NASA/Ames did those tests. I used a C function based on clock() to get the timings. I also ran a test of a system of order 1000 (also from Dongarra) and got a result of 0.383 Mflops. If anyone knows why the 3030 is slower than the 2400T on these tests, I would be interested. Also, if anyone wants to donate the coded BLAS, I'm sure I could put them to good use. John D. McCalpin mccalpin%fsu.mfenet@lll-mfe.arpa 23-Sep-86 11:07:17-PDT,423;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Tue 23 Sep 86 11:05:07-PDT Date: Tue, 23 Sep 86 13:21 EDT From: MCCALPIN%FSU.MFENET@LLL-MFE.ARPA Subject: Addendum to Benchmark Note To: INFO-IRIS@SUMEX-AIM.ARPA Sorry that I did not specify, but all the benchmarks that I have done, and the ones reported in Dongarra's papers, are the Fortran benchmarks. 23-Sep-86 18:47:18-PDT,1015;000000000000 Return-Path: Received: from decwrl.dec.com by SUMEX-AIM.ARPA with TCP; Tue 23 Sep 86 18:41:46-PDT Received: by decwrl.dec.com (5.54.2/4.7.34) id AA14619; Tue, 23 Sep 86 18:41:27 PDT Received: by sgi.SGI (5.9/5.6) id AA24367; Tue, 23 Sep 86 15:29:47 PDT Received: by radio.SGI (5.9/5.6) id AA29656; Tue, 23 Sep 86 15:28:12 PDT From: sgi!baskett@decwrl.DEC.COM (Forest Baskett) Message-Id: <8609232228.AA29656@radio.SGI> Date: 23 Sep 1986 1528-PDT (Tuesday) To: info-iris@sumex.stanford.edu Subject: Re: IRIS 3030 Benchmarks In-Reply-To: Your message of Tue, 23 Sep 86 11:13 EDT. We were able to quickly duplicate Dongarra's Iris 2400T numbers on a local Iris 3030, as should be the case, using the current software. The only explanations we can easily think of to account for McCalpin's slower numbers is either compiling without optimization or compiling with an old release compiler in which the code generator was not as good as in the current one. Forest 24-Sep-86 01:15:33-PDT,500;000000000000 Return-Path: Received: from Psych.Stanford.EDU by SUMEX-AIM.ARPA with TCP; Wed 24 Sep 86 01:15:15-PDT Received: by Psych.Stanford.EDU; Wed, 24 Sep 86 01:11:12 PDT To: INFO-IRIS@sumex-aim.arpa Subject: Kermit Cc: mis@Psych.Stanford.EDU Date: 24 Sep 86 01:11:10 PDT (Wed) From: mis@psych.stanford.edu Does anyone have or know about Kermit communication program that would run on a 2400T? Thanks in advance, Misha Pavel, 24-Sep-86 14:15:20-PDT,2061;000000000000 Return-Path: Received: from USNA.ARPA by SUMEX-AIM.ARPA with TCP; Wed 24 Sep 86 14:13:40-PDT Date: Wed, 24 Sep 86 15:02:58 EDT From: Brent W Baccala To: Info-Iris@SUMEX-AIM.ARPA Subject: install screws up chown on default installation Subject: install screws up chown on default installation Index: /etc/install 5.0+ (GL2-W3.4) Description: If install is run with the "-n" and "-u" options set and can't find the file to be installed in any of the standard places (i.e. it must use the directory specified in the "-n" option), it will try to do the chown on a file in the root directory, instead of the default directory. Install does this because the chown command uses an empty variable name, instead of the one with the directory name in it. I haven't checked for the bug or tested the fix on pre-3.4 systems. Repeat-By: Touch a file called "foo" (or some other funny name that won't show up as a program) and do the following: /etc/install -n /tmp -u root foo Note that the chown is attempted on /foo, not /tmp/foo. Fix: Change the variable name. A diff follows: 596c596 < chown $OWNER $direct/$FILE --- > chown $OWNER $LASTRES/$FILE NOTE: The name direct is a valid name at other points in the script. In fact, the above line (with direct) appears verbatim at several other points in the file. Therefore, make sure that the change is made on line 596 (W3.4), and that the command itself is in an if block introduced by the following lines (569-576 in 3.4): case $FOUND in "") echo "install: $FILE was not found anywhere!" exit 2;; y) : ;; n) $CMD $FILEP $LASTRES/$FILE if [ $? = 0 ] then $ECHO "$FILEP installed as $LASTRES/$FILE by default!" ... - BRENT W. BACCALA - Aerospace Engineering Department U.S. Naval Academy Annapolis, MD "I do graphics work on an SGI Iris, fun work on a VAX 11/780, grunge work on an IBM XT" 24-Sep-86 16:18:36-PDT,1065;000000000000 Return-Path: Received: from PROPHET.BBN.COM by SUMEX-AIM.ARPA with TCP; Wed 24 Sep 86 16:17:37-PDT Date: Wed, 24 Sep 86 12:31:27 EDT From: Dave Swindell To: info-iris@sumex-aim.arpa Subject: [PROPHET Memo Service: Failed mail (msg.a023112)] Misha: A friend I work with forwarded you message to me regarding Kermit on the Iris 2400T. I've just recently had exposure to the Iris series of workstations. We have on site a 3020 which runs Silicon Graphics's implementation of AT&T system V Unix. Over the weekend, I FTP'ed the sources for ckermit from the Columbia computer (cu20b) and built a working ckermit using the "sys3" directive to the Makefile provided from Columbia. I'm not familiar with the differences between the SGI Iris 2400T and the 3020, however, if these machines are compatible, you should have no problems. The ckermit sources are in the "ker:" directory and all have the prefix "ck". Hope this helps, Dave Swindell BBN Laboratories Incorporated 26-Sep-86 21:13:30-PDT,1158;000000000000 Return-Path: Received: from sdcsvax.UCSD.EDU.ucsd.edu (SDCS-VAX.ARPA.#Internet) by SUMEX-AIM.ARPA with TCP; Fri 26 Sep 86 21:11:38-PDT Received: by sdcsvax.UCSD.EDU.ucsd.edu (5.51/4.42) id AA26764; Thu, 25 Sep 86 23:16:43 PDT hops=0 Date: Thu, 25 Sep 86 23:16:43 PDT From: megatek@sdcsvax.ucsd.edu (Megatek) Message-Id: <8609260616.AA26764@sdcsvax.UCSD.EDU.ucsd.edu> To: BRUGGE@sumex-aim.arpa, info-iris@sumex-aim.arpa Subject: re: GNU Emacs Hi, My name is Derek Lai and I'm with Template, the software division of Megatek Corp. in San Diego. We are in the middle of porting our software to run on the Silicon Graphics Iris. I'm very interested in getting emacs to run on the Iris. (So much for AME. It's ok but does not have much feature in it). I saw the message by John and was wondering if I can get the source to GNU emacs from you. I got a version of GNU emacs that runs on VAXes but can't get it to work on the Iris. Please give me a reply by mail or phone, and I'll send a cartridge and the postage to you. Thanks in advance. Derek Lai. Template Megatek Corp. (619) 455-5590 x2034 26-Sep-86 21:14:01-PDT,1005;000000000000 Return-Path: Received: from sdcsvax.UCSD.EDU.ucsd.edu (SDCS-VAX.ARPA.#Internet) by SUMEX-AIM.ARPA with TCP; Fri 26 Sep 86 21:13:25-PDT Received: by sdcsvax.UCSD.EDU.ucsd.edu (5.51/4.42) id AA26117; Thu, 25 Sep 86 22:58:13 PDT hops=0 Date: Thu, 25 Sep 86 22:58:13 PDT From: megatek@sdcsvax.ucsd.edu (Megatek) Message-Id: <8609260558.AA26117@sdcsvax.UCSD.EDU.ucsd.edu> To: info-iris@sumex-aim.arpa Subject: emacs info requested Hi, Anyone out there knows of a version of EMACS that will run correctly on the Silicon Graphics Iris ? We have a 3030 here. I heard from Silicon Graphics that there's a version they know, but it does not work well and crashes the system often. Has anyone attempted to port the new GNU emacs over to the Iris? I have the source to it but I can't get it to work on the Iris. If anyone can give me some pointer, it will be greatly appreciated. Derek Lai Template Megatek Corp. (619) 455-5590 x 2034. 27-Sep-86 01:31:59-PDT,1259;000000000000 Return-Path: Received: from USNA.ARPA by SUMEX-AIM.ARPA with TCP; Sat 27 Sep 86 01:31:40-PDT Date: Sat, 27 Sep 86 4:28:35 EDT From: Brent W Baccala To: Info-Iris@sumex-aim.ARPA Subject: Install bug and EMACS 1) In <2061@USNA.ARPA>, I wrote: > 596c596 > < chown $OWNER $direct/$FILE > --- > > chown $OWNER $LASTRES/$FILE Hmmm...you can just knock out the "$LASTRES/" in the replacement; its redundent since install already cd'ed to $LASTRES. Mustn't have been thinking. 2) There have been a number of requests for EMACS or a version of it that runs on the IRIS. We run a version of EMACS known as JOVE (Jonhathan's Own Version of EMACS). It seems to work just fine, and I'm almost certain its public domain. I'm not sure if this is what you're looking for, but like I said, it works for us. If there's enough interest, I'll try to have it made available by anonymous ftp. UUCP'ers are requested to flag their requests as such. -bwb - BRENT W. BACCALA - Aerospace Engineering Department U.S. Naval Academy Annapolis, MD "I do graphics work on an SGI Iris, fun work on a VAX 11/780, grunge work on an IBM XT" 27-Sep-86 10:05:27-PDT,922;000000000000 Return-Path: Received: from topaz.rutgers.edu by SUMEX-AIM.ARPA with TCP; Sat 27 Sep 86 10:05:06-PDT Received: by topaz.rutgers.edu; Sat, 27 Sep 86 13:04:34 edt Date: Sat, 27 Sep 86 13:04:34 edt From: gallaher@topaz.rutgers.edu (Mike Gallaher) Message-Id: <8609271704.AA00988@topaz.rutgers.edu> To: info-iris@sumex-aim.arpa There is now an Iris driver in unipress emacs (V2.10 and later). It runs in a graphics port, both full-screen and under mex, can handle window size changes, and supports settable color schemes. Mouse input is encoded as keystroke sequences; the NO-SCRL key is used as a meta key. I've been using on our 2400T for a couple of months and it works quite well. This Emacs does cost money ($995 for source, less than half that for binary). The number for Unipress is 201 985 8000; if you have technical questions you can mail them to me. Mike Gallaher 28-Sep-86 07:53:34-PDT,738;000000000000 Return-Path: Received: from eneevax.umd.edu by SUMEX-AIM.ARPA with TCP; Sun 28 Sep 86 07:53:11-PDT Received: by eneevax.umd.edu (5.9/4.7) id AA10615; Sat, 27 Sep 86 15:12:48 EDT Date: Sat, 27 Sep 86 15:12:48 EDT From: Velu Sinha Message-Id: <8609271912.AA10615@eneevax.umd.edu> To: baccala@USNA.ARPA Cc: Info-Iris@sumex-aim.ARPA In-Reply-To: Brent W Baccala's message of Sat, 27 Sep 86 4:28:35 EDT Subject: Install bug and EMACS From my understanding - JOVE is NOT public domain. It uses parts of vi which are (c) by AT&T / Berkley. You need a Berkley license to run JOVE... Someone at BRL was working on a totaly PD version of JOVE - anyone have any info? 28-Sep-86 10:47:00-PDT,768;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Sun 28 Sep 86 10:46:28-PDT Date: Sun, 28 Sep 86 13:23:12 EDT From: Ron Natalie To: Velu Sinha cc: baccala@usna.arpa, Info-Iris@sumex-aim.arpa Subject: Re: Install bug and EMACS Message-ID: <8609281323.aa17818@SEM.BRL.ARPA> Jove never contained parts of VI. It used to contain some regular expression code from /bin/ed. However, I believe this is no longer the case. Anyhow, JOVE is available for next to nothing under license. The easiest way to get it is to look in the user contributed section of the 4.3 BSD tape. The version of JOVE there is much newer than any version that we have at BRL. -Ron 29-Sep-86 06:49:58-PDT,1242;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Mon 29 Sep 86 06:49:40-PDT Date: Sun, 28 Sep 86 17:08 EDT From: MCCALPIN%FSU.MFENET@LLL-MFE.ARPA Subject: IRIS 3030 Benchmarks Cont'd To: INFO-IRIS@SUMEX-AIM.ARPA I got a copy of the LINPACK benchmarks used by SGI (from Tom Barton in the Dallas office). These ran at the same speed as the 2400T results reported in the Dongarra paper because they used loop unrolling to optimize the BLAS routines (saxpy,sdot, etc). The version of the code that I retrieved off of Dongarra's bulletin board does not use loop unrolling in the BLAS. The SGI version uses unrolling to 4 operations per loop. The Dongarra benchmark program LUS shows this to be optimum for the IRIS f77 compiler. So with unrolling to 4 operations/loop, I get .40 Mflops in single precision, and .250 Mflops in double precision. These rates are for USER time only. Including system time drops the speeds slightly, to about .39 Mflops and .24 Mflops, respectively. John D. McCalpin mccalpin%fsu.MFENET@lll-mfe.ARPA mcalpin@fsuesr.BITNET 29-Sep-86 21:14:15-PDT,424;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Mon 29 Sep 86 21:12:11-PDT Date: Mon, 29 Sep 86 23:07:51 EDT From: Mike Muuss To: Megatek cc: info-iris@sumex-aim.arpa Subject: Re: emacs info requested Message-ID: <8609292307.aa25732@SEM.BRL.ARPA> Unipress emacs (formerly Gossling's) runs on the IRIS. -Mike 29-Sep-86 21:17:02-PDT,576;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Mon 29 Sep 86 21:12:44-PDT Date: Mon, 29 Sep 86 23:17:28 EDT From: Mike Muuss To: Brent W Baccala cc: Info-Iris@sumex-aim.arpa Subject: Re: Install bug and EMACS Message-ID: <8609292317.aa25763@SEM.BRL.ARPA> While visiting Cray two weeks ago, I greatly improved the "port" of JOVE to the SGI, and we are running it at BRL now. If people would like JOVE, I'll get my fixes to Brent and let him distribute it. -Mike 29-Sep-86 21:19:40-PDT,391;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Mon 29 Sep 86 21:14:00-PDT Date: Mon, 29 Sep 86 23:19:21 EDT From: Mike Muuss To: info-iris@sumex-aim.arpa Subject: SGI FTP bug Message-ID: <8609292319.aa25765@SEM.BRL.ARPA> In Version 3.4, /usr/bin/ftp is set user-id to root, with messy results. Beware. -Mike 30-Sep-86 10:36:16-PDT,911;000000000000 Return-Path: Received: from ames-nas.ARPA by SUMEX-AIM.ARPA with TCP; Tue 30 Sep 86 10:35:00-PDT Received: from ames-prandtl.ARPA (prandtl-ec) by ames-nas.ARPA; Tue, 30 Sep 86 10:09:55 pdt Received: by ames-prandtl.ARPA (4.12/4.7) id AA14611; Tue, 30 Sep 86 09:43:13 pdt Date: Tue, 30 Sep 86 09:43:13 pdt From: dat@ames-prandtl.ARPA (David A. Tristram) Message-Id: <8609301643.AA14611@ames-prandtl.ARPA> To: megatek@sdcsvax.ucsd.edu Subject: Re: emacs info requested Cc: info-iris@sumex-aim.ARPA I have put gnu on the iris, it works, we had to fix unexec to get it to dump dump itself, you are welcome to it. Yesterday, we compiled UNIpress 2.10 which is pretty close to working in graphports with the window manager. You can have full screen (~121 col) windows, and there is mouse support. Dave Tristram 415 694 6410 NASA Ames Research Center dat@ames-nas 1-Oct-86 13:04:00-PDT,1169;000000000000 Return-Path: Received: from decwrl.dec.com by SUMEX-AIM.ARPA with TCP; Wed 1 Oct 86 13:02:50-PDT Received: by decwrl.dec.com (5.54.2/4.7.34) id AA25960; Wed, 1 Oct 86 13:02:51 PDT Received: by sgi.SGI (5.9/5.6) id AA00433; Wed, 1 Oct 86 11:34:36 PDT Received: by radio.SGI (5.9/5.6) id AA09853; Wed, 1 Oct 86 11:33:01 PDT From: sgi!baskett@decwrl.DEC.COM (Forest Baskett) Message-Id: <8610011833.AA09853@radio.SGI> Date: 1 Oct 1986 1132-PDT (Wednesday) To: info-iris@sumex.stanford.edu Cc: dongarra@anl-mcs.ARPA Subject: Re: IRIS 3030 Benchmarks Cont'd In-Reply-To: Your message of Sun, 28 Sep 86 17:08 EDT. <8609291429.AA02964@decwrl.dec.com> About a year and a half ago, Jack Dongarra changed the posted version of the Linpack code from "by four" unrolled loops to fully rolled loops in the Fortran Blas routines. He did this for the benefit of the vector compilers on the vector machines that were becoming more numerous then. He accepts timing results from either version. As noted, you will get better results with the original unrolled loop code on current Iris systems. Forest Baskett 2-Oct-86 15:23:07-PDT,969;000000000000 Return-Path: Received: from WISCVM.WISC.EDU by SUMEX-AIM.ARPA with TCP; Thu 2 Oct 86 15:20:21-PDT Received: from (MAILER)UNBMVS1.BITNET by WISCVM.WISC.EDU on 10/02/86 at 17:19:25 CDT Date: 02 Oct 86 15:59:30 ADT From: To: info-iris@sumex-aim.ARPA Subject: floating point unit for the iris2400 Message-ID: Help Help Help !!! We have acquired a floating point unit for our IRIS 2400B How do I install it? Are there switchs to be set? Which Slot does it go in? Does the system(software) have to be reconfigured? We have 12 bitplanes and 1.5 Meg of real memory. Michael MacDonald Software Specialist, School of Computer Science University of New Brunswick Po. Box 4400 Fredericton, New Brunswick CANADA E3B 5A3 (506) 453-4566 Netnorth/BITNET: MIKEMAC @ UNBMVS1 3-Oct-86 21:11:48-PDT,571;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Fri 3 Oct 86 21:11:16-PDT Date: Fri, 3 Oct 86 23:37:49 EDT From: Mike Muuss To: info-iris@sumex-aim.stanford.EDU Subject: 3.4 tcp rots Message-ID: <8610032337.aa02115@SEM.BRL.ARPA> We find that we have to reboot our machines (3030s running 3.4 with TCP) about every two hours, due to the Excelan TCP "jamming up". This is a real pain. Is there anything easy we can do short of rebooting, or do we just wait for 3.5 with a real TCP? -Mike 6-Oct-86 09:18:53-PDT,928;000000000000 Return-Path: Received: from ames-nas.ARPA by SUMEX-AIM.ARPA with TCP; Mon 6 Oct 86 09:16:48-PDT Received: from ames-prandtl.ARPA (prandtl-ec) by ames-nas.ARPA; Mon, 6 Oct 86 09:16:18 pdt Received: by ames-prandtl.ARPA (4.12/4.7) id AA10793; Mon, 6 Oct 86 08:55:24 pdt Date: Mon, 6 Oct 86 08:55:24 pdt From: dat@ames-prandtl.ARPA (David A. Tristram) Message-Id: <8610061555.AA10793@ames-prandtl.ARPA> To: info-iris@sumex-aim.stanford.EDU, mike@BRL.ARPA Subject: Re: 3.4 tcp rots Mike, If you are getting hosed on an EXOS Panic Error, like the ones we see, you may be able to recover by just starting up the daemons again. We use the script appended to this message, well, I thought I was going to append it, but the machine its on just had an EXOS panic. The idea is, yuo kill the old daemons, and rerun rc.tcp, which sometimes has to be done twice. Dave Tristram. NAS 694-6410 6-Oct-86 10:59:12-PDT,1662;000000000000 Return-Path: <@oak.cadif.cornell.edu:garry@cadif.decnet> Received: from cu-arpa.cs.cornell.edu by SUMEX-AIM.ARPA with TCP; Mon 6 Oct 86 10:56:28-PDT Message-Id: <8610061755.AA01185@cu-arpa.cs.cornell.edu> Received: by cu-arpa.cs.cornell.edu (5.45/4.30) id AA01185; Mon, 6 Oct 86 13:55:30 EDT Date: 0 0 00:00:00 EDT From: "CADIF::GARRY" Subject: 3.4 tcp yuck To: "info-iris%sumex-aim.stanford.edu" Reply-To: "CADIF::GARRY" I haven't observed the system completely "jamming up" due to Tcp, but I *have* observed: - Many many lost packets or protocol errors between the Iris and a local 4.3 BSD Gould. What we see is ftp or telnet hanging randomly and frequently. None of our other machines has trouble talking to the Gould. - Lost packets and *machine crashes* (both the Iris end and the Vax end) when talking to a Wollongong (pseudo 4.1 BSD) Vax. None of our other machines has trouble talking to the Vax. - When running ftp on the Iris, and doing "gets", and nothing visibly going wrong, oftentimes no output file is created. Retrying the operation usually eventually results in a successfully transferred file. Telnet and Ftp coming *from* the Iris seem to work much worse than going *to* the Iris. So we try to avoid doing that. Haven't tried rcp, rlogin, etc. Haven't tried connecting from the Iris to very many different machines yet. Hope it helps to know you have company - garry wiegand (garry%cadif-oak@cu-arpa.cs.cornell.edu) ------ 7-Oct-86 08:36:57-PDT,1387;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.ARPA with TCP; Tue 7 Oct 86 08:36:37-PDT Date: Tue 7 Oct 86 08:03:16-PDT From: Lloyd La Comb Subject: TCP/IP problems To: Info-Iris@SUMEX-AIM.Stanford.EDU Message-ID: <12244910675.11.LACOMB@Sierra.Stanford.EDU> I've had a lot of problems with my TCP/IP kernel also. I find that if I'm loged in on the Iris and try to get or send a file to another machine using FTP it works about 20% of the time. The chances are greater if I'm talking to another UNIX machine. If I log in to the other machine (UNIX or not) and ftp to the Iris it works almost all the time. I don't have the "crashing" or "tying up" problems under 3.4 that I had under 3.3.1 but it hanges every once in a while. The other major question I have is does anybody out there have sendmail or anyway to get mail to the Irises over the network? It would sure save me a lot of time if I could just mail the files from my Iris rather than FTPing them to a machine with a mailer. I have tried rlogin and rsh and they both work well enough if I,m talking to a 4.2 machine but the 4.3 machines seem to hang up on me right after login. Thanks Lloyd La Comb lacomb@su-sierra.arpa ------- 7-Oct-86 14:53:59-PDT,512;000000000000 Return-Path: Received: from scubed by SUMEX-AIM.ARPA with TCP; Tue 7 Oct 86 14:51:57-PDT Received: from shiva (shiva.ARPA) by scubed (4.12/5.20b) id AA23474; Tue, 7 Oct 86 11:54:59 pdt Received: by shiva (4.12/5.20a) id AA15904; Tue, 7 Oct 86 11:52:35 pdt Date: Tue, 7 Oct 86 11:52:35 pdt From: me%shiva@scubed.ARPA (Mark Erikson) Message-Id: <8610071852.AA15904@shiva> To: Info-Iris@sumex-aim Subject: test message Attempting to send mail via arpanet. Mark 7-Oct-86 19:53:53-PDT,1052;000000000000 Return-Path: Received: from scubed by SUMEX-AIM.ARPA with TCP; Tue 7 Oct 86 19:53:31-PDT Received: from shiva (shiva.ARPA) by scubed (4.12/5.20b) id AA28551; Tue, 7 Oct 86 19:58:56 pdt Received: by shiva (4.12/5.20a) id AA01493; Tue, 7 Oct 86 19:56:36 pdt Date: Tue, 7 Oct 86 19:56:36 pdt From: warner%shiva@scubed.ARPA (Ken Warner) Message-Id: <8610080256.AA01493@shiva> To: Info-Iris@sumex-aim This probably has nothing to do with the problems others are having but ... We were having problems with rlogin and other network utilities. Sometimes they worked ... sometimes they didn't. We replaced the ethernet board. Same problem. When we replaced the board we noticed there wasn't any heat sinks on the, I dunno what, gate arrays? pals? ... they were square and they were HOT. So anyway, this board was in a slot between two other boards. We moved it into a slot that had an adjacent empty slot so to allow better cooling. No more problems. We are running a 2400T with GL2-W3.4 and an Eagal. Ken 8-Oct-86 07:45:10-PDT,980;000000000000 Return-Path: Received: from NRTC-GREMLIN.NORTHROP.COM by SUMEX-AIM.ARPA with TCP; Wed 8 Oct 86 07:44:49-PDT Received: from nrtc-gremlin by NRTC-GREMLIN.NORTHROP.COM id a008702; 6 Oct 86 10:28 PDT To: Mike Muuss cc: willson@nrtc-gremlin, info-iris@sumex-aim.ARPA Subject: Re: 3.4 tcp rots Date: Mon, 06 Oct 86 10:28:55 -0700 From: Stephen Willson Dear Mike and info-iris readers: We had the same problem with our 3030 when we first got it. Now we don't have the problem anymore! Initially, we could rlogin from another unix system but telnet wouldn't work. Now, both work reliably. I cut down on the number of outstanding getty's running, from about 8, down to 4. Why this worked, who knows. But it seems to have cured the problem. Sincerely, Dr. Stephen Hunter Willson Northrop Research and Technology Center Palos Verdes, CA willson@nrtc.northop.com 8-Oct-86 13:11:29-PDT,969;000000000000 Return-Path: Received: from WISCVM.WISC.EDU by SUMEX-AIM.ARPA with TCP; Wed 8 Oct 86 13:10:54-PDT Received: from (MAILER)UNBMVS1.BITNET by WISCVM.WISC.EDU on 10/08/86 at 15:10:25 CDT Date: 08 Oct 86 16:59:34 ADT From: To: info-iris@sumex-aim.ARPA Subject: floating point unit for the iris2400 Message-ID: Help Help Help !!! We have acquired a floating point unit for our IRIS 2400B How do I install it? Are there switchs to be set? Which Slot does it go in? Does the system(software) have to be reconfigured? We have 12 bitplanes and 1.5 Meg of real memory. Michael MacDonald Software Specialist, School of Computer Science University of New Brunswick Po. Box 4400 Fredericton, New Brunswick CANADA E3B 5A3 (506) 453-4566 Netnorth/BITNET: MIKEMAC @ UNBMVS1 9-Oct-86 06:24:30-PDT,1377;000000000000 Return-Path: Received: from USNA.ARPA by SUMEX-AIM.ARPA with TCP; Thu 9 Oct 86 06:24:09-PDT Date: Thu, 9 Oct 86 9:20:41 EDT From: Steve Satterfield To: info-ikonas@AMES-IO.ARPA, info-iris@SUMEX-AIM.ARPA cc: steve@USNA.ARPA, joe@USNA.ARPA Subject: Lyon-Lamb Video Animation We are presently demoing a Lyon-Lamb video animation system and have a few questions for anyone else with a such a system connected to either an Ikonas (Adage) or an Iris. Does any one have any software to control a frame by frame sequence from the host they would be willing to send me. The manual provided by Lyon-Lamb is very poor and learning by experimentation is rather slow. We have made some progress, but some samples on how you control the Lyon-Lamb would be very helpful. The second area is in the quality of the NTSC image. We hear that various filters can be used to improve the image quality and in the Ikonas case, there are various adjustments that can be made. We have been experimenting but again some of your experiences would be helpful. Thanks for any advise you can provide Steven G. Satterfield Computer Aided Design and Interactive Graphics Group U. S. Naval Academy Annapolis, Md. 21402 (301) 267-4413 decvax!brl-smoke!usna!steve UUCP seismo!usna!steve UUCP steve@usna.arpa DDN 9-Oct-86 13:14:16-PDT,371;000000000000 Mail-From: DUNCAN created at 9-Oct-86 13:13:22 Date: Thu 9 Oct 86 13:13:20-PDT From: Bruce Duncan Subject: time servers To: info-iris@SUMEX-AIM.ARPA Message-ID: <12245491410.26.DUNCAN@SUMEX-AIM.ARPA> Does anyone have code so that an IRIS workstation can get the time of day from a TCP timeserver? Bruce Duncan duncan@sumex ------- 9-Oct-86 16:26:56-PDT,5225;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Thu 9 Oct 86 16:25:20-PDT Date: Thu, 9 Oct 86 19:13:00 EDT From: Doug Kingston To: Bruce Duncan cc: info-iris@sumex-aim.arpa Subject: Re: time servers Message-ID: <8610091913.aa04372@SEM.BRL.ARPA> /* $Header$ */ /* * ndate.c - Get date from another network host * variation on a theme by rsm@brl * * Author: Christopher A. Kent * Dept. of Computer Sciences * Purdue University * Date: Thu Jun 23 1983 * Copyright (c) 1983 Christopher A. Kent */ /* $Log$ */ static char rcs_ident[] = "$Header$"; #include #include #include #include #include #include #include #define WTMP "/usr/adm/wtmp" struct utmp wtmp[2] = { {"|", "", 0}, {"{", "", 0}}; char *std_hostv[] = { "saturn", "sri-nic", "bbng", "usc-isib", "mit-devmultics", 0, }; char **hosts; char *u_hostv[128]; char u_hosts[256]; char aflag; /* all hosts */ char sflag; /* set time from first host */ char uflag; /* report time in GMT */ struct sockaddr_in sin = { AF_INET }; char *asctime(); char *ctime(); struct tm *localtime(); char *timezone(); main(argc, argv) char **argv; { register char *hostname; register struct hostent *host; register int s; struct timeval ntv, tv; struct timezone tz; char *tzn; char *ap; int wf; int success = 0; procargs(argc, argv); if(aflag && sflag){ fprintf(stderr, "%s: -a and -s mutually exclusive\n", argv[0]); exit(-1); } gettimeofday(&tv, &tz); sin.sin_port = htons(IPPORT_TIMESERVER); while(hostname = *hosts++){ /* pick a host and connect */ host = gethostbyname(hostname); if(host){ sin.sin_family = host->h_addrtype; bcopy(host->h_addr, (caddr_t)&sin.sin_addr, host->h_length); hostname = host->h_name; }else{ sin.sin_family = AF_INET; sin.sin_addr.s_addr = inet_addr(argv[1]); if(sin.sin_addr.s_addr == -1){ printf("%s: unknown host\n", hostname); continue; } } s = socket(AF_INET, SOCK_STREAM, 0); if(s < 0){ perror("ndate: socket"); continue; } if(connect(s, (caddr_t)&sin, sizeof(sin)) < 0){ extern int errno, sys_nerr; extern char *sys_errlist[]; register char *c; fprintf(stderr, "ndate: Can't connect to %s: ", hostname); c = "Unknown error"; if(errno < sys_nerr) c = sys_errlist[errno]; fprintf(stderr, "%s\n", c); continue; } printf("%s: ", hostname); if(read(s, &ntv.tv_sec, sizeof(ntv.tv_sec)) < 0){ perror("ndate: read"); continue; } close(s); success++; tv.tv_sec = ntohl(ntv.tv_sec); tv.tv_sec -= 2208988800; /* from Jan 1 1900 */ tv.tv_usec = 0; /* time is now Unix normal form (GMT) */ tzn = NULL; if(uflag){ ap = asctime(gmtime(&tv.tv_sec)); tzn = "GMT"; }else{ struct tm *tp; tp = localtime(&tv.tv_sec); ap = asctime(tp); tzn = timezone(tz.tz_minuteswest, tp->tm_isdst); } printf("%.20s", ap); if(tzn != NULL) printf("%s", tzn); printf("%s", ap+19); if(aflag == 0) break; } if(sflag == 0) exit(success == 0); wtmp[0].ut_time = tv.tv_sec; if (settimeofday(&tv, (struct timezone *)0) < 0) { success = 0; perror("Failed to set date"); } else if ((wf = open(WTMP, 1)) >= 0) { time(&wtmp[1].ut_time); lseek(wf, 0L, 2); write(wf, (char *)wtmp, sizeof(wtmp)); close(wf); } exit(success == 0); } /* * procargs - unified argument processing procedure * * This procedure contains the logic for converting the UNIX argument * list into global variables */ procargs(argc, argv) int argc; char *argv[]; { int arg, skip, unswitched, more; char *swptr; hosts = std_hostv; uflag = 0; aflag = 0; sflag = 0; unswitched = 0; skip = 1; for ( arg=1 ; arg Received: from BRL-SEM.ARPA by SUMEX-AIM.ARPA with TCP; Thu 9 Oct 86 17:42:03-PDT Date: Thu, 9 Oct 86 20:38:46 EDT From: Mike Muuss To: Lloyd La Comb cc: Info-Iris@sumex-aim.arpa Subject: Re: TCP/IP problems Message-ID: <8610092038.aa04730@SEM.BRL.ARPA> You probably need the "FIN-overtakes-final-data" fix for your 4.3 systems. See the net, or contact for the fix. -M 9-Oct-86 19:00:12-PDT,934;000000000000 Return-Path: Received: from XX.LCS.MIT.EDU by SUMEX-AIM.ARPA with TCP; Thu 9 Oct 86 18:59:49-PDT Received: from OZ.AI.MIT.EDU by XX.LCS.MIT.EDU via Chaosnet; 9 Oct 86 21:43-EDT Date: Thu 9 Oct 86 21:43:54-EDT From: "Jonathan Delatizky" Subject: Consultant wanted To: info-iris@SUMEX-AIM.ARPA cc: DELATZ%OZ.AI.MIT.EDU@XX.LCS.MIT.EDU Message-ID: <12245551586.50.DELATZ@OZ.AI.MIT.EDU> A friend of mine is looking for a consultant who is very familiar with the Iris graphics and MEX environments. He would like the person to spend a few days giving advice to a Silicon Valley vendor about porting their product (which has a bitblt-oriented graphics component) onto an Iris. If you are interested or know someone else who might be, call Richard Mott at (617) 626-1700 (you'll have to ask for him). Please do not reply directly to me. ------- 10-Oct-86 09:42:05-PDT,1281;000000000000 Return-Path: Received: from scubed by SUMEX-AIM.ARPA with TCP; Fri 10 Oct 86 09:41:33-PDT Received: from kelvin (kelvin.ARPA) by scubed (4.12/5.20b) id AA19581; Fri, 10 Oct 86 09:46:43 pdt Received: by kelvin (4.12/5.20a) id AA03566; Fri, 10 Oct 86 09:44:20 pdt Date: Fri, 10 Oct 86 09:44:20 pdt From: warner%kelvin@scubed.ARPA (Ken Warner) Message-Id: <8610101644.AA03566@kelvin> To: info-ikonas@AMES-IO.ARPA, info-iris@SUMEX-AIM.ARPA, steve@USNA.ARPA Subject: Re: Lyon-Lamb Video Animation Cc: joe@USNA.ARPA Steve, I've just completed such a package that is hosted on the IRIS. We've used it sucessfully to produce short movies. At the moment we don't know exactly how to price it for external distribution, (got to satisfy the bean counters) but it shouldn't be very much. Call me or mail me your phone number and we can talk more. We have a SONY 5850 vtr controlled by a Lyon-Lamb VAS IV. Our RGB is converted by an old Lyon-Lamb NTSC-1 encoder. It seems to work. The limiting factor here is the resolution of the SONY 5850. It only has 250 lines per inch resolution. Our graphics system is an IRIS 2400T with a 60HZ non-interlaced monitor running GL2-W3.4. Ken Warner warner@scubed.arpa (619) 453-0060 x341 11-Oct-86 03:38:19-PDT,981;000000000000 Return-Path: Received: from NRTC-GREMLIN.NORTHROP.COM by SUMEX-AIM.ARPA with TCP; Sat 11 Oct 86 03:37:58-PDT Received: from nrtc-gremlin by NRTC-GREMLIN.NORTHROP.COM id a019670; 8 Oct 86 9:35 PDT To: info-iris@sumex-aim.ARPA cc: willson@nrtc-gremlin Subject: rsh problem on 3030 Date: Wed, 08 Oct 86 09:35:00 -0700 From: Stephen Willson It is my experience that piping the output of a program on the 3030 through rsh, to another system, results in duplication of the input on the output. In other words, when I do this command: cat surveyor.tex | rsh gr "cat >surveyor.texc" I get different results from this command: rcp surveyor.tex gr:surveyor.texr Diff'ing the two files shows that the first file, surveyor.texc, contains a lot of extra text! Sincerely, Dr. Stephen Hunter Willson Northrop Research and Technology Center Palos Verdes, CA willson@nrtc.northop.com 11-Oct-86 03:38:43-PDT,777;000000000000 Return-Path: Received: from NRTC-GREMLIN.NORTHROP.COM by SUMEX-AIM.ARPA with TCP; Sat 11 Oct 86 03:38:03-PDT Received: from nrtc-gremlin by NRTC-GREMLIN.NORTHROP.COM id a019678; 8 Oct 86 9:36 PDT To: info-iris@sumex-aim.ARPA cc: willson@nrtc-gremlin Subject: ftp problems Date: Wed, 08 Oct 86 09:36:33 -0700 From: Stephen Willson I have not experienced any of the ftp problems that have been reported by others. We have a 3030, with release 3.4, and it does a terrific job of transferring files (70K-80K bytes/sec). Maybe this is only a problem on the 2400s. Sincerely, Dr. Stephen Hunter Willson Northrop Research and Technology Center Palos Verdes, CA willson@nrtc.northop.com 11-Oct-86 03:39:22-PDT,2197;000000000000 Return-Path: Received: from CSNET-RELAY.ARPA by SUMEX-AIM.ARPA with TCP; Sat 11 Oct 86 03:39:02-PDT Received: from waterloo by csnet-relay.csnet id aa01174; 10 Oct 86 16:08 EDT Received: from watcgl.uucp by watmath; Fri, 10 Oct 86 15:03:59 edt Received: by watcgl; Fri, 10 Oct 86 15:04:02 edt Date: Fri, 10 Oct 86 15:04:02 edt From: "Alan W. Paeth" Message-Id: <8610101904.AA03306@watcgl.uucp> To: info-ikonas@AMES-IO.ARPA, info-iris@SUMEX-AIM.ARPA, steve@USNA.ARPA Subject: Re: Lyon-Lamb Video Animation Cc: joe@USNA.ARPA I recently wrote a fairly extensive package to perform frame by frame animation on the Ikonas. Assuming that tools already exist to load a sequence of frames into the Ikonas memory, the tool does permutations of the crossbar plus zoom/pan/scrool registers to window (viewport, actually) onto the display screen. This involved a lot of reverse engineering of the Ikonas at or below the level described on the standard hardware reference on video register settings. The software is general is such in that one can specify the spatial and pixel definitions of the image set, plus the amount of (possibly offscreen) Ikonas memory involved in the sequence, and the whole thing is then run. We took advantage of R. Preston Gurd's C-compiler to move the package to the Ikonas Bit Slice, because it is impossible to get uniform, 60Hz frame time resolution by attempting to poke registers across the host interface. The Vax based driver is now nothing more than a simple framework to stuff the first 10 or 12 scratchpad locations with all the various parameters, and the program than cycles through the sequence for some specified number of times (and speed and direction). You might be interested either in our zoom_pan() C subroutine which provides a more orthogonal set of controls for setting the Ikonas hardware registers, or in the microcode itself. I believe that our .obj format matches the format distributed by Adage, so the microcode code, plus a copy of the driver program would be sufficient to get you on the air. /Alan Paeth 13-Oct-86 12:17:35-PDT,493;000000000000 Return-Path: Received: from cheme.ARPA by SUMEX-AIM.ARPA with TCP; Mon 13 Oct 86 12:16:49-PDT Date: 0 0 00:00:00 EST From: "SYSTEM" Subject: tn3270 for the IRIS To: "info-iris" Reply-To: "SYSTEM" We have an Iris 3020 and an Iris 3030 (TCP kernel). Does anyone out there have tn3270 running on such a machine? Steve Thompson olin@cheme.tn.cornell.edu School of Chemical Engineering Cornell University ------ 21-Oct-86 19:37:55-PDT,3917;000000000000 Return-Path: Received: from beaver.cs.washington.edu by SUMEX-AIM.ARPA with TCP; Tue 21 Oct 86 19:37:19-PDT Received: by beaver.cs.washington.edu (5.45/5.5.1.4) id AA09416; Tue, 21 Oct 86 02:49:41 PDT Received: by ssc-vax (4.12/4.7) id AA24363; Mon, 20 Oct 86 15:48:53 pdt Message-Id: <8610202248.AA24363@ssc-vax> To: ssc-vax!uw-beaver!info-iris@SUMEX-AIM.arpa Date: Mon, 20 Oct 86 14:59:59 PDT From: ssc-vax!voodoo!bhagwan@beaver.cs.washington.edu (A. L. McPherson) Subject: Some queue problems. X-Mailer: ELM [version 1.2] Greetings, I've been playing with queued devices on my 2400T lately and have run into some problems. I'm posting them for general info but if anyone has a fix or workaround I'd like to hear it. SGI has been notified of these problems. Problem 1: GL2 has a limit of 50 queue entries. This is undocumented as far as I can tell. When the queue is full there is no notification of it. Queued device interaction is lost until something is removed from the queue. Problem 2: Qreset doesn't appear to work as documented. It is supposed to clear all entries from the queue. It does and it doesn't. See the following short test program: /* * Title: qt - test some possible bugs in the IRIS queues * * Description: IRIS queued devices appear to have some problems. * The following program tries to duplicate errors * I've recently experienced. It appears to be a * timimg problem. */ #include "gl.h" #include "device.h" main () { Device dev, val; long i; winopen ("qt"); qdevice (MIDDLEMOUSE); printf ("\nTest started\n\n"); /* * The next statement will print the RIGHTMOUSE hit that attached * to the process */ printf ("%d: dev = %d, val = %d\n", i++, dev = qread (&val), val); /* * Now, while waiting for the LEFTMOUSE hit, press BPAD0 a few times * to get some entries into the queue */ while (!getbutton (LEFTMOUSE)); /* This will print the first queue entry. Val is wrong. Should be 0 * since the first entry is the button "down" or "press" */ printf ("%d: dev = %d, val = %d\n", i++, dev = qread (&val), val); /* * Now, reset the queue. */ qreset (); /* * The next statement blocks for queue entries (as it should). * So, press it once to move on. "val" is wrong here too, as above. */ printf ("%d: dev = %d, val = %d\n", i++, dev = qread (&val), val); printf ("%d: dev = %d, val = %d\n", i++, dev = qread (&val), val); /* * OK, things are almost correct to this point (except for the incorrect * "val" above. * * The queue should be empty but let's reset it just to be sure. */ qreset (); /* The following should wait for a queue entry. Press and release * MIDDLEMOUSE rapidly. */ printf ("%d: dev = %d, val = %d\n", i++, dev = qread (&val), val); /* * OK, reset the queue (should empty the "up" or "release" entry) */ qreset (); /* Alas, that entry is still there. THIS STATEMENT DOES NOT BLOCK. * It should. */ printf ("%d: dev = %d, val = %d\n", i++, dev = qread (&val), val); printf ("\nTest ended\n"); gexit (); } This is the output the above code produced on my 2400T: Test started 0: dev = 534, val = 0 1: dev = 102, val = 1 2: dev = 102, val = 1 3: dev = 102, val = 1 4: dev = 102, val = 0 5: dev = 102, val = 1 Test ended Well, that's it. Any help would be appreciated. Otherwise, watch out for queued IO in your applications. Al McPherson Voodoo Graphics Project Boeing Computer Services ....uw-beaver!ssc-vax!voodoo!bhagwan Everett, Washington (206) 342-1442 27-Oct-86 13:11:51-PST,1271;000000000000 Mail-From: BRUGGE created at 27-Oct-86 13:09:25 Date: Mon 27 Oct 86 13:09:23-PST From: John Brugge Subject: ELLE on the IRIS To: info-iris@SUMEX-AIM.ARPA Message-ID: <12250220203.66.BRUGGE@SUMEX-AIM.ARPA> Being frustrated with the size and slowness of GNU Emacs, I tried bringing up ELLE (Elle Looks Like Emacs), and was very pleasantly surprised: it compiled on the first try, starts up in a flash, and takes up about 1/6 of the space as GNU (object code). ELLE isn't easily extendable (like GNU's mu-lisp), and may not have all of the bells and whistles of Emacs, but for basic editing (what we do most), it is completely adequate. Keyboard macros, key-bindings and split window editing are there, the "info" tree is not. It is public domain, available from Ken Harrenstein at SRI (KLH@SRI-NIC). For those with ftp access, you can retrieve the source as follows: - ftp to SRI-TSC, with login anonymous - get the file "elle.tar", making sure you are using 8-bit transfer - after extracting it, look at the file "elle.doc" for instructions on constructing it. For people short on disk space, or who feel they just don't need everything GNU Emacs has, I'd highly recommend trying out ELLE. John ------- 27-Oct-86 13:17:08-PST,435;000000000000 Mail-From: BRUGGE created at 27-Oct-86 13:16:41 Date: Mon 27 Oct 86 13:16:41-PST From: John Brugge Subject: Re: ELLE on the IRIS To: info-iris@SUMEX-AIM.ARPA Message-ID: <12250221532.66.BRUGGE@SUMEX-AIM.ARPA> I forgot mention that this was done on a 3020, but the most specific you need to get in making it is telling it that it's System V, so it should work on 2400's (and 1400's?) John ------- 28-Oct-86 14:46:22-PST,544;000000000000 Return-Path: Received: from WISCVM.WISC.EDU by SUMEX-AIM.ARPA with TCP; Tue 28 Oct 86 14:44:53-PST Received: from (MAILER)CRNLIMAP.BITNET by WISCVM.WISC.EDU on 10/28/86 at 16:44:28 CST Received: by CRNLIMAP (Mailer X1.23b) id 1463; Tue, 28 Oct 86 16:29:23 EST Date: Tue, 28 Oct 1986 16:28 EST From: BILL MARTIN To: PLease remove me from your IRIS mialing list. Thanks. -- Bill Martin -- 29-Oct-86 06:58:18-PST,1214;000000000000 Return-Path: <@BRL-SMOKE.arpa:mike@BRL.ARPA> Received: from BRL-VGR.ARPA by SUMEX-AIM.ARPA with TCP; Wed 29 Oct 86 06:57:25-PST Received: from BRL-SMOKE.ARPA by VGR.BRL.ARPA id aa05064; 29 Oct 86 5:34 EST Date: Wed, 29 Oct 86 5:31:22 EST From: Mike Muuss To: info-iris%sumex-aim.stanford.edu@BRL-VGR.arpa Subject: TCP problem resolved Message-ID: <8610290534.aa05064@VGR.BRL.ARPA> The problem with SGI 3.4 systems talking to our 4.3 VAX systems (and Gould UTX 2.0 systems) has been resolved by applying the three sets of improvements to the 4.3 TCP posted by Mike Karels of Berkeley. The first source of the problem seems to be the Excelan dropping or missing a packet in the SYN & ACK sequence for opening a connection. Depending on particulars, this can provoke odd behaviors (like no communication at all) in the TCPs on one or both ends. Since the Excelan "firmware" in the SGI isn't something we can change, fixing the other machines was our only option. This is now quite nice, as we can use the "remote framebuffer" feature of our generic framebuffer package to zip images onto our Iris displays from our "cruncher" machines. Best, -Mike 29-Oct-86 10:25:40-PST,905;000000000000 Return-Path: Received: from nrtc-gremlin.arpa by SUMEX-AIM.ARPA with TCP; Wed 29 Oct 86 10:23:32-PST Received: from nrtc-gremlin by nrtc-gremlin.arpa id a001133; 29 Oct 86 10:19 PST To: info-iris@sumex-aim.ARPA cc: willson@nrtc-gremlin.arpa Subject: number of graphports Date: Wed, 29 Oct 86 10:19:55 -0800 From: Stephen Willson I have been prototyping some image processing routines on our 3030 which use a lot of MEX windows. I find that 20 isn't really enough for this kind of work. Somewhere around 64 graphports would be nice. I hope the 3.5 version of MEX has more graphports. Of course, the best thing would be a command line option to set the number, then I'll never run out. Sincerely, Dr. Stephen Hunter Willson Northrop Research and Technology Center Palos Verdes, CA willson@nrtc.northop.com 29-Oct-86 11:28:18-PST,940;000000000000 Return-Path: Received: from ames-nas.ARPA by SUMEX-AIM.ARPA with TCP; Wed 29 Oct 86 11:27:17-PST Received: from ames-prandtl.ARPA (prandtl-ec) by ames-nas.ARPA; Wed, 29 Oct 86 10:44:41 pst Received: by ames-prandtl.ARPA (4.12/4.7) id AA17882; Wed, 29 Oct 86 10:44:50 pst Date: Wed, 29 Oct 86 10:44:50 pst From: dat@ames-prandtl.ARPA (David A. Tristram) Message-Id: <8610291844.AA17882@ames-prandtl.ARPA> To: info-iris@sumex-aim.ARPA Subject: iris graphics in franz lisp Cc: dat@AMES-NAS.ARPA Franz (tm) Lisp provides a foreign function interface. We have used it to include iris graphics calls in the lisp environment. If you have Franz on your iris, you may be able to use our software. For a shar archive, reply to dat@ames-nas. compiles okay with gl2 (2.3, 3.[3-5]) uses franz opus 42.16.iris.2 does not implement every gl call. Dave Tristram 415-694-6410 NASA Ames Research Center 2-Nov-86 21:24:26-PST,14490;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Sun 2 Nov 86 21:24:01-PST Date: Sun, 2 Nov 86 21:23:26 pst From: michael zyda Message-Id: <8611030523.AA02335@nps-cs> To: info-iris@sumex-aim Subject: Backface Polygon Removal... One of the most frustrating things about the current IRIS product is its lack of support for double buffered hidden surface elimination. The only thing you can do is to order the drawing of your polygon's faces or, if your object is simple enough, use backface polygon removal. Backface polygon removal is a technique where the raster subsystem throws away polygons whose vertices are ordered clockwise and keeps polygons whose vertices are ordered counterclockwise. The effect of this technique is a pseudo-hidden surface effect, i.e. it works as long as you stay on the outside skin of the object you are examining. The only problem with this technique is that you need some sort of a tool to help you order your polygon's vertices. The code that follows in this file is one such tool. The code works on the principle that you know an interior point inside the 3D object whose vertices you want to order. You call a routine (bfinside) with that point. The rest of the routines in the package are shadow routines (i.e bfpolf,...) that mimick standard GL2 polygon calls. The routines in the package take care of the vertex ordering for you with respect to the interior point you provided... Michael Zyda Naval Postgraduate School, Code 52, Dept. of Computer Science Monterey, California 93943-5100 (408) 646-2305 zyda@nps-cs.arpa ucbvax!dual!lll-crg!nps-cs!zyda /* sample of the package's usage... */ /* this is file drawcube.c */ /* draw a cube with center (x,y,z), having the designated sidelength*/ /* the cube is drawn so that all outside facing polygons have their vertices ordered in a counterclockwise fashion (for hidden surface elimination). */ drawcube(x,y,z,sidelength) Coord x,y,z; /* center of the cube in 3-space */ float sidelength; /* length of cube's side */ { float halfside; /* length of half the side of the cube */ Coord p[4][3]; /* array to hold coords for the cube faces */ /* save current attributes */ pushattributes(); /* compute the halfside */ halfside=sidelength/2.0; /* set a point on the inside of the cube */ bfinside(x,y,z); /* back face */ p[0][0]=x-halfside; p[0][1]=y+halfside; p[0][2]=z-halfside; p[1][0]=x+halfside; p[1][1]=y+halfside; p[1][2]=z-halfside; p[2][0]=x+halfside; p[2][1]=y-halfside; p[2][2]=z-halfside; p[3][0]=x-halfside; p[3][1]=y-halfside; p[3][2]=z-halfside; color(BLUE); bfpolf(4,p); /* draw a filled blue face */ /* draw the front face */ /* this polygon is deliberately disordered. If you call straight polf without calling bfpolf, the front face will be missing when the program starts up. */ p[0][0]=x-halfside; p[0][1]=y+halfside; p[0][2]=z+halfside; p[1][0]=x+halfside; p[1][1]=y+halfside; p[1][2]=z+halfside; p[2][0]=x+halfside; p[2][1]=y-halfside; p[2][2]=z+halfside; p[3][0]=x-halfside; p[3][1]=y-halfside; p[3][2]=z+halfside; color(RED); bfpolf(4,p); /* draw a red filled face */ /* draw the top */ p[0][0]=x-halfside; p[0][1]=y+halfside; p[0][2]=z-halfside; p[1][0]=x-halfside; p[1][1]=y+halfside; p[1][2]=z+halfside; p[2][0]=x+halfside; p[2][1]=y+halfside; p[2][2]=z+halfside; p[3][0]=x+halfside; p[3][1]=y+halfside; p[3][2]=z-halfside; color(GREEN); bfpolf(4,p); /* draw a filled green face */ /* draw the bottom */ p[0][0]=x-halfside; p[0][1]=y-halfside; p[0][2]=z-halfside; p[1][0]=x+halfside; p[1][1]=y-halfside; p[1][2]=z-halfside; p[2][0]=x+halfside; p[2][1]=y-halfside; p[2][2]=z+halfside; p[3][0]=x-halfside; p[3][1]=y-halfside; p[3][2]=z+halfside; color(WHITE); bfpolf(4,p); /* draw a filled white face */ /* draw the left side */ p[0][0]=x-halfside; p[0][1]=y-halfside; p[0][2]=z-halfside; p[1][0]=x-halfside; p[1][1]=y-halfside; p[1][2]=z+halfside; p[2][0]=x-halfside; p[2][1]=y+halfside; p[2][2]=z+halfside; p[3][0]=x-halfside; p[3][1]=y+halfside; p[3][2]=z-halfside; color(YELLOW); bfpolf(4,p); /* draw a filled yellow face */ /* draw the right side */ p[0][0]=x+halfside; p[0][1]=y-halfside; p[0][2]=z-halfside; p[1][0]=x+halfside; p[1][1]=y+halfside; p[1][2]=z-halfside; p[2][0]=x+halfside; p[2][1]=y+halfside; p[2][2]=z+halfside; p[3][0]=x+halfside; p[3][1]=y-halfside; p[3][2]=z+halfside; color(MAGENTA); bfpolf(4,p); /* draw a magenta filled face */ /* the cube is drawn */ /* restore attributes before exiting */ popattributes(); } /* the actual vertex ordering package... */ /* this is file backface.c Written by: Michael J. Zyda Naval Postgraduate School Code 52, Dept. of Computer Science Monterey, California 93943-5100 (408) 646-2305 It contains routines that simplify the use of backface polygon removal. The routines: bfinside(x,y,z): This routine sets the inside point that is used for reference in orienting the polygons counterclockwise. This point should be an interior point of the object being drawn. bfmv(x,y,z): This routine issues the first point of a polygon. It is just like IRIS routine pmv. bfdr(x,y,z): This routine is used to specify all other points of the polygon after a bfmv has been called. This routine is just like IRIS routine pdr. bfclos(): This routine closes the polygon. No IRIS drawing commands are issued until this routine is called. This routine checks the orientation of the polygon with respect to the inside point and issues drawing commands for a counterclockwise oriented version of the previously input polygon. This routine is like IRIS routine pclos(). bfpolf(ncoords,xyz): This routine is just like IRIS routine polf except that is checks the orientation of the polygon before sending the coordinates. */ #include "gl.h" #include "device.h" /* Global Definitions for backface polygon removal */ #define MAXPOINTS 1000 /* max number of points in any polygon */ float insidex,insidey,insidez; /* inside point of the object This value is set by routine bfinside */ float coordinates[MAXPOINTS][3]; /* temp array to hold the polygon points */ long last = -1; /* last written coordinate */ /* this is routine bfinside This routine records the inside point of the object for polygon orientation reference. */ bfinside(x,y,z) float x,y,z; { /* record the point in a global array */ insidex = x; insidey = y; insidez = z; } /* this is routine bfmv This routine starts a polygon's definition and recording in the global data structures. */ bfmv(x,y,z) float x,y,z; { /* reset the global pointer at how many coords we have saved */ last = 0; coordinates[last][0] = x; coordinates[last][1] = y; coordinates[last][2] = z; } /* this is routine bfdr This routine saves away the polygon points in global arrays. */ bfdr(x,y,z) float x,y,z; { /* get the next spot in the save array */ last = last +1; if(last >= MAXPOINTS) { printf("BFDR: MAXPOINTS not large enough for this polygon's definition!\n"); last = last -1; return; } /* there was space, record the point */ coordinates[last][0] = x; coordinates[last][1] = y; coordinates[last][2] = z; } /* this is routine bfclos This routine checks the orientation of the polygon and then sends its definition out via IRIS graphics calls. The polygon is sent out so that its vertices are oriented counterclockwise with respect to the inside point specified. */ bfclos() { long polygonclockwise(); /* polygon orientation routine = 1 if clockwise = 0 if counterclockwise */ long i; /* temp loop variable */ /* check the polygon's orientation */ if(polygonclockwise(last+1,coordinates,insidex,insidey,insidez)) { /* the polygon is clockwise, must send out backwards */ for(i=last; i >= 0; i=i-1) { if(i == last) { pmv(coordinates[i][0],coordinates[i][1],coordinates[i][2]); } else { pdr(coordinates[i][0],coordinates[i][1],coordinates[i][2]); } } /* close the polygon */ pclos(); } /* endif polygon was oriented clockwise */ else { /* the polygon is already oriented counterclockwise */ polf(last+1,coordinates); } } /* this is routine bfpolf It performs just like routine polf in the IRIS package except that it orients the output polygon counterclockwise with respect to the inside point. */ bfpolf(ncoords,xyz) long ncoords; /* the number of coordinates */ float xyz[][3]; /* the input coordinates */ { long polygonclockwise(); /* polygon orientation routine = 1 if clockwise = 0 if counterclockwise */ long i; /* temp loop variable */ /* check the polygon's orientation */ if(polygonclockwise(ncoords,xyz,insidex,insidey,insidez)) { /* the polygon is clockwise, must send out backwards */ for(i=ncoords-1; i >= 0; i=i-1) { if(i == ncoords-1) { pmv(xyz[i][0],xyz[i][1],xyz[i][2]); } else { pdr(xyz[i][0],xyz[i][1],xyz[i][2]); } } /* close the polygon */ pclos(); } /* endif polygon was oriented clockwise */ else { /* the polygon is already oriented counterclockwise */ polf(ncoords,xyz); } } /* this is function polygonclockwise It is a function that determines if a polygon is clockwise or counterclockwise. = polygonclockwise(ncoords,xyz,xinside,yinside,zinside); ncoords = number of 3d coordinates. xyz[][3] = the 3d floating point coords. xinside, yinside, zinside = reference coordinate to compare against in determining direction. This coordinate should be inside the object for which polygon orientation is desired. Value returned = 1 if clockwise. = 0 if counterclockwise. */ #include long polygonclockwise(ncoords,xyz,xinside,yinside,zinside) long ncoords; float xyz[][3]; float xinside, yinside, zinside; { long i,j; /* loop temps */ float center[3]; /* center coordinate of the polygon */ float inside[3]; /* vector from inside point to center coordinate */ float a[3], b[3]; /* vector hold locations for the vectors that run from the center coordinate to the points of the polygon */ float xn[3], xmn[3]; /* points on line containing normal that are on opposite sides of the plane containing the polygon. */ float distton; /* distance to point n from pt inside. */ float disttomn; /* distance to point -n from pt inside. */ float normal[3]; /* the normal vector computed from a x b */ /* compute the center coordinate of the polygon */ center[0] = 0.0; center[1] = 0.0; center[2] = 0.0; for(i=0; i < ncoords; i=i+1) { for(j=0; j < 3; j=j+1) { center[j] = center[j] + xyz[i][j]; } } /* divide out by the number of coordinates */ for(j=0; j < 3; j=j+1) { center[j] = center[j]/(float)ncoords; } /* compute the vector that runs from the inside point towards the center coordinate */ inside[0] = center[0] - xinside; inside[1] = center[1] - yinside; inside[2] = center[2] - zinside; /* check the first 2 coordinates of the polygon for their direction */ /* compute vector a. It runs from the center coordinate to coordinate 0 */ for(j=0; j < 3; j=j+1) { a[j] = xyz[0][j] - center[j]; } /* compute vector b. It runs from the center coordinate to coordinate 1 */ for(j=0; j <3; j=j+1) { b[j] = xyz[1][j] - center[j]; } /* compute a x b to get the normal vector */ normal[0] = a[1]*b[2] - a[2]*b[1]; normal[1] = a[2]*b[0] - a[0]*b[2]; normal[2] = a[0]*b[1] - a[1]*b[0]; /* compute point n, offset pt from center in direction of normal */ for(j=0; j < 3; j=j+1) { xn[j] = center[j] + normal[j]; } /* compute point -n, offset pt from center in opposite direction from normal. */ for(j=0; j < 3; j=j+1) { xmn[j] = center[j] - normal[j]; } /* compute the distance the inside pt is from point n */ distton = sqrt((xn[0] - xinside) * (xn[0] - xinside) + (xn[1] - yinside) * (xn[1] - yinside) + (xn[2] - zinside) * (xn[2] - zinside)); /* compute the distance the inside pt is from point -n */ disttomn = sqrt((xmn[0] - xinside) * (xmn[0] - xinside) + (xmn[1] - yinside) * (xmn[1] - yinside) + (xmn[2] - zinside) * (xmn[2] - zinside)); /* if the dist(n) < dist(-n), then n points back towards the inside point and is on the same side of the plane as inside. a x b is then clockwise. */ if(distton < disttomn) { return(1); /* clockwise */ } else { return(0); /* counterclockwise */ } } 7-Nov-86 15:56:48-PST,732;000000000000 Return-Path: Received: from LLL-MFE.ARPA by SUMEX-AIM.ARPA with TCP; Fri 7 Nov 86 15:56:10-PST Date: Fri, 7 Nov 86 15:41 EST From: MCCALPIN%FSU.MFENET@LLL-MFE.ARPA Subject: TCP/IP terminal servers To: INFO-IRIS@SUMEX-AIM.ARPA We are searching for terminal servers for our expanding TCP/IP ethernet installation, and for our IRIS's in particular. We have found very few venders thus far. Is anyone out there using TCP/IP terminal servers? I would appreciate any pointers to venders of small (6-10 port) units. John D. McCalpin mccalpin%fsu.mfenet@lll-mfe.arpa mcalpin@fsuesr.bitnet 9-Nov-86 19:47:39-PST,971;000000000000 Return-Path: Received: from ME.RI.CMU.EDU by SUMEX-AIM.ARPA with TCP; Sun 9 Nov 86 19:47:17-PST Date: 9 Nov 1986 22:36-EST From: Antoon.K.Laane@me.ri.cmu.edu To: dat@prandtl cc: info-iris@sumex-aim.arpa Subject: gnu-emacs fixes for IRIS Message-Id: <531977778/akl@me.ri.cmu.edu> Hi, I just read your post from a few weeks ago regarding fixes you had for gnu-emacs on the IRIS. We have a 2400T here and I would like to bring up gnu-emacs as well. Could you please send me just the fixes you made? You said you modified unexec.c, and there is also some headerfile missing which defines 'struct bhdr' I think. Could you also tell me which version of gnu-emacs it applies to? I was also porting 18.26 to a Computer Vision SUN3, but that was unsuccesfull so we reverted to version 17. Thanks. Antoon Laane Mechanical Engineering Department Carnegie-Mellon University akl@me.ri.cmu.edu --------- 11-Nov-86 11:21:38-PST,1557;000000000000 Return-Path: Received: from RELAY.CS.NET by SUMEX-AIM.ARPA with TCP; Tue 11 Nov 86 11:20:23-PST Received: from waterloo by csnet-relay.csnet id ar01510; 11 Nov 86 8:41 EST Received: from watcgl.uucp by watmath; Mon, 10 Nov 86 15:12:39 est Received: from onfcanim.uucp by watcgl; Mon, 10 Nov 86 15:12:23 est Date: Mon, 10 Nov 86 15:10:17 est From: Dave Martindale Message-Id: <8611102010.AA15187@onfcanim.UUCP> To: Info-Iris <@RELAY.CS.NET,@watmath.waterloo.edu:Info-Iris@SUMEX-AIM.ARPA> Subject: serious security bug in 3.4 In the 3.4 release, the cp/mv/ln command is setuid root in order to be able to rename directories. (Cp, mv, and ln are three links to the same file). Unfortunately, it isn't careful enough about where it makes use of its root privileges. Making use of this bug, anyone can become the super-user by typing just a few commands. I do not intend to describe this method of breaking security here. However, to avoid becoming victim to it, you should remove setuid from cp/mv/ln. Although this means that only root will be able to rename directories, I can see no other way of protecting yourself from the bug until SGI fixes the program. This bug existed in a previous release and I reported the problem to SGI. Whoever "fixed" the bug simply masked some of the symptoms without fixing the problem. I've reported it once again; let's hope they fix it correctly this time. Dave Martindale watmath!onfcanim!dave 12-Nov-86 16:24:29-PST,847;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.ARPA with TCP; Wed 12 Nov 86 16:19:39-PST Date: Wed 12 Nov 86 16:16:01-PST From: Lloyd La Comb Subject: Lambert's cosine law To: Info-Iris@SUMEX-AIM.Stanford.EDU cc: lacomb@Sierra.Stanford.EDU Message-ID: <12254448484.34.LACOMB@Sierra.Stanford.EDU> I'm working on a display routine that uses Lambert's cosine law to determine the intensity of the reflected light from a surface. Does anyone out there know of or have an efficient routine to calculate the vector perpendicular to a 3D polygon. I have 64K polygons and the routine seems a little slow. Thanks, Lloyd La Comb lacomb@su-sierra.arpa ------- 17-Nov-86 01:22:00-PST,1662;000000000000 Return-Path: Received: from lindy.STANFORD.EDU (FORSYTHE.STANFORD.EDU.#Internet) by SUMEX-AIM.ARPA with TCP; Mon 17 Nov 86 01:21:32-PST Received: by lindy.STANFORD.EDU; Mon, 17 Nov 86 01:17:02 PST Date: Mon, 17 Nov 86 01:22:17 PST From: Reply-To: XBR2D96D%DDATHD21.BITNET@forsythe.stanford.edu To: Info-Iris@sumex-aim.stanford.edu Subject: Modula-2 for SUN 3/xxx and Iris 30xx Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 17 Nov 86 10:15:50 Date: Mon, 17 Nov 86 09:34:55 +0100 (Central European Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: Modula-2 for SUN 3/xxx and Iris 30xx To: Info-Iris@SUMEX-AIM.Stanford.Edu X-VMS-To: X%"Info-Modula-2@Rochester.Arpa",X%"Info-Iris@SUMEX-AIM.Stanford.Edu" Hallo, we are looking for Modula-2 Compilers for the SUN 3/xxx series and/or Iris 30xx series workstations. We would prefer freeware or PD-products, but we also look at commercial products. Minimum requirements: -Native Code (no special "run time system") -working with the common code generators of the above machines (we would like to mix C, FORTRAN-77 and Modula-2 if neccessary) -full support of the operating system functions and especially the graphics libraries. Please respond drirectly to me. Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: 21-Nov-86 17:51:12-PST,1860;000000000000 Return-Path: Received: from lindy.STANFORD.EDU (FORSYTHE.STANFORD.EDU.#Internet) by SUMEX-AIM.ARPA with TCP; Fri 21 Nov 86 17:50:46-PST Received: by lindy.STANFORD.EDU; Fri, 21 Nov 86 17:45:34 PST Date: Fri, 21 Nov 86 17:51:46 PST From: Reply-To: XBR2D96D%DDATHD21.BITNET@forsythe.stanford.edu To: Info-Iris@sumex-aim.stanford.edu Subject: Iris questions Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 21 Nov 86 18:32:10 Date: Fri, 21 Nov 86 18:31:08 +0100 (Central European Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: Iris questions To: Info-Iris@SUMEX-AIM.Stanford.Edu X-VMS-To: X%"Info-Iris@SUMEX-AIM.Stanford.Edu" Hallo, I've some (at the monent 2) questions about the Iris 30xx Workstations. We are considering to install 1 or 3 Iris 3020/3030 workstations. Under the assumption that they have powerful CPU's and that we are not doing graphics all the day, we want to connect some interactive users via asynchronous lines to them. Here are my questions: 1.) How many interactive users (editing, compiling, linking, etc.) can work at: a.) an Iris with 4 MB and no FPA b.) an Iris with 16 MB and FPA in a way that you can call "interactive". 2.) Does the Iris implementation of TCP/IP include the TELNET protocol? We want to install a Ethernet-Terminal-Server to connect users and peripherals. The devices from Bridge-Communications use TCP/IP and TELNET. Bridge-Com was mentioned together with other workstations and we want to know if we can use their equipment. Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: 21-Nov-86 20:29:12-PST,1624;000000000000 Mail-From: BRUGGE created at 21-Nov-86 20:28:54 Date: Fri 21 Nov 86 20:28:54-PST From: John Brugge Subject: Re: Iris questions To: XBR2D96D%DDATHD21.BITNET@FORSYTHE.STANFORD.EDU cc: info-iris@SUMEX-AIM.ARPA In-Reply-To: Message from "" of Fri 21 Nov 86 17:51:08-PST Message-ID: <12256853815.15.BRUGGE@SUMEX-AIM.ARPA> We have an Iris 3020 with the TCP/IP kernel and 4Mb of main memory, and have found the following: 1) while the TELNET protocol is supported, there are problems with the machine getting confused; it will accept telnet connections for awhile, then refuse one, and not accept any more unless rebooted. This gets very frustrating, and will hopefully be fixed with the next release of the system (expected to be fairly soon). 2) with 3 or 4 users connected to it, response varies, but expectedly: if people are editing, things are fine, if people are running number- crunching programs, performance of course suffers, notably any graphics that are running at the console. The only other machine I can compare it to for response-time feel is a VAX, and with 4 users I would say it is comparable (this is a purely subjective feel). Our Iris is the main computational machine for our research project, as well as the graphical display facility, so we have been pushing it quite a bit (even though its only 5 months old) and have been quite pleased (except for a problem with disk space on our 40Mb drive--we need much more!--and systems bugs that "should" be fixed with the next release). ------- 24-Nov-86 08:31:37-PST,1098;000000000000 Return-Path: Received: from lindy.STANFORD.EDU (FORSYTHE.STANFORD.EDU.#Internet) by SUMEX-AIM.ARPA with TCP; Mon 24 Nov 86 08:31:09-PST Received: by lindy.STANFORD.EDU; Sun, 23 Nov 86 23:54:00 PST Date: Mon, 24 Nov 86 00:00:59 PST From: Reply-To: XBR2D96D%DDATHD21.BITNET@forsythe.stanford.edu To: Info-Iris@sumex-aim.stanford.edu Subject: Another question Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 24 Nov 86 08:57:55 Date: Mon, 24 Nov 86 08:56:05 +0100 (Central European Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: Another question To: Info-Iris@SUMEX-AIM.Stanford.Edu X-VMS-To: INFO-IRIS Hallo again, I forgot to ask one question in my friday's posting: - has the Iris implementation of NFS (tm) full capabillities or only end-node functionality ?? Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: 25-Nov-86 03:19:10-PST,1224;000000000000 Return-Path: Received: from seismo.CSS.GOV by SUMEX-AIM.ARPA with TCP; Tue 25 Nov 86 03:18:46-PST Received: from ames.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP id AA01165; Tue, 25 Nov 86 06:18:07 EST Received: Mon, 24 Nov 86 10:18:51 PST by ames.arpa (5.45/1.2) Received: from elvin.sgi.com by sgi.sgi.com (5.51/861115) id AA05548; Mon, 24 Nov 86 10:18:25 PST Received: by elvin.sgi.com (5.15/861115) id AA12036; Mon, 24 Nov 86 10:17:31 PST From: ames!sgi!wen@seismo.CSS.GOV (Wen-ching Chow) Message-Id: <8611241817.AA12036@elvin.sgi.com> Date: 24 Nov 1986 1017-PST (Monday) To: decwrl!XBR2D96D%DDATHD21.BITNET@forsythe.stanford.edu Cc: Info-Iris@sumex-aim.stanford.edu, elvin!wen@seismo.CSS.GOV Subject: Re: Modula-2 for SUN 3/xxx and Iris 30xx In-Reply-To: Your message of Mon, 17 Nov 86 01:22:17 PST. Modula-2 compiler has been ported to the IRIS family of workstations. The third party software company who did it is: Djavaheri Brothers Stan Osborne President 697 Saturn Court P.O. Box 4759 Foster City, CA. 94404-0759 Phone: 415-341-1768 Wen Chow (415-962-3358 or 415-960-1980 X3358) International Sales Development Silicon Graphics, Inc. 26-Nov-86 03:51:55-PST,1251;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.ARPA with TCP; Wed 26 Nov 86 03:51:29-PST Received: by lindy.STANFORD.EDU; Wed, 26 Nov 86 03:43:29 PST Date: Wed, 26 Nov 86 03:50:47 PST From: Reply-To: XBR2D96D%DDATHD21.BITNET@forsythe.stanford.edu To: Info-Iris@sumex-aim.stanford.edu Subject: Iris Questions (again) Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 26 Nov 86 12:47:26 Date: Wed, 26 Nov 86 12:45:49 +0100 (Central European Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: Iris Questions (again) To: Info-Iris@SUMEX-AIM.Stanford.Edu X-VMS-To: X%"Info-Iris@SUMEX-AIM.Stanford.Edu" Hallo, its me again. I've got some more questions about the Iris stations a.) Is it possible to operate TCP/IP-NFS together with XNS at the same time, the same Ethernet-cable AND the same Iris workstation ? b.) Are there any reliable X.25 products (Hard and Software) useable with Iris workstations ? Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: 3-Dec-86 16:51:07-PST,1795;000000000000 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Wed 3 Dec 86 16:48:20-PST Received: by ucbvax.Berkeley.EDU (5.53/1.18) id AA08971; Wed, 3 Dec 86 16:47:55 PST Received: by ucscc (5.51/4.7) id AA09074; Wed, 3 Dec 86 16:22:38 PST Date: Wed, 3 Dec 86 16:22:38 PST From: ucscc!saupe@ucbvax.Berkeley.EDU (20010000) Message-Id: <8612040022.AA09074@ucscc> To: info-iris@sumex-aim.stanford.edu Subject: UCSC math IRIS new on SGI DL IRIS 3030 at UCSC, Dept. of Math. new on the SGI DL : We have an IRIS 3030 since April 1986. It is located at the Department of Mathematics at University of California, Santa Cruz. It talks to the local Computer Science / Computer Engineering network and to the campus wide network via TCP/IP Ethernet. We are also sharing a Betacam system with Computer Science for video animations (so far we have produced a couple of animations of e.g. Julia sets with changing parameters). Our applications are : A. Teaching graphics for mathematically inspired applications regarding topics such as : strange attractors Julia sets and Mandelbrot like sets partial differential equations cellular automata modelling dynamical systems random fractals raytracing algebraic surfaces minimal surfaces differential geometry B. Research on e.g. dynamical systems fractal dimension of Julia sets new minimal surfaces lip movement animation for speech perception experiments Dietmar Saupe Department of Mathematics UCSC Santa Cruz, Cal. 95064 ph. (408) 429-4642 e-mail saupe@ucscc.BITNET or saupe@ucscc.ucscc.edu (this in a little while when the work on our mail system is completed) 3-Dec-86 17:47:59-PST,1238;000000000000 Return-Path: Received: from seismo.CSS.GOV by SUMEX-AIM.ARPA with TCP; Wed 3 Dec 86 17:47:01-PST Received: from munnari.oz by seismo.CSS.GOV (5.54/1.14) with UUCP id AA07300; Wed, 3 Dec 86 20:46:48 EST Message-Id: <8612040146.AA07300@seismo.CSS.GOV> Received: from moncskermit by munnari with SunIII (5.5) id AA14837; Thu, 4 Dec 86 12:43:34 EST Date: Thu, 4 Dec 86 10:57:45 EST From: munnari!moncskermit.oz!jonmc@seismo.CSS.GOV (Jon McCormack) Received: by moncskermit .Monash (4.3) id AA03946; Thu, 4 Dec 86 10:57:45 EST To: info-iris@sumex-aim.arpa Subject: Iris serial port problem We wish to connect an Iris 3030 to a Sony Digital tape recorder via a standard RS-232 port. The Sony recorder's port will only run at 38,400 baud. While "stty 38400" does not produce an error message it seems to set the Iris port to only 19,200 baud. I was wondering if any other Iris users had used one of their serial ports (not the console port) at 38,400 baud? Any help would be appreciated. Jon McCormack, Video Paint Brush Co., Melbourne, AUSTRALIA. ACSnet: jonmc@moncskermit UUCP: seismo!munnari!moncskermit.oz!jonmc ARPA: jonmc%moncskermit.oz@seismo.css.gov 10-Dec-86 22:48:44-PST,36994;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.ARPA with TCP; Wed 10 Dec 86 22:47:23-PST Date: Wed, 10 Dec 86 22:49:14 pst From: michael zyda Message-Id: <8612110649.AA26225@nps-cs> To: info-iris@sumex-aim One of the frustrating things about the IRIS is its lack of support for filled surface patches. One of my students has put together a package that looks like the IRIS patch routines but produces a filled surface instead. Also included with this is a simple lighting model... Michael J. Zyda Naval Postgraduate School Code 52, Dept. of Computer Science Monterey, California 93943 (408) 646-2305 zyda@nps-cs.arpa ucbvax!dual!lll-crg!nps-cs!zyda Files: Makefile patch3.c (main program) npatch.c (patch replacement library) lightpoly.c (light a polygon routine) npoly_orient.c (compute a polygon's vertex orientation) "Makefile" ************************************************** CFLAGS = -Zf ALL = npatch \ npoly_orient \ lightpoly \ patch3 all: $(ALL) clean: rm -f *.o delete: rm -f *.o $(ALL) npatch: cc -c npatch.c $(CFLAGS) npoly_orient: cc -c npoly_orient.c $(CFLAGS) lightpoly: cc -c lightpoly.c $(CFLAGS) patch3: cc -o patch3 patch3.c npatch.o npoly_orient.o lightpoly.o $(CFLAGS) -Zg patch3: npatch.o npoly_orient.o lightpoly.o patch3.c ***************************************************** /* this is file patch3.c It draws the Bezier patch of program patch.c and changes one of the values in the control point array each time through the loop if MOUSE3 or MOUSE1 is pressed. MOUSE3 increases the Y coordinate of the control point. MOUSE1 decreases the Y coordinate of the control point. MOUSE2 allows the change of which control point is selected. All three mouse buttons pressed exits. Pressing the outer two mouse buttons (MOUSE1 and MOUSE3) toggles on/off the filling of the surface patch. */ #define DASHED 1 #include "gl.h" #include "device.h" Matrix bezier = { -1.0, 3.0, -3.0, 1.0, 3.0, -6.0, 3.0, 0.0, -3.0, 3.0, 0.0, 0.0, 1.0, 0.0, 0.0, 0.0 }; #define BEZIER 1 /* Control point arrays... These arrays are separate for each coordinate, i.e. geomx holds all the x coordinates, geomy holds all the y coordinates, and geomz holds all the z coordinates. */ Coord geomx[4][4] = { 0.0, 100.0, 200.0, 300.0, 0.0, 100.0, 200.0, 300.0, 700.0, 600.0, 500.0, 400.0, 700.0, 600.0, 500.0, 400.0 }; Coord geomy[4][4] = { 400.0, 500.0, 600.0, 700.0, 0.0, 100.0, 200.0, 300.0, 0.0, 100.0, 200.0, 300.0, 400.0, 500.0, 600.0, 700.0 }; Coord geomz[4][4] = { 100.0, 200.0, 300.0, 400.0, 100.0, 200.0, 300.0, 400.0, 100.0, 200.0, 300.0, 400.0, 100.0, 200.0, 300.0, 400.0 }; int toggle; /* a toggle switch to turn the user's routine on/off */ main(argc, argv) int argc; char *argv[]; { int light_poly(); /* what user routine we will use */ static long row = 1; /* currently selected row */ static long col = 2; /* currently selected col */ Colorindex wmask; /* writemask value */ int i; /* temp loop variable */ /* init the graphics package */ ginit(); /* put the iris into double buffer mode */ doublebuffer(); /* configure the iris */ gconfig(); /* enable all bit planes for writing */ wmask = (1 << getplanes()) -1; writemask(wmask); /* make sure we can see the cursor */ setcursor(0, RED, wmask); /* full screen viewport */ viewport(0,1023,0,767); /* orthographic viewport */ ortho(0.0,1023.0,0.0,767.0,1023.0,-1023.0); /* translate the picture */ translate(250.0,0.0,0.0); /* make the picture smaller */ scale(0.75,0.75,0.75); /* turn the cursor on */ curson(); /* set the picksize for the middle mouse button hits */ picksize(30,30); /* define a dashed linestyle */ deflinestyle(DASHED,0xf0f0); /* setup the Bezier patch stuff */ setupbezier(argc); /* set up a color ramp... */ for(i = 0 ; i < 256 ; i ++) { mapcolor(i + 8, i , i , i ); } while(TRUE) { if(getbutton(MOUSE1) && getbutton(MOUSE2) && getbutton(MOUSE3)) { break; } /* turn on patch filling */ if(getbutton(MOUSE1) && !getbutton(MOUSE2) && getbutton(MOUSE3)) { User_Routine(toggle = !toggle); ringbell(); while(getbutton(MOUSE1) && getbutton(MOUSE3)); } /* should we increase the Y coordinate? */ if(getbutton(MOUSE3) && !getbutton(MOUSE2) && !getbutton(MOUSE1)) { /* increase the y coordinate */ geomy[row][col] = geomy[row][col] * 1.10; } /* should we decrease the Y coordinate? */ if(getbutton(MOUSE1) && !getbutton(MOUSE2) && !getbutton(MOUSE3)) { /* decrease the Y coordinate */ geomy[row][col] = geomy[row][col] * 0.90; } /* should we change which control point we are using ? */ if(getbutton(MOUSE2) && !getbutton(MOUSE1) && !getbutton(MOUSE3)) { resetcontrolpt(&row,&col,geomx,geomy,geomz); } /* redraw the picture */ color(CYAN); clear(); /* draw the Bezier patch */ linewidth(1); color(BLACK); npatch(geomx,geomy,geomz); /* highlight the changing control point's loc */ controlptoutlines(geomx,geomy,geomz); /* put up some text */ linewidth(1); color(BLACK); cmov2i(200,10); charstr("The Bezier Patch"); swapbuffers(); } /* clear the screen reset */ color(BLACK); clear(); textinit(); swapbuffers(); gflush(); gexit(); } /* this is function setupbezier */ setupbezier(argc) { /* define a basis matrix called BEZIER */ ndefbasis(BEZIER,bezier); /* specify a basis for each direction in the patch */ npatchbasis(BEZIER,BEZIER); /* curve segments will be drawn in the s direction. curve segments will be drawn in the t direction */ npatchcurves(10,10); /* specify the minimum number of line segments for each direction. The actual number of line segments is a multiple of the number of curve segments being drawn in the opposite direction. */ npatchprecision(20,20); Set_User_Routine_for_npatch(light_poly); User_Routine(argc > 1 ? (toggle = 1) : (toggle = 0)); } /* this is controlptoutlines This routine draws the outlines of the input control point arrays. */ controlptoutlines(geomx,geomy,geomz) float geomx[4][4], geomy[4][4], geomz[4][4]; /* control pt arrays */ { long i,j; /* temp locations for the drawing of the control pts */ /* make the control pt lines red */ color(RED); setlinestyle(1); linewidth(3); /* loop in one direction */ for(i=0; i < 4; i=i+1) { for(j=0; j < 4; j=j+1) { if(j == 0) { move(geomx[i][j],geomy[i][j],geomz[i][j]); } else { draw(geomx[i][j],geomy[i][j],geomz[i][j]); } } } /* loop in the other direction */ for(j=0; j < 4; j=j+1) { for(i=0; i < 4; i=i+1) { if(i == 0) { move(geomx[i][j],geomy[i][j],geomz[i][j]); } else { draw(geomx[i][j],geomy[i][j],geomz[i][j]); } } } setlinestyle(0); } /* this is resetcontrolpt.c This routine uses the IRIS pick mechanism to select which control pt should be modified. */ resetcontrolpt(row,col,geomx,geomy,geomz) long *row, *col; /* currently selected row/col of the control pt array */ float geomx[4][4], geomy[4][4], geomz[4][4]; /* control pt arrays */ { short i,j; /* loop temps */ long nhits; /* number of menu pick hit sets */ #define MAXNAMES 50 /* max numberof names spaces */ short names[MAXNAMES]; /* array to hold returned names */ short k,l; /* temp loop variables */ short namecount; /* name counter for pick mode */ /* we have a hit on mouse2, this means we should do iris pick mode to find out what we hit. */ /* save the current view matrix or else... */ pushmatrix(); /* turn on pick mode */ pick(names,MAXNAMES); /* re-do the ortho viewing matrix */ ortho(0.0,1023.0,0.0,767.0,1023.0,-1023.0); /* translate the picture */ translate(250.0,0.0,0.0); /* make the picture larger */ scale(0.75,0.75,0.75); /* draw the pick picture with the associated names. These objects will not actually be displayed. */ namecount = -1; /* initialname for the stack */ for(i=0; i < 4; i=i+1) { for(j=0; j < 4; j=j+1) { namecount = namecount +1; pushname(namecount); /* put a name on the stack */ /* draw a point at each contrl pt as a hit target. */ pnt(geomx[i][j],geomy[i][j],geomz[i][j]); /* get rid of the last name put on */ popname(); } } /* endfor i */ /* turn off pick mode */ nhits = endpick(names); /* restore the matrix */ popmatrix(); /* did we get any hits? */ if(nhits > 0) { /* we had some hits */ j = -1; /* set up ptr for namesbuffer decoding */ /* for each hit set... */ for(i=0; i < nhits; i=i+1) { j = j + 1; /* j points at count of names in names for this hit set */ k = names[j]; /* k is the count of names this hit set */ /* loop for all names this set */ for(l=0; l < k; l=l+1) { j = j + 1; /* j points at the next names entry */ /* compute this row and column */ *row = names[j]/4; *col = names[j]%4; } /* endfor l ... */ } /* endfor i... (endfor all hit sets) */ } /* endif nhits > 0 */ } /* this is routine light_poly The purpose of this routine is to light the created triangles if called. */ int light_poly(Triangle) Coord Triangle[3][3]; { lightthepoly(Triangle, 3, 350.0, -1150.0, 250.0, 350.0, 1150.0, 0.0, 50, 264); } npatch.c **************************************************** /* this is file npatch.c It is a collection of routines that shadow the IRIS patch routines. The purpose of this set of routines is to provide filled surface patches instead of just wireframes. */ #include "gl.h" #include "stdio.h" #define OFF 0 typedef struct { Coord x; Coord y; Coord z; } Point; /* how points are stored */ static struct list_elem { long nid; /* matrix id number */ float *nmatrix; /* pointer to the matrix */ struct list_elem *next_elem_ptr; }; /* struct used to track user supplied matrices */ static Matrix Precision_Matrix_U ; /* used for forward difference computation in the U direction */ static Matrix Precision_Matrix_V ; /* used for forward difference computation in the V direction */ static int _Default_system_routine(); /* what the system does if you do not specify */ static float *current_U_basis; /* pointer to the currently defined U basis matrix */ static float *current_V_basis; /* pointer to the currently defined V basis matrix */ static long UCURVES; /* how many curves in the U direction */ static long VCURVES; /* how many curves in the V direction */ static long USEGMENTS; /* how may curve segments in the U direction */ static long VSEGMENTS; /* how may curve segments in the V direction */ static struct list_elem *head_of_list = NULL; /* pointer to linked list of user supplied basis matrices */ static int (*_User_routine)() = _Default_system_routine; /* set initial user routine to default */ static int _User_routine_is_on = OFF; /* initially do not call user's function */ /******************************************************************************* This routine is what the system automatically does if the user does not supply a particular intercept function. *******************************************************************************/ static int _Default_system_routine(Triangle) Coord Triangle[3][3]; { poly(3, Triangle); } /******************************************************************************* This function allows the user to supply an intercept function that will be used to manipulate the triangles that are generated in the the decomposition of the surface patch. *******************************************************************************/ void Set_User_Routine_for_npatch(routine) int (*routine)(); { _User_routine = routine; } /******************************************************************************* This function allows the user to turn his intercept function on or off at will. *******************************************************************************/ void User_Routine(boolean) int boolean; { _User_routine_is_on = boolean; } /******************************************************************************* This function allows the user to reset his intercept routine to the same routine used as the system default. *******************************************************************************/ void Set_Default_Routine_for_npatch() { _User_routine = _Default_system_routine; } /******************************************************************************* This function is equivalent to the IRIS defbasis function in that it allows the user to define a basis matrix for use in the generation of patches. matrix is saved and is associated with id. id may then be used in subsequent calls to npatchbasis. *******************************************************************************/ void ndefbasis(id, matrix) long id; Matrix matrix; { static int has_been_called = FALSE; struct list_elem *new_elem_to_add; struct list_elem *walking_ptr; float *pmatrix; int row; int column; /* get memory for the data structure */ new_elem_to_add = (struct list_elem *) malloc(sizeof(struct list_elem)); pmatrix = (float *) calloc(sizeof(Matrix), sizeof(float)); /* make a copy of the basis matrix passed in by the user */ for(row = 0; row < 4; row++) for(column = 0; column < 4; column++) { *(pmatrix + (4*row) + column) = matrix[row][column]; } /* put in the information into the data structure */ new_elem_to_add -> nid = id; new_elem_to_add -> nmatrix = pmatrix; /* determine how to add this information into the linked list of basis matrices */ switch(has_been_called) /* does a list already exist ? */ { case TRUE : /* Yes */ walking_ptr = head_of_list; /* point to the beginning of the list */ /* traverse the list */ while((walking_ptr -> nid != id) && (walking_ptr -> next_elem_ptr != head_of_list)) { walking_ptr = walking_ptr -> next_elem_ptr; } if(walking_ptr -> nid == id) /* this id already exists so we can re-use the data structure already in the list */ { /* get rid of the old basis matrix */ cfree(walking_ptr -> nmatrix, sizeof(Matrix), sizeof(float)); /* point to the replacement matrix */ walking_ptr -> nmatrix = pmatrix; /* get rid of the un-needed data structure */ cfree(new_elem_to_add, 1, sizeof(struct list_elem)); } else /* the id does not exist in the current linked list of basis matrices so we must add it into it */ { /* manipulate the pointers to add it in */ new_elem_to_add -> next_elem_ptr = head_of_list -> next_elem_ptr; head_of_list -> next_elem_ptr = new_elem_to_add; } break; case FALSE : /* No */ /* no linked list of basis matrices exists so we start up one */ head_of_list = (struct list_elem *) malloc(sizeof(struct list_elem)); head_of_list -> next_elem_ptr = head_of_list; new_elem_to_add -> next_elem_ptr = head_of_list -> next_elem_ptr; head_of_list -> next_elem_ptr = new_elem_to_add; has_been_called = TRUE; /* make sure we do not do this again */ break; default : break; } } /******************************************************************************* This function is equivalent to the IRIS patchbasis function in that it sets the current basis matrices for both the U and V parametric directions of a surface patch. The current U and V bases are used when the npatch command is issued. *******************************************************************************/ int npatchbasis(uid, vid) long uid, vid; { struct list_elem *walking_ptr; if(head_of_list == NULL) /* no linked list of basis matrices */ { fprintf(stderr, "\nnpatchbasis: no basis matrices defined\n\n"); exit(-1); } /* traverse the list looking for the desired U basis matrix */ walking_ptr = head_of_list; while((walking_ptr -> nid != uid) && (walking_ptr -> next_elem_ptr != head_of_list)) { walking_ptr = walking_ptr -> next_elem_ptr; } if((walking_ptr -> nid != uid) && (walking_ptr -> next_elem_ptr == head_of_list)) /* the desired U basis matrix does not exist in the linked list */ { fprintf(stderr, "\nnpatchbasis: undefined U basis matrix %d\n\n", uid); exit(-1); } current_U_basis = walking_ptr -> nmatrix; /* traverse the list looking for the desired V basis matrix */ walking_ptr = head_of_list; while((walking_ptr -> nid != vid) && (walking_ptr -> next_elem_ptr != head_of_list)) { walking_ptr = walking_ptr -> next_elem_ptr; } if((walking_ptr -> nid != vid) && (walking_ptr -> next_elem_ptr == head_of_list)) /* the desired V basis matrix does not exist in the linked list */ { fprintf(stderr, "\nnpatchbasis: undefined V basis matrix %d\n\n", vid); exit(-1); } current_V_basis = walking_ptr -> nmatrix; } /******************************************************************************* This function is similar to the IRIS patchcurves command. ucurves and vcurves set the subdivision parameters used in decomposing the surface patch. An individual patch will be decomposed into a ucurves * vcurves grid with each grid generating two triangles. *******************************************************************************/ void npatchcurves(ucurves, vcurves) long ucurves, vcurves; { /* prevent a negative number of curves */ UCURVES = (ucurves < 1 ? 10 : ucurves); VCURVES = (vcurves < 1 ? 10 : vcurves); /* set up the Precision_Matrix_U used in the forward difference along the U direction */ Precision_Matrix_U[0][0] = 6.0/(float)(UCURVES * UCURVES * UCURVES); Precision_Matrix_U[1][0] = 6.0/(float)(UCURVES * UCURVES * UCURVES); Precision_Matrix_U[1][1] = 2.0/(float)(UCURVES * UCURVES); Precision_Matrix_U[2][0] = 1.0/(float)(UCURVES * UCURVES * UCURVES); Precision_Matrix_U[2][1] = 1.0/(float)(UCURVES * UCURVES); Precision_Matrix_U[2][2] = 1.0/(float)(UCURVES); Precision_Matrix_U[3][3] = 1.0; /* set up the Precision_Matrix_V used in the forward difference along the V direction */ Precision_Matrix_V[0][0] = 6.0/(float)(VCURVES * VCURVES * VCURVES); Precision_Matrix_V[1][0] = 6.0/(float)(VCURVES * VCURVES * VCURVES); Precision_Matrix_V[1][1] = 2.0/(float)(VCURVES * VCURVES); Precision_Matrix_V[2][0] = 1.0/(float)(VCURVES * VCURVES * VCURVES); Precision_Matrix_V[2][1] = 1.0/(float)(VCURVES * VCURVES); Precision_Matrix_V[2][2] = 1.0/(float)(VCURVES); Precision_Matrix_V[3][3] = 1.0; } /******************************************************************************* This function is similar to the IRIS patchprecision routine but is only used to maintain consistency with the IRIS routines. It's results are not used by any other function in the suite. *******************************************************************************/ void npatchprecision(usegments, vsegments) long usegments, vsegments; { /* prevent a negative number of segments */ USEGMENTS = (usegments < 1 ? 10 : usegments); VSEGMENTS = (vsegments < 1 ? 10 : vsegments); } /******************************************************************************* This function does the actual display for the surface patch. *******************************************************************************/ static void nspeckle(COORD_ARRAY_POINTER) Point *COORD_ARRAY_POINTER[4]; { register Point *Patch_array; /* get enough memory to hold all the points that will be generated */ Patch_array = (Point *) calloc((UCURVES+1)*(VCURVES+1), sizeof(Point)); { register Point *WHERE_IT_IS_AT; register unsigned int total_points; register unsigned int point_count; register unsigned int t_count; register unsigned int count; register unsigned int Row; register unsigned int Column; Matrix control_matrix; Matrix inter1; /* for every curve in the the U parametric direction */ for(point_count = 0, total_points = 0 ; point_count <= UCURVES ; point_count++) { /* build a control matrix for the current curve */ for(count = 0; count < 4; count++) { WHERE_IT_IS_AT = (Point *) (COORD_ARRAY_POINTER[count] + point_count); control_matrix[count][0] = WHERE_IT_IS_AT -> x; control_matrix[count][1] = WHERE_IT_IS_AT -> y; control_matrix[count][2] = WHERE_IT_IS_AT -> z; } /* generate the matrix to compute the forward difference on */ pushmatrix(); loadmatrix(control_matrix); multmatrix(current_V_basis); multmatrix(Precision_Matrix_V); getmatrix(inter1); popmatrix(); /* save all the points generated for that curve */ for(t_count = 0 ; t_count <= VCURVES ; t_count++, total_points++) { (Patch_array + total_points) -> x = inter1[3][0] ; (Patch_array + total_points) -> y = inter1[3][1] ; (Patch_array + total_points) -> z = inter1[3][2] ; /* do the forward difference */ for(Row = 3; Row > 0; Row--) for(Column = 0; Column < 4; Column++) inter1[Row][Column] = inter1[Row][Column] + inter1[Row - 1][Column]; } } } { Coord Triangle_1[4][3]; register Point *WHERE_IT_IS_AT; register unsigned int Row; register unsigned int Column; /* decompose the patch into its individual triangles */ for(Row = 0; Row < UCURVES; Row++) for(Column = 0 ; Column < VCURVES; Column++) { WHERE_IT_IS_AT = (Patch_array + ((VCURVES + 1) * Row) + Column); Triangle_1[0][0] = WHERE_IT_IS_AT -> x; Triangle_1[0][1] = WHERE_IT_IS_AT -> y; Triangle_1[0][2] = WHERE_IT_IS_AT -> z; Triangle_1[1][0] = (WHERE_IT_IS_AT + 1) -> x; Triangle_1[1][1] = (WHERE_IT_IS_AT + 1) -> y; Triangle_1[1][2] = (WHERE_IT_IS_AT + 1) -> z; Triangle_1[2][0] = (WHERE_IT_IS_AT + VCURVES + 1) -> x; Triangle_1[2][1] = (WHERE_IT_IS_AT + VCURVES + 1) -> y; Triangle_1[2][2] = (WHERE_IT_IS_AT + VCURVES + 1) -> z; Triangle_1[3][0] = (WHERE_IT_IS_AT + VCURVES + 2) -> x; Triangle_1[3][1] = (WHERE_IT_IS_AT + VCURVES + 2) -> y; Triangle_1[3][2] = (WHERE_IT_IS_AT + VCURVES + 2) -> z; if(_User_routine_is_on) /* does the user have an intercept routine ? */ { /* Yes */ (*_User_routine) (&Triangle_1[0][0]); (*_User_routine) (&Triangle_1[1][0]); } else /* no user routine, so we use the default */ { _Default_system_routine(&Triangle_1[0][0]); _Default_system_routine(&Triangle_1[1][0]); } } } /* return the memory used to the system */ cfree(Patch_array, (UCURVES+1)*(VCURVES+1), sizeof(Point)); } /******************************************************************************* This function rearranges the input matrices into a form readily used in computing points along the four curves defined by those matrices. It then computes those points for each curve using the technique of forwards differencing of a matrix. *******************************************************************************/ void npatch(geomx, geomy, geomz) Coord geomx[4][4], geomy[4][4], geomz[4][4]; { register Point *COORD_ARRAY_POINTER[4]; /* one control matrix for each curve */ Matrix ctrl_pts1; Matrix ctrl_pts2; Matrix ctrl_pts3; Matrix ctrl_pts4; /* load the appropriate control matrix for each curve */ ctrl_pts1[0][0] = geomx[0][0]; ctrl_pts1[0][1] = geomy[0][0]; ctrl_pts1[0][2] = geomz[0][0]; ctrl_pts1[1][0] = geomx[1][0]; ctrl_pts1[1][1] = geomy[1][0]; ctrl_pts1[1][2] = geomz[1][0]; ctrl_pts1[2][0] = geomx[2][0]; ctrl_pts1[2][1] = geomy[2][0]; ctrl_pts1[2][2] = geomz[2][0]; ctrl_pts1[3][0] = geomx[3][0]; ctrl_pts1[3][1] = geomy[3][0]; ctrl_pts1[3][2] = geomz[3][0]; ctrl_pts2[0][0] = geomx[0][1]; ctrl_pts2[0][1] = geomy[0][1]; ctrl_pts2[0][2] = geomz[0][1]; ctrl_pts2[1][0] = geomx[1][1]; ctrl_pts2[1][1] = geomy[1][1]; ctrl_pts2[1][2] = geomz[1][1]; ctrl_pts2[2][0] = geomx[2][1]; ctrl_pts2[2][1] = geomy[2][1]; ctrl_pts2[2][2] = geomz[2][1]; ctrl_pts2[3][0] = geomx[3][1]; ctrl_pts2[3][1] = geomy[3][1]; ctrl_pts2[3][2] = geomz[3][1]; ctrl_pts3[0][0] = geomx[0][2]; ctrl_pts3[0][1] = geomy[0][2]; ctrl_pts3[0][2] = geomz[0][2]; ctrl_pts3[1][0] = geomx[1][2]; ctrl_pts3[1][1] = geomy[1][2]; ctrl_pts3[1][2] = geomz[1][2]; ctrl_pts3[2][0] = geomx[2][2]; ctrl_pts3[2][1] = geomy[2][2]; ctrl_pts3[2][2] = geomz[2][2]; ctrl_pts3[3][0] = geomx[3][2]; ctrl_pts3[3][1] = geomy[3][2]; ctrl_pts3[3][2] = geomz[3][2]; ctrl_pts4[0][0] = geomx[0][3]; ctrl_pts4[0][1] = geomy[0][3]; ctrl_pts4[0][2] = geomz[0][3]; ctrl_pts4[1][0] = geomx[1][3]; ctrl_pts4[1][1] = geomy[1][3]; ctrl_pts4[1][2] = geomz[1][3]; ctrl_pts4[2][0] = geomx[2][3]; ctrl_pts4[2][1] = geomy[2][3]; ctrl_pts4[2][2] = geomz[2][3]; ctrl_pts4[3][0] = geomx[3][3]; ctrl_pts4[3][1] = geomy[3][3]; ctrl_pts4[3][2] = geomz[3][3]; { register Point *WHERE_TO_SAVE; register unsigned int Row; register unsigned int Column; register unsigned int point_count; register unsigned int count; float *matrix_pointer[4]; Matrix inter1; matrix_pointer[0] = (float *) ctrl_pts1; matrix_pointer[1] = (float *) ctrl_pts2; matrix_pointer[2] = (float *) ctrl_pts3; matrix_pointer[3] = (float *) ctrl_pts4; /* get enough memory to hold the points */ COORD_ARRAY_POINTER[0] = (Point *) calloc(UCURVES + 1, sizeof(Point)); COORD_ARRAY_POINTER[1] = (Point *) calloc(UCURVES + 1, sizeof(Point)); COORD_ARRAY_POINTER[2] = (Point *) calloc(UCURVES + 1, sizeof(Point)); COORD_ARRAY_POINTER[3] = (Point *) calloc(UCURVES + 1, sizeof(Point)); /* for each curve */ for(count = 0; count < 4; count++) { /* generate the matrix used in the forward difference for this curve */ pushmatrix(); loadmatrix(matrix_pointer[count]); multmatrix(current_U_basis); multmatrix(Precision_Matrix_U); getmatrix(inter1); popmatrix(); /* for each curve generate points in the U parametric direction */ for(point_count = 0 ; point_count <= UCURVES ; point_count++) { WHERE_TO_SAVE = (Point *) (COORD_ARRAY_POINTER[count] + point_count); WHERE_TO_SAVE -> x = inter1[3][0]; WHERE_TO_SAVE -> y = inter1[3][1]; WHERE_TO_SAVE -> z = inter1[3][2]; /* compute the forward difference */ for(Row = 3; Row > 0; Row--) for(Column = 0; Column < 4; Column++) inter1[Row][Column] = inter1[Row][Column] + inter1[Row - 1][Column]; } } } nspeckle(COORD_ARRAY_POINTER); /* call function to finish computations and display */ /* return the memory used back to the system */ cfree(COORD_ARRAY_POINTER[0],(UCURVES + 1), sizeof(Point)); cfree(COORD_ARRAY_POINTER[1],(UCURVES + 1), sizeof(Point)); cfree(COORD_ARRAY_POINTER[2],(UCURVES + 1), sizeof(Point)); cfree(COORD_ARRAY_POINTER[3],(UCURVES + 1), sizeof(Point)); } lightpoly.c ************************************************ /* this is file lightpoly.c It is a routine that computes lighting for a polygon based upon the angle between the Normal vector of the polygon and the direction to the light source. lightthepoly(xyz,ncoords,ax,ay,az,lx,ly,lz,colormin,colormax) xyz[][3] = floating coords of the polygon. ncoords = number of coordinates. ax,ay,az = interior point of the whole object. Used to determine outward facing normal of the polygon. This is the same point of reference that would be used for backface polygon removal. lx,ly,lz = vector pointing in direction of the light source. colormin, colormax = indices used for the colors assigned to this polygon. The user is responsible for setting up the color ramp. Note: the routine also puts the polygons out ordered counterclockwise with respect to the interior point for ease of backface polygon removal. */ #include #include #define PIDIV2 1.570796327 #define CLOCKWISE 1 #define COLUMN 3 lightthepoly(xyz,ncoords,ax,ay,az,lx,ly,lz,colormin,colormax) Coord xyz[][3]; unsigned int ncoords; Coord ax,ay,az; /* interior point of the whole object. */ Coord lx,ly,lz; /* direction to the light source */ int colormin,colormax; /* color min/max indices */ { Coord *txyz; /* temp coord hold */ register unsigned short int i,j; /* loop temps */ int npoly_orient(); /* direction test function */ Coord v1[3],v2[3]; /* vectors used to compute the polygon's normal */ Coord normal[3]; /* the polygon's normal */ Coord normalmag; /* normal's magnitude */ Coord lightmag; /* light's magnitude */ float dotprod; /* dot product of N and L */ float radians; /* angle between N and L */ unsigned short int colortouse; /* color to use in drawing the polygon */ /* allocate memory for the temporary array */ /* this is a two dimensional array of ncoords by 3 */ txyz = (Coord *) calloc((ncoords * 3), sizeof(Coord)); /* orient the polygon so that its counterclockwise with respect to the interior point */ if(npoly_orient(ncoords,xyz,ax,ay,az) == CLOCKWISE) { /* the polygon is clockwise, reverse it. */ for(i=0; i < ncoords; i=i+1) { for(j=0; j < COLUMN; j=j+1) { *(txyz + (i * COLUMN) + j) = xyz[ncoords-i-1][j]; } } } else { /* no need to reverse */ for(i=0; i < ncoords; i=i+1) { for(j=0; j < COLUMN; j=j+1) { *(txyz + (COLUMN * i) + j) = xyz[i][j]; } } } /* the coordinates are ordered counterclockwise in array txyz */ /* compute the normal vector for the polygon using the first three vertices...*/ /* compute the first vector to use in the computation */ v1[0] = *(txyz + 6) - *(txyz + 3); /* txyz[2][0] - txyz[1][0] */ v1[1] = *(txyz + 7) - *(txyz + 4); /* txyz[2][1] - txyz[1][1] */ v1[2] = *(txyz + 8) - *(txyz + 5); /* txyz[2][2] - txyz[1][2] */ /* compute the second vector to use in computing the normal */ v2[0] = *(txyz ) - *(txyz + 3); /* txyz[0][0] - txyz[1][0] */ v2[1] = *(txyz + 1) - *(txyz + 4); /* txyz[0][1] - txyz[1][1] */ v2[2] = *(txyz + 2) - *(txyz + 5); /* txyz[0][2] - txyz[1][2] */ /* the normal is v1 x v2 */ normal[0] = v1[1]*v2[2] - v1[2]*v2[1]; normal[1] = v1[2]*v2[0] - v1[0]*v2[2]; normal[2] = v1[0]*v2[1] - v1[1]*v2[0]; /* compute the magnitude of the normal */ normalmag = sqrt((normal[0]*normal[0]) + (normal[1]*normal[1])+ (normal[2]*normal[2])); /* compute the magnitude of the light */ lightmag = sqrt((lx * lx) + (ly * ly) + (lz * lz)); /* compute N . L (normal dot product with the light source direction) */ dotprod = ((normal[0] * lx) + (normal[1] * ly) + (normal[2] * lz)); /* compute the unit normal */ dotprod = ((dotprod/(normalmag * lightmag))); /* dotprod = cos(theta) of the angle between N and L. Convert to angle in radians */ radians = acos(dotprod); /* compute the color we should use */ if(-PIDIV2 <= radians && radians <= PIDIV2) { /* if the angle is negative, set to positive */ if(radians < 0.0) { radians = -radians; } colortouse = ((colormax-colormin)/PIDIV2)*(PIDIV2-radians)+colormin; } else { colortouse = colormin; } /* set the color */ color(colortouse); /* draw the poly */ polf(ncoords,txyz); /* free up memory allocated for the temporary array */ cfree(txyz, (ncoords * 3), sizeof(Coord)); } npoly_orient.c ********************************************* /* this is file npoly_orient.c Its purpose is to determine the orientation of a polygon with respect to its interior point. */ #include #include int npoly_orient(ncoords,xyz,xinside,yinside,zinside) unsigned int ncoords; Coord xyz[][3]; Coord xinside, yinside, zinside; { register unsigned short int i,j; /* loop temps */ Coord center[3]; /* center coordinate of the polygon */ Coord a[3], b[3]; /* vector hold locations for the vectors that run from the center coordinate to the points of the polygon */ Coord xn[3], xmn[3]; /* points on line containing normal that are on opposite sides of the plane containing the polygon. */ float distton; /* distance to point n from pt inside. */ float disttomn; /* distance to point -n from pt inside. */ Coord normal[3]; /* the normal vector computed from a x b */ /* compute the center coordinate of the polygon */ center[0] = 0.0; center[1] = 0.0; center[2] = 0.0; for(i=0; i < ncoords; i++) { for(j=0; j < 3; j++) { center[j] += xyz[i][j]; } } /* divide out by the number of coordinates */ for(j=0; j < 3; j++) { center[j] = center[j]/(float)ncoords; } /* check the first 2 coordinates of the polygon for their direction */ /* compute vector a. It runs from the center coordinate to coordinate 0 */ for(j=0; j < 3; j++) { a[j] = xyz[0][j] - center[j]; } /* compute vector b. It runs from the center coordinate to coordinate 1 */ for(j=0; j <3; j++) { b[j] = xyz[1][j] - center[j]; } /* compute a x b to get the normal vector */ normal[0] = a[1]*b[2] - a[2]*b[1]; normal[1] = a[2]*b[0] - a[0]*b[2]; normal[2] = a[0]*b[1] - a[1]*b[0]; /* compute point n, offset pt from center in direction of normal */ for(j=0; j < 3; j++) { xn[j] = center[j] + normal[j]; } /* compute point -n, offset pt from center in opposite direction from normal. */ for(j=0; j < 3; j++) { xmn[j] = center[j] - normal[j]; } /* compute the distance the inside pt is from point n */ distton = sqrt((xn[0] - xinside) * (xn[0] - xinside) + (xn[1] - yinside) * (xn[1] - yinside) + (xn[2] - zinside) * (xn[2] - zinside)); /* compute the distance the inside pt is from point -n */ disttomn = sqrt((xmn[0] - xinside) * (xmn[0] - xinside) + (xmn[1] - yinside) * (xmn[1] - yinside) + (xmn[2] - zinside) * (xmn[2] - zinside)); /* if the dist(n) < dist(-n), then n points back towards the inside point and is on the same side of the plane as inside. a x b is then clockwise. */ if(distton < disttomn) { return(1); /* clockwise */ } else { return(0); /* counterclockwise */ } } 11-Dec-86 12:55:12-PST,4276;000000000000 Mail-From: BRUGGE created at 11-Dec-86 12:54:38 Date: Thu 11 Dec 86 12:54:38-PST From: John Brugge Subject: Directory for IRIS public domain software To: info-iris@SUMEX-AIM.ARPA Message-ID: <12262013998.28.BRUGGE@SUMEX-AIM.ARPA> As an attempt to provide a central location for public domain software that Info-Iris readers wish to share, a directory has been set up here on Sumex to hold the source code files, which people can then retrieve in some manner (explained below). How to get programs: 1. For those sites with FTP programs, one can access Sumex-Aim as user 'anonymous' and any password. The files are stored in the directory , with the file 00DIR giving an annotated listing of the contents (kept reasonably up-to-date). 2. For other sites, an arrangement can be made to either copy it to a cartridge tape you would provide, and mail it, or if the files are short enough, simply relay them by electronic mail. Note that most of the files currently in are those which have been part of mail messages to INFO-IRIS, so that many of you may already have them. How to submit programs: [ small =~ a couple files; medium =~ half a dozen files; large =~ >12 files] 1. For small to medium submissions, one should send them to Info-Iris-Request@Sumex-Aim to have them archived, and then send an announcement to Info-Iris stating their submission and describing them. Alternatively, if the program is small, and of general interest, one can send the source directly to Info-Iris, with a statement as to whether or not the submission should be archived also (I will only do so at the author's request). [ Note, though, that incoming messages to the list are not screened, so that you will have to use your own judgement as to what is a "reasonable" size to submit in this second manner--if it is not of *general* interest, I would urge you to submit it the first way, code and description seperately. ] 2. For large submissions, one should either send them electronically to Info-Iris-Request, or mail a cartridge tape containing the source files to the following: John Brugge Knowledge Systems Laboratory 701 Welch Rd, Bldg C Palo Alto, CA 94025 With "Attn: Info-Iris submission". One can then announce their submission on Info-Iris, along with a short description. What to submit: Utility programs, patches, demos; basically anything which you feel is something others might find useful. And which is not proprietary. What not to submit: Programs that are already in the public domain and maintained elsewhere (e.g. the editors Gnu Emacs (available from MIT) and ELLE (available from SRI)). Exceptions are patches to pd programs needed for them to run on an Iris (e.g. the specific .h files for Gnu). Below is the file 00DIR, which is a listing of the contents of the directory as it now stands. Send reports of any problems encountered retrieving any of the files to Info-Iris-Request@Sumex-Aim (but send bug reports to the program author!). Enjoy! John PS: 00DIR..1;P777752 1 1021(7) 11-Dec-86 08:35:06 BRUGGE An annotated directory listing (this file). 00README..1;P777752 1 231(7) 30-Oct-86 15:07:33 BRUGGE General description of the Info-Iris interest group DRAWCUBE.C.1;P777752 6 14350(7) 3-Nov-86 07:44:13 BRUGGE Backface polygon removal routines. FONTS..2;P777752 38 97080(7) 11-Dec-86 08:28:13 BRUGGE Files for creating fonts on the IRIS, as well as some font descriptions. CONFIG.H.1;P777752 2 3794(7) 30-Oct-86 14:58:55 BRUGGE M_TURBO.H.1;P777752 2 3509(7) 30-Oct-86 14:59:48 BRUGGE S_UNIPL50.H.1;P777752 2 4776(7) 30-Oct-86 14:59:35 BRUGGE Header files for GNU Emacs specific to the IRIS. Note that S_UNIPL50.H should be named "s-unipl5.0.h" on the IRIS, and M_TURBO.H should be named "m-turbo.h". PATCHES.C.2;P777752 15 36896(7) 11-Dec-86 08:21:23 BRUGGE Filled surface patches, as well as a simple lighting model. Total of 67 pages in 8 files ------- 12-Dec-86 04:36:25-PST,1464;000000000000 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.ARPA with TCP; Fri 12 Dec 86 04:36:06-PST Received: by ucbvax.Berkeley.EDU (5.53/1.19) id AA10306; Thu, 11 Dec 86 18:45:32 PST Received: by ucscc (5.51/4.7) id AA02700; Thu, 11 Dec 86 14:44:49 PST Date: Thu, 11 Dec 86 14:44:49 PST From: ucscc!saupe@ucbvax.Berkeley.EDU (20010000) Message-Id: <8612112244.AA02700@ucscc> To: info-iris@sumex-aim.stanford.edu Subject: IRIS Gouraud shading Re : Problem with Gouraud shaded polygons While the geometry engine handles the 3-dimensional clipping of polygons nicely, it cannot interpolate the colors for a newly created vertex in the clipping process. The result is a Gouraud shaded image with very visible flaws near the edges of the window. In order to deal with this problem one could send each polygon through the geometry engine in feedback mode and check whether the polygon gets clipped or not. In the first case an interpolating color has to be computed for the newly created or modified vertices. Then the clipped polygon can be sent through the engine again and should be rendered correctly. Is there anyone who has already carried out this program or another solution of the Gouraud shading/clipping problem and who is willing to share the software ? Dietmar Saupe Department of Mathematics UCSC Santa Cruz, Cal. 95064 ph. (408) 429-4642 e-mail saupe@ucscc.BITNET 13-Dec-86 02:05:01-PST,2053;000000000000 Return-Path: Received: from BRL-VGR.ARPA by SUMEX-AIM.ARPA with TCP; Sat 13 Dec 86 02:04:34-PST Date: Sat, 13 Dec 86 4:46:26 EST From: Mike Muuss To: info-iris@sumex-aim.stanford.EDU cc: Stay@BRL.ARPA Subject: hypot() bug in 3.5 Message-ID: <8612130446.aa23363@VGR.BRL.ARPA> In SGI release 3.4.1, I reported a problem with the hypot() routine smashing the stack frame of the CALLING function, obliterating saved registers, and resulting in very difficult to understand havoc many lines of code AFTER the call to hypot(). As best as I could tell from examining the library routine, this problem was due to the fact that hypot() was expecting "long float" arguments when it really was getting "floats" and "doubles" (same thing: 4 bytes). It then modified these call-by-value arguments as it ran. Smashing 8 bytes of stack frame. In SGI release 3.5, the stack frame no longer seems to get smashed. However, the routine hypot() does not deliver correct answers, even for simple cases. Like this one: #include #include main() { double f; f = hypot( 159559.0, 0.301084 ); printf("f = %g, x%x\n", f, f ); } The answer returned is INF, IEEE Infinity, 0x7f800001. Another irritation is that in /usr/include/sgimath.h (automaticly included by /usr/include/math.h), Revision 1.3 of 86/07/17, hypot() is declared as a function returning "long float". This is incorrect; it should return "float", and some OTHER function like _lhypot() should exist to provide the "long float" function. I have received profuse apologies from the management at SGI about the "long float" business. They seem quite sorry about it; most of them claim not to have known about it until after the first "long float" release had shipped to customers. Sigh. It is my hope that the person responsible for this long float abomination suffer a doubled burden of paperwork in the afterlife for every customer that has been nailed by this. -Mike 7-Jan-87 00:46:39-PST,1360;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed 7 Jan 87 00:46:19-PST Received: by lindy.STANFORD.EDU; Wed, 7 Jan 87 00:43:36 PST Date: Wed, 7 Jan 87 00:46:19 PST From: Reply-To: XBR2D96D%DDATHD21.BITNET@forsythe.stanford.edu To: Info-Iris@sumex-aim.stanford.edu Subject: IRIS NFS Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 07 Jan 87 09:41:48 Date: Wed, 7 Jan 87 09:39:20 +0100 (Central European Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: IRIS NFS To: Info-Iris@SUMEX-AIM.Stanford.Edu X-VMS-To: X%"Info-Iris@SUMEX-AIM.Stanford.Edu" Hallo, I've sent a similar request a few weeks ago and never got an answer, but I suppose that was due to problems with the ARPA/BITNET interface. So I repeat my questions: 1.) Is the NFS implementation for the IRIS "full functionality" or "client only"? Has anybody got experience with NFS/IRIS? 2.) Has anybody experiences connenting the Commodore AMIGA (NFS connection preferred) to the IRIS. Has anybody experinces with software development for the AMIGA on the IRIS? Regards Martin Knoblauch TH-Darmstadt Dept. Phys. Chem. I Petersenstrasse 20 D-6100 Darmstadt, FRG 12-Jan-87 12:31:43-PST,891;000000000000 Return-Path: Received: from nps-cs by SUMEX-AIM.STANFORD.EDU with TCP; Mon 12 Jan 87 12:30:50-PST Date: Mon, 12 Jan 87 12:30:16 pst From: michael zyda Message-Id: <8701122030.AA01259@nps-cs> To: info-iris@sumex-aim Subject: BSP Hidden Surface Algorithm Has anyone implemented the Binary Space Partitioning Algorithm of Henry Fuchs on the IRIS? This algorithm is useful for generating Hidden Surfaces via the Painter's Algorithm and hence could be useful for moving through fixed scenes in real-time using double buffering. If you have implemented this algorithm, are you willing to share you code and experiences with it? Thank you very much in advance!!! Michael Zyda Naval Postgraduate School, Code 52, Dept. of Computer Science Monterey, California 93943-5100 (408) 646-2305 zyda@nps-cs.arpa 13-Jan-87 09:38:35-PST,1462;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Tue 13 Jan 87 09:37:07-PST Received: by lindy.STANFORD.EDU; Tue, 13 Jan 87 09:34:32 PST Date: Tue, 13 Jan 87 09:36:50 PST From: Reply-To: mailer%uogvax2.BITNET@forsythe.stanford.edu To: info-iris@sumex-aim.stanford.edu Received: from UOGVAX2(MAILER) by UOGUELPH (Mailer X1.23b) id 2294; Tue, 13 Jan 87 12:26:58 EST Received: by snowhite (5.51/4.7) id AA06354; Tue, 13 Jan 87 12:21:40 EST Date: Tue, 13 Jan 87 12:21:40 EST From: rick@snowhite To: info-iris@sumex-aim.stanford.edu hi, this mail message is a grovelling request for help re unix based graphics software. we have three iris1400's and a few dec microvaxII's here, but very little budget for layered software. the two specific quests are: - a paint program for a colour raster display - any rendering/compositing systems for 3D objects and scenes if you have, or know of any software that is available as cheap unsupported sources that would help with the above, i would greatly appreciate hearing about it. in any case, all the best, rick addr: rick%uogvax2.bitnet@wiscvm.wisc.edu or rick@uogvax2.bitnet or rick macklem, dept. of computing and info. sc., university of guelph, guelph, ont. n1g 2w1, canada. phone:(519) 824-4120 ext.3284 13-Jan-87 23:33:30-PST,6559;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue 13 Jan 87 23:31:27-PST Date: Wed, 14 Jan 87 2:29:05 EST From: Mike Muuss To: rick%uogvax2.bitnet@wiscvm.wisc.EDU cc: info-iris@sumex-aim.stanford.EDU, info-graphics@ads.arpa, CADinterest^.es@xerox.COM Subject: BRL CAD Package Message-ID: <8701140229.aa10391@SEM.BRL.ARPA> This message is a formal announcement of the BRL CAD Package, a followup to the teaser I posted late last summer. When the printed documentation (315 pages) returns from the print shop (Friday, they tell me), we will begin shipping our backlog of requests. I'm sorry for the longish delay, but there wasn't much that could be done about it, given the numerous constraints that had to be met. The BRL CAD Package is a solid modeling system, with ray-tracer, framebuffer library, and lots of image tools. We have tested this software on VAXen running 4.2 and 4.3 BSD, Gould PowerNodes, SGI Irises, Sun Workstations, Cray XMP, Cray-2, Alliant FX/8, and Pyramids. (Benchmark comparisons included as part of the distribution, as well as the benchmark itself, so you can see how your favorite machine stacks up). The software included in this package is only the tip of the iceberg. The next release is expected to contain a serious image- and signal- processing toolkit to compliment the existing tools. Hopefully, many of you will find this a worthwhile software base to build upon, and will contribute your favorite graphics tools to round out the collection. Best, -Mike - - - - - - - - - - - - BALLISTIC RESEARCH LABORATORY SOLID MODELING SYSTEM and RAY-TRACING BENCHMARK DISTRIBUTION PACKAGE Release 1.15 (9-Jan-87) DISTRIBUTION DETAILS To obtain a copy of the distribution, you should send the authors: 1) Enough magnetic tape for 12 Mbytes of data. For 9-track 1/2 inch magtape, specify density (800, 1600, or 6250). Silicon Graphics and SUN tape cartridges can also be accommodated. Specify TAR or CPIO, and blocksize. 2) A letter indicating: -- Who you are -- What the BRL CAD package is to be used for -- Equipment and operating system(s) you plan on using -- That you agree to the conditions listed below. The software is distributed free of charge with the following conditions: 1. The BRL CAD package source files won't be passed on to third parties. If someone wants them, have them contact BRL. We need to know who has what, and what it is being used for. 2. BRL will be credited should the software be used in a product or written about in any publication. BRL will be referenced as the original source in any advertisements. 3. BRL assumes no legal responsibility for source code and its subsequent use. No warranty is expressed or implied. 4. If any bugs or problems are found they will be reported back to BRL. You will own full rights to any databases or images you create with this package. To obtain authorization for use at additional sites, or for permission to use this work as part of a commercial package, please contact the authors at the address below. For non-US sites, an extra step is required. You must send your letter and tape to your Ambasador to the United States in Washington DC, and have them forwarded to BRL through official channels. CONTENTS What you have here is a collection of software which includes: libsysv Some System-V compatability routines mged A solid-model editor librt A solid-model ray-tracing library rt A ray-tracing lighting model, for rendering db Several solid-model databases, in ASCII form conv ASCII/binary database converters bench Scripts to drive the RT benchmark pix Reference images for the RT benchmark, in ASCII form libpkg A "message-passing" interface to TCP network links libfb A generic frame-buffer library rfbd TCP server for remote frame-buffer access libtermio A library to handle terminal mode setting libplot3 A public-domain 2-D and 3-D UNIX-Plot library librle A Run-Length-Encoding library (originally from UofUtah) util Zillions of image-handling utilities, as tools fbed Frame-buffer image editor vdeck Convert mged models to GIFT-format card decks. dmdfb libfb support for layers in Teletype 5620 DMD terminal This distribution does NOT include the various BRL- specific model analysis tools such as GIFT, SAR, SLAVE, VAST, etc. ENHANCEMENTS, COMMUNICATION It is expected that new releases of this software will be issued roughly semi-annually. Information about new releases will be routinely provided to recipients of this software. If your address changes, please let us know, so we can update our records. You are invited to participate in the BRL CAD software mailinglist, called . Bug reports and discussions of new features are the main topics; volume of messages has been light (so far). Direct your bug reports to this address. Request a subscrip- tion by sending to . If you find bugs, please report your experiences. ** While BRL makes no offer of support, we are most ** interested in hearing about your experiences. Elec- tronic mail is vastly preferred over telephone contact. In dire circumstances, you may phone; 1500-1800 Eastern time is best. If you develop additional software for the BRL CAD environment that you would be willing to share, please send it to us for inclusion in the next release. Best Wishes, -Mike Muuss Leader, Advanced Computer Systems Team U.S. Army Ballistic Research Laboratory APG, MD. 21005-5066 USA ArpaNet: 14-Jan-87 16:22:52-PST,2828;000000000000 Return-Path: Received: from sdcsvax.UCSD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed 14 Jan 87 16:16:08-PST Received: by sdcsvax.UCSD.EDU (5.57/4.42) id AA01351; Wed, 14 Jan 87 16:14:17 PST hops=0 Received: by sdchema.chem.ucsd.edu (5.44) id AA18942; Wed, 14 Jan 87 16:15:52 PST Received: by sdchemf.chem.ucsd.arpa (4.12) id AA22673; Wed, 14 Jan 87 16:14:00 pst Date: Wed, 14 Jan 87 16:14:00 pst From: sd%chem@sdcsvax.ucsd.edu (Steve Dempsey) Message-Id: <8701150014.AA22673@sdchemf.chem.ucsd.arpa> To: info-iris@sumex-aim.stanford.edu Subject: tty input bugs in the 3.5 kernel I've found a couple of bugs with tty input in the 3.5 kernel. We are running the standard TCP/IP kernel on a 2400 Turbo (ser. #547). I've included a couple of simple test programs which demonstrate the problems. These programs run correctly on a VAX 750 (4.3BSD) and a Celerity 1260D (4.2BSD). I've reported these problems to the HOTLINE. The console, a direct connect terminal, and remote network terminals all exhibit the same behavior. ------------------------- first cut here-------------------------- /* * This test monitors the count returned by the FIONREAD ioctl. * Note that the count changes as you enter or delete characters. * This seems to indicate that the count is for the RAW input queue. * * Previous SGI systems (and all other UNIX based machines we have) * return the count for the CANONICAL input queue ****! * * The problem this creates occurs whe you are polling for tty input * and the user enters a line containing only a newline character. * The count for the raw queue goes to 1, but since the newline is the * end-of-line character it is moved almost immediately from the raw queue * to the canonical queue, so the count for the raw queue goes back to zero. * If the ioctl does not occur during the very short period while the newline * is still in the raw queue you will never know the newline was entered. */ #include #include main() { int lastcnt, ccnt; int readline(); lastcnt = 1000000; while(1) { ioctl(0, FIONREAD, &ccnt); if(ccnt != lastcnt) { printf("ioctl reports %d chars in input.\n", ccnt); lastcnt = ccnt; } sleep(1); } } ------------------------------------cut again here ---------------------- /* * This test shows the incorrect behavior of a read of tty input. * While the program is sleeping enter multiple lines of text. * When the read is executed all lines are read, not just the first one. */ #include main() { int nc; char lbuf[100]; sleep(10); nc = read(0, lbuf, sizeof lbuf); lbuf[nc] = 0; printf("nc=%d, read=%s", nc, lbuf); } -------------------------- last cut here ----------------------------------- 16-Jan-87 09:37:05-PST,863;000000000000 Return-Path: Received: from WISCVM.WISC.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Fri 16 Jan 87 09:36:15-PST Received: from (MAILER)UNBMVS1.BITNET by WISCVM.WISC.EDU on 01/16/87 at 11:35:52 CST Date: 16 Jan 87 13:30:53 AST To: Info-Iris@SUMEX-AIM.ARPA Subject: NTSC Encoders. From: MIKEMAC%UNBMVS1.BITNET@WISCVM.WISC.EDU Message-ID: We are looking for a reasonably good but cheap NTSC encoder for an IRIS2400 Does anyone know of a good one, one to stay away from? Where to get one? Approx cost? Suppliers in Canada perferred. Michael MacDonald Software Specialist, School of Computer Science University of New Brunswick Po. Box 4400 Fredericton, New Brunswick CANADA E3B 5A3 (506) 453-4566 Netnorth/BITNET: MIKEMAC @ UNBMVS1 16-Jan-87 14:21:16-PST,713;000000000000 Return-Path: Received: from orville.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Fri 16 Jan 87 14:19:24-PST Received: Fri, 16 Jan 87 14:12:24 PST by orville.arpa (5.51/1.2) Message-Id: <8701162212.AA04217@orville.arpa> To: michael zyda Cc: info-iris@sumex-aim.stanford.edu Cc: creon@orville.arpa Subject: Re: BSP Hidden Surface Algorithm In-Reply-To: Your message of Mon, 12 Jan 87 12:30:16 pst. <8701122030.AA01259@nps-cs> Date: 16 Jan 87 14:12:23 PST (Fri) From: creon@orville.arpa Yes, someone at SGI has done a BSP demo. His name is Kieth Seeto (at least that's how his name is pronounced, I'm not sure about the spelling). ---------- 16-Jan-87 15:44:48-PST,941;000000000000 Mail-From: ALTMAN created at 16-Jan-87 15:42:57 Date: Fri 16 Jan 87 15:42:52-PST From: Russ Altman Subject: 3d-Grid Code To: info-iris@SUMEX-AIM.STANFORD.EDU cc: altman@SUMEX-AIM.STANFORD.EDU Message-ID: <12271481808.27.ALTMAN@SUMEX-AIM.STANFORD.EDU> Does anyone have any code for manipulating (marking, unmarking) boxes in a 3 dimensional grid? I would ideally like to have each grid box contain a bit vector of attributes to switch on/off. One possible implementation of this kind of code might be oct-trees. References or code that runs or could be made to run with straightforward modifications would be much appreciated. My grids will be no bigger than 100 x 100 x 100 and probably more like 50 x 50 x 50. I need at least three attributes/grid box possible. Speed will be important since I am conducting many operations. Thanks, Russ Altman@sumex.stanford.edu ------- 19-Jan-87 13:12:22-PST,716;000000000000 Return-Path: Received: from G.BBN.COM by SUMEX-AIM.STANFORD.EDU with TCP; Mon 19 Jan 87 13:11:52-PST Date: 19 Jan 1987 16:07-EST Sender: MHARRIS@G.BBN.COM Subject: Re: NTSC Encoders. From: MHARRIS@G.BBN.COM To: MIKEMAC%UNBMVS1.BITNET@WISCVM.WISC.EDU Cc: Info-Iris@SUMEX-AIM.STANFORD.EDU, MHarris@G.BBN.COM Message-ID: <[G.BBN.COM]19-Jan-87 16:07:53.MHARRIS> In-Reply-To: Suggest you contact Broadcast Video Systems 40 West Wilmot Street Richmond Hill, Ontario L4B 1H8 CANADA (416) 764-1584 They rep Cox Video equipment, as well as their own, and have very competent sales persons. Good luck. -- Michael Harris 20-Jan-87 16:31:21-PST,3296;000000000000 Return-Path: Received: from utah-cs.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue 20 Jan 87 16:29:32-PST Received: by utah-cs.ARPA (5.31/4.40.2) id AA05673; Tue, 20 Jan 87 17:33:17 MST Received: by utah-gr.ARPA (5.31/4.40.2) id AA23031; Tue, 20 Jan 87 17:33:11 MST Date: Tue, 20 Jan 87 17:33:11 MST From: dietrich%utah-gr@utah-cs.arpa (Frank Dietrich) Message-Id: <8701210033.AA23031@utah-gr.ARPA> To: info-iris@sumex-aim.stanford.edu Subject: IRIS - Universe The IRIS Universe is coming... But we need your help. The IRIS Universe will be a magazine for and by the community of IRIS users. Silicon Graphics has agreed to produce it quarterly and we will be editing it. It will be as good as you will make it. Read on for more details ... GOAL: Create a dialog among users and between users and Silicon Graphics. FORMAT: We plan to have several different columns to include stories, notes, reference info, interviews, round-tables, etc. These are the columnes that we are considering: IDEAS in ACTION: longer articles that highlight the work of particular users (example: "Complex Images That Do Not Eat Up Time. An Adaptive Ray-Tracer With Preview Facilities", "Visual Mathematics as a Research Tool") length: 2-3 pages HI-TECH TIPS: important techniques, shortcuts, software improvements, etc. pointers to Info-IRIS and SGI Bulletin Board. features: scan-line Zbuffering, extracting 3-D data points from spline commands, BSP tree routines, etc. PIXELS in PERSPECTIVE: announcements on a variety of issues around the world. Motto: Anything goes ! IRIS COMMUNITY: info on user & special interest groups. TOOLS - SOFTWARE EXCHANGE: info on availabe software. examples: BRL-CAD package, Utah Raster Tool Kit, etc. INSIDE SGI: people, projects, products. MEDIA REFERENCES: listing of user's conference papers, video productions, etc. that can be made available. IMAGES: Considering the visual nature of our work there should be plenty of interesting images in the IRIS Universe. We are currently working on a scheme of using a run-lenght-encoding standard that will allow us to ship image data via 1/4" cartridge or MAC disks around. Images will be printed together with the text (initially in black&white) on a high-res digital phototypesetter. DATE: The first issue should be out for the User Group meeting in Philadelphia at NCGA in March '87. Your input, your information, your images will help to make the Universe a magazine that shows how innovative the IRIS community is and what is being done today at the borders of knowledge. Personal creativity is encouraged and reports on work-in-progress are welcome. Let us know your ideas and suggestions. Your contributions can start a dynamic process. Best greetings, Frank Dietrich Zsuzsanna Molnar University of Utah Silicon Graphics Inc. Dept. of Communication Techn. Marketing Manager Salt Lake City, UT 84112 2011 Stierlin Rd. (801) 581-5875 Mountain View, CA 94043 dietrich@utah-gr.edu (415) 960-1980 olympus!elvin!zsuzsa@ucbvax.berkeley.edu 21-Jan-87 12:55:50-PST,798;000000000000 Return-Path: Received: from nrtc-gremlin.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Wed 21 Jan 87 12:54:56-PST Received: from nrtc-gremlin by nrtc-gremlin.arpa id a005403; 21 Jan 87 10:40 PST To: Frank Dietrich cc: info-iris@sumex-aim.stanford.EDU, willson@nrtc-gremlin.arpa Subject: Re: IRIS - Universe Date: Wed, 21 Jan 87 10:40:38 -0800 From: Stephen Willson Well, we here at Northrop are very interested in the U of Utah toolkit! What do we do to find out more (short of waiting for the new magazine)? P.S. we have a 3030 machine. Sincerely, Stephen Hunter Willson, Ph.D. N o r t h r o p Research and Technology Center Palos Verdes, CA willson@nrtc.northrop.com 21-Jan-87 12:56:52-PST,870;000000000000 Return-Path: Received: from nrtc-gremlin.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Wed 21 Jan 87 12:55:12-PST Received: from nrtc-gremlin by nrtc-gremlin.arpa id a005412; 21 Jan 87 10:42 PST To: Frank Dietrich cc: info-iris@sumex-aim.stanford.EDU, willson@nrtc-gremlin.arpa Subject: Re: IRIS - Universe Date: Wed, 21 Jan 87 10:42:34 -0800 From: Stephen Willson Regarding this new magazine, I have developed a ``layered user interface'', which sits between the user and a unix process and maps mouse pointing and clicking into standard UNIX command arguments. What procedure would I use to submit this to your magazine? Stephen Hunter Willson, Ph.D. N o r t h r o p Research and Technology Center Palos Verdes, CA willson@nrtc.northrop.com 23-Jan-87 09:46:51-PST,962;000000000000 Return-Path: Received: from ATHENA by SUMEX-AIM.STANFORD.EDU with TCP; Fri 23 Jan 87 09:45:48-PST Received: by ATHENA (5.45/4.7) id AA09645; Fri, 23 Jan 87 12:47:12 EST Received: by APHRODITE (5.45/4.7) id AA04045; Fri, 23 Jan 87 12:46:42 EST Message-Id: <8701231746.AA04045@APHRODITE> To: info-iris@sumex-aim.stanford.edu Subject: GNUEMACS Date: Fri, 23 Jan 87 12:46:35 -0500 From: tbmoore@ATHENA.MIT.EDU I just got GNUEMACS running on an Iris 3030 running 3.4. I had to make some changes to the .h files that are at sumex. I also added a symbol and altered two routines: unexec.c and process.c. I managed to dump emacs, contrary to the CANNOT_DUMP symbol in s-unipl5.0.h. Oh yeah, the arrow keys at the workstation don't work, but I'll probably have to fool with TERMCAP. If anyone would like or can give advice on this, or would like to trade horror stories, send me mail. -Tim Moore (tbmoore@athena.mit.edu) 23-Jan-87 10:00:08-PST,610;000000000000 Mail-From: BRUGGE created at 23-Jan-87 09:59:08 Date: Fri 23 Jan 87 09:59:07-PST From: John Brugge Subject: Re: GNUEMACS To: tbmoore@ATHENA.MIT.EDU cc: info-iris@SUMEX-AIM.STANFORD.EDU In-Reply-To: <8701231746.AA04045@APHRODITE> Message-ID: <12273254240.28.BRUGGE@SUMEX-AIM.STANFORD.EDU> Tim, If you could forward the changes that you needed to make to the GNU Emacs .h files, I can update them here at Sumex so that they don't have to be rediscovered. Were the changes to unexec.c and process.c necessary for it to run, or cosmetic? Thanks, John ------- 4-Feb-87 10:32:44-PST,1410;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed 4 Feb 87 10:30:21-PST Date: Wed 4 Feb 87 10:30:18-PST From: Lloyd La Comb Subject: RGB mode questions To: Info-Iris@SUMEX-AIM.Stanford.EDU cc: lacomb@Sierra.Stanford.EDU Message-ID: <12276405644.33.LACOMB@Sierra.Stanford.EDU> I'm having a problem and I'm hoping that someone out there has already solved. I have three images of the same piece of data and currently display one each to red, green and blue in RGB mode and make a composite picture with each color representing a different pass of the data. All the pictures are the same size but because of the way the data is taken each image may not start at exactely same spot. More precisely, a feature that is at pixel location 10,10 on the green image might be at pixel location 15,9 on the red image. What I want to do is to display one image and to allign the other images with respect to the first. Is the some way that I can grab all the red pixels for instance and shift them as a unit like you can with some frame buffers? I have a 2400T with 32 bit planes and an FPA. Thanks, Lloyd La Comb lacomb@su-sierra.arpa ------- 5-Feb-87 03:54:38-PST,822;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu 5 Feb 87 03:54:00-PST Date: Wed, 4 Feb 87 21:06:48 EST From: Mike Muuss To: Lloyd La Comb cc: Info-Iris@SUMEX-AIM.Stanford.EDU, lacomb@sierra.stanford.EDU Subject: Re: RGB mode questions Message-ID: <8702042106.aa03283@SEM.BRL.ARPA> There is no hardware support for the operation that you desire within the SGI display. The BRL CAD Package contains tools that will permit you to perform the transformations you desire on the individual color planes, and then combine and display the results. Let me know if you want to know how to obtain this software (I think I posted the advertisment a few weeks back) -- it's free. Best, -Mike 5-Feb-87 14:42:16-PST,783;000000000000 Return-Path: <@SRI-NIC.ARPA:zyda@nps-cs.arpa> Received: from SRI-NIC.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu 5 Feb 87 14:40:26-PST Received: from nps-cs.arpa by SRI-NIC.ARPA with TCP; Thu 5 Feb 87 14:04:49-PST Received: by nps-cs.arpa (5.51/5.17) id AA08254; Thu, 5 Feb 87 14:06:43 PST Date: Thu, 5 Feb 87 14:06:43 PST From: zyda@nps-cs.arpa (michael zyda) Message-Id: <8702052206.AA08254@nps-cs.arpa> To: info-iris@sumex-aim.stanford.edu Subject: Enlarging the available swap space on the IRIS... Does anyone have a nice document that describes how one enlargens the swap space on the IRIS? Michael Zyda Naval Postgraduate School Code 52, Dept. of Computer Science Monterey, California 93943-5100 Arpanet: zyda@nps-cs.arpa 6-Feb-87 07:42:44-PST,1291;000000000000 Mail-From: BRUGGE created at 6-Feb-87 07:42:26 Return-Path: Received: from venera.isi.edu by SUMEX-AIM.STANFORD.EDU with TCP; Thu 5 Feb 87 17:55:12-PST Posted-Date: Thu, 05 Feb 87 17:13:50 PST Message-Id: <8702060113.AA05643@venera.isi.edu> Received: from LOCALHOST by venera.isi.edu (5.54/5.51) id AA05643; Thu, 5 Feb 87 17:13:52 PST To: info-iris-request@sumex-aim.stanford.edu Cc: pickard@venera.isi.edu Subject: >30Hz in doublebuffer mode query Date: Thu, 05 Feb 87 17:13:50 PST From: Kelly Pickard ReSent-Date: Fri 6 Feb 87 07:42:26-PST ReSent-From: John Brugge ReSent-To: info-iris@SUMEX-AIM.STANFORD.EDU ReSent-Message-ID: <12276899373.22.BRUGGE@SUMEX-AIM.STANFORD.EDU> Is it possible to muck with some registers or the like to increase the scan rate to about 45Hz? We'd like to limit the amount of flicker seen in a doublebuffer mode using 3D glasses. One thought is to shorten the vertical retrace, meaning that we sacrifice vertical resolution for a faster update rate. Any thoughts or implementation strategies graciously welcomed. Please reply directly . . . Will summarize . . . Thanks, Kelly Pickard ISI, Los Angeles 6-Feb-87 08:52:40-PST,1717;000000000000 Return-Path: Received: from nrl-aic by SUMEX-AIM.STANFORD.EDU with TCP; Fri 6 Feb 87 08:52:00-PST Date: 6 Feb 1987 11:27:43 EST (Fri) From: Russ Smith Subject: flight-dog-shadow-radar-VAX To: info-iris@sumex-aim.ARPA Message-Id: <539627263/smith@nrl-aic> Pardon if these have been asked or answered before... Shortly after the AI Center took delivery of an IRIS some of us were "joking" about an Expert System for Combat Manuevering. Well, the more we thought about it, the more interesting the idea became. As an extracurricular activity, we'd like to try some simple stuff out (to say the least, the problem is nontrivial...). The IRIS provides a nice test bed for trying things out so we would like to interface one or more of the onsite VAXen (or perhaps Symbolics) to the IRIS over an Ethernet (tcp/ip in this case) connection. Since the above SG programs all work over the network when more than one IRIS is present, we were wondering if nonIRIS machines can "join in". In particular, where does one find "how to connect" instructions, data formats, network port, and other information to enable intermachine (or interprocess such as "dog" to "autoACE") communications? We are also VERY interested in using a different machine for another project with an interface to the "robot" program (it seems on cursory examination of the binary (!) to have some network code in it). (1) Does THIS program also interface to a network, and (2), is it possible to do what we want?...(and (3), how do we get SOURCE!?). Any help would be appreciated. Russ JAYCOR Navy Center for Applied Research in Artificial Intelligence (whew!) 6-Feb-87 19:20:34-PST,806;000000000000 Return-Path: Received: from nrtc-gremlin.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Fri 6 Feb 87 19:20:08-PST Received: from nrtc-gremlin by nrtc-gremlin.arpa id a002825; 6 Feb 87 10:37 PST To: info-iris@sumex-aim.stanford.EDU cc: willson@nrtc-gremlin.arpa Subject: TeX previewer Date: Fri, 06 Feb 87 10:36:57 -0800 From: Stephen Willson Did anyone out there successfully obtain the TeX previewer that was advertised some time ago? We've been trying for months without success. Does anyone have any alternative strategies for obtaining it? Thanks in advance. Sincerely, Stephen Hunter Willson, Ph.D. N o r t h r o p Research and Technology Center M.S. 332/T30 Palos Verdes, CA willson@nrtc.northrop.com 9-Feb-87 08:48:02-PST,964;000000000000 Return-Path: Received: from wk18-ec ([128.102.6.40].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Mon 9 Feb 87 08:46:52-PST Received: Mon, 9 Feb 87 08:40:45 PST by wk18-ec (5.15/1.2) Date: Mon, 9 Feb 87 08:40:45 PST From: Dennis C. Jespersen Message-Id: <8702091640.AA14726@wk18-ec> To: info-iris@sumex-aim.stanford.edu Subject: TeX previewer for IRIS Cc: willson@nrtc-gremlin.arpa This is for Stephen Willson. Creon Levit asked me to handle this, as he is out of the country. We use a TeX previewer for the IRIS workstation written by Tomas Rokicki. To the best of my knowledge, this previewer is available through n^2 Computer Consultants (P.O. Box 2736, College Station TX 77841 -- this is the address given in the latest TUGboat). We also use a C implementation of TeX due to Rokicki. Presumably this is also available from n^2. Does this help? --Dennis Jesperse eul%jespersen@ames-io.arpa 10-Feb-87 14:10:42-PST,997;000000000000 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue 10 Feb 87 14:09:32-PST Received: from EUL by IO with VMS ; Tue, 10 Feb 87 13:36:17 PST Date: Tue, 10 Feb 87 13:36:17 PST From: JESPERSEN%EUL@ames-io.ARPA Subject: Stephen Willson's request for IRIS-TeX previewer info To: info-iris@sumex-aim.stanford.edu This is for Stephen Willson. Creon Levit asked me to handle this as he is out of the country. At NASA Ames we have a TeX previewer for the IRIS; it was written by Tomas Rokicki. I believe the previewer is available from Norman Naugle n^2 Computer Consultants P.O. Box 2736 College Station TX 77841 (this address information copied from the latest issue of TUGboat). We are also using a C implementation of TeX, again from Rokicki. I presume that is also available, from the same address. Hope this helps some. --Dennis Jespersen eul%jespersen@ames-io.arpa 13-Feb-87 10:03:43-PST,1528;000000000000 Return-Path: Received: from nps-cs.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Fri 13 Feb 87 10:03:01-PST Received: by nps-cs.arpa (5.51/5.17) id AA14357; Fri, 13 Feb 87 10:01:44 PST Date: Fri, 13 Feb 87 10:01:44 PST From: zyda@nps-cs.arpa (michael zyda) Message-Id: <8702131801.AA14357@nps-cs.arpa> To: info-iris@sumex-aim.stanford.edu Subject: FTP and RCP Problems with BSD 4.3 We just changed our VAX from Berkeley 4.2 Unix to Berkeley 4.3 Unix. We did this to fix our mailer (so that it puts on the domain addressing piece). I now have a problem with FTP between that Vax and my Turbo IRIS. I can get files from the IRIS to the Vax. I cannot always get files from the Vax to the IRIS. The symptoms of this problem are very strange. Long files sent from the Vax to the IRIS (6000 bytes) are sent correctly. Short files (3500 bytes) are sent incorrectly. FTP reports that it sent the first 2048 bytes and then stops the transfer. On the IRIS, some 1987 bytes are actually received (or approximately the first 61 line of the file). This happens for all files about 3500 bytes in length. We are running release 3.4 on our Turbo. Has anyone got a fix for this problem? I can transfer files from my Vax 11/785 (4.3 BSD) to my Vax 11/750 (4.2 BSD) and then to the IRIS correctly. Michael Zyda Naval Postgraduate School Code 52, Dept. of Computer Science Monterey, California 94943-5100 (408) 646-2305 Arpanet: zyda@nps-cs.arpa 13-Feb-87 10:46:05-PST,932;000000000000 Return-Path: Received: from nps-cs.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Fri 13 Feb 87 10:44:40-PST Received: by nps-cs.arpa (5.51/5.17) id AA14640; Fri, 13 Feb 87 10:14:41 PST Date: Fri, 13 Feb 87 10:14:41 PST From: zyda@nps-cs.arpa (michael zyda) Message-Id: <8702131814.AA14640@nps-cs.arpa> To: info-iris@sumex-aim.stanford.edu Subject: Videodisks and the IRIS... Has anyone put together a Videodisk recording system on an IRIS? I am thinking of recording animations from the IRIS that do not run in real-time. I either need a single step Videotape unit and controller or some type of videodisk and single step controller. I know the selection for Videotape (Lyon/Lamb...) but am interested in anyone with Videodisk experience. Michael Zyda Naval Postgraduate School, Code 52, Dept. of Computer Science Monterey, Cliafornia 93943-5100 (408) 646-2305 19-Feb-87 14:10:09-PST,434;000000000000 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu 19 Feb 87 14:09:15-PST Received: from PLU by IO with VMS ; Thu, 19 Feb 87 14:00:22 PST Date: Thu, 19 Feb 87 14:00:22 PST From: SPIRKOV%PLU@ames-io.ARPA Subject: please add me to the mailing list To: info-iris@sumex-aim.stanford.edu thank you. Lilly Spirkovska (spirkov@ames-pluto.arpa) 19-Feb-87 22:23:07-PST,1051;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu 19 Feb 87 22:22:34-PST Date: Thu, 19 Feb 87 19:28:21 EST From: Mike Muuss To: michael zyda cc: info-iris@sumex-aim.stanford.EDU Subject: Re: FTP and RCP Problems with BSD 4.3 Message-ID: <8702191928.aa19572@SEM.BRL.ARPA> The problem is actually with the poor TCP implementation in the Excelan boards. SGI 3.4 depends on the outboard Excelan TCP. 4.2 was more tolerant about dealing with this brokenness, but we found that SGI 3.4's TCP also has failure modes. I'm happy to report that SGI's 3.5 release, which incorporates the Berkeley TCP, fixes these problems, and gives much better network performance as well. You might also check to see if your 4.3 machine has the "vital three" bug fixes installed -- they were widely distributed on the net in various UNIX mailing lists and news groups, and correct some serious flaws in the vanilla 4.3 TCP. Best, -Mike 23-Feb-87 18:03:19-PST,1735;000000000000 Return-Path: Received: from utah-cs.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon 23 Feb 87 18:02:18-PST Received: by utah-cs.ARPA (5.31/4.40.2) id AA08876; Mon, 23 Feb 87 18:16:20 MST Received: by utah-gr.ARPA (5.31/4.40.2) id AA17556; Mon, 23 Feb 87 18:16:18 MST Date: Mon, 23 Feb 87 18:16:18 MST From: dietrich%utah-gr@utah-cs.arpa (Frank Dietrich) Message-Id: <8702240116.AA17556@utah-gr.ARPA> To: info-iris@sumex-aim.stanford.edu Subject: Last Call for Universe This is the last call for submitting material to the premier issue of the IRIS Universe. It will feature articles on Visual Mathematics, and on ALPHA_1: Non-uniform, Rational Modelling. Other topics are: Fluid-Dynamics Simulation, BSP Tree Algorithm, and IRIS interaction at SIG-CHI in Toronto. We will tune-in to the SGI Bulletin Board and the network, and cover a number of substantial software packages that have been announced recently: BRL-CAD Modelling & Ray-Tracing, The Utah Raster ToolKit, and the GNU Editing Environment. Please let me know of any written or visual referrence material of your recent activities. Anecdotes, brief notes, and images are very welcome. Absolute deadline is March 6. Then the Universe will go to press. The next issues will cover: The Supercomputer Connection. New Approaches in CG Education, High-Quality Hardcopy & Videorecording. Keep the dynamics going and cooperate on a fine publication. And keep your eyes open for the first issue in your mail. Frank Dietrich University of Utah Dept. of Communication Salt Lake City, UT 84112 (801) 581-5875 4-Mar-87 16:02:53-PST,1336;000000000000 Mail-From: BRUGGE created at 4-Mar-87 16:01:50 Return-Path: Received: from bu-cs.bu.edu by SUMEX-AIM.STANFORD.EDU with TCP; Wed 4 Mar 87 15:58:14-PST Received: from bucasb (bucasb.bu.edu) by bu-cs.bu.edu (3.2/4.7) id AA01294; Wed, 4 Mar 87 18:58:53 EST Return-Path: Received: by bucasb (4.12/4.7) id AA01137; Wed, 4 Mar 87 18:40:54 est Date: Wed, 4 Mar 87 18:40:54 est From: mike@bucasb.BU.EDU (Michael Cohen) Message-Id: <8703042340.AA01137@bucasb> To: info-iris-request@sumex-aim.ARPA Subject: FTP/Telnet,NFS between BSD4.2 workstation and Iris Organization: Boston U., Center for Adaptive Systems Cc: mike ReSent-Date: Wed 4 Mar 87 16:01:47-PST ReSent-From: John Brugge ReSent-To: info-iris@SUMEX-AIM.STANFORD.EDU ReSent-Message-ID: <12283806022.47.BRUGGE@SUMEX-AIM.STANFORD.EDU> Is there any problems/difficulties is doing ftp/telnet/rlogin between a BSD4.2 (In our case a Celerity 1260D) and Silicon Graphics Iris workstations. What difficulties if any is their porting code to the workstation from a standard BSD4.2 system. Please CC to me as I am not a member of the list. My Email address is mike@bucasb.bu.edu Thanks much in advance. -- Michael Cohen ---- Center for Adaptive Systems Boston University (617-353-7857) 4-Mar-87 16:45:35-PST,927;000000000000 Return-Path: Received: from bu-cs.bu.edu by SUMEX-AIM.STANFORD.EDU with TCP; Wed 4 Mar 87 16:44:49-PST Received: from bucasb (bucasb.bu.edu) by bu-cs.bu.edu (3.2/4.7) id AA02354; Wed, 4 Mar 87 19:46:02 EST Return-Path: Received: by bucasb (4.12/4.7) id AA01498; Wed, 4 Mar 87 19:28:02 est Date: Wed, 4 Mar 87 19:28:02 est From: mike@bucasb.BU.EDU (Michael Cohen) Message-Id: <8703050028.AA01498@bucasb> To: info-iris@sumex-aim.ARPA Subject: Iris 3130 Reliability Organization: Boston U., Center for Adaptive Systems Cc: mike I would like any information you may have on Silicon Graphics Iris reliability especially the 3130 which we are thinking of purchasing. Please post directly to me as I am not a member of your list. Thanks much. My email address is mike@bucasb.bu.edu. -- Michael Cohen ---- Center for Adaptive Systems Boston University (617-353-7857) 4-Mar-87 17:06:15-PST,1030;000000000000 Mail-From: BRUGGE created at 4-Mar-87 17:05:41 Date: Wed 4 Mar 87 17:05:40-PST From: John Brugge Subject: Re: Iris 3130 Reliability To: mike@BUCASB.BU.EDU cc: info-iris@SUMEX-AIM.STANFORD.EDU In-Reply-To: <8703050028.AA01498@bucasb> Message-ID: <12283817650.47.BRUGGE@SUMEX-AIM.STANFORD.EDU> I don't have any numbers on failure rates or most-common-problems, but can say that in the 8 months that we have had our 3030 we have had few hardware problems; primarily a bad optical mouse that was promptly replaced, and a cartridge tape drive that will occasionally hang the system (still not sure why). So far we've escaped major catastrophies (such as a disk crash), and the minor ones haven't held us up. As for the *software* reliability, that's another question, but I haven't seen the latest release of the system to see how much has been fixed. Overall, ours has been a pretty reliable system (but still worthy of a service contract, just to be sure). John ------- 5-Mar-87 10:33:29-PST,1657;000000000000 Mail-From: BRUGGE created at 5-Mar-87 10:32:36 Return-Path: Received: from bu-cs.bu.edu by SUMEX-AIM.STANFORD.EDU with TCP; Thu 5 Mar 87 06:11:28-PST Received: from bucasb (bucasb.bu.edu) by bu-cs.bu.edu (3.2/4.7) id AA12746; Thu, 5 Mar 87 09:12:55 EST Return-Path: Received: by bucasb (4.12/4.7) id AA02691; Thu, 5 Mar 87 09:13:27 est Date: Thu, 5 Mar 87 09:13:27 est From: rasesh@bucasb.BU.EDU (Rasesh Trivedi) Message-Id: <8703051413.AA02691@bucasb> To: Info-Iris-Request@SUMEX-AIM.Stanford.edu Subject: Info. for Iris and 4.2BSD Compitability ReSent-Date: Thu 5 Mar 87 10:32:35-PST ReSent-From: John Brugge ReSent-To: info-iris@SUMEX-AIM.STANFORD.EDU ReSent-Message-ID: <12284008237.65.BRUGGE@SUMEX-AIM.STANFORD.EDU> We are planning to buy new workstation Iris 3010 based on system V. Our major concerns are following. 1. Transferring files to Iris from our 4.2BSD based Celerity System. 2. ftp utility from Iris to other 4.2 system. I heard about some bugs in ftp utility for Iris. 3. nfs support on Iris. Can nfs mount the filesystems on Iris from other 4.2 systems. Basically we have to put Iris on Ethernet TCP/IP protocol. 4. Any problems with mail systems. 5. The key point about the reliability of Iris system. From the net I read certain responces which gives more concern about service contract and maintainance cost of this workstation. Any one had any serious problems? Please respond to me if you can be of any help giving some information. We have to take decision in next week or so. Thanks. -Rasesh 6-Mar-87 08:58:03-PST,987;000000000000 Return-Path: Received: from IUS2.CS.CMU.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Fri 6 Mar 87 08:57:24-PST Date: 6 Mar 1987 11:47-EST From: Ralph.Hyre@ius2.cs.cmu.edu To: info-iris@sumex-aim Subject: Semaphores on the IRIS Message-Id: <542047672/ralphw@ius2.cs.cmu.edu> Does anybody have any information? We're running a 3.4 kernel with the TCP option. Date: 26 Feb 1987 19:06-EST From: Carlo.Tomasi@ius1.cs.cmu.edu To: ralphw@ius2 Subject: semaphores on the IRIS I'm trying to use semaphores on the IRIS (as described in the semctl(2), semget(2) and semop(2) manual entries); unfortunately, trying to get a semaphore identifier, I get an ENOSPC error ("No space left on device"). Trying to find out what is wrong, I issued the ipcs (interprocess communication facilities status) command, but the reply was "No memory file". Can the problem be solved by setting something to its proper value, or is it hopeless? Thanks Carlo 9-Mar-87 19:05:52-PST,2537;000000000000 Return-Path: Received: from cu-arpa.cs.cornell.edu by SUMEX-AIM.STANFORD.EDU with TCP; Mon 9 Mar 87 19:04:30-PST Received: by cu-arpa.cs.cornell.edu (5.54/4.30) id AA01312; Mon, 9 Mar 87 21:25:28 EST Date: Mon, 9 Mar 87 21:25:22 EST From: garry@tcgould.tn.cornell.edu (Garry Wiegand) Received: by tcgould.TN.CORNELL.EDU (5.52/1.1nn-Cornell-Theory-Center) id AA02495; Mon, 9 Mar 87 21:25:22 EST Message-Id: <8703100225.AA02495@tcgould.TN.CORNELL.EDU> To: info-iris@sumex-aim.stanford.edu Subject: Hoops announcement {2nd try at posting; the first vanished. Please excuse duplications.} ** Graphics Product Announcement ** In keeping with network etiquette, I will try to make this as brief and to-the- point as possible. Apologies in advance to anyone who may be offended (but I hope no one is!) What we have is a beast called "Hoops". Hoops is a large, 2-D/3-D, general- purpose display-list graphics subroutine library. Hoops deals with such things as lines, polygons, text, windows, colors, and cameras. It is designed to run on on many machines and many displays, and its basic purpose is to make your life easier when you sit down to write a graphics application. We've put a lot of effort into: 1) a clean design, 2) speedy program execution, and 3) keeping it cheap! Software completed: C language binding Fortran language binding Support for X-Windows (tested on Ultrix microVax/GPX's) Support for the microVax/GPX running VMS Support for the Parallax 1280 on microVax's running VMS Support for Postscript laser printers, including the Apple In progress: Pascal language binding Support for the Silicon Graphics Iris workstation Support for the Sun 3 workstation Support for the IBM 5080 on IBM mainframes Support for the Number Nine "Pro1280" on IBM PC/AT's Support for the Pixelworks "ClipperBoard" on IBM PC/AT's Commercial licenses are moderately priced, with large discounts for volume purchases. University licenses are generally priced at 25% of commercial licenses; university license fees may, under some conditions, be waived entirely. Source code is available; demo copies are available. For further information, call: Gary Wayne Flying Moose Systems & Graphics (607) 273-3690 // The Clinton House // Ithaca, New York 14850 Or send your post-office address to me. Thanks for listening - Garry Wiegand (c/o garry@oak.cadif.cornell.edu) 11-Mar-87 15:30:17-PST,895;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed 11 Mar 87 15:28:32-PST Date: Wed 11 Mar 87 15:28:50-PST From: Lloyd La Comb Subject: sendmail on 3.5 To: Info-Iris@SUMEX-AIM.Stanford.EDU cc: lacomb@Sierra.Stanford.EDU Message-ID: <12285635031.51.LACOMB@Sierra.Stanford.EDU> Has anyone out there tried to get the 3.5 network mailer sendmail to work. Here at Stanford we have a network with over 200 hosts on it. I'm trying to "asjust" my sendmail.cf file to be able to send mail with anyone on campus and users on the arpanet. Everyone on campus talks TCP and STMP or SMTP whichever one it is so it seemed like any easy job but that was over a week ago. Thanks. Lloyd LaComb lacomb@su-sierra.arpa ------- 16-Mar-87 17:14:33-PST,1373;000000000000 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon 16 Mar 87 17:13:58-PST Received: from PLU by IO with VMS ; Mon, 16 Mar 87 17:10:30 PST Date: Mon, 16 Mar 87 17:10:30 PST From: SPIRKOV%PLU@ames-io.ARPA Subject: peripheral recommendations? To: info-iris@sumex-aim.stanford.edu hi. i'm trying to set up a graphics lab at the AI division at NASA Ames & i've got a bunch of questions! i just finished reading the backlog of info-iris & didn't find answers to all of them, so here it goes. so that i don't overwhelm people with all of them at once, i'll ask only about hardware. i'd really appreciate any & ALL information i can get. can anyone recommend (or warn me about) digitizers movie cameras (like the Dunn) video animation systems (like the Lyon&Lamb) laser printers (is there a pub domain driver for postscript printers?) color hardcopiers/plotters (differences? is a hardcopier better or a plotter?) terminals (graphics) if you know a lot (or not a lot but something) about any of the above, would you mind if i asked you more detailed questions? and no, i don't mean become a pest. like i said, i'd appreciate all the information i can get! thanks a lot! Lilly ps: i have a 3130, if that makes a difference. 18-Mar-87 17:06:18-PST,794;000000000000 Return-Path: Received: from venera.isi.edu by SUMEX-AIM.STANFORD.EDU with TCP; Wed 18 Mar 87 17:05:45-PST Posted-Date: Wed, 18 Mar 87 17:06:19 PST Message-Id: <8703190106.AA25781@venera.isi.edu> Received: from LOCALHOST by venera.isi.edu (5.54/5.51) id AA25781; Wed, 18 Mar 87 17:06:21 PST To: info-iris@sumex-aim.stanford.edu Cc: pickard@venera.isi.edu Subject: CEMACS Terminfo Entry Date: Wed, 18 Mar 87 17:06:19 PST From: Kelly Pickard Hello, I'm looking for the CEMACS Terminfo Entry for our IRIS 3030. I checked thru the back issues of info-iris and found no mention of it. Anybody out there written one? Thanks, Kelly Pickard USC/ISI Marina del Rey, CA (213) 822-1511, x120 31-Mar-87 01:25:25-PST,1143;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Tue 31 Mar 87 01:25:02-PST Received: by lindy.STANFORD.EDU; Tue, 31 Mar 87 01:26:04 PST Date: Tue, 31 Mar 87 01:27:03 PST From: To: info-iris@sumex-aim.stanford.edu Subject: VT-100 Emulator for the IRIS 31xx console Terminal Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 31 Mar 87 11:19:02 Date: Tue, 31 Mar 87 11:15:16 +0200 (Central European Sommer Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: VT-100 Emulator for the IRIS 31xx console Terminal To: info-iris@sumex-aim.stanford.edu X-VMS-To: X%"info-iris@sumex-aim.stanford.edu",D96D Hallo, we are looking for an VT-100 emulator for the IRIS 31xx console terminal (wsiris). It should be inexpensive (PD) and obtainable over the net (incl. sources). Can anybody help us? Regards Martin Knoblauch TH-Darmstadt, Phys. Chem. I Petersenstrasse 20 D-6100 Darmstadt, F.R.G. 31-Mar-87 09:59:55-PST,926;000000000000 Return-Path: Received: from hera.CS.UCLA.EDU ([128.97.2.20].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Tue 31 Mar 87 09:58:53-PST Received: by hera.CS.UCLA.EDU (Sendmail 5.54/5.14) id AA25825; Tue, 31 Mar 87 09:57:42 PST Message-Id: <8703311757.AA25825@hera.CS.UCLA.EDU> To: info-iris@SUMEX-AIM.STANFORD.EDU Cc: trainor@CS.UCLA.EDU Reply-To: trainor@CS.UCLA.EDU Subject: Any Iris code out there??? Date: Tue, 31 Mar 87 09:57:40 PST From: Vulture of Light Hello, I am interested in collecting a bunch of self-contained demoish programs that will run on our Iris 1400. They can range from absolute junky code to slick demos -- I don't care. Their purpose is to help independent students to learn-by-example on the Iris. Appreciably, Douglas PS: One person asked about code for doing menus, and the status of SGI's Rubik's cube program. 31-Mar-87 11:15:06-PST,1139;000000000000 Mail-From: BRUGGE created at 31-Mar-87 11:14:35 Date: Tue 31 Mar 87 11:14:33-PST From: John Brugge Subject: Re: Any Iris code out there??? To: trainor@CS.UCLA.EDU cc: info-iris@SUMEX-AIM.STANFORD.EDU In-Reply-To: <8703311757.AA25825@hera.CS.UCLA.EDU> Message-ID: <12290831620.40.BRUGGE@SUMEX-AIM.STANFORD.EDU> The latest system release from SGI contains what a tutorial package for programming the IRIS. It includes a book that leads you through some of the basics, from drawing to transformations, to user-interaction, with source code for the examples included (hardcopy and on the distribution tape). It also encourages you to experiment as you go through the lessons. I imagine the code should work on a 1400, but I don't know. And since the code is distributed in /usr/people/gifts, it shouldn't cost anything to get it (or maybe that just means that it's not supported). You might contact SGI about it. I haven't used the package yet, but I believe it has a short section on the window manager and menus; not alot, but enough to get you started. Good luck, John ------- 31-Mar-87 14:49:45-PST,528;000000000000 Return-Path: Received: from nps-cs.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Tue 31 Mar 87 14:49:11-PST Received: by nps-cs.arpa (5.51/5.17) id AA19426; Tue, 31 Mar 87 14:46:17 PST Date: Tue, 31 Mar 87 14:46:17 PST From: zyda@nps-cs.arpa (michael zyda) Message-Id: <8703312246.AA19426@nps-cs.arpa> To: info-iris@sumex-aim.stanford.edu Subject: ADA on the IRIS? Are there any versions of ADA running on the IRIS available that anyone knows about ? Michael Zyda (408) 646-2305 31-Mar-87 16:59:23-PST,632;000000000000 Return-Path: Received: from orville.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Tue 31 Mar 87 16:58:53-PST Received: Tue, 31 Mar 87 16:58:58 PST by orville.arpa (5.51/1.2) Message-Id: <8704010058.AA12719@orville.arpa> To: zyda@nps-cs.arpa (michael zyda) Cc: info-iris@sumex-aim.stanford.edu Subject: Re: ADA on the IRIS? In-Reply-To: Your message of Tue, 31 Mar 87 14:46:17 PST. <8703312246.AA19426@nps-cs.arpa> Date: 31 Mar 87 16:58:56 PST (Tue) From: creon@orville.arpa Mike, SGI has ADA (done by Vertex, I believe), as a $10,000 option. Contact your SGI sales rep. --creon 3-Apr-87 15:21:10-PST,627;000000000000 Return-Path: Received: from braggvax.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Fri 3 Apr 87 15:20:10-PST Message-Id: <8704032319.AA06961@braggvax.arpa> To: Info-Iris@SUMEX-AIM.Stanford.edu Subject: Golf demo program for Iris 3020 Date: Fri, 03 Apr 87 18:19:39 EST From: sigcen@braggvax.arpa I am looking for a "golf demo" program for an Iris 3020. The graphics and number crunching features of this machine would make a great platform for such a program. Has anyone written something along these lines ? Thanks (Mr.) Tracy Wood 404-791-3782 sigcen@braggvax 6-Apr-87 09:59:27-PDT,625;000000000000 Mail-From: BRUGGE created at 6-Apr-87 09:58:41 Date: Mon 6 Apr 87 09:58:40-PDT From: John Brugge Subject: Administrivia To: info-iris@SUMEX-AIM.STANFORD.EDU Message-ID: <12292379748.47.BRUGGE@SUMEX-AIM.STANFORD.EDU> As of this morning, the NIC at SRI has a new HOSTS.TXT host table file which no longer includes most host nicnames. Since this file is used by many hosts to resolve host names, mail sent to Info-Iris and Info-Iris-Request should use the full name of this host, Sumex-AIM.Stanford.Edu (case is not significant) to avoid being lost or returned. John ------- 6-Apr-87 11:13:33-PDT,998;000000000000 Return-Path: Received: from venera.isi.edu by SUMEX-AIM.STANFORD.EDU with TCP; Mon 6 Apr 87 11:12:15-PDT Posted-Date: Mon, 06 Apr 87 10:47:19 PDT Message-Id: <8704061747.AA13493@venera.isi.edu> Received: from LOCALHOST by venera.isi.edu (5.54/5.51) id AA13493; Mon, 6 Apr 87 10:47:29 PDT To: info-iris@sumex-aim.stanford.edu Cc: pickard@venera.isi.edu Subject: Bitmap to 3D fonts Date: Mon, 06 Apr 87 10:47:19 PDT From: Kelly Pickard Just wondering . . . Has anyone written a program to convert Mike Zyda's IRIS fonts to a 3D format, i.e., splines, polf(), etc. If not, how about this: does anyone have experience implementing Maureen Stone's 1983 SIGGRAPH paper, "Curve-Fitting with Piecewise Parametric Cubics"? 'Seems like a plausible solution. Finally, any comments on internal font representation are welcome. Regards, Kelly USC/ISI Marina del Rey, CA 7-Apr-87 07:35:06-PDT,236;000000000000 Return-Path: Received: from nswc-g.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue 7 Apr 87 07:34:45-PDT Date: Tue, 7 Apr 87 10:35:19 est From: sking@nswc-g.ARPA To: info-iris@sumex-aim.stanford.edu < intromail 7-Apr-87 08:23:57-PDT,1152;000000000000 Return-Path: Received: from nswc-g.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue 7 Apr 87 08:23:14-PDT Full-Name: Date: Tue, 7 Apr 87 10:39:48 est From: sking@nswc-g.ARPA To: info-iris@sumex-aim.stanford.edu Hi there fellow IRIS users! We are NSWC in Dahlgren, Virginia. We have been working with an IRIS 3030 for a little over a year. Our work is centered around the display of the trajectory (flight path) of missiles. We have some questions and hope that someone out there has some answers! 1) We have a TEKTRONIX 4662 ink pen plotter. We would like to have software that converts IRIS primitives into commands that the plotter can recognize. Has anyone done this or have any information on it at all? 2) We also have the RS170A option and have been told we need the NTSC option in order to connect a VCR to record the monitor image. Has anyone done this or have any information on how to do this? 3) Does anyone have any software that displays a simple Mercator Cartesian map of the world? Information about any of these items would be greatly appreciated. 7-Apr-87 17:45:22-PDT,1746;000000000000 Return-Path: Received: from aplvax.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Tue 7 Apr 87 17:44:12-PDT Received: by aplvax.arpa (5.51/1.14) id AA15461; Tue, 7 Apr 87 19:43:07 EST Date: Tue, 7 Apr 87 19:43:07 EST From: marc@aplvax.arpa (Marcus H. Gates) Message-Id: <8704080043.AA15461@aplvax.arpa> To: info-iris@sumex-aim.stanford.edu Subject: running 2.5 on 2300's We are currently running 1 2400T, 2 2400 and 3 2300 Iris machines. Recently SGI came out with new software releases (3.5 for the 2400T, 2.5 for the 2400) which among other things included tcp/ip in the kernel. (There is a bug in the mkboot program as distributed on the 2.5 release, it incorrectly computes the number of blocks for dd to use in copying the boot filesystem to tape. I have reported the bug (and fix) to Ron Ludwig on the hotline). I asked our local SG sales/support people about upgrading the 2300's as well in order to keep all systems compatible and was told that there were no plans to have any 2.5 upgrade package for the 2300's. I have just completed upgrading the 2300's myself and now have 5 2400's (3 with small disks) and everything appears to be working fine. As with the past 2300's there is a subset of the commands in /bin and /usr/bin in order to conserve disk space. I am partly posting this in response to a recent posting from this group which I can't find anywhere. NOTE: creon@ames, I have tried sending you mail requesting info in your remote-graphics library using the new tcp/ip. If you read this please send me information on how I might get the above-mentioned software. Thanks. marc gates johns hopkins applied physics lab laurel, md marc@aplvax.arpa 8-Apr-87 00:45:22-PDT,1649;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed 8 Apr 87 00:44:55-PDT Date: Wed, 8 Apr 87 3:36:44 EDT From: Mike Muuss To: info-iris@sumex-aim.stanford.EDU cc: Dietrich@utah-gr.arpa, olympus!elvin!zsuzsa@berkeley.EDU Subject: MEX Wishes Message-ID: <8704080336.aa25151@SEM.BRL.ARPA> There are several things I wish I could do in MEX that I have become quite used to in SUNTOOLS. None should be difficult, but I don't have the inclination to attempt to modify MEX. *) Screen lock. On the main menu, run some program that locks the screen/keyboard until the user's login password is corectly entered. Playing the game of life as the idle loop is optional. *) "Close" window. When not using a window, turn it into an icon which can be moved to the corner of the screen for later. *) ".mexrc" extention to allow specification of initial window placements and an optional command to run (if not $SHELL). *) Ability to extend main MEX menu to allow direct startup of programs other than $SHELL. For example, rlogin. *) It should be possible to specify a mode of operation where input is entered into the window that contains the cursor, without having to click the mouse. This issue borders on the religious -- how about supporting both, and letting each user choose? I'd be interested in knowing what SGI's plans for MEX are (in general terms, anyways). Are we likely to see any level of support for X from SGI (I realize that at least until X version 11, X and the SGI are not the best match)? Best, -Mike 8-Apr-87 02:16:58-PDT,564;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed 8 Apr 87 02:16:10-PDT Date: Wed, 8 Apr 87 5:15:09 EDT From: Mike Muuss To: Kelly Pickard cc: info-iris@sumex-aim.stanford.EDU, pickard@venera.isi.EDU Subject: Re: Bitmap to 3D fonts Message-ID: <8704080515.aa26441@SEM.BRL.ARPA> I'd be interested in seeing 3-D fonts. I'd be even more interested in seeing 3-D fonts that were in a format that made them easy to ray-trace. Best, -Mike 8-Apr-87 04:38:14-PDT,401;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed 8 Apr 87 04:37:52-PDT Date: Wed, 8 Apr 87 5:16:07 EDT From: Mike Muuss To: info-iris@sumex-aim.stanford.EDU Subject: More MEX Exposures Message-ID: <8704080516.aa26487@SEM.BRL.ARPA> It would also be nice if MEX knew how to cut-and-paste between windows. -Mike 8-Apr-87 04:40:53-PDT,1864;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed 8 Apr 87 04:40:26-PDT Received: by lindy.STANFORD.EDU; Wed, 8 Apr 87 04:41:14 PST Date: Wed, 8 Apr 87 04:41:58 PST From: To: info-iris@sumex-aim.stanford.edu Subject: TCP/IP Kermit or FTP required. Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 08 Apr 87 13:29:03 Date: Wed, 8 Apr 87 13:23:46 +0200 (Central European Summer Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: TCP/IP Kermit or FTP required. To: info-iris@sumex-aim.stanford.edu X-VMS-To: X%"info-vax@sri-kl.arpa",X%"info-kermit@cu20b.columbia.edu",X%"info-ir is@sumex-aim.stanford.edu" Hallo Networld, we have a [small] communication problem. We have 2 (3) Silicon Graphics IRIS 31xx workstation connected with TCP/IP on an ethernet. On the net is also an Micom/Interlan NTS/TCP terminal-server. Connected to this server are several VAX-RS232 ports. We can now use TELNET on the IRIS to connect to the server-ports and then login to the VAX. But if we want to do file transfer, the problem arises. We either need an UNIX C-Kermit with an TELNET-protocol driver instead of the serial driver, or we need an VAX/VMS FTP-protocol Program that works via an serial line (which is connected to the terminal server, which we can reach via FTP). This program should be written in FORTRAN or C. It also should be public-domain and available on the net. Can anybody help us ? Please reply direct to me, because I'm not a member of all addressed lists. Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: 9-Apr-87 20:44:59-PDT,1062;000000000000 Return-Path: Received: from Sun.COM by SUMEX-AIM.STANFORD.EDU with TCP; Thu 9 Apr 87 20:44:29-PDT Received: from sun.Sun.COM by Sun.COM (3.2/SMI-3.2) id AA00602; Tue, 7 Apr 87 17:54:03 PST Received: by sun.Sun.COM (3.2/SMI-3.2) id AA14076; Mon, 6 Apr 87 15:44:31 PST Received: from vienna.sgi.com by sgi.sgi.com (5.52/870223.vjs) id AA05631; Mon, 6 Apr 87 16:43:58 PDT Received: by vienna.sgi.com (5.51/870223.vjs) id AA03457; Mon, 6 Apr 87 16:42:58 PST From: zsuzsa@vienna.sgi.com (Zsuzsanna Molnar) Message-Id: <8704070042.AA03457@vienna.sgi.com> Date: 6 Apr 1987 1642-PST (Monday) To: ucbvax!CS.UCLA.EDU!trainor@Sun.COM Cc: trainor@CS.UCLA.EDU, info-iris@SUMEX-AIM.STANFORD.EDU Subject: Re: Any Iris code out there??? In-Reply-To: Your message of Tue, 31 Mar 87 09:57:40 PST. <8703311757.AA25825@hera.CS.UCLA.EDU> Send Monica Schulze at SGI your address and she'll set you up with source code to flight & robot demos. Address here is 2011 Stierlin Road M/S 2L-420 Mountain View, CA 94043 10-Apr-87 04:48:20-PDT,1031;000000000001 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Fri 10 Apr 87 04:47:59-PDT Received: by lindy.STANFORD.EDU; Fri, 10 Apr 87 04:49:07 PST Date: Fri, 10 Apr 87 04:49:54 PST From: To: info-iris@sumex-aim.stanford.edu Subject: Carriage control characters in mail from info-iris Date: 10 Apr 87 08:41:35 ADT From: To: info-iris@sumex-aim.stanford.edu, postmaster@sumex-aim.stanford.edu cc: bcl@unbmvs1.bitnet Subject: Carriage control characters in mail from info-iris Message-ID: Sometime recently, all mail from info-iris began arriving here with each line beginning with what the systems programming people called "machine carriage control characters." Is this affecting anyone else? Is it a deliberate change? Are we doing something wrong? dedourek@unbmvs1.bitnet 10-Apr-87 08:12:49-PDT,901;000000000001 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Fri 10 Apr 87 08:12:09-PDT Received: from PLU by IO with VMS ; Fri, 10 Apr 87 08:05:50 PST Date: Fri, 10 Apr 87 08:05:50 PST From: SPIRKOV%PLU@ames-io.ARPA Subject: LMI & IRIS To: info-iris@sumex-aim.stanford.edu we're having problems connecting the IRIS to an LMI machine. we have code from LMI that supposedly accepts connections. and code from SGI that connects. but we still can't get them to talk to each other. the error is "connection refused". has anyone been successful in connecting them? the iris is a 3130. (i'm not sure if LMI has any other models. as far as i know, it's only a lambda. (yup, the iris is my baby.)) Lilly ps: we've tried it in the other direction too (iris accepts, & lmi tries to connect). same error. 10-Apr-87 15:27:32-PDT,646;000000000000 Return-Path: Received: from gremlin.nrtc.northrop.com (NRTC-GREMLIN.ARPA.#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Fri 10 Apr 87 15:25:53-PDT Received: from gremlin by gremlin.nrtc.northrop.com id a004955; 10 Apr 87 15:17 PST To: info-iris@sumex-aim.stanford.EDU cc: willson@gremlin.nrtc.northrop.COM Subject: flight software Date: Fri, 10 Apr 87 15:17:38 -0800 From: Stephen Willson Speaking of the flight software, how come the 3.5 version doesn't work with tcp/ip? I've heard rumors that a tcp/ip version exists. Anybody know what gives? 10-Apr-87 16:31:21-PDT,1386;000000000000 Return-Path: Received: from venera.isi.edu by SUMEX-AIM.STANFORD.EDU with TCP; Fri 10 Apr 87 16:29:00-PDT Posted-Date: Fri, 10 Apr 87 16:29:20 PDT Message-Id: <8704102329.AA03553@venera.isi.edu> Received: from LOCALHOST by venera.isi.edu (5.54/5.51) id AA03553; Fri, 10 Apr 87 16:29:22 PDT To: Stephen Willson Cc: info-iris@sumex-aim.stanford.edu, pickard@venera.isi.edu Subject: Re: flight software In-Reply-To: Your message of Fri, 10 Apr 87 15:17:38 -0800. <8704102315.AA02913@venera.isi.edu> Date: Fri, 10 Apr 87 16:29:20 PDT From: Kelly Pickard I offer the following comment from SGI: --------- Forwarded message From: msc@ramoth.sgi.com (Mark Callow) Message-Id: <8711122104.AA01317@ramoth.sgi.com> To: venera.isi.edu!pickard@Sun.COM Subject: Re: Flight simulator for 3030 running TCP TCP based dog will be in the next software release due this summer. It still needs thorough testing here. -Mark -- >From the TARDIS of Mark Callow msc@sgi.sgi.com, ...{ames,decwrl,sun}!sgi!msc "There is much virtue in a window. It is to a human being as a frame is to a painting, as a proscenium to a play. It strongly defines its content." --------- End forwarded message Keep those wings level :-) Kelly. 13-Apr-87 14:52:43-PDT,1530;000000000000 Return-Path: Received: from gremlin.nrtc.northrop.com by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 13 Apr 87 14:51:27 PDT Received: from gremlin by gremlin.nrtc.northrop.com id a027190; 13 Apr 87 14:42 PST To: Mike Muuss cc: Stephen Willson , info-iris@sumex-aim.stanford.EDU Subject: Re: flight software Date: Mon, 13 Apr 87 14:42:15 -0800 From: Stephen Willson Hmm, I have some other changes too. For instance, with the shadow program you can play movie director by moving the eye position of the control tower, either with the mouse or with the digitizing pad. The latter option lets you instantaneously move the eye position by picking up the puck and then setting it down at another viewpoint. (The height setting is adjusted with the dial box.) Another change I made to dog is to allow you to change your view to the POV (point-of-view) of the last missle you launched. That gives you an unusual view of things. One more change was to allow you to zoom in/out from the cockpit view. This gives you an interesting idea of the kind of work that a camera that sees 40 miles out in front of the aircraft has to do to keep locked in on a target. The slightest change in the aircraft's flight path has a rather radical effect on the view out the window. Does the version of the software that you have include the heads-up display and threat zones? 13-Apr-87 22:18:31-PDT,929;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 13 Apr 87 22:18:05 PDT Date: Fri, 10 Apr 87 23:38:46 EDT From: Mike Muuss To: Stephen Willson cc: info-iris@sumex-aim.stanford.EDU, willson@gremlin.nrtc.northrop.COM Subject: Re: flight software Message-ID: <8704102338.aa26087@SEM.BRL.ARPA> BRL has a version of the flight programs that operates over TCP (even across gateways, multiple buildings!) Even though it's neat, we don't use it much (too much work). The work was done by Ron Natalie before he left BRL. We can make it availible to anybody who has a source code license, and would be pleased to return it to SGI for incorporation into their distributed version. Amazingly enough, it only took Ron one evening to replace the XNS code with the TCP code. Best, -Mike 14-Apr-87 09:26:03-PDT,356;000000000000 Return-Path: Received: from nswc-g.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 14 Apr 87 09:25:35 PDT Date: Tue, 14 Apr 87 12:26:30 est From: jrovert@nswc-g.ARPA To: info-iris@sumex-aim.stanford.edu Please remove my name from the info-iris mailing list. My address is : jrovert@nswc-g.arpa thanks jrovert 16-Apr-87 09:51:35-PDT,677;000000000000 Return-Path: Received: from braggvax.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 16 Apr 87 09:51:13 PDT Message-Id: <8704161751.AA00769@braggvax.arpa> To: Info-Iris@SUMEX-AIM.Stanford.edu Subject: Lisp on Iris 3020 Date: Thu, 16 Apr 87 12:51:01 EST From: sigcen@braggvax.arpa We are looking for a Lisp programming package to run on our Iris 3020. It should be Zeta Lisp with Flavors. Our AI expert says he could survive with Common Lisp. If anyone knows a source please let me know - Thank You, Tracy Wood, US Army Signal Center Attn:ATZH-CDC Fort Gordon GA 30905-5090 Phone 404-791-3782/3561 16-Apr-87 11:45:55-PDT,1353;000000000000 Return-Path: Received: from nrl-aic.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 16 Apr 87 11:44:51 PDT Return-Path: Received: Thu, 16 Apr 87 13:44:51 est by nrl-aic.ARPA id AA21348 Date: 16 Apr 1987 13:26:33 EST (Thu) From: Russ Smith Subject: Problem with "capture"? To: info-iris@sumex-aim.stanford.edu Message-Id: <545595995/smith@nrl-aic> We have a model 3030 with version 3.5 software. Attached is a Tektronix 4692 printer. First we "capture" the screen, then the colormap, then we map the captured image into something "correct", then print it using "lp" in the appropriate manner. In general, this works. Unfortunately, in specific, it doesn't... In particular...if we are using "mex" and have the "light" demo as one of the items on the screen, the *printed* image shows severe dropouts in the "light" window. This hasn't (yet) happened with any other programs' windows. Since the printing is taking place just fine, we have to assume that the "capture" program is not handling some sort of peculiarity of the "light" program correctly. Has anyone else experienced such? Anyone have a fix? Anyone know WHY "light" is strange vis-a-vis "capture"? Russ JAYCOR Navy Center for Applied Research in Artificial Intelligence (whew!) 16-Apr-87 13:47:35-PDT,720;000000000000 Return-Path: Received: from gremlin.nrtc.northrop.com by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 16 Apr 87 13:46:34 PDT Received: from gremlin by gremlin.nrtc.northrop.com id a019204; 16 Apr 87 13:35 PST To: Russ Smith cc: info-iris@sumex-aim.stanford.EDU, willson@gremlin.nrtc.northrop.COM Subject: Re: Problem with "capture"? Date: Thu, 16 Apr 87 13:35:43 -0800 From: Stephen Willson The problem is that the capture routine reads the back buffer in double buffer mode, which doesn't necessarily contain the complete picture at any particular time. The light demo runs in double buffer mode, so ... 16-Apr-87 14:07:21-PDT,1022;000000000000 Return-Path: Received: from orville.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 16 Apr 87 14:06:53 PDT Received: Thu, 16 Apr 87 14:04:45 PDT by orville.arpa (5.51/1.2) Message-Id: <8704162104.AA18253@orville.arpa> To: sigcen@braggvax.arpa Cc: Info-Iris@SUMEX-AIM.Stanford.edu Subject: Re: Lisp on Iris 3020 In-Reply-To: Your message of Thu, 16 Apr 87 12:51:01 EST. <8704161751.AA00769@braggvax.arpa> Date: 16 Apr 87 13:04:43 PST (Thu) From: creon@orville.arpa Franz lisp runs on the IRIS and has flavors. We here at NASA have hooked most of the graphics library into franz lisp, and it works quite well. It is available from Franz Inc. (415)-769-5656. Also, ExCl COmmon Lisp, from the same people, runs on the IRIS and has an even better gl2 interface. I think it also has flavors. Creon Levit MS 258-5 NASA Ames Research Center Moffett Field, California 94035 (415)-694-4403 creon@ames-nas.arpa (arpanet/milnet) ihnp4!ames!amelia!creon (uucpnet) 20-Apr-87 14:29:23-PDT,588;000000000000 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 20 Apr 87 14:27:57 PDT Received: from PLU by IO with VMS ; Mon, 20 Apr 87 14:26:31 PST Date: Mon, 20 Apr 87 14:26:31 PST From: SPIRKOV%PLU@ames-io.ARPA Subject: sendmail To: info-iris@sumex-aim.arpa i'm having trouble getting sendmail to work with the latest release of the OS. the error i get is: no local mailer defined and no prog mailer defined anyone have that problem? or anyone get sendmail to work? thanks. Lilly 20-Apr-87 19:57:54-PDT,2427;000000000000 Return-Path: Received: from cs.utah.edu by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 20 Apr 87 19:57:25 PDT Received: by cs.utah.edu (5.54/utah-1.0) id AA03736; Mon, 20 Apr 87 20:59:32 MDT Received: by utah-gr.ARPA (5.31/4.40.2) id AA14569; Mon, 20 Apr 87 20:59:27 MDT Date: Mon, 20 Apr 87 20:59:27 MDT From: dietrich%gr@cs.utah.edu (Frank Dietrich) Message-Id: <8704210259.AA14569@utah-gr.ARPA> To: info-iris@sumex-aim.stanford.edu Subject: First issue of Iris Universe Welcome to the IRIS Universe, The first issue of the IRIS Universe is rolling off the presses. It is a 20 page magazine with color images on the cover. Topics include "Mathematics of parametrized surfaces," "Geometric modeling," "Software exchange," "Ideas in action," "IRIS community," and more. If you like to receive a copy, just mail us your address, it's free. Members of the IRIS user group and everybody on the customer mailing list will automaticlly receive the Universe. We like to thank everybody that contributed to get the magazine started in such a nice way. Simultaneously we invite your contributions for the next issue to be published in time for SIGGRAPH. We are particularily interested in articles that cover: * Graphics & the supercomputer connection * Data Visualization * CG Education * Animation and recording * Hardcopy and digital printing. We are also looking for shorter notes on events, research activities, etc. The next Universe will feature a comprehensive listing of media references, i.e. papers, articles, video and film productions. Please send us copies of your publications for inclusion in this reference list. A special section will be devoted to activities of the IRIS community at SIGGRAPH. Again, keep us informed about your plans. Think visually! You will see that we tried to publish as many pictures as possible. The IRIS Universe is made up off many interesting and meaningful pictures. Let's show more of them. Stay in touch, Frank Dietrich Zsuzsanna Molnar Editor Technical Marketing Manager University of Utah Silicon Graphics Inc. Dept. of Communication 2011 Stierlin Road Salt Lake City, UT 84112 Montain View, CA 94043 (801) 581-5875 (415) 962-3315 21-Apr-87 07:03:57-PDT,1359;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 21 Apr 87 07:03:41 PDT Received: by lindy.STANFORD.EDU; Tue, 21 Apr 87 07:04:34 PST Date: Tue, 21 Apr 87 07:05:43 PST From: To: info-iris@sumex-aim.stanford.edu Subject: Configuration of /usr/lib/sendmail.cf for IRIS 3130, SW Rel. 3.5 Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 21 Apr 87 15:44:27 Date: Tue, 21 Apr 87 15:37:39 +0200 (Central European Summer Time) From: XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) Subject: Configuration of /usr/lib/sendmail.cf for IRIS 3130, SW Rel. 3.5 To: info-iris@sumex-aim.stanford.edu X-VMS-To: X%"info-iris@sumex-aim.stanford.edu" Hallo, I've a problem that I can't fix with the standard documentation (it seems I'm simply stupid). We have three IRIS 31xx workstations running on an Ethernet using TCP/IP and NFS (we have just upgraded to Rel 3.5R1 of the Software). The systems have the names pc1,pc2 and pc3. Can some people help me to set up the sendmail.cf file for this configuration? Regards Martin Knoblauch Ps: Please reply via WISCVM, because files from Stanford arrive corrupted. 21-Apr-87 17:29:58-PDT,978;000000000000 Return-Path: Received: from gremlin.nrtc.northrop.com by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 21 Apr 87 17:29:37 PDT Received: from gremlin by gremlin.nrtc.northrop.com id a022193; 21 Apr 87 17:23 PST To: info-iris@sumex-aim.stanford.EDU cc: willson@gremlin.nrtc.northrop.COM Subject: sendmail Date: Tue, 21 Apr 87 17:23:56 -0800 From: Stephen Willson I also find the sendmail documentation fairly opaque. I would simply like to tell my 3030 that it should give all off-machine mail to a friendly neighbor machine which can forward or deliver it as necessary, and I am having a hard time figuring that out. The sendmail documentation refers to a sendmail directory tree, which, unfortunately, I can't locate. The header to /usr/lib/sendmail.cf is interesting, but I tried making the recommended changes and the system tries to deliver things through uucp (uux). Ug. 22-Apr-87 10:59:19-PDT,2745;000000000000 Return-Path: Received: from Sierra.Stanford.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 22 Apr 87 10:58:29 PDT Date: Wed 22 Apr 87 10:56:43-PDT From: Lloyd La Comb Subject: sendmail.cf To: info-iris@SUMEX-AIM.Stanford.EDU cc: lacomb@Sierra.Stanford.EDU Message-ID: <12296584618.32.LACOMB@Sierra.Stanford.EDU> Ever since I loaded the 3.5 update I've been fingting with sendmail, and to a lesser extent with SGI about sendmail.cf. I can offer a few suggestions based upon my attempts to get the mailer to work on the STANFORD net. The problem about no local mailer and no program mailer happened to me if I tried to "freeze" the configuration file using sendmail -bz. The only way I found around that was the delete the sendmail.fc file and run it "unfrozen" and then I didn't have any problems. I was never able to get my machines (2 2400Ts) that talk to most of the machines on campus directly (I was able to get my two Irises to talk to each other but only after a lot to "lets try this next" attemps) but I was able to find one machine that I could use as a forwarding host. I declared the few machines that I could talk to directly as CShostname. I then declared the forwarding machine as DFforwardhost and CFforwardhost. As near as I can figure what this means is that if I didn't list the machine in the CS declarations it would send it to the machine I declared in the DF declaration and then let that machine decide what to do with it. This works pretty well, I was able to send things out over both the Stanford net and the arpa net. The major draw back was that I COULDN'T ever recieve any mail through the forwarding host, because most the other machines on expect to send mail directly and they can't talk to me directly. When I complained to the HOTLINE about this I got lots of understanding about to quality of the documentation and the undreadability of the .cf file, but not a lot of insight into what messages like ...not a typewriter... really mean. They said that I should just be able to copy the sendmail.cf file straight from a VAX as use it is, that worked only o.k. mainly because when I tried to read my mail the Iris local mail program complained that my mail messaged didn't start with From and then aborted. I tried most of the "obvious" fixes to the .cf file but none of them solved the problem. If any one want to see my sendmail.cf file I will mail it to you but I'm not sure how much it will help. Lloyd La Comb lacomb@su-sierra.arpa or lacomb@su-sierra.stanford.edu ------- 22-Apr-87 18:23:03-PDT,2295;000000000000 Return-Path: Received: from sdcsvax.UCSD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 22 Apr 87 18:22:30 PDT Received: by sdcsvax.UCSD.EDU (5.57/5.0) id AA07510 for info-iris@sumex-aim.stanford.edu; Wed, 22 Apr 87 17:22:44 PST Received: by sdchema.chem.ucsd.edu (5.44) id AA29368; Wed, 22 Apr 87 18:21:45 PST Received: by sdcheme.chem.ucsd.arpa (4.12) id AA20012; Wed, 22 Apr 87 18:19:47 pdt Date: Wed, 22 Apr 87 18:19:47 pdt From: sd%chem@sdcsvax.ucsd.edu (Steve Dempsey) Message-Id: <8704230119.AA20012@sdcheme.chem.ucsd.arpa> To: info-iris@SUMEX-AIM.Stanford.EDU Subject: Re: sendmail.cf Here at the UCSD Chemistry Dept. we ran into the same situation as Lloyd La Comb. We had an existing network of Vaxes, Celeritys, and one SUN all sitting on a local network. We have a single sendmail.cf for all of these machines. They were happily interchanging mail with each other and the outside world. So when we got sendmail for the IRIS we just naturally expected our sendmail.cf file to work. Needless to say it didn't. Like LLoyd, our first problem was the "no local mailer..." errors, which turned out to be the problem where sendmail can't read "frozen" (.fc) config files. Next we found that mail was being delivered to the IRIS ok, but when we tried to read it 'mail' complained that there were no messages! Why? Because the "UNIX style From" line was missing from the beginning of the message. The problem here turned out to be due to a difference between the SYS V version of /bin/mail on the IRIS and the BSD version running on all of our other machines. In our sendmail.cf file is a line that looks like: Mlocal, P=/bin/mail, F=rlsDFMmn, S=10, R=20, A=mail -d $u ^ The significant character here is the 'n' in the F field. According to Appendix C of the Sendmail Installation and Operation Guide (p. f-28 of the IRIS Communications Guide), this flag tells the mailer NOT to insert a "UNIX style From" line at the beginning of the message. On a BSD system this makes sense because the From line is already there, but on SYS V it isn't!!!! So we removed the 'n' and now our IRIS is happy. Hope this helps. Steve Dempsey UCSD Chemistry Computer Facility 23-Apr-87 08:20:53-PDT,1379;000000000000 Return-Path: Received: from cs.utah.edu by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 23 Apr 87 08:20:35 PDT Received: by cs.utah.edu (5.54/utah-1.0) id AA13462; Thu, 23 Apr 87 09:22:49 MDT Received: by gr.utah.edu (5.54/utah-1.0-slave) id AA26870; Thu, 23 Apr 87 09:22:28 MDT Date: Thu, 23 Apr 87 09:22:28 MDT From: fish%gr@cs.utah.edu (Russ Fish) Message-Id: <8704231522.AA26870@gr.utah.edu> Newsgroups: fa.iris Subject: Re: Lisp on Iris 3020 Summary: Expires: References: <8704161751.AA00769@braggvax.arpa> Sender: Reply-To: gr.utah.edu!fish@cs.utah.edu (Russ Fish) Followup-To: Distribution: Organization: University of Utah CS Dept Keywords: Iris, Lisp Apparently-To: info-iris@sumex-aim.stanford.edu We use PSL (Portable Standard Lisp) with C code linked in to implement the Alpha_1 Geometric Modeling System. Our modeling objects use the objects (flavors) package in PSL extensively, so I can attest that it works. (The objects package originally came from Alan Snyder et al. at HP Labs.) We use it on several machines, including the Iris. There is a Common Lisp overlay of PSL called PCLS that could probably meet your needs now. The next version of PSL will be a straight Common Lisp. Send mail to Bob Kessler (kessler@orion.utah.edu) for more info. -Russ (fish@gr.utah.edu, {decvax,ihnp4}!utah-cs!fish} 23-Apr-87 10:51:03-PDT,838;000000000000 Return-Path: Received: from gremlin.nrtc.northrop.com by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 23 Apr 87 10:50:35 PDT Received: from gremlin by gremlin.nrtc.northrop.com id a027344; 23 Apr 87 10:47 PST To: info-iris@sumex-aim.stanford.EDU cc: willson@gremlin.nrtc.northrop.COM Subject: Re: IRIS sendmail.cf Date: Thu, 23 Apr 87 10:46:59 -0800 From: Stephen Willson [My local mailer doesn't know this address, so I am replying via info-iris: To: Vernon Schryver ] YOU ARE A GENIUS! Well, anyway, you did it. The one thing I hadn't done was to add my OWN machine into the CS group. MAJOR HAPPINESS! Bless you, etc. P.S. Are all of your machines at SGI named after spy satelites? -- Stephen Willson 23-Apr-87 21:54:26-PDT,2434;000000000000 Mail-From: BRUGGE created at 23-Apr-87 21:54:06 Date: Thu, 23 Apr 87 21:54:06 PDT From: John Brugge Subject: Additions to Iris PD directory on Sumex To: info-iris@SUMEX-AIM.STANFORD.EDU Message-ID: <12296966435.31.BRUGGE@SUMEX-AIM.STANFORD.EDU> For those who may have misplaced some of the pd code that has been submitted through Info-Iris (or for those who joined the list after a piece was submitted), I have updated the Iris software directory on Sumex to include these programs. The files are in the directory on host Sumex-Aim.Stanford.Edu, and can be retrieved by anonymous ftp. Below is an annotated listing of the contents of the directory; the additions are the last three files, qtest.c (Al McPherson, Boeing Computer Services) timeserver.c (Doug Kingston, BRL) ttytest.c (Steve Dempsey, UCSD) Thanks to the authors for their submissions. John ----- PS: 00DIR..3;P777752 1 1056(7) 11-Dec-86 08:36:00 BRUGGE An annotated directory listing (this file). 00README..1;P777752 1 231(7) 30-Oct-86 15:07:33 BRUGGE General description of the Info-Iris interest group DRAWCUBE.C.1;P777752 6 14350(7) 3-Nov-86 07:44:13 BRUGGE Backface polygon removal routines. FONTS..2;P777752 38 97080(7) 11-Dec-86 08:28:13 BRUGGE Files for creating fonts on the IRIS, as well as some font descriptions. CONFIG.H.1;P777752 2 3794(7) 30-Oct-86 14:58:55 BRUGGE M_TURBO.H.1;P777752 2 3509(7) 30-Oct-86 14:59:48 BRUGGE S_UNIPL50.H.1;P777752 2 4776(7) 30-Oct-86 14:59:35 BRUGGE Header files for GNU Emacs specific to the IRIS. Note that S_UNIPL50.H should be named "s-unipl5.0.h" on the IRIS, and M_TURBO.H should be named "m-turbo.h". PATCHES.C.2;P777752 15 36896(7) 11-Dec-86 08:21:23 BRUGGE Filled surface patches, as well as a simple lighting model. QTEST.C.2;P777752 2 3588(7) 23-Apr-87 21:21:51 BRUGGE A test of some possible bugs in the IRIS queue routines. TIMESERVER.C.2;P777752 2 5099(7) 23-Apr-87 21:23:07 BRUGGE Functions for retrieving the date from another network host. TTYTEST.C.2;P777752 1 2452(7) 23-Apr-87 21:24:19 BRUGGE Two test programs to demonstrate bugs with tty input in the 3.5 kernel. Total of 67 pages in 8 files ------- 25-Apr-87 15:28:43-PDT,1294;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Sat, 25 Apr 87 15:28:17 PDT Received: by lindy.STANFORD.EDU; Sat, 25 Apr 87 14:31:41 PST Date: Sat, 25 Apr 87 14:33:00 PST From: To: info-iris@sumex-aim.stanford.edu Subject: Imagen Printers Received: by PUCC (Mailer X1.24) id 5572; Sat, 25 Apr 87 17:12:23 EDT Date: Sat, 25 Apr 87 17:10:51 EDT From: "Amit S. Joshi" Subject: Imagen Printers To: Iris Conference Hi, I had a general request I wonder if someone out there could answer. The Iris here is on an ethernet and we have an Imagen (Impress language) printer also sitting on the ethernet. Both talk TCP/IP and I have managed to get the Imagen to act as a dumb printer for the Iris. It however seems a shame to waste the capabilities of the printer and not be able to dump screens and so on either over the ethernet or otherwise. I was wondering if anybody has looked into this kind of a thing ? I would be glad to know of some programs. If they do not connect to the Ethernet I would prefer source code so I can modify them Thanks Amit 28-Apr-87 14:37:37-PDT,738;000000000000 Return-Path: Received: from nps-cs.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 28 Apr 87 14:34:58 PDT Received: by nps-cs.arpa (5.51/5.17) id AA22009; Tue, 28 Apr 87 14:11:11 PST Date: Tue, 28 Apr 87 14:11:11 PST From: zyda@nps-cs.arpa (michael zyda) Message-Id: <8704282211.AA22009@nps-cs.arpa> To: info-iris@sumex-aim.stanford.edu Subject: Eikonix digitizer camera... Has anyone out there interfaced an Eikonix digitizer camera to the Silicon Graphics, Inc. IRIS? I have a need to do this and would appreciate hearing from anyone who has. Michael Zyda Naval Postgraduate School, Code 52, Dept. of Computer Science Monterey, California 93943-5100 (408) 646-2305 28-Apr-87 20:07:29-PDT,1171;000000000000 Return-Path: Received: from RELAY.CS.NET by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 28 Apr 87 20:07:06 PDT Received: from relay2.cs.net by RELAY.CS.NET id af12186; 28 Apr 87 23:05 EDT Received: from tektronix.tek.com by RELAY.CS.NET id ai04020; 28 Apr 87 23:00 EDT Received: by tektronix.TEK.COM (5.51/6.20) id AA24297; Tue, 28 Apr 87 16:36:20 PDT Received: by teklds.TEK.COM (5.31/6.19) id AA17952; Tue, 28 Apr 87 16:35:15 PDT Received: by zeus.TEK.COM (5.31/6.19) id AA05364; Tue, 28 Apr 87 16:35:32 PDT Message-Id: <8704282335.AA05364@zeus.TEK.COM> To: michael zyda Cc: info-iris@SUMEX-AIM.STANFORD.EDU, jayb%zeus.tek.com@RELAY.CS.NET Subject: Re: Eikonix digitizer camera... In-Reply-To: Your message of Tue, 28 Apr 87 14:11:11 PST. <8704282211.AA22009@nps-cs.arpa> Date: 28 Apr 87 16:35:31 PDT (Tue) From: "Jay Beck - Tektronix Inc./CAE/Silicon Design Products" (503)629-1485 Try calling Mark Heinen at BBN-Delta Graphics, Inc. (206) 746-6800. They have both and may have done this already. If he isn't in, try Drew Johnston (VP), he will know also. 28-Apr-87 22:35:14-PDT,1300;000000000000 Return-Path: Received: from BRL-SEM.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 28 Apr 87 22:34:49 PDT Date: Wed, 29 Apr 87 1:31:35 EDT From: Mike Muuss To: Q3696%PUCC.BITNET@forsythe.stanford.EDU cc: info-iris@sumex-aim.stanford.EDU Subject: Re: Imagen Printers Message-ID: <8704290131.aa05343@SEM.BRL.ARPA> The BRL CAD Package contains a program (bw-impress) to convert a 8-bit monochrome image to a dithered bitmap for the Imagen, which you can send directly using a simple TCP program like TTCP.C or pieces of TELNET. If you are using the screen in RGBmode, the BRL CAD program "fb-pix" piped into "pix-bw" will do what you want. If you are running in 12-bit mode, you will need to modify one of the provided demo programs to acquire the portion of the image that you are interested in. Hopefully that part won't daunt you, and you will find the Imagen interface useful. Please write me if you need information on acquiring the BRL CAD Package. Best, -Mike Muuss ArpaNet: Postal: Mike Muuss Leader, Advanced Computer Systems Team Systems Engineering and Concepts Analysis Division U.S. Army Ballistic Research Laboratory Attn: SLCBR-SECAD (Muuss) APG, MD 21005-5066 29-Apr-87 08:29:47-PDT,1042;000000000000 Return-Path: Received: from jade.berkeley.edu by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Apr 87 08:29:24 PDT Received: by jade.berkeley.edu (5.54 (CFC 4.22.3)/1.16.13) id AA09691; Wed, 29 Apr 87 08:30:06 PDT Message-Id: <8704291530.AA09691@jade.berkeley.edu> Received: (from MAILER@UCHIMVS1 for MAILER@UCHIMVS1 via NJE) (BITMAIL-2027; 19 LINES); Wed, 29 Apr 87 09:55:52 CDT Date: Wed 29 Apr 87 09:54:37-CDT From: Stuart Schmukler Subject: NCAR graphics on an IRIS To: info-iris@sumex-aim.stanford.edu Has anyone ported the the NCAR graphics libraries to the IRIS? Does any one know of a good (cheap) GKS package for the IRIS? The NCAR libraries are poplar high level routines for the 2-D and 3-D presentation of data. We have a number of programs that depend on the NCAR graphics library, so the fastest way to get them running is to port NCAR graphics to the IRIS without taking advantage or the IRIS special features at first. SaS ------- 29-Apr-87 11:38:22-PDT,995;000000000000 Return-Path: Received: from bnl.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Apr 87 11:36:44 PDT Date: Wed, 29 Apr 87 14:27:40 edt From: thieb@bnl.arpa (Ed Thieberger) Message-Id: <8704291827.AA06865@bnl.arpa> Received: by bnl.arpa; Wed, 29 Apr 87 14:27:40 edt To: Info-Iris@SUMEX-AIM.Stanford.edu Subject: ZIP Board Has anyone had any experience connecting a Mercury Systems ZIP 3232 array processor to an Iris? Mercury provides BSD 4.2 software but not System V. What is involved in adapting the software to run on the IRIS. We currently have the ZIP running on a Sun workstation which does the number crunching and pipes coordinates for plotting to our IRIS 1400 over the Ethernet. We would like to get the ZIP running on the IRIS. Any insight into the process would be appreciated. Ed --------------------------------------------------------------------- Ed Thieberger thieb@bnl.arpa Applied Math Dept. Brookhaven Nat'l Lab 29-Apr-87 15:34:16-PDT,1092;000000000000 Return-Path: Received: from venera.isi.edu by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Apr 87 15:32:51 PDT Posted-Date: Wed, 29 Apr 87 15:32:46 PDT Message-Id: <8704292232.AA03424@venera.isi.edu> Received: from LOCALHOST by venera.isi.edu (5.54/5.51) id AA03424; Wed, 29 Apr 87 15:32:48 PDT To: info-iris@sumex-aim.stanford.edu Cc: pickard@venera.isi.edu Subject: ip2mapio() function Date: Wed, 29 Apr 87 15:32:46 PDT From: Kelly Pickard OK, here's a good one . . . I'd like to control bits 1 & 3 at address 5000 hex on the CG1 (genlock) board. If you can set 'em true, a +5V signal shows up on pins 7 & 9, respectively, on the control port on the back of the IRIS. (And you were wondering what that connector was for . . . ) Fortunately, the 3.5 software includes several functions to address multibus memory. (Try "man ip2mapio".) Does anyone have any experience with these functions, yet? Kelly USC/ISI Marina del Rey, CA (213) 822-1511, x193 1-May-87 13:49:50-PDT,16963;000000000000 Return-Path: Received: from orville.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 1 May 87 13:45:50 PDT Received: Fri, 1 May 87 13:40:53 PDT by orville.arpa (5.51/1.2) Message-Id: <8705012040.AA07152@orville.arpa> To: info-gnu-emacs@prep.ai.mit.edu, info-iris@sumex-aim.stanford.edu Cc: seismo!elsie!ncifcrf!randy@ames.arpa, brugge@sumex-aim.arpa, msommer@bbn-prophet.arpa Subject: gnu emacs 18.41 on iris 3.5 turbos Date: 01 May 87 13:40:50 PDT (Fri) From: raible@orville.arpa So the following s-, m-, and diffs should be sufficient to get a reasonable gnu emacs on a silicon graphics 3.5 machine. Features: dumps, asynchronous subprocesses with ptys, uses the iris directory routines and alloca, sockets, select, etc. Known bugs: - PURESIZE is too big. Anyone know how to read out of the running emacs how much of PURESIZE was actually used? - Starting new processes sometimes losses due to (random?) SIGIOT's. A work-around is included. - etc/loadst only gets the time - nothing else - No mouse support (has anyone done this yet?) Have fun... Eric (raible@ames-nas.arpa) ==================================================================== # This is a shell archive. Remove anything before this line, then # unpack it by saving it in a file and typing "sh file". (Files # unpacked will be owned by you and have default permissions.) # # This archive contains: # /tmp/README /tmp/xemacs-diffs m-irist.h s-iris3-5.h echo x - /tmp/README cat > "/tmp/README" << '//E*O*F /tmp/README//' This file contains all of the files and changes (relative to v18.41) needed to bring up gnu emacs on a SGI iris. In brief, the changes are: additional header files: m-irist.h s-iris3-5.h config.h changed to use the above files small changes (in context diff form) to: keyboard.c process.c sysdep.c unexec.c //E*O*F /tmp/README// echo x - /tmp/xemacs-diffs cat > "/tmp/xemacs-diffs" << '//E*O*F /tmp/xemacs-diffs//' *** keyboard.c-dst Tue Mar 17 08:23:05 1987 --- keyboard.c Fri May 1 10:32:43 1987 *************** *** 42,49 **** #include #endif /* not USG */ ! #ifdef HPUX /* ioctl (0, FIONREAD, addr) always seems to return -1 ! with errno 22 EINVAL. I don't know what's wrong */ #undef FIONREAD #endif HPUX --- 42,52 ---- #include #endif /* not USG */ ! #if defined(HPUX) || defined(IRIS35) ! /* For HPUX: ioctl (0, FIONREAD, addr) always seems to return -1 ! with errno 22 EINVAL. I don't know what's wrong */ ! /* For IRIS release 3.5, the effect having this defined is that ! all keystrokes are delayed one keystroke. "Don't know why" */ #undef FIONREAD #endif HPUX *** process.c-dst Fri Mar 20 03:54:51 1987 --- process.c Wed Apr 29 16:23:17 1987 *************** *** 47,52 **** --- 47,56 ---- #include #endif /* USG */ + #ifdef IRIS + #include /* for "minor" */ + #include + #else #ifdef HAVE_TIMEVAL #if defined (USG) && !defined (UNIPLUS) #include *************** *** 54,59 **** --- 58,64 ---- #include #endif #endif /* HAVE_TIMEVAL */ + #endif /* IRIS */ #if defined (HPUX) && defined (HAVE_PTYS) #include *************** *** 220,233 **** --- 225,248 ---- sprintf (ptyname, "/dev/pty%c%x", c, i); #endif /* not MASSCOMP */ #endif /* not HPUX */ + + #ifdef IRIS + *ptyv = open ("/dev/ptc", O_RDWR | O_NDELAY, 0); + if (*ptyv < 0 || fstat (*ptyv, &stb) < 0) + return 0; + #else if (stat (ptyname, &stb) < 0) return 0; *ptyv = open (ptyname, O_RDWR | O_NDELAY, 0); + #endif /* IRIS */ if (*ptyv >= 0) { /* check to make certain that both sides are available this avoids a nasty yet stupid bug in rlogins */ + #ifdef IRIS + sprintf (ptyname, "/dev/ttyq%d", minor(stb.st_rdev)); + #else #ifdef HPUX sprintf (ptyname, "/dev/pty/tty%c%x", c, i); #else *************** *** 237,247 **** --- 252,267 ---- sprintf (ptyname, "/dev/tty%c%x", c, i); #endif /* not RTU */ #endif /* not HPUX */ + #endif /* not IRIS */ #ifndef UNIPLUS if (access (ptyname, 6) != 0) { close (*ptyv); + #ifdef IRIS + return (0); + #else continue; + #endif /* IRIS */ } #endif /* not UNIPLUS */ /* *************** *** 1996,2001 **** --- 2019,2037 ---- p->sentinel = sentinel; } + + #ifdef IRIS + ignore_signal_IRIS (sig) + int sig; + { + /* Don't know why the IRIS gets random SIGIOT's sometimes when + starting new processes, but this allows us to limp along. */ + + signal (SIGIOT, ignore_signal_IRIS); + message1 ("Got a mysterious SIGIOT - kill the last process started."); + } + #endif + init_process () { register int i; *************** *** 2009,2014 **** --- 2045,2054 ---- #endif ) signal (SIGCHLD, child_sig); + #endif + + #ifdef IRIS + signal (SIGIOT, ignore_signal_IRIS); #endif input_wait_mask = ChannelMask(0); *** sysdep.c-dst Fri Mar 20 07:12:58 1987 --- sysdep.c Wed Apr 29 16:27:34 1987 *************** *** 1886,1891 **** --- 1886,1912 ---- #endif /* not HAVE_VFORK */ + #ifdef IRIS + + /* The IRIS (3.5) has timevals, but uses sys V utime, and doesn't have the + utimbuf structure defined anywhere but in the man page. */ + + struct utimbuf { + long actime; + long modtime; + }; + + utimes (name, tvp) + char *name; + struct timeval tvp[]; + { + struct utimbuf utb; + utb.actime = tvp[0].tv_sec; + utb.modtime = tvp[1].tv_sec; + utime (name, &utb); + } + #endif /* IRIS */ + #ifdef HPUX /* HPUX sets HAVE_TIMEVAL but does not implement utimes. */ *** unexec.c-dst Fri Mar 20 08:57:05 1987 --- unexec.c Wed Apr 29 16:23:17 1987 *************** *** 297,303 **** #else /* not HPUX */ ! #ifdef USG static struct bhdr hdr, ohdr; #define a_magic fmagic #define a_text tsize --- 297,303 ---- #else /* not HPUX */ ! #if defined (USG) && ! defined (IRIS) static struct bhdr hdr, ohdr; #define a_magic fmagic #define a_text tsize //E*O*F /tmp/xemacs-diffs// echo x - m-irist.h cat > "m-irist.h" << '//E*O*F m-irist.h//' /* m- file for Silicon Graphics Iris 2500 Turbos Copyright (C) 1985, 1986 Free Software Foundation, Inc. This file is part of GNU Emacs. GNU Emacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. No author or distributor accepts responsibility to anyone for the consequences of using it or for whether it serves any particular purpose or works at all, unless he says so in writing. Refer to the GNU Emacs General Public License for full details. Everyone is granted permission to copy, modify and redistribute GNU Emacs, but only under the conditions described in the GNU Emacs General Public License. A copy of this license is supposed to have been given to you along with GNU Emacs so you can know your rights and responsibilities. It should be in a file named COPYING. Among other things, the copyright notice and this notice must be preserved on all copies. */ /* The following three symbols give information on the size of various data types. */ #define SHORTBITS 16 /* Number of bits in a short */ #define INTBITS 32 /* Number of bits in an int */ #define LONGBITS 32 /* Number of bits in a long */ /* Define BIG_ENDIAN iff lowest-numbered byte in a word is the most significant byte. */ /* #define BIG_ENDIAN */ /* Define NO_ARG_ARRAY if you cannot take the address of the first of a * group of arguments and treat it as an array of the arguments. */ #define NO_ARG_ARRAY /* Define WORD_MACHINE if addresses and such have * to be corrected before they can be used as byte counts. */ #define WORD_MACHINE /* Define how to take a char and sign-extend into an int. On machines where char is signed, this is a no-op. */ #define SIGN_EXTEND_CHAR(c) (c) /* Now define a symbol for the cpu type, if your compiler does not define it automatically: Ones defined so far include vax, m68000, ns16000, pyramid, orion, tahoe, APOLLO and many others */ #ifndef m68000 #define m68000 #endif /* Use type int rather than a union, to represent Lisp_Object */ /* This is desirable for most machines. */ #define NO_UNION_TYPE /* Define EXPLICIT_SIGN_EXTEND if XINT must explicitly sign-extend the 24-bit bit field into an int. In other words, if bit fields are always unsigned. If you use NO_UNION_TYPE, this flag does not matter. */ #define EXPLICIT_SIGN_EXTEND /* Data type of load average, as read out of kmem. */ #define LOAD_AVE_TYPE long /* Convert that into an integer that is 100 for a load average of 1.0 */ #define FSCALE 1.0 #define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE) /* Define CANNOT_DUMP on machines where unexec does not work. Then the function dump-emacs will not be defined and temacs will do (load "loadup") automatically unless told otherwise. */ /* #define CANNOT_DUMP */ /* Define VIRT_ADDR_VARIES if the virtual addresses of pure and impure space as loaded can vary, and even their relative order cannot be relied on. Otherwise Emacs assumes that data space precedes text space, numerically. */ /* #define VIRT_ADDR_VARIES */ /* LIBS_TERMCAP is used only in ymakefile */ #define LIBS_TERMCAP -ltermcap /* Define C_ALLOCA if this machine does not support a true alloca and the one written in C should be used instead. Define HAVE_ALLOCA to say that the system provides a properly working alloca function and it should be used. Define neither one if an assembler-language alloca in the file alloca.s should be used. */ /* #define C_ALLOCA */ #define HAVE_ALLOCA /* Define NO_REMAP if memory segmentation makes it not work well to change the boundary between the text section and data section when Emacs is dumped. If you define this, the preloaded Lisp code will not be sharable; but that's better than failing completely. */ /* #define NO_REMAP */ //E*O*F m-irist.h// echo x - s-iris3-5.h cat > "s-iris3-5.h" << '//E*O*F s-iris3-5.h//' /* Definitions file for GNU Emacs running on Silicon Graphics 3.5 Copyright (C) 1985, 1986 Free Software Foundation, Inc. This file is part of GNU Emacs. GNU Emacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. No author or distributor accepts responsibility to anyone for the consequences of using it or for whether it serves any particular purpose or works at all, unless he says so in writing. Refer to the GNU Emacs General Public License for full details. Everyone is granted permission to copy, modify and redistribute GNU Emacs, but only under the conditions described in the GNU Emacs General Public License. A copy of this license is supposed to have been given to you along with GNU Emacs so you can know your rights and responsibilities. It should be in a file named COPYING. Among other things, the copyright notice and this notice must be preserved on all copies. */ /* * Define symbols to identify the version of Unix this is. * Define all the symbols that apply correctly. */ #define USG #define USG5 #define IRIS #define IRIS35 /* SYSTEM_TYPE should indicate the kind of system you are using. It sets the Lisp variable system-type. */ #define SYSTEM_TYPE "silicon-graphics-unix" /* nomultiplejobs should be defined if your system's shell does not have "job control" (the ability to stop a program, run some other program, then continue the first one). */ #define NOMULTIPLEJOBS /* Emacs can read input using SIGIO and buffering characters itself, or using CBREAK mode and making C-g cause SIGINT. The choice is controlled by the variable interrupt_input. Define INTERRUPT_INPUT to make interrupt_input = 1 the default (use SIGIO) SIGIO can be used only on systems that implement it (4.2 and 4.3). CBREAK mode has two disadvatages 1) At least in 4.2, it is impossible to handle the Meta key properly. I hear that in system V this problem does not exist. 2) Control-G causes output to be discarded. I do not know whether this can be fixed in system V. Another method of doing input is planned but not implemented. It would have Emacs fork off a separate process to read the input and send it to the true Emacs process through a pipe. */ /* #define INTERRUPT_INPUT */ /* Letter to use in finding device name of first pty, if system supports pty's. 'a' means it is /dev/ptya0 */ #define FIRST_PTY_LETTER 'a' /* * Define HAVE_TERMIO if the system provides sysV-style ioctls * for terminal control. */ #define HAVE_TERMIO /* * Define HAVE_TIMEVAL if the system supports the BSD style clock values. * Look in for a timeval structure. */ #define HAVE_TIMEVAL /* * Define HAVE_SELECT if the system supports the `select' system call. */ #define HAVE_SELECT /* * Define HAVE_PTYS if the system supports pty devices. */ #define HAVE_PTYS /* Define HAVE_SOCKETS if system supports 4.2-compatible sockets. */ #define HAVE_SOCKETS /* * Define NONSYSTEM_DIR_LIBRARY to make Emacs emulate * The 4.2 opendir, etc., library functions. */ /* #define NONSYSTEM_DIR_LIBRARY */ /* Define this symbol if your system has the functions bcopy, etc. */ #define BSTRING /* subprocesses should be defined if you want to have code for asynchronous subprocesses (as used in M-x compile and M-x shell). This is generally OS dependent, and not supported under most USG systems. */ #define subprocesses /* If your system uses COFF (Common Object File Format) then define the preprocessor symbol "COFF". */ /* #define COFF */ /* define MAIL_USE_FLOCK if the mailer uses flock to interlock access to /usr/spool/mail/$USER. The alternative is that a lock file named /usr/spool/mail/$USER.lock. */ /* #define MAIL_USE_FLOCK */ /* Define CLASH_DETECTION if you want lock files to be written so that Emacs can tell instantly when you try to modify a file that someone else has modified in his Emacs. */ /* #define CLASH_DETECTION */ /* We use the Berkeley (and usg5.2.2) interface to nlist. */ #define NLIST_STRUCT /* The file containing the kernel's symbol table is called /vmunix. */ #define KERNEL_FILE "/vmunix" /* The symbol in the kernel where the load average is found is named _avenrun. */ #define LDAV_SYMBOL "_avenrun" /* Special hacks needed to make Emacs run on this system. */ /* * Make the sigsetmask function go away. Don't know what the * ramifications of this are, but doesn't seem possible to * emulate it properly anyway at this point. */ #define sigsetmask(mask) /* Null expansion */ /* The IRIS defines SIGIO in signal.h, but doesn't implement it. */ #undef SIGIO #define LIBS_MACHINE -lbsd -ldbm -lPW #define C_SWITCH_MACHINE -I/usr/include/bsd #define PURESIZE 150000 /* There is an inconsistency between the sgi assembler, linker which barfs on these. */ #define internal_with_output_to_temp_buffer stupid_long_name1 #define Finsert_abbrev_table_description stupid_long_name2 /* setjmp and longjmp can safely replace _setjmp and _longjmp, but they will run slower. */ #define _setjmp setjmp #define _longjmp longjmp /* On USG systems the system calls are interruptable by signals that the user program has elected to catch. Thus the system call must be retried in these cases. To handle this without massive changes in the source code, we remap the standard system call names to names for our own functions in sysdep.c that do the system call with retries. */ #define read sys_read #define open sys_open #define write sys_write #define INTERRUPTABLE_OPEN #define INTERRUPTABLE_IO /* On USG systems these have different names */ #define index strchr #define rindex strrchr /* USG systems tend to put everything declared static into the initialized data area, which becomes pure after dumping Emacs. Foil this. Emacs carefully avoids static vars inside functions. */ /* #define static */ /* Compiler bug bites on many systems when default ADDR_CORRECT is used. */ #define ADDR_CORRECT(x) (int)((char *)(x) - (char*)0) /* some errno.h's don't actually allocate the variable itself */ #define NEED_ERRNO //E*O*F s-iris3-5.h// exit 0 1-May-87 16:25:26-PDT,551;000000000000 Mail-From: BRUGGE created at 1-May-87 16:23:56 Date: Fri, 1 May 87 16:23:55 PDT From: John Brugge Subject: Re: gnu emacs 18.41 on iris 3.5 turbos To: info-iris@SUMEX-AIM.STANFORD.EDU In-Reply-To: <8705012040.AA07152@orville.arpa> Message-ID: <12299003479.31.BRUGGE@SUMEX-AIM.STANFORD.EDU> The shell script file included in the last message for updating the GNU Emacs header files to work with SGI's Iris Release 3.5 has been archived as NEWGNU.IRIS on Sumex-Aim.Stanford.Edu. John ------- 4-May-87 22:57:46-PDT,1293;000000000000 Return-Path: Received: from orville.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 4 May 87 22:57:20 PDT Received: Mon, 4 May 87 22:56:32 PDT by orville.arpa (5.51/1.2) Message-Id: <8705050556.AA19460@orville.arpa> To: info-iris@sumex-aim.stanford.edu Subject: spurious SIGIOTs Cc: raible@orville.arpa Date: 04 May 87 22:56:30 PDT (Mon) From: raible@orville.arpa So has anyone experienced seemingly spurious SIGIOTs on a 2500t? I have brought up gnu emacs here, but every now and then (and especially the first time after starting it up) when trying to spawn a new asynchrnous subprocess, I get a SIGIOT. I made a quick scan of the kernel sources, and it doesn't seem to be generated anywhere. Obviously, it is also not generated explicitly by emacs. Oh - if you want the diffs for gnu emacs relative to 18.41, they are ftpable from: sumex-aim.stanford.edu as NEWGNU.IRIS Any help with this SIGIOT would be much appreciated. One more thing: anyone gotten FIONREAD to work under 3.5? (In cooked mode, it returns a count before a newline, and then a read will hang, in raw mode, it seems to eat the first character). Because it doesn't work right, I had to #undef FIONREAD as part of the diffs mentioned above. 5-May-87 11:01:10-PDT,1301;000000000000 Return-Path: Received: from sdcsvax.UCSD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 5 May 87 10:59:40 PDT Received: by sdcsvax.UCSD.EDU (5.57/5.0) id AA04126 for info-iris@sumex-aim.stanford.edu; Tue, 5 May 87 10:00:02 PST Received: by sdchema.chem.ucsd.edu (5.44) id AA19399; Tue, 5 May 87 10:58:38 PDT Received: by sdcheme.chem.ucsd.arpa (4.12) id AA02099; Tue, 5 May 87 10:56:54 pdt Date: Tue, 5 May 87 10:56:54 pdt From: sd%chem@sdcsvax.ucsd.edu (Steve Dempsey) Message-Id: <8705051756.AA02099@sdcheme.chem.ucsd.arpa> To: info-iris@sumex-aim.stanford.edu Subject: Re: FIONREAD ioctl in 3.5 Cc: raible@orville.arpa The problem with the FIONREAD ioctl is that it returns the number of characters in the RAW input queue instead of the CANONICAL input queue. This bug has been reported to SGI. Note that this is a new feature of GL2-W3.5. It worked correctly in earlier versions. The problem was not corrected in the GL2-W3.5r1 bug fix release. In the meantime you can use the BSD system call 'select' to achieve the same results. There are other misbehaviors of the tty driver as well. The source code for a couple of simple programs which expose these buggers is in the IRIS public domain software directory on SUMEX-AIM.STANFORD.EDU. 5-May-87 14:58:41-PDT,1068;000000000000 Return-Path: Received: from navajo.stanford.edu by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 5 May 87 14:57:48 PDT Received: from Iris-MJ320.Stanford.EDU by navajo.stanford.edu with TCP; Tue, 5 May 87 14:37:01 PDT Received: by iris-mj320.STANFORD.EDU; Mon, 4 May 87 04:43:15 PDT Date: Mon, 4 May 87 04:43:15 PDT From: Superuser To: info-iris@sumex-aim.stanford.edu Hello! Being new on the Iris board , I would like to introduce myself first. I am taking care of an iris 2400 at Stanford university.My name is Oliver Orciere and I am trying to bring this iris to life. A lot of people asked me for software and I was unable to give them an answer. Essentially I would like to know if a copy of the following software is available. -XNS kernel -GNU emacs (I tried to write to prep.ai.mit.edu but the network was unreachable) I also tried to settle a version of matlab on iris but I am missing some files in the library calls (did anybody else tried ?) Olivier. 7-May-87 10:19:10-PDT,1430;000000000000 Return-Path: Received: from jade.berkeley.edu by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 7 May 87 10:17:42 PDT Received: by jade.berkeley.edu (5.54 (CFC 4.22.3)/1.16.14) id AA13738; Thu, 7 May 87 10:17:48 PDT Received: from cernvax.UUCP (cernvax) by mint.cern (cernvax) (4.12/3.14) id AA01866; Thu, 7 May 87 17:42:45 +0200 From: meyer%unizh.UUCP%cernvax.bitnet@BERKELEY.EDU Received: by cernvax.UUCP (4.12/4.7) id AA29720; Thu, 7 May 87 17:43:18 +0200 Received: by unizh.UUCP (4.12/4.7) id AA26215; Thu, 7 May 87 15:01:15+0100 Date: Thu, 7 May 87 14:54:00 -0100 Message-Id: <8705071354.AA18438@gorgo.UUCP> Received: by gorgo.UUCP id AA18438; Thu, 7 May 87 14:54:00 -0100 To: info-iris@sumex-aim.stanford.edu Subject: Inquiry: New Iris Workstations Does anyone know of new versions of Iris Workstations which are presumably going to be released this summer? I do not remember having seen something around on the net for the last two months, maybe because I'm relatively new to this mailing list. Did anybody hear anything? Please post it! Urs ------------------------------------------------------------------------ Urs Meyer, University of Zuerich, Computer Science Department, Computer Graphics Group, Winterthurerstr. 190, 8057 Zuerich, Switzerland UUCP: mcvax!cernvax!unizh!meyer CHUNET: meyer@ifi.unizh.chunet 7-May-87 13:40:32-PDT,938;000000000000 Return-Path: Received: from sdcsvax.UCSD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 7 May 87 13:39:22 PDT Received: by sdcsvax.UCSD.EDU (5.57/5.0) id AA03174 for info-iris@sumex-aim.stanford.edu; Thu, 7 May 87 12:39:16 PST Received: by sdchema.chem.ucsd.edu (5.44) id AA06174; Thu, 7 May 87 13:37:54 PDT Received: by sdcheme.chem.ucsd.arpa (4.12) id AA10049; Thu, 7 May 87 13:36:06 pdt Date: Thu, 7 May 87 13:36:06 pdt From: sd%chem@sdcsvax.ucsd.edu (Steve Dempsey) Message-Id: <8705072036.AA10049@sdcheme.chem.ucsd.arpa> To: info-iris@sumex-aim.stanford.edu Subject: Re: Inquiry: New Iris Workstations The new IRIS is called the IRIS 4D/60. Your local SGI rep should have brochures and price lists, but machines are very scarce. One of them is supposed to show up in the San Diego area in a few weeks. When it does I'm going to try to port my MMS (Molecular Modeling System) to it. 19-May-87 15:28:51-PDT,434;000000000000 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 19 May 87 15:26:17 PDT Received: from PLU by IO with VMS ; Tue, 19 May 87 14:46:52 PDT Date: Tue, 19 May 87 14:46:53 PDT From: SPIRKOV%PLU@ames-io.ARPA Subject: joysticks To: info-iris@sumex-aim.stanford.edu has anyone connected a joystick (preferably 2 of them) to an iris? Lilly 20-May-87 05:29:17-PDT,2178;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 20 May 87 05:28:50 PDT Received: by lindy.STANFORD.EDU; Wed, 20 May 87 05:28:47 PDT Received: by Forsythe.Stanford.EDU; Wed, 20 May 87 05:29:24 PDT Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 20 May 87 13:41:36 Date: Wed, 20 May 87 13:38:49 +0200 (Central European Summer Time) From: XBR2D96D@ddathd21.bitnet (Knobi der Rechnerschrat) Subject: HW Questions To: info-iris@sumex-aim.stanford.edu X-Vms-To: X%"info-iris@sumex-aim.stanford.edu",D96D Hallo, I've got (at least) three questions about the IRIS hardware. 1.) We have a Cypher streamer-tape (1600/3200 BPI) connected to an IRIS 3130. The question is: "How can I use the high-density mode of that tape?" 2.) On the same IRIS we have an additional Fujitsu EAGLE disk drive. The default partitions are: a. 1 / 32 root, boot b. 33 / 48 swap c. 81 / 56 d. 137 / 700 e. 137 / 350 f. 487 / 350 g. 0 / 837 The meaning of a., b., d., e. and f. is clear. The question is: "what is the meaning of the 28Mb in c. ?" 3.) We have an IRIS 3130 with an GENELOCK/PAL card. The question is: "Where can we get informations about pin-assignment and programming of the 9-pin Genlock-control-port ?" 4.) Now a software question: In /usr/lib are a handful lib???.a files (e.g. libplot.a, lib4014.a) which contain identical entrypoints. These entrypoints look like a standard plot-interface for various output devices. The question is: "Where can we get informations about these routines (parameters, return-values, etc.)? I can't find them in the standard IRIS documentation." Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: PS: Please respond directly to my above mentioned BITNET-address. The return path via Stanford is very unreliable. 21-May-87 09:45:43-PDT,2226;000000000000 Return-Path: Received: from nmfecc.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 21 May 87 09:45:00 PDT Received: from fsu.mfenet by ccx.mfenet with BrainDamage via MfeNet ; Thu, 21 May 87 09:43:11 PDT Date: Thu, 21 May 87 09:43:11 PDT From: MINUIT%FSU.MFENET@nmfecc.arpa Message-Id: <870521094311.01a@nmfecc.arpa> To: INFO-IRIS@SUMEX-AIM.STANFORD.EDU.ARPA Comment: From MINUIT@FSU.MFENET on 21-MAY-1987 12:43:35.65 EDT Subject: problems linking microemacs I am trying to bring up a copy of microemacs on one of our IRISes here. I set the ifdef's in the file estruct.h for UNIX system V and for terminal I/O to be done using the termcap file. The programs all compiled without a hitch, but the linker balked about some multiply defined symbols in /usr/lib/junipersw.o. Has anyone ever tried to compile microemacs on their IRIS before? or does anyone know what the library routines in junipersw.o do? I suspect that either this library is included by more than one of the programs making up microemacs or that our copy of this library might be messed up. Any advice would be appreciated. David LaSalle SCRI (Fla St Univ) minuit%fsu@nmfecc.arpa Here is a listing of the error output from the linker: cc -O ansi.o basic.o bind.o buffer.o display.o fileio.o hp150.o line.o lock.c main.o random.o region.o search.o spawn.o tcap.o termio.o vt52.o window.o word.o exec.o input.o isearch.o -ltermcap -lc -o emacs aldiv: ld:/usr/lib/junipersw.o: multiply defined raldiv: /usr/lib/junipersw.o: multiply defined ldiv: /usr/lib/junipersw.o: multiply defined rldiv: /usr/lib/junipersw.o: multiply defined lmul: /usr/lib/junipersw.o: multiply defined rlmul: /usr/lib/junipersw.o: multiply defined lrem: /usr/lib/junipersw.o: multiply defined rlrem: /usr/lib/junipersw.o: multiply defined uldiv: /usr/lib/junipersw.o: multiply defined ruldiv: /usr/lib/junipersw.o: multiply defined ulmul: /usr/lib/junipersw.o: multiply defined rulmul: /usr/lib/junipersw.o: multiply defined *** Error code 2 27-May-87 08:42:18-PDT,1483;000000000000 Return-Path: Received: from lindy.STANFORD.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 27 May 87 08:41:40 PDT Received: by lindy.STANFORD.EDU; Wed, 27 May 87 08:41:22 PDT Received: by Forsythe.Stanford.EDU; Wed, 27 May 87 08:42:25 PDT Date: 27 May 87 11:33:03 ADT To: info-iris@sumex-aim.stanford.edu Subject: Problems with mex? From: MIKEMAC%UNBMVS1.BITNET@forsythe.stanford.edu Message-Id: First, let me explain that I know very little about the iris and mex etc. I just try to pick up pieces when things get broken. We have an iris 2400. When the system boots to the prom monitor everything looks normal ( text area is the right size and in the right place). As soon as we boot UNIX (to single user mode) the text area is shifted about half way to the right so only about 40 columns of output is shown. The grad student (just left) who was using a great one for mex etc crashed the system several times with mex and multiple windows open. 1) Is it possible that mex crashing has left the text area shifted? 2) If this is possible how do I fix it. 3) if this isn't what might be wrong? 4) and how do I fix it Michael MacDonald Software Specialist, School of Computer Science University of New Brunswick Po. Box 4400 Fredericton, New Brunswick CANADA E3B 5A3 (506) 453-4566 Netnorth/BITNET: MIKEMAC @ UNBMVS1 27-May-87 14:34:05-PDT,462;000000000000 Return-Path: Received: from ames-io.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 27 May 87 14:32:43 PDT Received: from PLU by IO with VMS ; Wed, 27 May 87 14:05:02 PDT Date: Wed, 27 May 87 14:05:02 PDT From: SPIRKOV%PLU@ames-io.ARPA Subject: mex To: info-iris@sumex-aim.arpa i keep getting this error: mex: screwy message received: 0 does anyone know what this means?? thanks. Lilly 23-Jun-87 18:52:37-PDT,1662;000000000000 Return-Path: <@wiscvm.wisc.edu:TSHAW@UNCAEDU.BITNET> Received: from wiscvm.wisc.edu by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 23 Jun 87 18:52:07 PDT Received: from UNCAEDU.BITNET by wiscvm.wisc.edu ; Tue, 23 Jun 87 20:50:46 CDT Date: 22 JUNE 1987 11:58 From: TSHAW%UNCAEDU.BITNET@wiscvm.wisc.edu To: info-iris@sumex-aim.stanford.edu Subj: hardware questions We have decided for various reasons that we need to acquire a Silicon Graphics machine to display the neurological models that we are developing here. The problem we have is not new or unique - not enough dollars in our graphics fund. Does anyone out there know of a used machine that we could purchase (even if it's old like a 2400 - if it was cheap enough we could afford to upgrade it)? Also i wonder if anyone has had any experience in adding third party disks to these machines - we do not think that the factory config has enough storage for our needs. I have been told that this machine uses a Multibus backplane, for which there are many disk controllers available, but is it a standard implementation or some weird sub/superset? And what about the system aspects of adding a larger disk? I am not a Unix type (i live mostly in a VMS world) so this area is a mystery to me. Thank you in advance for any insights that you can provide. Terry Shaw | BITNET TSHAW@UNCAEDU Research Assistant | Fonemail 403-220-5894 Faculty of Medicine | University of Calgary | Don't bother to write; we're having our Calgary, Alberta, CANADA. | annual postal strike. 3-Jul-87 10:07:40-PDT,1297;000000000000 Return-Path: Received: from bu-cs.BU.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 3 Jul 87 10:06:33 PDT Received: from bucasb (BUCASB.BU.EDU) by bu-cs.BU.EDU (3.2/4.7) id AA06684; Fri, 3 Jul 87 13:07:06 EDT Return-Path: Received: by bucasb (4.12/4.7) id AA18131; Fri, 3 Jul 87 13:04:06 edt Date: Fri, 3 Jul 87 13:04:06 edt From: mike@bucasb.BU.EDU (Michael Cohen) Message-Id: <8707031704.AA18131@bucasb> To: info-iris@sumex-aim.stanford.edu Subject: Re: GNU Emacs on 3130 Workstation From: mike@bucasb.BU.EDU (Michael Cohen) To: info-iris@sumex-aim.ARPA Newsgroups: bu.mail.info-iris In-Reply-To: <9034@bu-cs.BU.EDU> Organization: Boston U., Center for Adaptive Systems Does anybody have The latest version 18.47 -- 18.48 up on Silicon Graphics 3130 workstations. If so, can you tell me How I can get the version up as we are having some problems getting the software up using the IRIS C compiler. Thanks much. -mike -- Michael Cohen ---- Center for Adaptive Systems Boston University (617-353-7857) Email: mike@bucasb.bu.edu Smail: Michael Cohen Center for Adaptive System Department of Mathematics, Boston University 111 Cummington Street Boston, Mass 02215 3-Jul-87 13:08:20-PDT,1368;000000000000 Return-Path: Received: from cs.utah.edu by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 3 Jul 87 13:07:51 PDT Received: by cs.utah.edu (5.54/utah-1.0) id AA28469; Fri, 3 Jul 87 14:11:23 MDT Received: by utah-kloo.ARPA (4.12/4.40.2) id AA00431; Fri, 3 Jul 87 13:58:58 mdt From: peterson%museum@cs.utah.edu (John W. Peterson) Message-Id: <8707031958.AA00431@utah-kloo.ARPA> Date: Fri, 3 Jul 87 13:58:45 MDT Subject: Re: GNU Emacs on Iris Workstations To: info-iris@sumex-aim.stanford.edu We recently brought up Gnu emacs version 18.44 on an Iris 2400 turbo, using the fixes posted by raible@ames-nas.arpa a while ago. We made one important fix to get subprocess to work reliably. In process.c, routine create_process(), we found that adding a sleep after the child started got rid of the spurious "mysterious SIGIOT" problems (see diff below). Cheers, jp child_setup_tty (xforkout); child_setup (xforkin, xforkout, xforkout, new_argv, env); } environ = save_environ; } + /* Sleep added to avoid race condition with child opening pty */ + sleep( 2 ); + /* If the subfork execv fails, and it exits, this close hangs. I don't know why. So have an interrupt jar it loose. */ signal (SIGALRM, create_process_1); alarm (1); close (forkin); ------- 6-Jul-87 14:04:32-PDT,3376;000000000000 Mail-From: BRUGGE created at 6-Jul-87 14:03:09 Date: Mon, 6 Jul 87 14:03:07 PDT From: John Brugge Subject: New Coordinator needed for Info-Iris To: info-iris@SUMEX-AIM.STANFORD.EDU Message-ID: <12316279352.40.BRUGGE@SUMEX-AIM.STANFORD.EDU> Having changed in status from Graduate Student to Real World Person, and with my new employer not as involved with IRISes and computer graphics, I will need to give up the reins as Coordinator of the INFO-IRIS group very soon. To keep the community going, then, I am looking for someone in the group who is willing to take over this role. The responsibilities of the position include - maintaining the distribution list of net addresses (adding and deleting names as requested), - if possible, maintaining a directory of public-domain software submitted by readers of the list, and available to the INFO-IRIS community, - generally keeping the list alive. The coordinator should be at a site that is on one of the major networks, with a host machine capable of sending and receiving mail to/from any of a number of other networks. The host machine should also ideally be accessible for remote file access to as many INFO-IRIS users as possible for making the public domain software available (such as via the FTP protocol between hosts on the ARPANet). The tasks of this position have been fairly light in the past, requiring on average 1-2 hours/week of attention; the most difficult chore I've found is dealing with network/mailer errors that prevent messages from making it to all sites on the list, most of which are problems with local mailers that can be cleared up by notifying the postmaster at the problem site. Since the list is not currently administrated in a moderated format, there is no need to "screen" or bundle incoming messages-- anything sent to the general INFO-IRIS address simply gets forwarded to everyone. INFO-IRIS has been around now for only a year, but I believe has already proved its usefulness in providing a communications avenue within the user community. It reaches an audience at close to 150 sites, from universities to computer graphics firms (even SGI!). I have found it fascinating to hear of the diversity of applications for which these machines are being used, and invaluable to catch some of the experiences of others before having to reinvent the wheel (or scratch my head for too long on a bug that someone else has already found a fix for). If anyone is interested in the position of Coordinator, and has the resources available at their site (you should talk with your systems manager before making too much of a commitment), please contact me by e-mail. Thanks, John Brugge P.S. The position is available immediately. P.P.S. If anyone at a BITNET site is willing to act as a local coordinator for BITNET subscribers, please contact me also; the people at the BITNET <-> ARPANET gateway have asked all ARPANET distribution lists to try to use a single BITNET address as a local burster so that multiple copies of messages don't have to go through the already overloaded gateway. The responsibilities there would be just maintaining that subset of the INFO-IRIS distribution list containing BITNET net addresses. ------- 6-Jul-87 21:00:03-PDT,4874;000000000000 Return-Path: Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 6 Jul 87 20:59:29 PDT Received: by ucbvax.Berkeley.EDU (5.58/1.26) id AA22930; Mon, 6 Jul 87 20:55:47 PDT Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-iris@sumex-aim.stanford.edu (info-iris@sumex-aim.stanford.edu) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 7 Jul 87 02:23:40 GMT From: kelvin@sally.utexas.edu (Kelvin Thompson) Organization: U. Texas CS Dept., Austin, Texas Subject: Iris RS232 fix Message-Id: <8429@ut-sally.UUCP> Sender: info-iris-request@sumex-aim.stanford.edu To: info-iris@sumex-aim.stanford.edu SYNOPOSIS: Iris documentation apparently does not contain some (potentially) important information about using an Iris' RS232 ports for non-login I/O. Specifically, our documentation (Version 2.0 of Unix 1B) does not describe some tricks you need to know to receive single characters from the serial ports. If you think you might at some time connect an RS232-controlled device (like a video tape recorder controller) to your Iris, you might want to save this note for future reference. There is an example routine at the end of the posting. PREREQUISITES: You'll eventually need to read the TERMIO(7) section of Unix Volume 1B (and some associated passages in Section 2). You probably don't need to read these sections to get a general idea of what I'm talking about. CONTEXT: You wish to hook up a remote, non-login device to one of your Iris' RS232 ports. An application program -- probably running on the console or in background -- will exchange ASCII characters with the device over the serial line. In our case we have a device that controls a Video Tape Recorder. We send certain ASCII characters to the device to make the VTR play and record images and rewind and advance the tape. At the end of each action, the controller sends the Iris a character confirming that the command was completed successfully. PROBLEM: Following the Iris documentation, it is seemingly impossible to receive single characters from the remote device. Depending on how you juggle the terminal modes described in TERMIO(7), you can either buffer all characters through a linefeed, or buffer sets of two or four characters. There seems to be no way to receive a single character sent by the device. SOLUTION: You have to use 'open' to open the RS232 device (/dev/ttyd?). (If you want to use stream I/O, I think you can use 'fdopen' after 'open'.) Then you have to fetch the device's modes using 'ioctl'. The modes will be fetched into a struct of type 'termio', defined in . You then modify this struct with the various modes described in TERMIO(7) to get raw, uninterpreted data from the serial port. Then -- AND THIS IS NOT DOCUMENTED -- you set the 'c_cc[VMIN]' field of the struct to 1. Finally you call 'ioctl' to set the new modes, and you are ready for I/O (or for 'fdopen'). Great thanks to Tom Barton and George Smith of SGI Dallas for tracking down this information. An example function for the Lyon/Lamb VTR controller: /* ************************************ * * * llopen * * * ************************************ DESCRIPTION: Open the serial port '/dev/ttyd1' for I/O to the Lyon/Lamb controller. SIDE EFFECTS: Sets global 'llfile' to the device id. Sets 'llfile' to -1 for some failure types. EXIT: Returns TRUE on success, FALSE for trouble. */ #include #include #define TRUE 1 #define FALSE 0 llopen ( ) { register temp; struct termio termdata; /* try to open the file */ llfile = open( "/dev/ttyd1", O_RDWR ); if ( llfile < 0 ) return FALSE; /* fetch current terminal modes */ temp = ioctl( llfile, TCGETA, &termdata ); if ( temp == -1 ) return FALSE; /* change to the correct modes */ termdata.c_iflag = 0 | IGNBRK /* ignore break signals */ | ISTRIP; /* strip to seven bits */ termdata.c_oflag = 0; /* no special output processing */ termdata.c_cflag = 0 | B300 /* 300 baud */ | CS8 /* 8 data bits */ & ~CSTOPB /* one stop bit */ | CREAD /* enable receiver */ & ~PARENB /* no parity */ | CLOCAL; /* local line (not dialup) */ termdata.c_lflag = NOFLSH; /* no processing */ termdata.c_cc[VMIN] = 1; /* 1-byte buffer -- UNDOCUMENTED */ /* set the modes */ temp = ioctl( llfile, TCSETA, &termdata ); if ( temp == -1 ) return FALSE; return TRUE; } -- -- Kelvin Thompson, Lone Rider of the Apocalypse kelvin@sally.utexas.edu {ihnp4,ctvax,seismo,ucbvax}!ut-sally!kelvin 7-Jul-87 17:58:28-PDT,1143;000000000000 Return-Path: Received: from orville.arpa ([128.102.20.2].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 7 Jul 87 17:57:07 PDT Received: Tue, 7 Jul 87 17:57:23 PDT by orville.arpa (5.51/1.2) Message-Id: <8707080057.AA08556@orville.arpa> To: info-iris@sumex-aim.stanford.edu Subject: GNU on iris's Date: 07 Jul 87 17:57:20 PDT (Tue) From: raible@orville.arpa *** IRIS support in standard GNU emacs *** Starting with version 18.47, standard gnu emacs has iris support. The relevant files are s-iris3-5.h and m-irist.h. There changes to four source files: src/{keyboard,unexec,sysdep,process}.c. These work perfectly work on 2500T's running both 3.5 and 3.6. As far as I know, they should work for 3130's and non-turbo 2500's. Thanks to casetek@crvax.sri.com, seismo!elsie!ncifcrf!randy for their help in debugging early versions of these files. - Eric (raible@ames-nas) PS - the race problem which caused spurious SIGIOTs has been fixed. It was actually caused by the strange semantics of the Iris pty code which doesn't allow a pty to be re-opened once it is closed. 16-Jul-87 09:23:54-PDT,1408;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 16 Jul 87 09:23:39 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa19060; 16 Jul 87 9:10 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa18958; 16 Jul 87 8:55 EDT Received: from WISCVM.WISC.EDU by SMOKE.BRL.ARPA id aa14073; 16 Jul 87 8:47 EDT Received: from DDATHD21.BITNET by wiscvm.wisc.edu ; Thu, 16 Jul 87 07:45:40 CDT Received: from BR2.THD.DA.D.EUROPE by DDATHD21.BITNET via GNET with RJE ; 16 Jul 87 14:20:42 Date: Thu, 16 Jul 87 14:19:08 +0200 (Central European Summer Time) From: Knobi der Rechnerschrat Subject: Problems with dbx To: info-iris@BRL.ARPA X-VMS-To: X%"info-iris@brl.arpa" Message-ID: <8707160847.aa14073@SMOKE.BRL.ARPA> Hallo, we have encountered a strange problem with dbx: A c program compiled with the -g switch had dumped a core file. Typing 'dbx pgmname' at the consoleterminal worked fine. Typing the same command at a TELNET terminal resulted in the following message dbx: fatal error: invalid argument when using the same files 'pgmname' and 'core'. Any suggestions? Is it a known problem? Regards Martin Knoblauch TH-Darmstadt Dept. Physical Chemistry 1 Petersenstrasse 20 D-6100 Darmstadt West-Germany BITNET: 21-Jul-87 22:36:27-PDT,2047;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 21 Jul 87 22:35:43 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa27492; 21 Jul 87 21:13 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa27431; 21 Jul 87 21:03 EDT Received: from aero2.larc.nasa.gov by SMOKE.BRL.ARPA id aa27886; 21 Jul 87 20:59 EDT Received: Tue, 21 Jul 87 08:40:37 EDT by aero2.larc.nasa.gov (5.52/5.17) Date: Tue, 21 Jul 87 08:40:37 EDT From: Walt Halsey x2601 865-1111 ms294 Message-Id: <8707211240.AA11276@aero2.larc.nasa.gov> To: info-iris@BRL.ARPA Subject: Info-Iris mailing list I tried (unsuccessfully) to have my name added to the Info-Iris Mailing list at sumex-aim.stanfor.edu. I received a letter from John Brugge that he could not respond electronically to my mail and that the group had moved to the Ballistics Research Lab. Therefore I am trying again. Please add my name to the Info-Iris Mailing list: Walter F. Halsey Bldg 1229 ms 294 NASA Langley Research Center Hampton, Virginia 23665-5225 We were (and still are) having trouble receiving mail on our IRIS 3030. We can send mail ok but can't seem to get back responses. As soon as we can get some data cartridges, I intend to dump (backup) all of the files from disk and reboot the system from tape. We also seem to have a few problems with errors "segmentation violation" and zapping the kernal. When the machine was first installed, it was powered down nightly by just flipping the power switches and I think the file system is corrupted big time. We now PROPERLY power the system down for weekends as NASA powers down the building to conserve electricity. Hope you can respond to this. We frequently send and receive mail with the Ames computers and I can't figure out why John had a problem from Stanford. By the way, I am sending this from my GOULD supermini because of the above mentioned IRIS problem (receiving). halsey@aero2 21-Jul-87 22:48:17-PDT,695;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 21 Jul 87 22:48:01 PDT Received: from BRL-VMB.ARPA by VMB.BRL.ARPA id aa27770; 21 Jul 87 21:35 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa27625; 21 Jul 87 21:24 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa28382; 21 Jul 87 21:11 EDT Received: from bnl.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 20 Jul 87 14:05:40 PDT Date: Mon, 20 Jul 87 17:06:11 edt From: Ed Thieberger Message-Id: <8707202106.AA24171@bnl.arpa> Received: by bnl.arpa; Mon, 20 Jul 87 17:06:11 edt To: Info-Iris@SUMEX-AIM.Stanford.EDU 21-Jul-87 23:56:59-PDT,1756;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 21 Jul 87 23:56:41 PDT Received: from BRL-VMB.ARPA by VMB.BRL.ARPA id ac27770; 21 Jul 87 21:35 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa27664; 21 Jul 87 21:26 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa28612; 21 Jul 87 21:13 EDT Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 20 Jul 87 16:05:59 PDT Received: by ucbvax.Berkeley.EDU (5.58/1.27) id AA21526; Mon, 20 Jul 87 15:42:57 PDT Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-iris@sumex-aim.stanford.edu (info-iris@sumex-aim.stanford.edu) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 20 Jul 87 21:16:56 GMT From: Michael Cohen Organization: Boston U., Center for Adaptive Systems Subject: Wierd Bug using GNU on SGI machine Message-Id: <553814216.23162@bucasb.bu.edu> Sender: info-iris-request@sumex-aim.stanford.EDU To: info-iris@sumex-aim.stanford.EDU We encountered a strange problem in running GNU on our 3130. If certain users in arbitrary directory did a M-X compile, followed by a make -k, or a M-X shell. The entire computer system hung. We have 32MB swap space for our 170MB disk. I tracked the problem down with the emacs-debugger to a call to the function start_process. The problem was wierd because of its user specificity some users saw it independent of logon time. Our fix was to reload the operating system from cartridge tape which reloaded the root file system. FSCK detected no serious or other anomalies. Any ideas how to track such a problem down 22-Jul-87 00:13:11-PDT,1206;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 22 Jul 87 00:13:02 PDT Received: from BRL-VMB.ARPA by VMB.BRL.ARPA id ab27770; 21 Jul 87 21:35 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa27651; 21 Jul 87 21:25 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa28508; 21 Jul 87 21:12 EDT Received: from bnl.arpa by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 20 Jul 87 14:07:23 PDT Date: Mon, 20 Jul 87 17:07:45 edt From: Ed Thieberger Message-Id: <8707202107.AA24205@bnl.arpa> Received: by bnl.arpa; Mon, 20 Jul 87 17:07:45 edt To: Info-Iris@SUMEX-AIM.Stanford.EDU Subject: stereo vision Hi, Does anyone out there know of an inexpensive stereoscopic viewing system for the IRIS? Stereographics has a system out for ~$12,000. Anyone know of something less expensive? Is $12,000 a reasonable price to pay for such a system? Thanks. Ed ---------------------------------------- Ed Thieberger thieb@bnl.ARPA Applied Math Dept. Brookhaven National Laboratory To iterate is human, to recurse, divine. 23-Jul-87 00:07:30-PDT,2121;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 23 Jul 87 00:07:22 PDT Received: from BRL-VMB.ARPA by VMB.BRL.ARPA id aa12986; 23 Jul 87 1:57 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa12969; 23 Jul 87 1:44 EDT Received: from SUN.COM by SMOKE.BRL.ARPA id aa14147; 23 Jul 87 1:38 EDT Received: from sun.Sun.COM by Sun.COM (4.0/SMI-3.2) id AA19657; Wed, 22 Jul 87 22:39:21 PDT Received: from elvin.sgi.com by sun.Sun.COM (4.0/SMI-4.0) id AA15475; Wed, 22 Jul 87 22:40:51 PDT Received: from elvin.sgi.com by sgi.sgi.com (5.52/870627.vjs) id AA24425; Wed, 22 Jul 87 22:37:18 PDT Received: by elvin.sgi.com (5.51/870627.vjs) id AA00546; Wed, 22 Jul 87 22:40:04 PDT From: Frank Dietrich Message-Id: <8707230540.AA00546@elvin.sgi.com> Date: 22 Jul 1987 2240-PDT (Wednesday) To: info-iris@BRL.ARPA Subject: New Universe at SIGGRAPH The second issue of the IRIS Universe will be out in time for SIGGRAPH'87. Participants of the Second International IRIS User Forum, to be held in Anaheim on Tuesday, July 28, 4:00 - 7:00 pm, will receive their copies fresh off the press. In the Universe you will find a number of articles by presenters at the IRIS User Forum: * Kirk Alexander, Princeton University, Data Visualization * Terry Higgins, National Film Board of Canada Pastel: An RGBA Paint System * Julian Gomez, RIACS, TWIXT: A 3D Animation System * Chuck Dickens, Boeing Computer Services and Creon Levit, NASA Ames, Aerodynamic Simulation & the Interactive Supercomputing Environment Other events at the User Forum include SGI R&D Engineering Panel, a Roundtable discussion with SGI executives and the Software Exchange & Reception. If you can't make it, read the Universe. If you're not already on the mailing list send a note to: dietrich%sgi.com@berkeley.edu. We are again looking for articles, news, and software notes for the fall issue. Be in touch and contribute to the IRIS Universe. See you at SIGGRAPH. Frank Dietrich & Zsuzsanna Molnar 23-Jul-87 08:37:02-PDT,1018;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 23 Jul 87 08:36:50 PDT Received: from BRL-VMB.ARPA by VMB.BRL.ARPA id aa15549; 23 Jul 87 10:02 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa15519; 23 Jul 87 9:54 EDT Received: from [128.89.0.87] by SMOKE.BRL.ARPA id aa25417; 23 Jul 87 9:45 EDT Date: Thu, 23 Jul 87 09:38 EDT From: Jonathan Delatizky Subject: Stereo To: info-iris@BRL.ARPA Message-ID: <8707230945.aa25417@SMOKE.BRL.ARPA> There is also a stereo system called Spacegraph that is available in limited quantities from BBN Laboratories Incorporated. It uses a vibrating mirror to generate a significantly better illusion of 3-D than does the Tektronix, and you don't need any special glasses to see it. I don't know about the availability of IRIS drivers for it, however. If you're interested in learning more, call Larry Sher at (617) 497-3426 (email sher@bbn.com). ...jon delatizky 26-Jul-87 16:08:41-PDT,1522;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Sun, 26 Jul 87 16:08:33 PDT Received: from BRL-VMB.ARPA by VMB.BRL.ARPA id aa06542; 26 Jul 87 18:21 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa06510; 26 Jul 87 18:10 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa13582; 26 Jul 87 18:01 EDT Received: from lindy.stanford.edu by SUMEX-AIM.STANFORD.EDU with TCP; Sun, 26 Jul 87 15:03:00 PDT Received: by lindy.stanford.edu; Sun, 26 Jul 87 14:14:57 PDT Received: by Forsythe.Stanford.EDU; Sun, 26 Jul 87 14:14:08 PDT Received: by PUCC (Mailer X1.24) id 1319; Sun, 26 Jul 87 16:05:56 EDT Date: Sun, 26 Jul 87 16:04:07 EDT From: "Robert L. Wald" Subject: List Removal To: Iris List Message-ID: <8707261801.aa13582@SMOKE.BRL.ARPA> Please remove me from the Info-Iris mailing list. Thanks. I may be listed as 6090617@PUCC instead of RLWALD@PUCC. That was my old account and things get fowarded. P.S. Please acknowledge receipt, outgoing mail is flakey. Thanks. -Rob Wald Bitnet: RLWALD@PUCC.BITNET Uucp: {ihnp4|allegra}!psuvax1!PUCC.BITNET!RLWALD Arpa: RLWALD@PUCC.Princeton.Edu "Why are they all trying to kill me?" "They don't realize that you're already dead." -The Prisoner Acknowledge-To: 28-Jul-87 09:40:32-PDT,1853;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 28 Jul 87 09:40:18 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa22726; 28 Jul 87 10:58 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa22724; 28 Jul 87 10:56 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa25077; 28 Jul 87 10:47 EDT Received: from NMFECC.ARPA ([128.115.3.7].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 28 Jul 87 07:48:42 PDT Received: from fsu.mfenet by ccx.mfenet with Tell via MfeNet ; Tue, 28 Jul 87 07:45:14 PDT Date: Tue, 28 Jul 87 07:45:14 PDT From: MCCALPIN%FSU.MFENET@NMFECC.arpa Message-Id: <870728074515.01d@NMFECC.ARPA> Subject: Encore Annex terminal server To: info-iris@sumex-aim.stanford.EDU Comment: From MCCALPIN@FSU.MFENET on 28-JUL-1987 10:47:11.00 EDT Does anyone out there have experience running an Encore Annex terminal server using an IRIS as the boot/manager host ??? I have just brought up the Annex rev 2.1 software on my 3130 with the 3.5 operating system. The erpc daemon which boots the Annex works fine, as does the IEN-116 nameserver daemon. However, the network administrator program refuses to talk to the Annex - it times out after about 15 seconds. The nice people at Encore are looking into the problem, but they are more used to dealing with 'real' Berkeley O/S's.... P.S The code all works fine on a SUN 3/280 john mccalpin mcalpin@fsu.BITNET mccalpin@fsu.MFENET ( mccalpin%fsu.MFENET@nmfecc.ARPA ) mccalpin@masig1.fsu.edu ( probably not reachable ) 29-Jul-87 07:16:15-PDT,1926;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 07:14:05 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa05970; 29 Jul 87 9:22 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa05949; 29 Jul 87 9:13 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa21290; 29 Jul 87 9:08 EDT Received: from NMFECC.ARPA ([128.115.3.7].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 06:09:06 PDT Received: from fsu.mfenet by ccx.mfenet with Tell via MfeNet ; Wed, 29 Jul 87 06:04:52 PDT Date: Wed, 29 Jul 87 06:04:52 PDT From: MCCALPIN%FSU.MFENET@NMFECC.arpa Message-Id: <870729060452.039@NMFECC.ARPA> Subject: nameservers & such To: INFO-IRIS@SUMEX-AIM.STANFORD.EDU Comment: From MCCALPIN@FSU.MFENET on 29-JUL-1987 08:58:54.80 EDT Does anyone out there know what support exists in the current (3.5) IRIS software for BSD 4.3 domain nameservers? Our site is just getting up on the Internet, and we are installing a domain nameserver on a SUN here. Under real 4.3 BSD, I understand that the gethostbyname() stuff does address resolution by way of the nameservers - what about the IRIS? Also, are the telnet and ftp utilities clever enough to request name translation from a nameserver? Our hosttable is already about 200kB, and I get tired of having to add a node every time someone finds a new site to ftp to (since ftp will not accept numerical IP addresses). I have talked to the Geometry Hotline folks, and no one I found had ever heard of a nameserver before, so maybe I will have some luck in the community at large.... john mccalpin mccalpin@fsu.MFENET mcalpin@fsu.BITNET mccalpin@masig1.fsu.edu (soon!) 29-Jul-87 07:59:58-PDT,1926;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 07:59:23 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa05970; 29 Jul 87 9:22 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa05949; 29 Jul 87 9:13 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa21290; 29 Jul 87 9:08 EDT Received: from NMFECC.ARPA ([128.115.3.7].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 06:09:06 PDT Received: from fsu.mfenet by ccx.mfenet with Tell via MfeNet ; Wed, 29 Jul 87 06:04:52 PDT Date: Wed, 29 Jul 87 06:04:52 PDT From: MCCALPIN%FSU.MFENET@NMFECC.arpa Message-Id: <870729060452.039@NMFECC.ARPA> Subject: nameservers & such To: INFO-IRIS@SUMEX-AIM.STANFORD.EDU Comment: From MCCALPIN@FSU.MFENET on 29-JUL-1987 08:58:54.80 EDT Does anyone out there know what support exists in the current (3.5) IRIS software for BSD 4.3 domain nameservers? Our site is just getting up on the Internet, and we are installing a domain nameserver on a SUN here. Under real 4.3 BSD, I understand that the gethostbyname() stuff does address resolution by way of the nameservers - what about the IRIS? Also, are the telnet and ftp utilities clever enough to request name translation from a nameserver? Our hosttable is already about 200kB, and I get tired of having to add a node every time someone finds a new site to ftp to (since ftp will not accept numerical IP addresses). I have talked to the Geometry Hotline folks, and no one I found had ever heard of a nameserver before, so maybe I will have some luck in the community at large.... john mccalpin mccalpin@fsu.MFENET mcalpin@fsu.BITNET mccalpin@masig1.fsu.edu (soon!) 29-Jul-87 14:57:53-PDT,2358;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 14:56:45 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa10226; 29 Jul 87 14:33 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa10184; 29 Jul 87 14:23 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa05578; 29 Jul 87 14:12 EDT Received: from uxv.larc.nasa.gov by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 11:14:09 PDT Received: Wed, 29 Jul 87 14:16:12 edt by uxv.larc.nasa.gov (4.12/1.2) Date: Wed, 29 Jul 87 14:16:12 edt From: Michael S Fischbein Message-Id: <8707291816.AA08751@uxv.larc.nasa.gov> To: info-iris@SUMEX-AIM.STANFORD.EDU We seem to be having a problem with the tape drives on our 3030's, running GL3.5. During a backup or other tape write (we usually use tar, but the same problem occurs with cpio, cat, and with using a C program) the tape will spontaneously rewind, resulting in an "unexpected end of tape" error. We have been using Scotch DC600A's for almost two years with nary a problem until the last two months (these particular tapes are about six months old. It happens with all available tapes. This problem is occuring on at least two machines. When it occurs, the problem is highly repeatable. Changing the tape, the files being copied, or the machine (when working on system directories that are identical on the two machines) will frequently cancel the problem, or cause it to occur at some other point on the tape. Both tape drives are clean. If a tape has been written successfully, it can be read by either machine. The problem isn't the tape, because the same tape will work on the other machine or on the same machine, but tar-ing a different file system; it isn't the drive because sometimes it works; the disk seems fine, etc, etc. Frankly, I'm stuck, which is why I'm appealing to the net. Does anybody have any ideas? By the way, I tried asking for help on the SGI BBS three weeks ago: no reply. We don't have hardware maintenance, so no hotline requests. mike Michael Fischbein msf@prandtl.nas.nasa.gov ...!seismo!decuac!csmunix!icase!msf These are my opinions and not necessarily official views of any organization. 29-Jul-87 15:20:47-PDT,1501;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 15:20:24 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa11722; 29 Jul 87 16:14 EDT Received: from [192.5.23.3] by VMB.BRL.ARPA id aa11643; 29 Jul 87 15:57 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa09750; 29 Jul 87 15:47 EDT Received: from RELAY.CS.NET by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 29 Jul 87 12:48:43 PDT Received: from relay2.cs.net by RELAY.CS.NET id ab28965; 29 Jul 87 15:44 EDT Received: from eg.ti.com by RELAY.CS.NET id aa07441; 29 Jul 87 15:36 EDT Date: Wed, 29 Jul 87 14:30 CDT From: "Multihack -- lindahl%ngstl1@ti-eg.csnet" Subject: Portable Standard LISP for the IRIS ... To: info-iris@SUMEX-AIM.STANFORD.EDU X-VMS-To: SKACSL::IN%"info-iris@sumex-aim.stanford.edu",LINDAHL Message-ID: <8707291547.aa09750@SMOKE.BRL.ARPA> Hello. This is my first posting to INFO-IRIS --- I hope that this hasn't been asked in another place at an earlier time. Anyway, in the July issue of IEEE SOFTWARE magazine, in an article detailing the porting of Portable Standard LISP to the CRAY, mention was made that an IRIS implementation of PSL has been done. I called our local (Dallas) office, and they hadn't heard of the system. Can somebody please point me at a source of information on this? Thanx, Charlie S. Lindahl Texas Instruments DSEG AI lab 4-Aug-87 07:58:11-PDT,1209;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 4 Aug 87 07:56:56 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa02726; 4 Aug 87 9:52 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa02668; 4 Aug 87 9:35 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa07005; 4 Aug 87 9:23 EDT Received: from lindy.stanford.edu by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 4 Aug 87 06:23:00 PDT Received: by lindy.stanford.edu; Tue, 4 Aug 87 06:22:13 PDT Received: by Forsythe.Stanford.EDU; Tue, 4 Aug 87 06:21:23 PDT Date: Sun, 2 Aug 87 14:27 EST From: FOLEY%GWUVAX.BITNET@forsythe.stanford.EDU MMDF-Warning: Parse error in original version of preceding line at BRL.ARPA Subject: Please delete me To: info-iris@sumex-aim.stanford.EDU X-Original-To: info-iris@sumex-aim.stanford.EDU Message-ID: <8708040923.aa07005@SMOKE.BRL.ARPA> I have enjoyed the IRIS mailings, but don't have a continuing need for them, nor time to read them. Please remove me from the mailing list. Thanks, Jim Foley Dept of EE&CS George Washington University Washington DC 20052 202-994-4952 foley@gwuvax.bitnet 4-Aug-87 20:57:00-PDT,1255;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 4 Aug 87 20:56:53 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa01676; 4 Aug 87 23:03 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa01664; 4 Aug 87 22:49 EDT Received: from [36.10.0.13] by SMOKE.BRL.ARPA id aa29267; 4 Aug 87 22:37 EDT Date: Tue 4 Aug 87 19:35:07-PDT From: Lloyd La Comb Subject: getting more disk space To: info-iris@BRL.ARPA cc: lacomb@Sierra.Stanford.EDU Message-ID: <12323941966.17.LACOMB@Sierra.Stanford.EDU> Does anyone out there know if there is a utility that lets you "squeeze", or "compress" the hard disks on the Iris. Most personal computers have some kind of utitliy that allows you to contatenate all the file fragments together into a continuous file. I currently have about 5-7% of my disk that is unavailable because of the file partitioning. One solution to to backup to tape and then restore it all back, but this is awkward and potentially dangerous. I looked through the Unix manuals but didn't find anything in any of the "obvious" places. Thanks, Lloyd J. La Comb Jr. lacomb@sierra.stanford.edu ------- 5-Aug-87 19:44:34-PDT,1318;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 5 Aug 87 19:44:16 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa00554; 5 Aug 87 19:13 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id ab00509; 5 Aug 87 19:06 EDT Received: from CHEME.TN.CORNELL.EDU by SMOKE.BRL.ARPA id aa00756; 5 Aug 87 18:53 WET DST Date: 5 Aug 87 17:36:00 EST From: "CHEME::OLIN" Subject: Camera software To: info-iris cc: olin@cheme.tn.cornell.EDU Reply-To: "CHEME::OLIN" Message-ID: <8708051853.aa00756@SMOKE.BRL.ARPA> We are about to attach a Matrix camera system to our Iris 3030, and are looking for some software to drive it. Previously we have used the camera with a Grinnell frame buffer attached to our VAX (running VMS); I wrote some software for that but I don't really want to have to port it to the Iris. Has anyone out there done this? If so, would you like to share your experiences/software with us? We will be doing both single images and 16mm animation. Thanks a bunch. Steve Thompson School of Chemical Engineering Cornell University Ithaca NY 14853 (607) 255 4616 thompson@cheme.tn.cornell.edu ------ 17-Aug-87 18:16:18-PDT,2208;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 17 Aug 87 18:15:08 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa27099; 17 Aug 87 19:09 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa27065; 17 Aug 87 18:55 EDT Received: from SUN.COM by SMOKE.BRL.ARPA id aa11718; 17 Aug 87 18:47 EDT Received: from sun.Sun.COM by Sun.COM (4.0/SMI-3.2) id AA05060; Mon, 17 Aug 87 15:42:34 PDT Received: from elvin.SGI.COM by sun.Sun.COM (4.0/SMI-4.0) id AA11191; Mon, 17 Aug 87 15:47:00 PDT Received: from elvin.SGI.COM by sgi.sgi.com (5.52/870809.vjs) id AA25387; Mon, 17 Aug 87 15:39:08 PDT Received: by elvin (5.51/870809.vjs) id AA07583; Mon, 17 Aug 87 15:43:31 PDT From: Frank Dietrich Message-Id: <8708172243.AA07583@elvin> Date: 17 Aug 1987 1543-PDT (Monday) To: info-iris@BRL.ARPA Cc: Subject: Summer Iris Universe is out & fall Universe is in the works Summer Iris Universe out & next Universe in the works! The summer issue of the Iris Universe is out. It was handed out fresh off the press at the International Iris User Forum at SIGGRAPH. If you did not attend you missed some smashing live presentations, but you still can read about most of them in the Universe: Terry Higgins, Nat. Film Board of Canada: Pastel: An RGBA Paint System Kirk Alexander, Princeton: Data Visualization Tools Julian Gomez, Reacs: Twixt, a 3D Animation System plus: Mike Carson, U of Alabama: CG in Crystallography Martin Phlaen, Template: A High-Performance PHIGS Implementation NASA-Ames Software Exchange, Community News, etc. We are planning the fall Universe now. Again, we invite your contributions in the form of text & images. Feel free to tell the community about your work, your programs, and your experiences. Deadline for the fall issue is the middle of September and for the winter issue the end of November. (No exceptions!) We also welcome your comments and suggestions. Let's hear from you. Zsuzsa Molnar (415) 962-3315 Frank Dietrich (415) 494-9019 ucbvax!sgi!zsuzsa ucbvax!sgi!dietrich 25-Aug-87 14:19:55-PDT,1071;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 25 Aug 87 14:19:38 PDT Received: by VMB.BRL.ARPA id aa09401; 25 Aug 87 16:49 EDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa07977; 25 Aug 87 15:26 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa07783; 25 Aug 87 15:14 EDT Received: from FORD-WDL1.ARPA by SMOKE.BRL.ARPA id aa12311; 25 Aug 87 15:07 EDT Received: by FORD-WDL1.ARPA (5.51/5.9) id AA24225; Tue, 25 Aug 87 12:07:31 PDT Date: Tue, 25 Aug 87 12:07:31 PDT From: Rion Cassidy Message-Id: <8708251907.AA24225@FORD-WDL1.ARPA> To: info-iris@BRL.ARPA Subject: erroneous mail Several times now I have gotten mail that was sent to info-iris.BRL.ARPA. How or why it was sent to me, I have no idea, but it must be indicative of a problem that needs to be corrected. The last one I got said From: zyda@nps-cs.arpa To: info-iris.BRL.ARPA Note that my name and address are not mentioned at all, yet I get the mail!! Rion Cassidy 28-Aug-87 13:15:30-PDT,1527;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 28 Aug 87 13:13:31 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa23340; 28 Aug 87 15:16 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa23001; 28 Aug 87 15:02 EDT Received: from GREMLIN.NRTC.NORTHROP.COM by SMOKE.BRL.ARPA id aa26525; 28 Aug 87 14:47 EDT Received: from gremlin by gremlin.nrtc.northrop.com id a000803; 28 Aug 87 11:38 PDT To: info-iris@BRL.ARPA cc: willson@gremlin.nrtc.northrop.COM Subject: .logout file Date: Fri, 28 Aug 87 11:38:11 -0700 From: Stephen Willson Message-ID: <8708281447.aa26525@SMOKE.BRL.ARPA> Attached is the .logout file I use. It kills off mex. It isn't perfect, in that any extra shells in textports invisibly remain. I don't use them that frequently, so it doesn't matter. But it will clean up all the graphics windows you are using. All graphics tools are removed when you logout; the script sleeps for 2 seconds then kills off mex. Silicon graphics should provide a mechanism for doing this properly. Stephen Willson Northrop Corporation willson@nrtc.northrop.com ----cut here--- if ($term == wsiris) clear ismex if ($status == 1 && `tty` == "/dev/console") then # Kill off mex the hard way # This still doesn't get rid of any textports! *Sigh* (sleep 2; kill -9 ` ps x | grep 'mex$' | awk '{print $1}' `) & endif echo -n "logout " $user " "; date; 1-Sep-87 14:27:09-PDT,1056;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 1 Sep 87 14:26:51 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa13389; 1 Sep 87 16:27 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa13327; 1 Sep 87 16:16 EDT Received: from USNA.MIL by SMOKE.BRL.ARPA id aa16030; 1 Sep 87 16:03 EDT Date: Tue, 1 Sep 87 15:57:59 EDT From: "David F. Rogers" To: munnari!cidam.rmit.oz!mg@seismo.css.GOV, alliant!mrmarx!sdr@eddie.mit.EDU, eclrae@USNA.MIL, mbb@portia.stanford.EDU, bnb@xx.lcs.mit.EDU, info-iris@BRL.ARPA cc: dfr@USNA.MIL Subject: Mail!!! Message-ID: <8709011558.aa01051@CAD.USNA.MIL> Hi all, Our Vax 11/780 has been down with hardware problems since 15 August!!! This is the mail machine at USNA. So...you probably have all sorts of bounced mail to me. Please resend if possible. This hardware problems were both 500meg disks and then the LSI-11 boot machine. Sigh .... Thanks, Dave Rogers 2-Sep-87 15:53:25-PDT,1358;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 2 Sep 87 15:53:16 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa03954; 2 Sep 87 17:31 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa03945; 2 Sep 87 17:25 EDT Received: from ZORAC.ARPA by SMOKE.BRL.ARPA id aa14297; 2 Sep 87 17:22 EDT Received: by zorac.ARPA (4.12/25-eef) id AA19623; Wed, 2 Sep 87 11:45:38 edt Received: by dciem.UUCP (smail2.3) id AA03470; 2 Sep 87 11:41:16 EDT (Wed) To: zorac!brl.arpa!Info-Iris@zorac.arpa Subject: precision timing Date: 2 Sep 87 11:41:16 EDT (Wed) From: dciem!tim@zorac.arpa Message-Id: <8709021141.AA03470@dciem.UUCP> I have to write some code for a user-interface experiment. This experiment requires times as precise as possible. Does anybody know of easy way of getting times at least as precise as 1/60th of a second? Does anybody know of a way of getting times down to a 60th which is cleaner (better style and more portable) than either digging into /dev/kmem to look at the "lbolt" variable or examining one of the TIMER valuators? Anybody know why SYS V (as implemented on the IRIS in 2.5/3.5) did away with the "ftime" system call that exists in V7 and 4.2 systems? Tim Pointing, DCIEM tim@zorac.arpa, dciem!tim@zorac.arpa uunet!mnetor!dciem!tim 2-Sep-87 20:57:47-PDT,596;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 2 Sep 87 20:57:40 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa05408; 2 Sep 87 23:07 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa05400; 2 Sep 87 23:02 EDT Date: Wed, 2 Sep 87 22:52:10 EDT From: Phil Dykstra To: dciem!tim@zorac.arpa cc: info-iris@BRL.ARPA Subject: Re: precision timing Message-ID: <8709022252.aa19027@SMOKE.BRL.ARPA> Try gettimeofday(3). It's a BSD routine but the Iris supports it. - Phil 9-Sep-87 00:50:13-PDT,1806;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 9 Sep 87 00:50:04 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa18439; 8 Sep 87 18:51 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa18435; 8 Sep 87 18:42 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa12471; 8 Sep 87 18:38 EDT Date: Tue, 8 Sep 87 15:40:19 PDT From: John Brugge Subject: [DOLATA@jvax.ccit.arizona.edu: Help with Gnuemacs??] To: info-iris@BRL.ARPA Message-ID: <12333074262.57.BRUGGE@SUMEX-AIM.STANFORD.EDU> We no longer use Gnu Emacs (having switched to elle), so don't have a copy readily available on our machine. Anybody have one handy? John --------------- Return-Path: Received: from jvax.ccit.arizona.edu ([128.121.50.100].#Internet) by SUMEX-AIM.STANFORD.EDU with TCP; Sat, 5 Sep 87 17:09:03 PDT Date: Sat, 5 Sep 87 16:55 MST From: DOLATA@jvax.ccit.arizona.edu Subject: Help with Gnuemacs?? To: brugge@SUMEX-AIM.STANFORD.EDU X-VMS-To: IN%"brugge@sumex-aim.stanford.edu" I have an IRIS 3150 which is linked to the outside world only through a 300 baud modem. I would like to bring up GNUemacs on it, but at 300 baud any transfers would take FOREVER. I would like to get a copy of GNUemacs, ready to run on an Iris, on an Iris cartridge tape. Can you help me? If not, could you send this to the mailing list so that a reader could help me? I can either send a tape beforehand if needs be, but it would nice to save time and send one as a replacement or upon mail notification that one has been slipped int he Post, as I am eager to get going! Thanks for your help! Dan Dolata ------- 10-Sep-87 23:26:42-PDT,1095;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 10 Sep 87 23:26:37 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id ab19257; 10 Sep 87 14:04 EDT Received: from ZORAC.ARPA by VMB.BRL.ARPA id aa19228; 10 Sep 87 13:59 EDT Received: by zorac.ARPA (4.12/25-eef) id AA17794; Thu, 10 Sep 87 13:57:24 edt Date: Thu, 10 Sep 87 13:57:24 edt From: Tim Pointing Message-Id: <8709101757.AA17794@zorac.ARPA> To: info-iris@brl-vmb.arpa Subject: scrolling on the IRIS I find it neccessary to have a scrolling window for an experiment that I am writing. Does anybody know of an implementation of Mac-like scroll bars for the IRIS? (I'm using a non-turbo 2400 running GL2.5 if it matters.) Anybody have any other suggestions for being able to pan and scroll a window over a large world-space (reduced scale is not an alternative since this experiment is going to compare several different methods of displaying the data.) Thanks in advance, Tim Pointing, DCIEM tim@zorac.arpa, uunet!mnetor!dciem!tim 10-Sep-87 23:27:31-PDT,1851;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 10 Sep 87 23:27:19 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa20712; 10 Sep 87 15:40 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa20617; 10 Sep 87 15:32 EDT Received: from GELAC.ARPA by SMOKE.BRL.ARPA id aa18336; 10 Sep 87 15:24 EDT Received: by gelac.arpa (4.12/25) id AA29050; Thu, 10 Sep 87 15:20:02 edt Date: Thu, 10 Sep 87 15:20:02 edt From: "Mr. Barry W. Webb" Message-Id: <8709101920.AA29050@gelac.arpa> To: info-iris@BRL.ARPA Subject: Mailing List Addition I would like to be added to the info-iris mailing list and would like to take this opportunity to introduce our facility. Lockheed Aeronautical Systems Company (previously Lockheed-Georgia) is located in Marietta Georgia and builds C-130 and C-5 aircraft. My department (Intelligent Systems) is currently working on a DARPA AI contract titled Pilot's Associate. As part of the simulation environment we have built a cockpit with crt displays and other associated components. The crts are driven by iris computers which are fed data from vaxes, sels and symbolics through an ethernet. Currently we have one 2400, one 2400T, one 3020 and three 3120s. There are other iris computers in the plant and we expect two more machines in the near future. The ethernet is XNS for now with plans to switch to TCP/IP. The iris computers provide a reconfigurable display surface in the cockpit that can be controlled from an expert system running on one of the symbolics. Can't think of much more that would be interesting but I'm sure looking forward to exchanging information with other people with similar interests. Barry Webb Lockheed Aeronautical Systems Company (404)425-6952 bwebb@gelac.arpa 10-Sep-87 23:27:56-PDT,2277;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 10 Sep 87 23:27:50 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa22095; 10 Sep 87 20:20 EDT Received: from [128.102.29.31] by VMB.BRL.ARPA id aa22091; 10 Sep 87 20:15 EDT Received: Thu, 10 Sep 87 17:15:23 PDT by carma.arc.nasa.gov (5.51/1.2) Date: Thu, 10 Sep 87 17:15:23 PDT From: Glenn Meyer Message-Id: <8709110015.AA00695@carma.arc.nasa.gov> To: info-iris@brl-vmb.arpa, tim@zorac.arpa Subject: Re: scrolling on the IRIS > From info-iris-request@brl-vmb.arpa Thu Sep 10 11:21:01 1987 > Received: Thu, 10 Sep 87 11:20:58 PDT by carma.arc.nasa.gov (5.51/1.2) > Received: Thu, 10 Sep 87 11:20:32 PDT by ames-aurora.arpa (5.51/1.2) > Received: from BRL-VMB.ARPA by VMB.brl.ARPA id ab19257; 10 Sep 87 14:04 EDT > Received: from ZORAC.ARPA by VMB.BRL.ARPA id aa19228; 10 Sep 87 13:59 EDT > Received: by zorac.ARPA (4.12/25-eef) > id AA17794; Thu, 10 Sep 87 13:57:24 edt > Date: Thu, 10 Sep 87 13:57:24 edt > From: Tim Pointing > Message-Id: <8709101757.AA17794@zorac.ARPA> > To: info-iris@brl-vmb.arpa > Subject: scrolling on the IRIS > Status: RO > > I find it neccessary to have a scrolling window for an experiment that I am > writing. Does anybody know of an implementation of Mac-like scroll bars > for the IRIS? (I'm using a non-turbo 2400 running GL2.5 if it matters.) > Anybody have any other suggestions for being able to pan and scroll > a window over a large world-space (reduced scale is not an alternative > since this experiment is going to compare several different methods of > displaying the data.) > > Thanks in advance, > Tim Pointing, DCIEM > tim@zorac.arpa, uunet!mnetor!dciem!tim > > --------------------------------------------------------- Dennis Yeo (Software Systems, 1212 Yosemite Avenue, San Jose, Cal. 95126, 408-995-0689), has implemented a very good Mac-like interface manager for two applications that his company sells. One is a text editor, the other an editor for 3D visual databases such as the ones used in flight simulators. You might give him a call, to see whether he'd be willing to unbundle the interface manager. 11-Sep-87 07:29:52-PDT,2439;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 11 Sep 87 07:29:32 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa02099; 11 Sep 87 8:41 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa02058; 11 Sep 87 8:37 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa04238; 11 Sep 87 8:32 EDT Received: from lindy.stanford.edu by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 11 Sep 87 05:33:06 PDT Received: by lindy.stanford.edu; Fri, 11 Sep 87 05:32:53 PDT Received: by Forsythe.Stanford.EDU; Fri, 11 Sep 87 05:31:25 PDT Date: 11 Sep 87 09:31:34 ADT To: info-iris@sumex-aim.stanford.EDU Subject: TCP/IP Help? From: DEDOUREK%UNB.BITNET@forsythe.stanford.EDU Message-Id: We have an IRIS 1400 and a 2400 which are a few years old. Various updates have been made to the hardware and software. At one time, SGI used the XEROX Protocol (XNS?) on the Ethernet. They now apparently use TCP/IP as the standard protocol. I have been asked to determine the feasibility of connecting one or both of our IRIS'S to a TCP/IP Ethernet. Neither system is currently on an Ethernet. What I know: IRIS 1400 has an Ethernet board: Excelan EXOS201 S/N 002636 Assy #9900007-02 rev C Data code 8612 ECN 1095 Chips (ROM?) Marked NX200L NX200H 9520002-00 9520001-00 Rev 4.4 Rev 4.4 IRIS 2400 has an Ethernet board: Excelan EXOS201 S/N 005598 Assy #9900007-02 rev e Data code 8611 ECN 1283 Chips (ROM?) Marked NX200L NX200H 9520002-00 9520001-00 Rev 5.0 Rev 5.0 What I think that I need to know: --Will hardware upgrades be required? (New ROMS?) --What software is required? --Can I check (by looking in directories) whether the XNS or the TCP/IP or neither software is on the systems? Please reply via e-mail to: DEDOUREK@UNBMVS1.BITNET John DeDourek Professor of Computer Science School of Computer Science University of New Brunswick P.O. Box 4400 Fredericton, New Brunswick, CANADA E3B 5A3 (506) 453-4566 Electronic mail: DEDOUREK@UNBMVS1.BITNET -- BITNET/NETNORTH 11-Sep-87 18:41:44-PDT,921;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 11 Sep 87 18:41:33 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa09244; 11 Sep 87 20:04 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa09224; 11 Sep 87 19:58 EDT Received: from NPS-CS.ARPA by SMOKE.BRL.ARPA id aa25291; 11 Sep 87 19:50 EDT Received: by nps-cs.arpa (5.51/5.17) id AA18996; Fri, 11 Sep 87 16:45:33 PST Date: Fri, 11 Sep 87 16:45:33 PST From: michael zyda Message-Id: <8709120045.AA18996@nps-cs.arpa> To: info-iris@BRL.ARPA Subject: shared memory and makeobjs... We are having a problem with our IRIS-3120. If we have an attached shared memory segment and attempt to call gl2 routine 'makeobj', we get a core dump. Does the implementation of objects conflict in some way with shared memory? Michael Zyda (408) 646-2305 14-Sep-87 11:43:53-PDT,984;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 14 Sep 87 11:43:02 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa05315; 14 Sep 87 12:54 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa05236; 14 Sep 87 12:44 EDT Received: from APLPY.ARPA by SMOKE.BRL.ARPA id aa06204; 14 Sep 87 12:32 EDT Received: by aplpy.ARPA (4.12/4.7) id AA08890; Mon, 14 Sep 87 12:33:09 edt Date: Mon, 14 Sep 87 12:33:09 edt From: "Marcus H. Gates" Message-Id: <8709141633.AA08890@aplpy.ARPA> To: info-iris@BRL.ARPA, zyda@nps-cs.arpa Subject: Re: shared memory and makeobjs... When you attach shared-memory where do you attach it? Do you specify the address to attach or do you let the system pick the first available one. If the system picks the first available address, malloc() will no longer work. It could be that makobj tries to use malloc and doesn't properly handle a failed malloc. 14-Sep-87 12:19:03-PDT,1676;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 14 Sep 87 12:18:04 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa05646; 14 Sep 87 13:16 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa05582; 14 Sep 87 13:09 EDT Received: from GREMLIN.NRTC.NORTHROP.COM by SMOKE.BRL.ARPA id aa07219; 14 Sep 87 13:00 EDT Received: from gremlin by gremlin.nrtc.northrop.com id a017513; 14 Sep 87 9:51 PDT To: info-iris@BRL.ARPA cc: willson@gremlin.nrtc.northrop.COM Subject: Triangularization of Polygons Date: Mon, 14 Sep 87 09:51:15 -0700 From: Stephen Willson Message-ID: <8709141300.aa07219@SMOKE.BRL.ARPA> Does anyone have any pointers to the literature which will help me solve the following problem with triangularization of polygons? I can easily triangulate a simple convex polygon: xxxxxxxx x x x x xxxxx But more complicated ones, like this: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx x x x xxxxxxxxxxxxxxx x xxxxxxxxxxxxxxxxx x x x xxxxxxxxx x x x x x x x xxxxxxxxx xxxxxxxxxxxxxxxxx x x x xxxxxxxxxxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx are hard to do. I have a list of edges -- not just the endpoints. Any help will be greatly appreciated. Sincerely, Stephen Hunter Willson, Ph.D. N o r t h r o p Research and Technology Center M.S. 332/T30 Palos Verdes, CA 90274 willson@nrtc.northrop.com (213) 544-5353 14-Sep-87 14:19:41-PDT,1368;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Mon, 14 Sep 87 14:19:12 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa06185; 14 Sep 87 13:59 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa06141; 14 Sep 87 13:57 EDT Received: from FORD-WDL1.ARPA by SMOKE.BRL.ARPA id aa08978; 14 Sep 87 13:49 EDT Received: by FORD-WDL1.ARPA (5.51/5.9) id AA09537; Mon, 14 Sep 87 10:48:37 PDT Date: Mon, 14 Sep 87 10:48:37 PDT From: Rion Cassidy Message-Id: <8709141748.AA09537@FORD-WDL1.ARPA> To: BRUGGE@sumex-aim.stanford.EDU, info-iris@BRL.ARPA Subject: Re: [DOLATA@jvax.ccit.arizona.edu: Help with Gnuemacs??] I have recently seen a lot of discussion about getting gnu emacs on IRIS's as well as questions about having a mouse interface for emacs. We here at Ford Aerospace don't have enough room on our IRIS for gnu emacs (it's a real space hog), but have opted for an editor called 'advanced mouse editor' which is availble from Software Systems in San Jose. The reason I point this out is because I have used vi, gnu emacs, and Unipress emacs, and strongly prefer Software Systems' 'AME' editor over all of them. It's interface is very MacIntosh-like and it only costs about $400. Their phone number is (408)995-0689. Rion Cassidy 15-Sep-87 09:14:28-PDT,1063;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 15 Sep 87 09:14:20 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa05333; 15 Sep 87 10:51 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa05323; 15 Sep 87 10:48 EDT Received: from LINC.CIS.UPENN.EDU by SMOKE.BRL.ARPA id aa00978; 15 Sep 87 10:41 EDT Received: by linc.cis.upenn.edu id AA00583; Tue, 15 Sep 87 10:41:53 EDT Posted-Date: Tue, 15 Sep 87 10:46 EDT Message-Id: <8709151441.AA00583@linc.cis.upenn.edu> Date: Tue, 15 Sep 87 10:46 EDT From: Norm Badler Subject: Willson--triangulation of polygons. To: info-iris@BRL.ARPA The most recent (and complete) reference would be two papers in ACM Transactions on Graphics, April 1984, vol 3, no. 2: "Triangulation and shape complexity" by Chazelle and Incerpi, and "Triangulating simple polygons and equivalent problems" by Fournier and Montuno. Note that "simple" does not mean convex; they do all the cases. Norm Badler 15-Sep-87 20:49:41-PDT,1018;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Tue, 15 Sep 87 20:49:33 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa00454; 15 Sep 87 23:06 EDT Received: from BRAGGVAX.ARPA by VMB.BRL.ARPA id aa00452; 15 Sep 87 23:01 EDT Message-Id: <8709160012.AA24961@braggvax.arpa> To: info-iris@brl-vmb.arpa Subject: Emulating MS-DOS's Print Screen. Suggestions? Date: Tue, 15 Sep 87 20:12:14 EDT From: sigcen@braggvax.arpa Iris Users- Does any one out there have a simple solution for emulating MS-DOS's "PrintScreen" function on an IRIS3020? While we use our Seiko copier for some very expensive graphics screen dumps, we would like to do simple ASCII character screen dumps using our ALPS P2000G dot matrix printers. (We use Advanced Mouse Editor if that helps in describing a solution.) Thank You T.K.Wood US Army Signal Center ATZH-CDC Fort Gordon GA 30905-5090 404-791-3782 (sigcen@braggvax.arpa) 16-Sep-87 01:40:27-PDT,1789;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 16 Sep 87 01:40:19 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa01701; 16 Sep 87 3:38 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa01694; 16 Sep 87 3:32 EDT Received: from WISCVM.WISC.EDU by SMOKE.BRL.ARPA id aa03336; 16 Sep 87 3:28 EDT Received: from DKARH02.BITNET by wiscvm.wisc.edu ; Wed, 16 Sep 87 02:27:47 CDT Date: Wed, 16 Sep 87 09:26 B From: KEMBIOS%DKARH02.BITNET@wiscvm.wisc.EDU MMDF-Warning: Parse error in original version of preceding line at BRL.ARPA Subject: Wanna join the info-iris network To: info-iris@BRL.ARPA X-Original-To: info-iris@brl.arpa, KEMBIOS Message-ID: <8709160328.aa03336@SMOKE.BRL.ARPA> Dear Chuck Kennedy: I have tried e-mail'ing you a message before, but I have never heard if you got it. So, I try again! I would like to join the info-iris network. We have 2 Iris'es in our lab, a 3030 and a 2400. They are used mainly for molecular modelling and display, and for program development. The Iris'es are connected by ethernet to several VAX'es and MicroVAX'es, and to a large number of SUN, PERQ and XEROX workstations in the Computer Science Department. Unfortunately, we are not yet on the UUCP network, however you can e-mail stuff to my BITNET address. Looking forward to hear from you! Regards, Morten Kjeldgaard Biostructural Chemistry Aarhus University Langelandsgade 140 DK8000 Aarhus C DENMARK (voice: +45 6 124633) PS: I would like *very much* to receive the GNU EMACS configuration files for the Iris. Could you send them on the network, or should I contact someone else?? 16-Sep-87 10:21:33-PDT,1073;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 16 Sep 87 10:20:47 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa07592; 16 Sep 87 11:40 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa07454; 16 Sep 87 11:33 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa14750; 16 Sep 87 11:27 EDT Date: Wed, 16 Sep 87 08:27:37 PDT From: Craig Cornelius Subject: Has anybody tried To: info-iris@SUMEX-AIM.STANFORD.EDU Message-ID: <12335092643.20.CORNELIUS@SUMEX-AIM.STANFORD.EDU> the SGI 3115? This is a $25K list price version of the 3020, limited to 8 bit planes. I'm interested in the performance of this vs. other 3000 series machies. ALso, does anyone know it the main memory can be increased over 4 Mbytes? I'd also like to hear about any experiences with CommonLISP of any flavor on the IRIS workstations. In particular, how are performance vs. memory size, bugginess, and support? Craig Cornelius ------- 16-Sep-87 11:23:11-PDT,768;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Wed, 16 Sep 87 11:22:50 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa08727; 16 Sep 87 12:55 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa08545; 16 Sep 87 12:45 EDT Received: from SCUBED.ARPA by SMOKE.BRL.ARPA id aa17005; 16 Sep 87 12:40 EDT Received: from s3mickey (s3mickey.ARPA) by SCUBED.ARPA (1.2/5.20b) id AA04218; Wed, 16 Sep 87 09:42:09 pdt Received: by s3mickey (4.12/5.20b) id AA09269; Wed, 16 Sep 87 09:41:13 pdt Date: Wed, 16 Sep 87 09:41:13 pdt From: Ken Warner Message-Id: <8709161641.AA09269@s3mickey> To: info-iris@BRL.ARPA Subject: remove me from the mailing list ... thanks 17-Sep-87 16:37:15-PDT,1315;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 17 Sep 87 16:36:26 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa25321; 17 Sep 87 18:11 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa25319; 17 Sep 87 18:06 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa24261; 17 Sep 87 17:57 EDT Received: from gremlin.nrtc.northrop.com by SUMEX-AIM.STANFORD.EDU with TCP; Thu, 17 Sep 87 14:58:13 PDT Received: from gremlin by gremlin.nrtc.northrop.com id a017386; 17 Sep 87 10:40 PDT To: Craig Cornelius cc: info-iris@sumex-aim.stanford.EDU, willson@gremlin.nrtc.northrop.COM Subject: Re: Has anybody tried Date: Thu, 17 Sep 87 10:40:14 -0700 From: Stephen Willson Message-ID: <8709171757.aa24261@SMOKE.BRL.ARPA> Hi, I just talked to our sales rep (Jene Cates) a couple of days ago and she told me that due to popular demand the 3115 will be able to go up to 12 bit planes for an extra, uh, $2000.00, or so (give or take $500.00). I found the idea of the machine very attractive until I heard about the 8 bit plane limit -- I am pleased to see that limitation has been removed. -- Stephen Willson Northrop 18-Sep-87 14:53:25-PDT,1381;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 18 Sep 87 14:52:34 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa10015; 18 Sep 87 16:26 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa09949; 18 Sep 87 16:16 EDT Received: from SUMEX-AIM.STANFORD.EDU by SMOKE.BRL.ARPA id aa20225; 18 Sep 87 16:05 EDT Received: from ucbvax.Berkeley.EDU by SUMEX-AIM.STANFORD.EDU with TCP; Fri, 18 Sep 87 13:04:56 PDT Received: by ucbvax.Berkeley.EDU (5.58/1.27) id AA16387; Fri, 18 Sep 87 12:43:50 PDT Received: from USENET by ucbvax.Berkeley.EDU with netnews for info-iris@sumex-aim.stanford.edu (info-iris@sumex-aim.stanford.edu) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 18 Sep 87 17:41:31 GMT From: Adam Beguelin Organization: University of Colorado, Boulder Subject: Windows for Iris 1000 Message-Id: <2253@sigi.Colorado.EDU> Sender: info-iris-request@sumex-aim.stanford.EDU To: info-iris@sumex-aim.stanford.EDU We have an iris 1000 but it doesn't seem to have any software to do windowing. It's connected to a unix machine thru the serial port but it would still be nice to have a windowing environment running on it. Does anyone know of any such software? Thanks, Adam Beguelin adamb@boulder.colorado.edu 20-Sep-87 23:35:10-PDT,1281;000000000000 Return-Path: Received: from BRL-VMB.ARPA by SUMEX-AIM.STANFORD.EDU with TCP; Sun, 20 Sep 87 23:35:02 PDT Received: from BRL-VMB.ARPA by VMB.brl.ARPA id aa18840; 21 Sep 87 1:49 EDT Received: from brl-smoke.arpa by VMB.BRL.ARPA id aa18829; 21 Sep 87 1:39 EDT Received: from [192.5.10.127] by SMOKE.BRL.ARPA id aa11802; 21 Sep 87 1:37 EDT Received: by usc-cse.usc.edu (4.12/S2.5) id AA13589; Sun, 20 Sep 87 22:09:49 pdt Date: Sun, 20 Sep 87 22:09:49 pdt From: "Kevin R. Martin" Message-Id: <8709210509.AA13589@usc-cse.usc.edu> To: bwebb@gelac.arpa, info-iris@BRL.ARPA Subject: Re: Mailing List Addition Barry Webb, Its good to hear about some other simulation labs using IRIS equipment. I work at Hughes Aircraft Co. in Los Angeles and have similar equipment (and problems?). We have a 2400, 2400T, and are getting a 4D system. We have been having problems with XNS to our Vax 8600 and plan to switch to TCP/IP someday. Our pilots associate work has been limited to some small studies that where very interesting. Nothing new on the horizon. Where you at SIGGRAPH 87? What do you think will come out of the realtime users group? I think it will take S.G. to make it worthwhile. Kevin