I didn't wanted to post it here in fear of the thread getting shut down because of double posting. But this matter touches the development of the AKAI OS, the JJ OS for the MPC 1k, 2k500 at least...so I think it's okay, to post it here too...
The following translates into English the comment which JJ obtained from HAYASHI.
JJ is no comment about this.
HAYASHI-> JJ -> MURAI->stan
The comment of HAYASHI
------------------------------------------------------------
I am HAYASHI.
I am not JJ.
The name of JJ is HASEGAWA.
JJ was my assistant.
He wrote a part of code of MPC.
I am not the employee of AKAI.
I am the manager of a software developer.
My company had contracted with AKAI (JP).
I wrote MPC2000, MPC2000XL, and the code of MPC4000, MPC1000, and MPC2500.
These were not necessarily written by only me.
I am only the member of a team.
"Akai professional" was a Japanese company.
November 30, 2005.
AKAI(JP) went bankrupt suddenly.
The engineer of AKAI (JP) lost his job.
I also lost my job.
After one week.
Since the same amount of money as former was paid from AKAI (USA), there was a request "Continue work."
I decided to continue this work.
There were two things for which money is not remitted even if it sends a bill.
I and AKAI (USA) had trouble.
The end of April, 2006.
I sent the bill for April to AKAI (USA).
Money was not remitted even if two week had passed.
There was also no connection.
It was the 3rd time now.
I asked AKAI (USA).
AKAI(USA): -- "discount Pleas whose wages of yours are too high."
I told AKAI(USA) good-bye.
OS (MPC2500) of my last was released immediately.
I was surprised, because I will not do work of AKAI from now on.
But they have released without testing the OS.
Correction of a bug will generate a new bug.
This is repeated and, finally a bug is lost.
It took in three years until OS of MPC2000XL was stabilized.
I do not make a bug intentionally.
A bug is generated even if it does not carry out it.
The number of the bugs of MPC4000 was about 1800.
The number of the bugs of MPC1000 was about 800.
These are the bugs in the middle of development.
These are set to 0 and released.
A new bug is still discovered.
It was required for six more months to stabilize MPC2500.
----------------------------------------------------------------------.
After three weeks June, 2006.
I got to know the bug of "SYSTEM ERROR".
I told the agency (japan) of AKAI (USA) as follows.
USA -- "please correct" -- if it says, I will correct.
However, the reply did not come.
----------------------------------------------------------------------.
[he even broke the MTC on the MPC2500 before he left us].
When a new bug is corrected, it is an everyday occurrence for the portion which was operating normally to break.
AKAI should correct any bugs.
The engineer who went away is irresponsible.
As for MPC1000, two persons' software engineer other than me wrote the code.
They went away two years ago.
The serious bug existed also in the code which they produced.
I corrected them all.
After I go away, the engineer of AKAI should correct.
When asking me for correction of a bug, I corrected it.
You did not do it.
[he stole our code].
I want AKAI (USA) to cancel about this affair.
May, 2006.
AKAI (USA) and AKAI (JP) had fought for the ownership of the OS code.
I do not know whether it was ended whether the argument would continue now.
I had contracted with AKAI (JP).
When was the contract ended?
I think that it is an important problem.
I have not contracted with AKAI (USA).
P.S
I liked work of MPC.
I think that highest MPC2500 was made when continuing.
The staff of MPC is good people.
They love MPC.
It is not their responsibility that a bug is not repaired.
Since AKAI (USA) did not treat me carefully, I went away.
I will not be concerned with MPC from now on.
HAYASHI
I grew up watching "Blood In, Blood Out (Bound By Honor!)"... product of a mis-spent youth watching too many movies!