Gavin continues at length after Jon, et. al.:

>> Would you agree that some of the functional details
>> of the emulator can be hammered out by open discussion?
>
> Of course I think I know *exactly* how such an emulator
> should work, but feel free to discuss away :-)

My guess is G. really meant ";-)" there, instead of
":-)"..  I say that because I have the audacity to think
that I know what Gavin is thinking about WRT above (and
if I'm wrong expect he will correct me);  i.e.:

There are important details to be worked out WRT license
fees, distribution mechanisms, etc., etc...  But as far
as FUNCTIONAL details of an emulator are concerned, I
have never seen a better description than one Gavin
himself provided on one list or another some months ago:

"Load and go"...  i.e.:

The objective of this emulator would be to PRECISELY
emulate the PA-RISC instruction set. PA-RISC instruction
set is very well known and defined.  Either the emulator
accurately and reliably emulates ALL of the PA-RISC
instructions that MPE ever uses, or it doesn't...  So
WRT functional technical details of emulator operation,
IMO Gavin does indeed know *exactly* how it should work.
:-)

I expect those "other (non-functional) details" will be
more than enough to keep us busy for some time...  Note
I am considering whether or not to implement HPSUSAN and
HPCPUNAME, etc. as essentially non-functional issues.

Ken Sletten