The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    10.5.6 problem

    Discussion in 'Apple and Mac OS X' started by Colton, Dec 20, 2008.

  1. Colton

    Colton Also Proudly American

    Reputations:
    1,253
    Messages:
    2,086
    Likes Received:
    0
    Trophy Points:
    55
    Ok, so when Apple released the update 10.5.6, I was ready to jump on it as soon as I got home. I got on the Apple website, went to the download, and clicked download. It downloaded fine, no problems there, and now it's time to reboot. When I went to reboot, it was about halfway done when I accidently closed my screen, as it is a habit for me to close my screen when I leave my computer. When I opened it back up, it was frozen. I shut it off. Now when ever I turn it on, I get a panic screen. I have tried resetting the Pram, with no avail. Has anybody experienced this? Does anybody know what the problem is, as I am suspecting it is a Kernal Panic. Does anybody know any solutions? Thanks!
     
  2. CanadianDude

    CanadianDude Notebook Deity

    Reputations:
    507
    Messages:
    1,476
    Likes Received:
    2
    Trophy Points:
    56
    I did that once, tried to turn it back on but got the same results as you.

    I just did a cold shut down, (pressed and hold power buttom for 5 secs) until it shut down, then started it back up and it went into the OS and continued with the procedure.

    Not sure why its not working for you
     
  3. Colton

    Colton Also Proudly American

    Reputations:
    1,253
    Messages:
    2,086
    Likes Received:
    0
    Trophy Points:
    55
    Yeah I was assuming that it would just reboot with a cold shutdown, but nothing happened but the same screen. I am worried that it might be something serious enough that I cannot fix it. My only other option is to take it to the Apple Store and get it fixed for a flat fee of $49.95, but I don't want to spend that if I don't really have to.
     
  4. CanadianDude

    CanadianDude Notebook Deity

    Reputations:
    507
    Messages:
    1,476
    Likes Received:
    2
    Trophy Points:
    56
    Try taking the battery out
     
  5. Colton

    Colton Also Proudly American

    Reputations:
    1,253
    Messages:
    2,086
    Likes Received:
    0
    Trophy Points:
    55
    Ok I'll try that.
     
  6. Calzon_V_

    Calzon_V_ Notebook Consultant

    Reputations:
    17
    Messages:
    277
    Likes Received:
    0
    Trophy Points:
    30
    Do you have important information in your hard drive? if not, If it was me, I would rather format and reinstall the Mac OS than paying some cash...
     
  7. Colton

    Colton Also Proudly American

    Reputations:
    1,253
    Messages:
    2,086
    Likes Received:
    0
    Trophy Points:
    55
    I've tried to format the HDD and also reinstall Mac OS X onto it, but halfway through the installation, it will go directly back to the error screen. I'm going to try to restore my HDD back to where it was before I tried to update it using Time Machine, to see if that helps. Thanks for the replies guys!
     
  8. ltcommander_data

    ltcommander_data Notebook Deity

    Reputations:
    408
    Messages:
    1,398
    Likes Received:
    0
    Trophy Points:
    55
    You can also try resetting the SMC. Shut down, take out the power and battery, and hold down the power button for 5 seconds. This is separate from resetting the PRAM.

    Updates that require a restart actually install critical components during the reboot probably because it can't overwrite files when they are in use so they wait to do it on reboot before they load. Sleeping on restart would probably mess up the update and could corrupt the OS. That doesn't explain why you are having trouble reinstalling OS X from scratch though. A corrupt firmware update could explain it, but Apple usually doesn't bundle them with OS updates and keeps them separate to allow people to be more careful with them.
     
  9. Colton

    Colton Also Proudly American

    Reputations:
    1,253
    Messages:
    2,086
    Likes Received:
    0
    Trophy Points:
    55
    I ended up using Time Machine to restore the system to a week ago through my external drive, so things are back to normal for the moment. I'm going to try to install 10.5.6 a bit later, and I'll MAKE SURE that the screen doesn't accidently get closed :p . Thanks for the replies!
     
  10. Paul

    Paul Mom! Hot Pockets! NBR Reviewer

    Reputations:
    759
    Messages:
    2,637
    Likes Received:
    0
    Trophy Points:
    55
    Okay, so I didn't have quite this kind of problem. But ever since the update, my MacBook won't boot to OS X by default. After it's been shut down, when I turn it back on, it goes to a black screen saying "No bootable device found. Insert bootable disk and press any key to continue..." The only way to get into OS X is to hold the option button down when turning it on and manually select Macintosh HD.

    This leads me to believe it's a problem with Boot Camp. I don't have Windows installed, but I tried once. Unfortunately, my spare XP disc was only SP1 so it wouldn't install. So I deleted the Boot Camp partition in OS X, and I didn't notice any problems until after the update, but they could have been there ever since then (I'm not sure if I had actually shut the computer down since the failed attempt). Any ideas on what I can fix?
     
  11. fastrandstrongr

    fastrandstrongr Notebook Evangelist

    Reputations:
    146
    Messages:
    517
    Likes Received:
    0
    Trophy Points:
    30
    Just solved this problem the other day because I was having the same issue following the 10.5.6 install. Go to System Prefs -> Startup Disk -> Select Mac OS X disk. Restart.

    Should do the trick.