MPC5000 reviews, bug reports and fellow user support on the most recent standalone, hardware MPC from Akai
By ibzayalexander Sun Jan 25, 2009 4:55 am
ok so peep this, im using a basically brand new 5k right...and i have it loaded with samples well. i set the utility settings to automatically load the pgm's that are on my CF (compact flash)..someone plz tell me :roll: why the hell are all of my pgm's not loading..on start up when everything is loading i get this error message after that says.."NO MEMORY AVAILABLE"..can any of u tell my i am having to go through this shit. i updated my MPC and everything and it wont even let me load all of my pgm's...its there a doctor in the house.. :?

-Zay
User avatar
By UBANKRECORDS Sun Jan 25, 2009 7:06 pm
It basically means what it's telling you. You put too many files/progs/samples in the autoload folder. It can only load 64MB (unless you have the 128MB expansion bay). Delete some progs/files out of the autoload folder and your problem will be fixed.
By diegoeskryptic Mon Jan 26, 2009 9:31 pm
it can be what Ubank said... or it can be that you didn't read the manual when it said to FORMAT THE CF CARD (via the MPC) BEFORE PUTTING ANYTHING ON IT.

Back-up all your sounds. Format the CF card from the options on the 5k, then put your sounds back on. Should work if theres enough space. Let us know how it goes...
By ibzayalexander Thu Feb 05, 2009 4:07 am
ok i can digg it but this is the weird thing about it, when i go to the utility settings and i change the setting so that it wont load anything at all..i load all of the pgm's manually and it works.. all of the pgms load when i load them anually but wont do it on autoload..is there any explanation for this? i hope this is normal kinda seems odd to me, i mean if i cant load them on autoload..shouldnt i not be able to load them all manually when i dont have my mpc set to autoload??
By diegoeskryptic Thu Feb 05, 2009 4:19 am
prolly some buffer overflow type ish going on. I would submit the error directly to Akai.

For now, just use the workaround you discovered. Hopefully it will benefit others who have the same problem...