[comp.sys.amiga] Problems with cherry keyboard

wizard@sosaria.imp.com (Chris Brand) (05/03/90)

pochron@cat52.cs.wisc.edu (David Pochron) writes:

>My question is this: I have the older Cherry keyboard and it seems to work
>fine if the FASTROM option on SetCPU is disabled; however, when FASTROM is
>enabled, the keyboard gets kinda flakey, repeating keys for the longest time.

The following is a patch that eliminates this. You can only use it after
setcpu fastrom.

begin 777 keyhack
M   #\P         !               Q   #Z0   #%!^0 @   @/ !?__XRX
M/  HLEAG"%6 ;OAP%$YU#)  0 X 9O ,J'@ 1@  !&;F+P@L>0    1R " \X
M    3$ZN_SI*@&8&(%]@ /_.)$ H0"!?6(@CR    +Q'^@ 8,#P $R3;4<C_X
M_%V(,/Q.^2#,< !.=0 H $ . "\ P?S__\'\___!_/__P?S__\'\___!_/__X
MP?S__\'\___!_/__P?S__\'\___!_/__P?S__\'\___!_/__(!].^?____X X
;       #[     $         5@        /RX
 X
end


--
------------------------------------
Chris Brand - wizard@sosaria.imp.com
"Justice is the possession and doing 
of what one is entitled to" - Platon
------------------------------------

daveh@cbmvax.commodore.com (Dave Haynie) (05/04/90)

In article <03698.AA03698@sosaria.imp.com> wizard@sosaria.imp.com (Chris Brand) writes:

>pochron@cat52.cs.wisc.edu (David Pochron) writes:

>>My question is this: I have the older Cherry keyboard and it seems to work
>>fine if the FASTROM option on SetCPU is disabled; however, when FASTROM is
>>enabled, the keyboard gets kinda flakey, repeating keys for the longest time.

>The following is a patch that eliminates this. You can only use it after
>setcpu fastrom.

But be careful.   First, if you're using SetCPU V1.5, you can get it to trick
the keyboard scanning routines by specifying "SetCPU FASTROM KEYPATCH 10" to
start with, and changing the "10" as necessary; larger numbers increase the
patch delay, use the smallest number that works.  This patch was supposed to
work for 1.3 and 1.2, but, well, it's broken under 1.2.  In any case, if you're
using SetCPU V1.5, you'll also find that some of the "KeyHack" programs that
fixed your problem with the SetCPU V1.4 FASTROM don't fix it under SetCPU V1.5.
That's because the ROM image is write protected at both physical and logical 
locations with SetCPU V1.5, but only at the logical ROM address with SetCPU V1.4.
The original KeyHack program written by Jez San snoops out the physical ROM 
images and modifies it; that doesn't work when that image is write protected.

>Chris Brand - wizard@sosaria.imp.com



-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	"I have been given the freedom to do as I see fit" -REM