Post your questions, opinions and reviews of the MPC1000. This forum is for discussion of the OFFICIAL Akai OS (2.1). If you wish to discuss the JJ OS, please use the dedicated JJ OS forum
By yunguno Fri Sep 12, 2008 10:53 pm
Hi. i just copped my mpc 1000 and i installed a hynix pin 133 cl3 256 mb ram and a dan elec flash card. now everything works fine ( ram loads perfectly etc). but everytime i record a sample on my mpc it freezes and when i hit a pad an error appears saying "CPU ADDRESS ERROR (read). could the ram be the problem?? do i have to get a new ram? or is the MPC??
User avatar
By distortedtekno Fri Sep 12, 2008 11:41 pm
Remove the RAM and try working with the MPC.
If you don't get any errors, it could be faulty RAM.
But anyway, if the MPC works fine without the RAM, try installing it again. Maybe it's not sitting correctly in the slot. Be careful not to break the plastic on the RAM slot. Be firm but gentle.

Next, make sure to back up any data from the CF card to your computer. Then format the card using the MPC.

You can also try to doing a Factory Reset if you're still getting errors.
If I remember correctly, hold the ERASE button while powering up the MPC.

Let me know if any of this sorts out the problem.

Did you buy your MPC new or used?
By yunguno Sat Sep 13, 2008 3:18 am
hey thanks for the tips. the mpc is BRAND NEW and i dont think the mpc has to do with these errors because the mpc works fine without the ram. i tried everything else you told me but the error appears everytime i hit a pad or record something. im thinking its the ram that doesnt function properly
User avatar
By J-tawn Mon Sep 15, 2008 2:50 pm
yea same shit happen to me.. funny thing is my friend actually did break one of the lil plastic things that hold the card firmly together i got so pissed .. anyway it still seems stable enoguh so now im just gona pick up ram which i ordered from akai to avoid this problem in the future kus if its made by them then there cant me compatability error.. btw my errors came out of no where and it was a different type of error message