Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!psuvax1!psuvm!dxb132
From: DXB132@psuvm.psu.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Help: *@$#%! Joysticks....
Message-ID: <91015.145934DXB132@psuvm.psu.edu>
Date: 15 Jan 91 19:59:34 GMT
References: <`42^3D|@rpi.edu>
Organization: Penn State University
Lines: 15

In article <`42^3D|@rpi.edu>, peck@ral.rpi.edu (Joseph Peck) says:

>will be easy to fix.....  I am *attempting* to be multi-tasking friendly
>and not do anything that will trash other programs running in the
>background.  (Geee, where's Mike Farren when you need him?  I think

I don't see how reading the ports directly is going to "trash" other programs.
Really, I think this is a case of going     overboard in trying to be a
friendly program. (A worthy goal, especially if it's not an arcade-type game).

Kind of reminds me of the long, complicated program in AmigaMail a while back
about how to toggle the LED that could have been done quite nicely with
bchg #1,$bfe001 / rts. What 2.0 REALLY needs is an led.resource....:-) :-) :-)

-- Dan Babcock