Macbook pro 13" won't install OS X 10.4 after harddisk erased and dvd will not eject!

Question

Level 1

0 points

Macbook pro 13" won't install OS X 10.4 after harddisk erased and dvd will not eject!

After backing up the machine, I took what I thought was the correct installation disk and booted from the CD/DVD. I erased the hard disk using the Disk Utility. Then I tried to reboot to install the original operating system. After several hours I received the message: Cannot install Mac OS X on this machine. The computer was running 10.4.3 before I erased it. I don't understand why the restore to factory settings didn't work. Now I have another problem. The CD/DVD does not eject. Without an operating system on the hard drive, it automatically boots from the CD/DVD and will not eject the boot disk!

What do I do? How do I get the CD/DVD out? How do I find a good disk

MacBook Pro, Mac OS X (10.4.3)

Posted on Apr 23, 2013 1:27 AM

Reply

Answer 1

BDAqua

Level 10

238,997 points

Apr 23, 2013 10:47 AM in response to mom.iefbr14

Hello, hold the mouse button down while booting up to eject it.

The original Disc would be gray.

If you don't know the model, find the Serial# & use it on one of these sites, but don't post the Serial# here...

http://www.chipmunk.nl/klantenservice/applemodel.html

http://www.appleserialnumberinfo.com/Desktop/index.php

How to find the serial number of your Apple hardware product...

http://support.apple.com/kb/HT1349

Reply

Answer 2

rccharles

Level 6

12,957 points

Apr 23, 2013 12:59 PM in response to mom.iefbr14

Restore Tiger 10.4 & Leopard 10.5 DVDs are available from Apple by calling 800-767-2775 as of January 20, 2013. Have your serial number ready. Have your credit card ready too. There is a small fee.

https://discussions.apple.com/thread/4720126?tstart=0

--------------------------------------------------------------

Any special meaning to iefbr14?

I remember some IBM OS program called something like iefbr14. I forget the first few letters, but ended with br14. BR14 stood for branch regiser 14. It was a lame workaround to allow for file manipulation.

Robert

Reply