Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!nike!oliveb!glacier!navajo!ali
From: ali@navajo.STANFORD.EDU (Ali Ozer)
Newsgroups: net.micro.amiga
Subject: Re: A crazy (game) program for those who liked Boing! & Oing!
Message-ID: <851@navajo.STANFORD.EDU>
Date: Tue, 23-Sep-86 16:54:51 EDT
Article-I.D.: navajo.851
Posted: Tue Sep 23 16:54:51 1986
Date-Received: Wed, 24-Sep-86 22:29:40 EDT
References: <847@navajo.STANFORD.EDU> <1328@jade.BERKELEY.EDU>
Reply-To: ali@navajo.UUCP (Ali Ozer)
Organization: Stanford University
Lines: 26
Keywords: Negative YaBoing, Task Priority

[]

In article <1328@jade.BERKELEY.EDU> mwm@eris.UUCP (Mike Meyer) writes:
>After a couple a minutes play, I decided I like the negative game
>(catch the green ball, miss the red ones) better. It even scores that
>correctly :-)

Yes, in fact, playing the negative game you have no upper (or shall we
say lower) bound on the score. Playing normally, your high score is limited
to 100 (as only 100 red balls get thrown in). Of the 3 sprites, one is always
assigned to green and the other two red... Thus, you should normally get
50 green balls, with an effective score of -50. BUT, if you're quick enough
and kill green balls as soon as they appear, you can get a lower score.

One question --- I was playing with YaBoing at priority set to various
values, and even crazy ones like -100 and +100. At -100, of course, any
other task pretty much can do whatever it wants... BUT, at +100, we were
doing a diskcopy in the back, and diskcopy failed with "unrecoverable error
in source disk."  Is it possible that because a task was running with a
priority higher than anything else in the system diskcopy actuall screwed
up and also killed the source disk? (Otherwise, running YaBoing at its
default priority, I had no problems using diskcopy or any other task in the
background. In fact, running YaBoing at priority = 100, I was able to do a lot
of things, even disk related, like "list," etc...)

Ali Ozer