Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!ncar!boulder!sunybcs!bingvaxu!leah!itsgw!steinmetz!uunet!topologix!devin
From: devin@topologix.topologix.com (Devin Hooker)
Newsgroups: comp.windows.x
Subject: Re: xtrek problem
Message-ID: <173@topologix.topologix.com>
Date: 18 Oct 88 20:30:50 GMT
References: <8810171520.AA28417@ATHENA.MIT.EDU>
Reply-To: devin@topologix (Devin Hooker)
Organization: Topologix Incorporated, Denver CO
Lines: 39

In article <8810171520.AA28417@ATHENA.MIT.EDU> DEG41560@UA1VM.BITNET (Rob Smith) writes:
<
<Hi,
< I have a little xtrek problem, but, it's only a game, so don't knock
<yourself out to answer me.
< I have two Vaxstation 2000's.  They are networked, but they run completly
<separate versions of Ultrix and X10r4.  I just got xtrek.v4 from scam.berkley.
<edu.  It compiles and runs fine.  I've played against a robot successfully.
<
<
< But my machines don't seem to know when there is a player on the other
<machine.
<
	...
< What is the answer?
<
<
<                                             Thanks,
<
<
<                                               Rob.

	If one machine is called foo and the other one bar:

	on foo:  type xhost +bar

	on bar:	 type xtrek -d foo:0.0 &
		      xtrek &

	This will make the two machines recognize one another.  I think that
the two xtreks need to be running on the same CPU to work correctly.

			-Devin
				Hope this helps...
-- 
Devin Hooker
Software Engineer
4860 Ward Rd.
Denver, Co.  80033    (303) 421-7700