Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!aramis.rutgers.edu!remus.rutgers.edu!declan From: declan@remus.rutgers.edu (Declan McCullagh/LZ) Newsgroups: comp.sys.next Subject: Re: NXHost between OS 2.0 and OS 1.0a Summary: Not possible Message-ID: Date: 18 Dec 90 00:25:25 GMT References: <9012171803.AA03446@nextasy2.eecs.wsu.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 19 In article <9012171803.AA03446@nextasy2.eecs.wsu.edu>, schneidj@NEXTASY2.EECS.WSU.EDU (John B. Schneider) writes: > I have had no success using the -NXHost flag on an OS 2.0 machine when > the target machine is an OS 1.0a machine. Am I doing something > incorrectly or are these machines not on speaking terms? (I have no > problem with getting 1.0a machines to behave properly, so that > rules out the obvious explanations like not setting Public Window > Server.) I would think that we should be able to use some 040's as > compute servers for our 1.0a 030's (at least until we receive all our > upgrades). Your second guess was correct - the machines aren't on speaking terms. From ReleaseNotes/AppKit.rtf: You cannot run an application over the network from a 1.0 machine to a 2.0 machine or vice versa (i.e. NXHost only works between machines of the same major release version). Declan McCullagh Independent NeXT Developer