Technical questions for the MPC2000xl and the MPC2000

By hfinal Wed Jun 06, 2007 1:04 pm
How do I change the 2mb ?

By Formant024 Wed Jun 06, 2007 3:01 pm
well, you dont, or shouldnt when you dont have experience and considering its all smd electronics on the print. Below the Intel chip, on the board, is a (i believe) 6 pin jumper which bypasses the machinelanguage command to boot the flashed program stored onto it. Why is there, i think this has to do with the production facility's way of installing the OS during the production process. Akai techs probably use these jumpers for service purposes (read out error data, burn promm).

By mpc3000le Thu Jun 07, 2007 1:45 am
Formant024 wrote:well, you dont, or shouldnt when you dont have experience and considering its all smd electronics on the print. Below the Intel chip, on the board, is a (i believe) 6 pin jumper which bypasses the machinelanguage command to boot the flashed program stored onto it. Why is there, i think this has to do with the production facility's way of installing the OS during the production process. Akai techs probably use these jumpers for service purposes (read out error data, burn promm).


The MPC2000XL main board has a socket present for the purpose of holding an "OS-RECOVERY-ROM".

True that it was used when manufacturing.

Anyone who has obtained an "MPC2000XL-OS-RECOVERY-ROM" from me knows what this is all about.

It is possible for the OS FLASH to become corrupted over time/for no reason/no obvious reason/other un-quantifiable glitches...

Re-loading the OS FLASH via the downloaded file from AKAI's web site doesn't always fix the problem.

Often a clean flash is required and for this a recovery ROM is required.

If the flash still seems corrupt after reloading from the recovery ROM then then the OS can instead be run straight from the recovery ROM.

Rohan.

By 4dahaterz Thu Jun 07, 2007 10:25 pm
well for me... i use to have the problem all the time a few years ago, maybe about 2001 or 2002, but it hasnt done it since... havent seen the screen in some years... but the problem worked itself out, for me anyway