[Coco] DAC sound output and keyboard input

[Paul Barton]

In the past, I had an 8-bit A/D (game bus connected) and patched BASIC in
the joystick area. It proved that the JOYSTK command processes 8-bits
correctly and returns the unmasked 8-bits for a truly nice JOYSTK. I just
read the JOYSTK(0)/(1) as a regular JOYSTK and the patched
software(firmware) did the monkey jumping (hahaha).
This gave JOYSTK movements that would transverse the whole screen no matter
how big it was.

Paul



On Fri, Jun 20, 2014 at 11:20 AM, Nick Marentes <nickma2 at optusnet.com.au>
wrote:

> On 20/06/2014 10:17 PM, Mark McDougall wrote:
>
>> On 20/06/2014 12:25 AM, John W. Linville wrote:
>>
>>  Bit 7 is JOYIN (the comparator output), used to read the joysticks
>>> (via successive approximation ADC).  You probably should mask that
>>> when you are doing your "any key" check.
>>>
>>
>> Doh! I don't know why I didn't realise this, since I've been staring at
>> the Coco keyboard matrix for weeks now. In my defence, I'm intimately more
>> familiar with the TRS-8 Model I matrix, in which rows are read rather than
>> columns (and you can get all the arrows keys and spacebar in a single read!)
>>
>> All sorted now, thanks!
>>
>> Regards,
>>
>>
> As I said, no need for 6-bit DAC sound if you're only emulating the Apple
> II 1-bit sound.
>
> Maybe use the 6-bit DAC to add joystick control to the game? To dig, with
> the fire button held down, move the joystick left or right to dig left or
> right. Did the Apple II version supprt Apple joysticks?
>
> I could never use the cursor arrow key cluster for player control. I
> always preferred the TRS-80 Model 1 (and CoCo 1/2) arrow key positions for
> game control.
>
> Nick
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>



-- 
Paul T Barton
paultbarton.1944 at gmail.com