Can't erase Internal memory

Right now, my MPCs internal memory has reached maximum capacity. Viewing the contents in the internal memory, it looks really weird. I have garbled text names for files/programs that are suppose to be there.

Now, when I try to save programs/samples to internal memory to get rid of the crap currently their, I get an error message saying File Too Big, Can't execute. I could have only one same in a single program and it will no longer save or erase anything in the internal memory.

Anyone else have any issues with this?

i have also noticed that when i browse the internal memory theres alot of "programming code" as file names too.

i havent tryed saving to the internal memory tho.

also i wouldnt think its wise to delete those "programming code" files either cos the OS wont run properly.

I dont save to internal memory much at all,but check this, if you try to save a very small sample file,maybe a single snr hit it should be enough for the MPC to execute the save with a file not to big for the error to be
displayed.
you might have aleast a MB or less of memory left that you can use to
recover with, using a file not too big.


Let me know if this help at all.



PEACE.

I tried saving a single snare to a program but it wouldn't save. Before the JJ OS ugrade, I had samples and a program in the internal flash RAM. When the latest JJ OS installed, it appears to add some of JJ's code there in addition to my files. Now the flash memory is maxed and there is no way to replace/erase any of the contents in flash memory.

I just tried what i suggested to you earlier and it did not work on mines.
the only option i got to save to internal memory was ALL PROGRAMS.
my situation is a little different than yours, i have 5.06 on my mpc and
in the past i have n't save much to internal memory. i'm no where close
to max,might be a bug of sorts.

Jahrome, out of curiosity, are you saving to the internal memory because you don't have the internal hard drive installed, or is their some other advantage?

Naw, I have my MPC 2500 maxed out.....internal hard drive, CDM25, and Akai memory.

I was just wondering what's up with the flash memory and this new OS. It doesn't seen right that I have sames in flash that I can no longer erase or save anything to.

You could try going back to an earlier OS, deleting any samples you have there, then reinstalling the latest.

Not sure what you are seeing.
On 5.09 the only thing i see in my Internal is a file called Blank (which is the save all PGM and Samples that I used to erase the factory set) and slots that say Unused.
The JJ O.S. does still allow me to save all pgms and samples to Internal option but when you try to use it the message File to Big Can't Execute comes up.
So it's not just you.
If JJ had to use part of that area for coding storage it would appear this is the way it's being protected.
Maybe it has to do with something like he stored the machine ID and serial number that's tied to the software there.

Jahrome, since you see garbled text, did you by any chance re-install 1.22 and try to access the Internal storage?
If so was it garbled before that?

you would probably find, jj's using all the internal memory for all the added extra's thats in the new os. kind of a compromise, if you know what i mean. i would say he's noticed that most mpc owners max out there mps's (hdd, ram, cd) so the internal memory compromise for the new and far more optioned os (jj's) is quite understandable.

M-CJessop wrote:you would probably find, jj's using all the internal memory for all the added extra's thats in the new os. kind of a compromise, if you know what i mean. i would say he's noticed that most mpc owners max out there mps's (hdd, ram, cd) so the internal memory compromise for the new and far more optioned os (jj's) is quite understandable.

The Internal memory we are referring to is where the factory sounds were stored.
It was never an area that you could use like normal memory so you aren't loosing anything.
This is why Akai never advertised that area as storage.
Based on all the ways the 2500 allows you to save and store loosing that little 5MB is ok.
BUT
if you load 5.04 back it will allow you to save all Programs to the Internal, and that is listed as one of the bug fixes for 5.04 so it more than likely is a bug not something intentional.
It should be reported to JJ as a bug.

the internal memory, has two partitions (no different to any pda's, sd card's, or anything which uses flash memory!) partitions 1: where the OS is stored ALSO the information for the size of partition 2.

now partition 1 can only be accessed by "power-on + function key" to uploaded the OS also the information of how much space the partition 2 is allocated!

now partition 2 can be accessed freely (in other words to can store info on to it) base on how much space it has been allocated.

so you may find that jj has changed the allocation volumes so he can make the OS bigger! by reducing the partition2 so it big enough to have the built in samples but not much more allowing the partition1 tobe bigger.

M-CJessop wrote:
so you may find that jj has changed the allocation volumes so he can make the OS bigger! by reducing the partition2 so it big enough to have the built in samples but not much more allowing the partition1 tobe bigger.

Doesn't look like the case, my internal consist of nothing except one program with one empty sample since you had to save something to erase the internal sounds.
So in other words mine is only contains a few KB and still it will not save and gives the too big message.
It did nothing to change the size of the available since some had the factory sounds while others had changed what was in the Internal.
Yet it will still tell you that any file no matter how small you make it and how empty the Internal on your machine may actually be is too big.
Just looks like a block out not available space.
If I go back to an earlier version like 5.04 it works fine and will save.
I understand what you are talking about on the PDA since my iPAQ alows me to change the allocation my self.

yeah i agree Sovereign, it does look like more of a bug rather than an attempt to resize the OS partition for future upgraded functions, its worth posting the bug up on jj website, achually its been a while since a new upgrade has been posted,

thats not a complaint, just means that theres less and lesser bugs.
great work jj!!!!! and thank you[/i]

Hmm. I've got a load of garbled rubbish in there too.