Technical questions for the MPC2000xl and the MPC2000
By FK90 Mon Nov 19, 2012 1:51 pm
My MPC still isn't working. I got multiple ZIP disks with either 1.14 or 1.20 on it, but when I insert them (before booting) it still says Insert MPC2000XL Disk! Am I doing something wrong or might there be another problem to my MPC? Please help me, because I'm getting seriously desperate for solutions.
By FK90 Mon Nov 19, 2012 1:58 pm
Maybe it is worth notifying that all the lights on the MPC are on. The first time I booted it 5 minutes ago (since a long time) the screen displayed nothing while all the lights were on.
By FK90 Mon Nov 19, 2012 3:11 pm
Okay, I figured out I didn't have a jumper on the drive. Stupid. So now the MPC boots with an 1.14 OS (which is weird I guess, since I've been told to use 1.20). Now I get in the usual 'menu' where I usually made my beats, but when I insert a 1.20 disk it gives ???? at the LOAD screen and when I boot with this disk, it gives the error again. Do I need to install 1.14 some kind of way?
User avatar
By mr_debauch Mon Nov 19, 2012 7:36 pm
okay, if you got it working with 1.14..... great, leave it at that.
By FK90 Mon Nov 19, 2012 7:42 pm
Yeah, I already discovered that the hard way. Updating to 1.20 worked for a full 10 minutes, then I got the error again with all the numbers. Rebooting fixed this for a couple of times, now all I get is a blank screen and all the LEDs on. I think I have to go back to 1.14, since I read that people have less issues with that. I am only not sure if my card readers is compatible with 1.14
User avatar
By mr_debauch Mon Nov 19, 2012 7:45 pm
FK90 wrote:Yeah, I already discovered that the hard way. Updating to 1.20 worked for a full 10 minutes, then I got the error again with all the numbers. Rebooting fixed this for a couple of times, now all I get is a blank screen and all the LEDs on. I think I have to go back to 1.14, since I read that people have less issues with that. I am only not sure if my card readers is compatible with 1.14


well card readers if they are using the IDE port often are not compatible with 1.14, only with 1.20. Essentially, 1.14 is the full os... but they removed a couple of things from that to have room to include the ide "driver" type information in 1.20... that is all 1.20 is good for.

The jumbled letters probably doesn't have anything to do with the OS..
By FK90 Mon Nov 19, 2012 10:00 pm
My MPC is really trippin the F out right now. For the last couple of hours the screen has been blank and the LEDs were lighting up when booting, so I removed all the components and kept on rebooting, but still with the same result. Now after a while I reassembled everything and still the blank screen came up. Then one time it actually booted normally, but was looking for a data medium (I have the ZIP drive installed, but had no disk in it). Then I put a disk in, but the screen said it was still searching. I rebooted the MPC, this time the screen was all F'ed up, the screen was almost all black. Another reboot resulted into yet another blank screen.

What the F is going on here? I hope this can be fixed without buying anything new, because it is very hard and expensive for me to get anything MPC related here and I'm short on money.
User avatar
By JUKE 179r Mon Nov 19, 2012 10:23 pm
mr_debauch wrote:okay, if you got it working with 1.14..... great, leave it at that.

+1
To anyone else reading this, OS 1.14 lets you partition your Zips discs and CompactFlash cards. OS 1.2 doesn't do this.


FK90 wrote:My MPC is really trippin the F out right now. For the last couple of hours the screen has been blank and the LEDs were lighting up when booting, so I removed all the components and kept on rebooting, but still with the same result. Now after a while I reassembled everything and still the blank screen came up. Then one time it actually booted normally, but was looking for a data medium (I have the ZIP drive installed, but had no disk in it). Then I put a disk in, but the screen said it was still searching. I rebooted the MPC, this time the screen was all F'ed up, the screen was almost all black. Another reboot resulted into yet another blank screen.

What the F is going on here? I hope this can be fixed without buying anything new, because it is very hard and expensive for me to get anything MPC related here and I'm short on money.


Honestly it sounds like something inside your 2000Xl isn't connected correctly. Recheck everything inside for tight, secure connections and that your Zip's IDE cable is inserted correctly.
User avatar
By mr_debauch Mon Nov 19, 2012 11:18 pm
JUKE 179r wrote:Honestly it sounds like something inside your 2000Xl isn't connected correctly. Recheck everything inside for tight, secure connections and that your Zip's IDE cable is inserted correctly.


yes.. take the ram out.. try rebooting a few times... this type of thing happens sometimes for me.. once a year or so.. but it goes away and works fine.
User avatar
By SimonInAustralia Tue Nov 20, 2012 3:20 am
mr_debauch wrote:well card readers if they are using the IDE port often are not compatible with 1.14, only with 1.20. Essentially, 1.14 is the full os... but they removed a couple of things from that to have room to include the ide "driver" type information in 1.20... that is all 1.20 is good for.

JUKE 179r wrote:To anyone else reading this, OS 1.14 lets you partition your Zips discs and CompactFlash cards. OS 1.2 doesn't do this.


So, why do you need to use OS 1.2?

Is it only if your card reader does not work with OS 1.14?

Can some card readers work with OS 1.14, and not need OS 1.2?

What was taken out of OS 1.2?
User avatar
By mr_debauch Tue Nov 20, 2012 7:41 am
SimonInAustralia wrote:
Can some card readers work with OS 1.14, and not need OS 1.2?

What was taken out of OS 1.2?


1) yes

2) I dont know 100% for sure... but I believe it is that atapi and IDE are not quite the same thing... atapi being some sort of protocol, and IDE referring more to the type of physical connection.

some card readers that are atapi may not need 1.20, while IDE card readers that are not atapi require the 1.20 so they can be used as atapi devices... sorry if that doesn't quite make sense or has some technical aspects that are off etc...

scsi for samplers before they went under had some atapi readers that connected to the ide port (as all atapi devices do) and they could make use of 16 and possibly 32 gig cards under 1.14. There is a 1 gig limit with 1.20. this normally would have a 9 gig limit via scsi on any OS I believe....

anyone feel free to correct me if there are wrong parts etc.. or if I have the story wrong.
By FK90 Tue Nov 20, 2012 10:14 pm
After disassembling all the parts and keep on trying and rebooting, it apparently works now. I don't know which part it actually was that was not connected so well, but at least I got it working again. So everybody that helped, I really appreciate it. Thanks.

Now I got 1.14 OS on it again and I'm not sure if I should install my CF reader again. I got a 2 GB card on it, this will only work with 1.20? I rather not go to that OS again, since it really messed my sh*t up. I hope this is more stable. I think I will work with all the ZIP discs I got, even though that will work slower than the CF reader. What would you recommend I should do?
By FK90 Thu Nov 22, 2012 9:11 pm
As of now I still haven't had 10 minutes without the MPC acting weird. It keeps varying from booting normally to booting with a blank screen, mostly the latter and I even keep getting the error with all the numbers. Is there something seriously wrong with the machine? Because I tried reconnecting all the cables and it still does this.

Is there anyone reading this who had the same problem? How did you repair it?
User avatar
By mr_debauch Fri Nov 23, 2012 5:41 am
FK90 wrote:As of now I still haven't had 10 minutes without the MPC acting weird. It keeps varying from booting normally to booting with a blank screen, mostly the latter and I even keep getting the error with all the numbers. Is there something seriously wrong with the machine? Because I tried reconnecting all the cables and it still does this.

Is there anyone reading this who had the same problem? How did you repair it?


try removing the 32 megs of ram if you have it and run off only the stock ram.. see if that makes a difference.