home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!uwm.edu!rutgers!sgigate!odin!fido!fangio.asd.sgi.com!rck
- From: rck@fangio.asd.sgi.com (Robert Keller)
- Newsgroups: comp.sys.sgi
- Subject: Re: lrectwrite 4.0.5 bug?
- Keywords: lrectwrite, 4.0.5, bug, irritation
- Message-ID: <pniqg98@fido.asd.sgi.com>
- Date: 11 Sep 92 16:58:06 GMT
- References: <craig.716179200@godzilla.cgl.citri.edu.au>
- Sender: news@fido.asd.sgi.com (Usenet News Admin)
- Organization: Silicon Graphics, Inc., Mountain View, CA
- Lines: 22
-
- craig@cgl.citri.edu.au (Craig McNaughton) writes:
- >Situation : 340VGX running 4.0.5 talking to Entry Indigo running 4.0.1
- :
- >It works fine on any local machine, or from a 4.0.5 machine to
- >another 4.0.5 machine, but 4.0.5 to 4.0.1 causes the problems.
-
- When you say "4.0.5 to 4.0.1" do you mean
- - 4.0.5 DGL client to a 4.0.1 DGL server, or
- - using a 4.0.5 GL binary on a 4.0.1 machine?
-
- In either case, situations like this are not guaranteed to work.
- One CAN generally take an IRIX binary from an older release and
- expect it to run on a newer release. One CANNOT, in general,
- take a IRIX binary from a newer release and expect it to run on
- an older version of the Operating System (although in some cases
- it may happen to work).
-
- The same goes for the DGL protocol: Newer DGL servers understand
- older clients, but Newer clients are not guaranteed to be able to
- talk with older servers.
-
- ...robert
-