Weird Startup Error

Discussion in 'Macintosh Computers' started by CubaTBird, Sep 27, 2004.

  1. macrumors 68020

    Joined:
    Apr 18, 2004
    #1
    Today I turned on my iBook and it started to boot up okay but then I just go to this blue screen and it just hanged there. I could hear the computer some sort of clicking noise (think of someone closeing a pad lock). I forcefully shut the laptop down by holding the power button and then turned it back on again. It works fine now, what does this mean though? I have several important docs on this laptop and can't afford to lose em one day b/c my comp won't start up. Also, it was just a blue screen, no text or anything. :confused:

    Oh yea, also, yesterday I opened up the laptop just to see if their was anything to see inside by taking out the keyboard and then putting it back. Would this have had anything to do with it? I didn't change anything inside the comp itself.
     
  2. macrumors 68040

    Macmaniac

    #2
    It sounds like something hung when you went to startup. Backup your important data and if it happens again talk to someone at Apple, or better take it to an authorized repair store and have them look at it.
    You should always back up regularly even if everything is fine.
     
  3. thread starter macrumors 68020

    Joined:
    Apr 18, 2004
    #3
    so removing the laptop keyboard while the machine was off just to see what was inside the day before this happened prolly has nothing to do with it then?
     
  4. macrumors 68030

    slughead

    Joined:
    Apr 28, 2004
    #4
    PERMISSIONS!

    Whenever my comp does this, a permissions fix always makes it better.
     
  5. macrumors 68040

    Macmaniac

    #5
    No the keyboard should have not effected the system in any way. Try repairing your permissions like slughead said.
     
  6. thread starter macrumors 68020

    Joined:
    Apr 18, 2004
    #6
    yeah, i did the repair permissions thing and it found no errors what so ever. When I get home today, I shall check to see if this problem happens the second time around.
     

Share This Page