Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!think!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: Neat Bard'sTale trick ( correction ) : NOT a spoiler
Message-ID: <8708191505.AA07141@cogsci.berkeley.edu>
Date: Wed, 19-Aug-87 11:05:59 EDT
Article-I.D.: cogsci.8708191505.AA07141
Posted: Wed Aug 19 11:05:59 1987
Date-Received: Sat, 22-Aug-87 00:51:15 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 34
Keywords: Bardstale FACC

In article <> oconnor@sunray.steinmetz.UUCP (Dennis Oconnor) writes:
>
>This is such a neat trick, I've got to pass it on ...
>When you leave the BARDSTALE game, you get a CLI. This gives you some
>useful capability in SPITE of the BL**DY COPY-PROTECTION...
>
>1. Boot Bardstale in DF0 :
>2. Leave the game  [you are now in the CLI]

Why not just edit bardstale's startup-sequence file?  Change it:

-from-
bardstale
-to-
run bardstale

Then add "run" to the command directory (copy c:run to bardstale:c)


Bard's Tale leaves the Workbench open with a full CLI.  Since that CLI
is running Bard's tale, you can't multitask.  By adding the run everything
is fixed.
(Except the brain-dead "I hate fast memory".  You will probably need
"nofastmem" to turn off your fast memory.)
(Except for the copy-protection.  Crashes if it can't find it.  If only it
would take a preliminary look and say "hey, where's the disk??" then try
and find the protection.  Twice or more to get the same security without
the "leak" of the requester code (that code would be easy to spot))

-----
|\ /|  . Ack! (NAK, EOT, SOH)
{o O} . 
( " )	bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce
  U	"Success leads to stagnation; stagnation leads to failure."