[Prev][Next][Index][Thread]

Looking for volunteers with new (ADB Keyboard) NeXT hardware



Dear Folks,

Due to the way we originally wrote our keyboard mapping routines,  
Executor 1.2.1 doesn't work with the new ADB-Keyboard based NeXTs.   
Obviously we need to rewrite our keyboard mapping routines and will  
do so for Executor 1.3 due out in late December.  However, in the  
meantime, we need to have a fix for people who buy the new hardware  
and want to use Executor 1.2.1.

I've written a program, "ExecutorPatcher", which will modify  
Executor, HFS_XFer, and even Executor-DEMO to work with the new  
ADB-Keyboard machines.  I think it will work.  The problem is, there  
don't appear to be any ADB-Keyboard based machines nearby.  Normally  
stuff like this makes a great excuse to pry oneself away from the  
keyboard and drive out to Stone Design, but even Andrew appears to  
not yet have a new machine.

So, if any of you have access to an ADB based machine, please let me  
know, ASAP (best bet is to mail to both  
"iclone!ctm@unmvax.cs.unm.edu" *and* "ctm@ardi.com").  If you already  
have Executor, that will be a win.  If you don't, let me know and  
we'll work something out.  Ability to spend a half hour of Sunday's  
time on this is the best.  I want to get ExecutorPatcher on the  
archives ASAP.  I'll also add a copy of it to our Executor building  
system so new purchasers will automatically have access to it, but I  
have to test it first.

When stripped and compressed, ExecutorPatcher is only 9531 bytes, so  
I should be able to painlessly NeXTmail it to anyone who is  
interested.  It will both patch and unpatch programs, so if you don't  
have an ADB-based system and you want to fiddle with it and give me  
pointers on the user interface, you can do that, but please let me  
know whether or not you'll be able to test it on an ADB based system.

Thanks.

	--Cliff