Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ccicpg!harald
From: harald@ccicpg.UUCP ( Harald Milne)
Newsgroups: comp.sys.amiga
Subject: MIDI
Message-ID: <2633@ccicpg.UUCP>
Date: Fri, 18-Sep-87 03:41:06 EDT
Article-I.D.: ccicpg.2633
Posted: Fri Sep 18 03:41:06 1987
Date-Received: Sat, 19-Sep-87 18:56:24 EDT
Organization: CCI CPD, Irvine CA
Lines: 26
Keywords: Response, Realtime


	I don't understand all this claptrap about Amiga MIDI. From running
tasks in background, that were CPU intensive, and various priorities, I 
concluded the following behaviour of the OS:
	1) Tasks that are CPU intensive with high priority have precedence
	   over tasks of similar nature at a lower priority.
	2) So much so, that similar tasks at a lower priority are effectively
	   locked out.
	3) The Amiga OS doesn't have fairness in mind concerning task
	   priorities. You put it there, it's there. UNIX on the other
	   hand tries to be fair to multiple users. This I consider to be
	   a flaw, becuase of the lockout. A low priority task should RUN
	   sometime. 
	4) Because of this lockout effect, a task set at high enough 
	   priority will do nothing but DO WHAT IT HAS TO DO!


	The bottom line is, with the proper priority, the Amiga will
do nothing else but wait for something to happen! That's realtime in my
book!


-- 
Work: Computer Consoles Inc. (CCI), Advanced Development Group (ADG)
      Irvine, CA (RISCy business! Home of the CCI POWER 6/32)
UUCP: uunet!ccicpg!harald