Div. Err 3000:00F4

what's that error mean?

don't know about that one specifically..save your work. the mpc 2000xl does crash and regretably you should expect it to crash, save your work everytime you do anything you want to keep. Don't move from screen to screen too fast and watch out w/ heavy-duty use of delay effects on the samples as it seems to crash a bit more often..ill have my 2kxl on all dy long w/ no crashes, then the next day ill load up some cursed sample and it will crash three times in an hour and a half...save your work before you regret it.
peace

incurablebeatlust wrote:don't know about that one specifically..save your work. the mpc 2000xl does crash and regretably you should expect it to crash, save your work everytime you do anything you want to keep. Don't move from screen to screen too fast and watch out w/ heavy-duty use of delay effects on the samples as it seems to crash a bit more often..ill have my 2kxl on all dy long w/ no crashes, then the next day ill load up some cursed sample and it will crash three times in an hour and a half...save your work before you regret it.
peace

couldnt of said it better

I've just loaded samples and wanted to work on them, and that happened. It blocks and i have no other way - just restart it. I have the classic version, but i don't think it makes any difference, i'll try to put more saving to my work scheme.

seuquencing to much midi data, ala sysex can also be a curse.

andrzej00 wrote:what's that error mean?

It's a memory error, troubleshoot your RAM modules to see if one is malfunctioning.

Peace.

"It's a memory error"

Not necessarily. The error is reporting what line of code in the OS that the error occurred. It does not automatically mean that there is a memory error.

I could probably check it and find out the issue, but I doubt it is worth it.

mpc3000 wrote:"It's a memory error"

Not necessarily. The error is reporting what line of code in the OS that the error occurred. It does not automatically mean that there is a memory error.

I could probably check it and find out the issue, but I doubt it is worth it.

According to the service manual, you should troubleshoot the memory first. Try it andrzej00, it can't hurt.

ok. thx.

"According to the service manual, you should troubleshoot the memory first"

Well, it would certainly help if you posted the memory troubleshooting procedure.

mpc3000 wrote:"According to the service manual, you should troubleshoot the memory first"

Well, it would certainly help if you posted the memory troubleshooting procedure.

How do you troubleshoot a memory module or multiple modules. You run each module independently until you're using the one that generates the fault indicated. Of if you're using only one module, have another one on hand to confirm the problem. Make sure you're only using 16 or 32 MB denominations in your unit and that they are 70 ns clock speed.

My apologies mpc3000, next time I make posts that bear your stamp of approval. One reason I'm not a fan of boards is that it's hard to determine intention. I like this board though because people here are helpful, but nonchalance like yours makes me wonder. I hope that the above comment is not a personal insult or swipe at me. Most people will know what troubleshooting is and how to go about doing it. At least I'm trying to help the guy out.

MPC3000 said:
"I could probably check it and find out the issue, but I doubt it is worth it."

If I ever told a customer or one of my corporate contractors some bullshyte like this, I have to close my shop tomorrow. For a guy with almost 1500 posts, You should be the most helpful cats around here. No one I don't know you personally but I got mutual respect for everyone on here. All I would expect is the same. I've seen some of your posts, you go on like you're some kind of Don up in here. Big up talk and answers all over the place. "I have the best sources in the world." "Whatever, you're such a noob, pick up a telephone." "That's a very wrong answer" Who the ass are you? I've seen your pattern of posting on this site and found it very abrasive but hey at least you didn't levie an abrasive post at me...until now.

You want to play big man, that's fine. Your condescending tone might work with others, but don't play that shyte with me. I never finished high school but I have 10 + years experience in my field and manufacturer warranty contracts for 20 large A/V corporations. "I have the best sources in the world"...I'll take a shyte on your sources. You're not talking to some little 16-year-old kid here, I'm a partner in the largest private service depot in the City of Toronto and I am a consummate professional. I don't take shyte from presidents and managers and supervisors and I'm definitely not going to take it from you.

I'm sure that I will be treated with extreme prejudice for lashing out against such a valued member as yourself so let me leave you with this one thought mpc3000. Learn some humility. Learn to be helpful without condesencion. You and those you help will benefit. You may think you know everything but you still got a lot to learn my friend, your deameanor here proves it.

Moderators, you can kill this account.

Peace.

You and no one here are my "customers". No one here owes anyone anything. Don't like the attitude, then complain and beg the moderators to kill my account. I have said that many times before.

"Big up talk and answers all over the place."

Let clarify. I would not consider it "all over the place." I post only under ceratin conditions: 1) Someone else posts wrong, incomplete or misleading information. 2) Technical forums 3) And I am 100% percent sure that I am correct in my answer. I would never need to respond ever again if people were thorough and correct in their answers. If everyone hit home runs, the cleanup batter would have nothing to do. My departure from this forum is in the hands of the other posters.

"Most people will know what troubleshooting is and how to go about doing it."

Apparently you have not been here long. The very reason there are thousands of posts in the technical forum alone is that most people lack basic troubleshooting skills. And this is not necessarily expected of them, as most of them are striving musicians and would rather be making beats than "learning" how to troubleshoot. If you consider "fix the memory" help, then you have got a long way to go to learn what it is actually to help other people.

"Make sure you're only using 16 or 32 MB denominations in your unit"

Correct answers would help. The poster never mentioned which MPC he was referring to. 32 meg modules do not work in the MPC2000. Maybe you know what machine he is using, but someone searching the archives and finding this post is going to think that they can put 32 Meg modules in the MPC2000.

"Whatever, you're such a noob,"

Nice misquote. I suggest you re-read it.

wow

damn it aint that serious tho

LOL CotDamn!