home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!spool.mu.edu!nigel.msen.com!emory!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!bcsystems!spruce.pfc.forestry.ca!news.u.washington.edu!raven.alaska.edu!acad2.alaska.edu!asdmf
- Newsgroups: vmsnet.sources.games
- Subject: Re: Vmsnetrek: Wollingong vs. Multinet
- Message-ID: <1992Nov17.173630@acad2.alaska.edu>
- From: asdmf@acad2.alaska.edu (The Electric Messiah)
- Date: Wed, 18 Nov 1992 02:39:40 GMT
- Reply-To: asdmf@acad2.alaska.edu (The Electric Messiah)
- Sender: news@raven.alaska.edu (USENET News System)
- References: <1992Nov16.111116.1@slacvx.slac.stanford.edu>
- <1992Nov13.140910.1@acad2.alaska.edu> <1992Nov15.163205.3985@arizona.edu> <1992Nov15.151913.1@acad2.alaska.edu>
- Distribution: world,local
- Organization: University of Alaska Anchorage
- Nntp-Posting-Host: acad2.alaska.edu
- Lines: 6
-
- Ok, now what you then will need to do is Change it in the link.com where it
- starts linking the executable to your multinet library specifics...
-
- Where ever your Multinet Library is, just replace the Twg$tcp:[netdist.lib]
- stuff..
-
-