Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!haven!wam!walrus
From: walrus@wam.umd.edu (Udo K Schuermann)
Newsgroups: comp.sys.amiga
Subject: Re: Risk (the game)
Message-ID: <1990Mar29.224543.7921@wam.umd.edu>
Date: 29 Mar 90 22:45:43 GMT
References: <1383@mindlink.UUCP>
Sender: usenet@wam.umd.edu (USENET Posting)
Reply-To: walrus@wam.umd.edu (Udo K Schuermann)
Organization: University of Maryland at College Park
Lines: 17

In article <1383@mindlink.UUCP> a1406@mindlink.UUCP (Elise Tarrant) writes:
>I tried really hard to get Risk onto my harddrive, but failed. I looked at the
>program with CygnusEd and found that there are several text strings which I
>assume are used for loading the various files and they all refer to a volume
>name 'pix:'. I haven't tried changing that right in the program itself, but I
>suspect that may be the only way around booting with the Risk disk.

No! No!  Just put an  ASSIGN PIX: DH0:GAMES/RISK  in your s:startup-sequence
and you're in business.  You'd have to change the executables only if they
referred to a physical device instead of a logical volume.  Remember, F/18
had a bunch of references to "df0:"; once changed to something like "f18:"
along with the proper ASSIGNment, F/18 runs fine off the HD.

Risk does things properly, referring to a volume like PIX:

Udo Schuermann
walrus@cscwam.umd.edu