Problem booting up Mac OS X 10.4.9

I have a mac book pro.. and It was working fine.. and I went to open microsoft word and it froze so I thought it would be a good time to reboot because I hadnt in a week or so and I rebooted and when It booted up, the top tool bar appeared (the part that says like Finder, File, Edit, View - etc but only enough of it to see the Date and time, then the rest of it appeared, then all my desktop icons showed up, then the program menu in the bottom appeared, but I couldnt click anything, then the cursor changed to the spinning circle, then the screen refreshed (everything dissapeared except for my background, then it all appeared again, and it just keeps doing that until I turn it off. I tried doing the fsck thing and it said it repaired everything. The screensaver comes on, everthing appears to be fine so I have no idea what is wrong. I dont want to have to re-install anything bc I dont want to lose my files but I dont have an external harddrive so I want to try to avoid formating unless I have to.
Any idea whats wrong?
Thanks!!

$2,000 + for the machine, but don't have $100 for a bootable, external HD to backup the machine. Not a good choice. Enough of that, boot the machine with the install disk, enter your language, and, when the menu bar pops up, Utilities->Disk Utility and repair the disk and permissions. If it reveals it can't be fixed, then for another $100 get DiskWarrior and fix the HD. If it gives it a clean bill of health, then reinstall the OS selecting the Archive & Install option, saving user and network settings. If that fixes the problem, most likely a corrupted finder prefs file or a conflict with the microsloth stuff, then back the installation up. Once that's done, manually reinstall the latest COMBO and security updates. When you're convinced the OS is stable, delete the Previous System folder, and backup again.

Similar Messages

  • Problem booting Power Mac G4 DA

    Hello,
    Have a G4 PowerMac (DigitalAudio) and can't get it to boot. Here are the specs: G4,1.5Ghz,1GB RAM, MacOS 10.5.4, Superdrive, 6 HD's - 150GB(main),2 IDE 500GB+1 150BG on IDE card,2 SATA 160GB in IDE card, USB&Firewire expansion cards & ATI video card. All was working fine until after a power failure. Started not showing video;replaced the card but the problem is still there. Tested the monitor and cables with another computer and all is OK. Finally showed video, but then a message showed indicating I have to trun the computer off or restart (in gray screen after the wheel spiined for a few seconds. Stopped showing video again & the power button blinked 3 times. Went back to turning on with the restart message in the gray screen, but now shuts the computer off automatically. Flashed the PRAM and did a hard reset, re-started with the install discs and still the same problem. Any ideas? Thanks in advance.

    Tried a new battery? Old Macs respond in all sorts of unexpected ways when the batteries are getting low. The power outage may have forced your computer to use the battery and pushed it over the edge.
    If you have a digital multimeter you can check the condition of your present battery. It should read at least 3.2V if it is the 3.6V half-AA battery type. Ideally this should be measured while the battery is under load; added recommendation from Hans777:
    I have recently found out that an exhausted battery will still indicate >3.6 V with a high internal resistance VM.
    Checking incircuit: powercord disconnected press PMU reset button for >about 5 sec before measuring.
    Checking outside: load the battery with a 1500 Ohm resistor when measuring.

  • Problems booting Mac color

    Hello
    Problems booting Mac color
    I'm a Mac Pro models: MD 313
    System OS: Lion 1.7.4
    My Mac Index (before Apple logo) is blue. I need to be gray?
    Or has a problem with my Mac?
    Please please help? I'm worried.
    Please help with your photos.
    Thanks

    Does it boot?

  • Hey Guys i have a problem with my mac since last month and it wont boot up it freezes in a grey apple logo and and spinning gear any body know how to fix this?

    Hey Guys i have a problem with my mac since last month and it wont boot up it freezes in a grey apple logo and and spinning gear any body know how to fix this?

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
    a. Boot into Recovery by holding down the key combination command-R at the startup chime, or from a local Time Machine backup volume (option key at startup.) Release the keys when you see a gray screen with a spinning dial. When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    How to use and troubleshoot FireWire target disk mode
    c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Before reconnecting an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
    Step 3
    Boot in safe mode.* The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    *Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Post for further instructions.
    When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is damaged and the drive is probably malfunctioning. In that case, go to step 5.
    If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
    If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 4
    Sometimes a boot failure can be resolved by resetting the NVRAM.
    Step 5
    Launch Disk Utility in Recovery mode (see above for instructions.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it produces. Look for the line "Permissions repaired successfully" at the end of the output. Then reboot as usual.
    Step 6
    Boot into Recovery again. When the OS X Utilities screen appears, follow the prompts to reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.
    Step 7
    Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a backup.
    Step 8
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

  • There is a problem on my mac mini. I install windows7 in my mac then i cancelled the installation did not finish..after that i saw the black screen on my monitor..

    There is a problem on my mac mini. I install windows7 in my mac then i cancelled the installation did not finish..after that i saw the black screen on my monitor untill now the monitor is black..

    It maybe trying to boot from the incomplete install.
    Try starting your Mac while holding down the Option key, it should then list all the available boot drives including the Mac OS X one. Boot from the Mac one and then you can wipe the damaged PC one or set the Mac to stay booting in to OS X.

  • Need to boot broken Mac-Mini using retail Snow Leopard 10.6 DVD

    Hi,
    In Summary:
    ==========
    I have Mac Mini (late 2009) which does not boot anymore and I need to install Snow Leopard using retail DVD (version 10.6). The OS/installer from the DVD does not seem to boot either. I always very much appreciate the efforts of true geeks. So please, any casual beginner, please do not demoralize with something like "cannot be done" etc.
    The complete story:
    ==================
    The start of the problem:
    1. All of a sudden, one fine day, on start up, my Mac Mini strated to shut itself down without no apparent reason to me. When trying to boot, it would show a progress bar for about 5 minutes - I am assuming that was disk-consistency check being performed. My best guess is that right after the use of Carbon-Copy Cloner (but I am not 100% sure) it all strated to happen.
    2. Performed Mac's Disk-Util check and [Verify Volume] used to display "invalid directory item count, should be 31 instead of 29". Surface scan said disk hardware is 100% fine. Volume Repair never worked, since OS X was installed on the primary disk. I lost the DVDs that came with this Mac Mini, so the option to boot from that DVD and launch Disk Util etc. was not possible.
    TechTool Pro - No Help:
    3. Started googling and had to choose between [TechTool Pro] and [Disk Warrior], opted for TechTool Pro. Tried its bootable DVD only to learn that TechTool Pro cannot fix it. Again, it's surface scan suggested disk hardware is 100% fine. Sent the details to TechTool Pro support team, they couldn't help either after a couple of e-mails+data exchange. (How do I claim my lost money with TechTool Pro - suggestions appreciated as well).
    Googling / Mac Forums:
    4. Started looking into forums, learnt that someone had successfully repaired this problem using Ubuntu 11.04 install DVD (i.e., without installing the Ubuntu, but just using its 'try from DVD' feature). I had that handy, but forgot to disable HFS+ journaling before attempting to fix the problem. Anyway, attempting volume repair that way couldn't fix the problem as well. However this step took away my ability to boot from Mac.
    5. However using Ubuntu's bootable disk, I could access Mac-HDDs contents - and was able to successfully back-up *all* my important data.
    6. Googled and learnt that just attempting to boot using Ubuntu DVD can take away ability to boot using Mac bootable media - possibly due to EFI internals. Suspecting EFI is now corrupt, I tried other 'hacks' like:
      6.1 eEFIt Boot Disk - which does not work at all,
      6.2 Empire EFI w/ Chameleon - not sure how to proceed with options presented - trying either does not work,
      6.3 Super GRUB2 - boots fine, but attempting to boot from Mac-HDD fails after a couple of seconds,
      6.4 Boot-132 - boots fine, prompt asks for input, but then I cannot eject/replace the DVD due to Mac-Mini (lack of) design,
      6.5 Ubuntu 11.04 / 11.10 - still boots fine - just that I cannot go into Mac-OS-X from here,
      6.6 TechTool Pro bootable DVD - which used to boot fine earlier stopped to boot.
    As you can see, none worked successfully. So I didn't yet try other popular rescue media - as I suspect that is not the direction I need to go into.
    >> Looks like most of my problems are due to the fact that I have Mac-Mini which does not allow eject/replace of DVD from command prompt / out side of Mac-OS-X.
    7. Tried emptying EFI partition, playing with EFI/Mac-OS partitions boot flags, Zapping the PRAM, nothing still allows me to boot either from Mac-HDD or any Mac-Bootable-DVD.
    Current State:
    8. Now while boot time, Mac displays a gray screen for a few seconds, and then a blinking prompt on black background. That's it!
    Snow Leopard 10.6 Retail Install DVD:
    9. Went to Mac store and bought this DVD only to witness that I can't boot from it as well. (This is a huge shocker, how is Apple able to sell these DVDs if these don't work on genuine MacMini itself. After all we are able to boot from and install Windows/Linux on a variety of Machines).
    I am hoping for a very small step/fix that I am missing, since I can still see and access all Mac-HDD contents after booting from Ubuntu bootable DVD. However I am prepared for a good amount of exercise as well - assuming someone posts a valid/verified fix.
    Things available right now:
    ==========================
    A. Genuine Mac-Mini (Late 2009) who lost it's ability to boot either from its HDD or Mac-bootable DVDs (TechTools Pro, Mac OS X retail DVD)
    B. Mac OS X 10.6 Retail DVD
    C. NOT AVAILABLE - DVD that came with this Mac-Mini
    D. Variety of rescue DVDs, listed in section 6 above
    E. Another machine/PC with Ubuntu 11.04 - giving me ability to access internet
    Thanks for reading.
    Zita

    I had a similar discussion recently with another user.
    Your Mac mini (late 2009) originally came with Mac OS X 10.6.2 build 10A432 or build 10C2234 see http://support.apple.com/kb/HT1159 it would have come with an original install disc specific to your model of Mac which you could use to run Disk Utility from or to do a complete reinstall.
    The retail boxed copy of Mac OS X 10.6 (Snow Leopard) was originally intended for older Macs which had previously come with Mac OS X 10.5 or 10.4. It would have on it a version of Mac OS X 10.6 or 10.6.1 which would be able to boot these older Macs, but had no need to boot newer Macs which were released after the launch of Mac OS X 10.6 since all those newer Macs already shipped with their own discs.
    So it is normal that the retail boxed Snow Leopard installer does not work on your model Mac mini. You should be using the one that shipped with your Mac mini instead. I am guessing you have lost it.
    Assuming you have lost the Mac mini original disc, I can suggest the following options to try and workaround this.
    If you have another Mac, an older Mac, one that will be bootable using the retail Snow Leopard install disc you have, you could do either of the following.
    Connect an empty external GUID partitioned hard disk to this other Mac
    Boot from the retail Snow Leopard installer
    Install on to the external disk
    Once the install is complete, update it using the combo update not the one via Software Update to Mac OS X 10.6.8. This will add all the newer drivers needed to allow it to work on your newer Mac mini. You can download this combo update from here http://support.apple.com/kb/DL1399
    You can now disconnect the external drive and connect it to your Mac mini and boot from it by holding down the Option key when you turn the Mac mini on
    or a similar process if you want to wipe the Mac mini and reinstall directly on to it
    Boot the Mac mini in FireWire Target Disk Mode (see http://support.apple.com/kb/ht1661 )
    Connect the Mac mini as an external hard disk to the other older Mac
    Boot from the retail Snow Leopard installer
    Install on to the external disk
    Once the install is complete, update it using the combo update not the one via Software Update to Mac OS X 10.6.8. This will add all the newer drivers needed to allow it to work on your newer Mac mini. You can download this combo update from here http://support.apple.com/kb/DL1399
    You can now disconnect the Mac mini and boot from it as normal
    Note: While the Mac mini is connected in FireWire Target Disk mode to the second Mac, you could backup (if you don't already have a backup) any files you need to retrieve.
    If you don't have a suitable second Mac you may have to either borrow someone else's, or get the help of an Apple Store if one is in your area.

  • How do you boot a Mac Pro hardrive as an external drive on an iMac?

    Hi All,
    I hope you can help me.
    I have a Mac Book Pro. The mother board has died but the hard drive is still working fine according to the technicians.
    I decided not to repair the Mac Book Pro as its quite old and I wanted a bigger screen so I got a new iMac.
    The problem is when the Mac Book Pro died there were two files on the desktop that I had not backed up.
    I know its not a massive problem. But my curiosity has made me wonder if it is possible to plug the Mac Book Pro into the iMac and boot the Mac Book Pro's hard disk as an external disk on the iMac so I can recover the files.
    I'm sure it must be possible. But how?
    Any ideas?
    Thanks in advance.
    Gem

    From what you have said about the disk drive coming from an older Mac, my initial response is no. The odds are that the version of OS X and the drivers on the disk drive from the old MBP will not be able boot the new iMac.
    But do you really need to boot from the old disk drive or just gather the data from it?
    If all you need is the data that should be doable by putting the disk drive in an external enclosure and connecting it to the iMac.

  • Booting two Macs from one external drive: 10.8 and App Store?

    I boot two Macs from one external harddrive. Does this mean that when 10.8 is sold exclusively via the App Store and thereby linked to a unique hardware identifier, I am going to have issues with activation/authentification each time I switch machines? I have avoided the App Store since I discovered that an app I bought there, and which I really needed to open automatically on log-in, had to be manually re-activated with my Apple ID after every switch (so that I eventually deleted it and reverted to an earlier, non-App Store version).

    Welcome to the forum!
      There are a couple of "solutions" to your problem.  The easiest, and possibly the best for you (although it is a bit slower) is to copy your catalog onto the external drive as well.
    Then when you plug in the drive, you will always have your latest catalog for access.
    The other way is to keep a local copy of your catalog, and copy it onto the local drive as a way to transfer it from one computer to the other.
    This has the problem of possibly not being in sync, that is, you forgot to copy it over once and did some editing.  Then you would end up with essentually two different catalogs, instead of one in two places.
      You can copy the catalog either with your OS, or you can "export as catalog" and specify the external drive as the destination.  Then, on your other computer, "import from catalog" and only take the meta-data settings (it's on the import dialog box).
    Personally, when I'm traveling, I have my catalog on my external drive as well.  It just makes life easier, and I don't have to worry about it being out of sync, or losing it (and not the images).
    So, I would go with the first method, at least to start.  To get your catalog over there, you can either export as catalog or copy it, either one will work.
    You can find the location of your catalog file (if you don't know where it is) in the catalog settings menu prompt.  Both the location and the name will be displayed.
    Cheers!

  • Error code -50 on boot partition (Mac OS Extended (Journaled) )

    I`m often experiencing error code -50 when trying to change or move files on boot partition (Mac OS Extended (Journaled) ) on my MacBook PRO 5,5.
    I already know that this error is related to MS-DOS formatted disks. But this one is all the time Mac OS Extended (Journaled).
    All the files are created on Mac OS X 10.6.7 - so there can`t be a problem with a filename.
    Is there another solution than corrupted harddisk?

    while the next error code -50, I looked into Console and kernel says: "BootCache: too many history clusters (151, limit 151)". So that`s the cause of error, but how can I manage with it?
    I tried this one in Terminal
    code:
    /usr/sbin/BootCacheControl stop
    but no success. "-BootCacheControl: could not stop cache: Operation not permitted"
    any ideas?

  • Slow boot time Mac Osx when USB external hard drive is connected

    I have bought some days ago an external hard drive, the Western Digital 500 GB Elements.
    It goes very well by now but I have a problem.
    When I turn on my MBP, after the "bong", I have to wait 60 second more than the normal boot time.
    The screen stay grey and after 60 second it appears the apple.
    It appens only when the external hdd is connected.
    Someone has a solution?

    Some time ago, I read that the OS has a problem waking from sleep or booting if an external was attached (USB or Firewire), something about it being confused about the startup order. Anyway, since then, I have religiously followed this procedure when I'm done using the external: unmount, unplug, and then turn it off (if necessary). I have never experienced a problem with my Mac not recognizing or not being able to boot because of an external. It certainly doesn't involve more than a second or two to unplug a USB drive.

  • How to remove boot options while booting in mac with the options key

    I've just installed windows trough bootcamp, but somethings went little bit wrong,
    Everythings works fine, mac works and windows 7 works properly. But when i hold down the option key while booting i dont have the normal 3 options (Mac, Windows, Mac Restore). I now see these options (MAC, Windows, Windows, Windows efi, mac restore).
    MAC -> works fine
    1e windows -> (error no operating system installed)
    2e windows -> works fine
    3e Efi windows (boots into mac)
    MAc restore -> works fine
    So is there an way to clean up these options?
    Thanks

    You think someone will use Boot Camp Assistant?
    EFI is / was always there. Sometimes it shows up (from using Disk Warrior).
    Windows has its own 100MB system reserved as well that is the boot area.
    I'd start with Lion Recovery, show hidden features and partitions, and check the health of all, and repair HFS volume.
    Also try your Windows DVD and see if it sees a problem.

  • Unable to boot on Mac Os X DVD

    Hi,
    i've bootcamp (lastest version), i use rEFIt to choose from wich partition i'll boot.
    My problem is, can't boot on Mac Os X partition anymore.
    I got the white screen with the Apple logo, and nothing else..
    but i can boot on Windows XP !
    I tried to boot on the Mac OS X DVD (for an authorization check-up), but i can't ! The screen stay grey and nothing happens..
    What can i do ?
    Thanks for your help
    ( sorry for my poor english )

    Consider posting under Boot Camp Public Beta found under the section Windows Compatible Technology, for a quicker response.

  • Very strange hard disk problem - Boot Camp/Windows related?

    On my first gen 1.83 GHz MacBook Pro (now at 10.5.2 with all System Updates applied), I've had Win XP Home installed under Boot Camp (from the very first beta, updated to the release Boot Camp assistant now) for well over a year. At one time about 14 months ago I tried using Parallels, but that used too much battery power, so I deleted Parallels. I don't know whether that left any traces of itself behind.
    More recently I've been amazed at how well VMWare Fusion works on my Mac Pro, so I decided to try it on my laptop. I installed the Fusion application and tried to "adopt" my Boot Camp partition installation of Win XP. I think I goofed and didn't install VMWare tools at the proper moment, because Windows went on a self-directed hunt for drivers after installation, and when I tried to start the virtual machine inside Fusion, Windows told me it needed to be activated by Microsoft and wouldn't even allow me to log in to do the activation.
    Wondering whether there might be some residual of the Parallels "hooks" to Windows contaminating things, I decided just to reinstall Windows.
    I used Boot Camp Assistant to remove the Windows partition. The first clue that something was now amiss was that I decided to reboot the laptop after reclaiming the Windows partition, and when I did so I encountered a black screen with a decidedly "microsoft pre-start up" text message on my screen, something like "press any key to start up from the removable media drive", then "press any key to start up", neither of which would work (even with a bootable disk in the optical drive).
    So, I rebooted holding down the option key and was able to start up Mac OS X 10.5.2. Only one volume was shown now in "About this Mac" and on my desktop, so I ran Boot Camp Assistant again to re-create a Boot Camp partition. UNFORTUNATELY, in the midst of this, I encountered my first ever kernal panic ("windowshade" effect descending down the screen and multiple-language dialog telling me I needed to reboot).
    I rebooted and ran Disk Utility, which told me my partition map was wrong and that I was missing about the amount of disk space I'd allocated to Windows in my previous Boot Camp partition. I thought at THAT point I'd solved my problem - I could just run disk utility from my Leopard startup disk. HOWEVER, the Leopard installation disk will no longer reboot the laptop!
    I confirmed that the problem is not the Leopard installation DVD, because it will boot my Mac Pro and it mounts on the desktop and Disk Utility says it's fine.
    So, I tried to repair my laptop's drive using DiskWarrior 4. That worked (at least it made a new directory, and after it did so, when I boot into the Mac OS, Disk Utility run from the hard drive also says the disk is fine). HOWEVER, the Leopard DVD still won't boot the MacBook Pro. I made one more attempt to create a Windows partition using Boot Camp assistant, and once again generated a kernal panic in the midst of partitioning.
    It seems that I've done something to the stuff on the hard drive that's needed at boot time or partitioning time. I can't erase and reformat the drive, because the Leopard install DVD won't start up the machine. Even though DiskWarrior creates a directory that Disk Utility says is fine, I cannot recreate a Windows partition.
    Any advice what I can or should do next? I can try using the System Install DVD that came with the laptop, or perhaps the system restore DVD, but my bet is they won't start the machine either.
    Please feel free to ask any questions, send me to any other resources, or contact me via email if you have ideas. I have a 10 day business trip beginning Sunday March 30, and I desperately need a working laptop by then.
    Thanks so much.

    "Responding" to my own post: the Install DVD that came with my MacBook Pro will boot it!
    So, I'll try running the earlier version of Disk Utility that came on IT (10.5.4, current Leopard version is 11.0) to repair the MacBook Pro's internal hard drive, THEN see if I can boot from the Leopard install disk (the notion being that I can (groan) recreate a virgin Leopard environment on the laptop with no traces of prior disk formatting nightmares.
    (a few minutes later): the Leopard Installer DVD will now boot the MacBook Pro. As one last attempt to avoid the whole reinstall nightmare, I'll try running Disk Utility from the Leopard Install DVD, and if it passes, make one more attempt to create a boot camp partition on my hard drive. If that doesn't work, next step is to wipe the internal drive and do a clean install of Leopard and all my other necessary stuff.
    Any other ideas?

  • After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.

    After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.
    This is boot camp problem, because in other normal notebooks (e.g. SONY VAIO, Lenovo with Windows 7) the gadgets are working normally.
    I am attaching the screen shot of Desktop Gadgets and Security updates of Windows 7.
    Kindly solve this issue ASAP.
    Shailendra Gupta
    <edited by host>

    You are not addressing Apple, but a community of unpaid volunteers. So ASAP won't cut it. Also, you should refrain from posting personal information (like your email address) in the body of your comments, as this is part of the community usage guidelines.
    Have you reinstalled the latest Boot Camp Windows 7 drivers, just in case Microsoft overwrote some of them during the Windows 7 security update?
    If you want to communicate issues with Apple about Boot Camp and OS X, click on the link. Just don't hold your breath on receiving a response.

  • [SOLVED] MacbookPro 8,1 13" - Dual boot with Mac OS X #rEFIt

    Hi everyone, I want to share my experience and request for help regarding my attempt to install Arch on my MBP 8,1. I can't count the times I've tried to install it this week.
    What have I done?
    So I followed the Beginner's Guide to aid me in the installation, with some exceptions:
    * I used Linux Mint 14 to use GParted. The reason I used it is because rEFIt won't sync the GPT and MBR tables properly when I try and use `mkfs.ext4 /dev/sdaX` inside the Archiso. With Archiso, the filesystem types are considered to be "Unknown" (#wtf no. 1), whereas with Mint that doesn't happen.
    * In fstab I had something like:
    # /dev/sda4
    UUID=c35d9121-a3f1-4cd6-ab53-61fe0f474eee / ext4 rw,noatime 0 1
    # /dev/sda5
    UUID=390185f6-6d55-430c-a9ba-d3d0b4c7798b /home ext4 rw,relatime,codepage=437 0 2
    The wiki mentioned the noatime and codepage flags for the respective partitions and so I complied.
    One thing to notice is I have no /boot mount because syslinux apparently doesn't like that.
    * Installing syslinux (along with gptfdisk), I issued:
    syslinux-install_update -iam
    , and reviewed /boot/syslinux/syslinux.cfg like this:
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    ----APPEND root=/dev/disk/by-uuid/c35d9121-a3f1-4cd6-ab53-61fe0f474eee ro----
    APPEND root=/dev/disk/by-partuuid/c35d9121-a3f1-4cd6-ab53-61fe0f474eee ro **still doesn't work, it's not found**
    INITRD ../initramfs-linux.img
    LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    ----APPEND root=/dev/disk/by-uuid/c35bod9121-a3f1-4cd6-ab53-61fe0f474eee ro----
    APPEND root=/dev/disk/by-partuuid/c35d9121-a3f1-4cd6-ab53-61fe0f474eee ro **still doesn't work, it's not found**
    INITRD ../initramfs-linux-fallback.img
    I used UUID's to avoid the mess on sdaX discrepancies.
    Results
    * rEFIt correctly shows Arch as a boot option. It boots correctly to Syslinux.
    * The kernel load fails due to something like:
    Unknown filesystem 'vfat'
    ... and/or ...
    Waiting 10 seconds for /dev/sdaX ...
    This stroke me as #wtf no.2. VFAT?? Has anyone experienced this before?
    For now this is all I have. I was hoping the community could give me helpful pointers on solving this as I intend to contribute with documentation on this setup in the wiki.
    I'll be updating this post with newer information. Thanks for helping!
    Last edited by josemota (2012-12-31 18:05:09)

    I don't have much experience with SYSLINUX or booting a Mac in BIOS mode, but I can help answer a couple of your questions and offer some alternative approaches....
    josemota wrote:
    Hi everyone, I want to share my experience and request for help regarding my attempt to install Arch on my MBP 8,1. I can't count the times I've tried to install it this week.
    What have I done?
    So I followed the Beginner's Guide to aid me in the installation, with some exceptions:
    * I used Linux Mint 14 to use GParted. The reason I used it is because rEFIt won't sync the GPT and MBR tables properly when I try and use `mkfs.ext4 /dev/sdaX` inside the Archiso. With Archiso, the filesystem types are considered to be "Unknown" (#wtf no. 1), whereas with Mint that doesn't happen.
    This issue is a limitation of the "gptsync" program that's included with rEFIt, not with rEFIt itself. It's also not caused by mkfs; gptsync doesn't even look inside the partitions, AFAIK. Instead, it looks at partition type codes. It understands just a few of them, including the one that all but the very latest versions of libparted use on Linux filesystem partitions. The trouble is that the libparted developers long ago "borrowed" that code from Windows, but they shouldn't have done so. That's being corrected, and gdisk can use the correct code for Linux ("8300" in gdisk). In the future, libparted will use this code, too; the support is already present but isn't yet widely distributed. You could have set the type code to "0700" in gdisk from Arch and gptsync would have worked.
    You may be interested to know that gdisk can do the same job that gptsync does, and gdisk can do so much more flexibly. You can read more in the gdisk hybrid MBR documentation. Be aware that hybrid MBRs (which is what gptsync creates) are ugly and dangerous hacks. Sadly, they're necessary to dual-boot Windows and OS X on Macs, but you may be able to dual-boot OS X and Linux without a hybrid MBR. The trick here is to install an EFI boot loader for Linux rather than a BIOS boot loader for Linux. Macs use EFI natively, so this is the superior way to get started, at least theoretically.
    The Arch wiki has a number of pages on EFI issues, such as:
    https://wiki.archlinux.org/index.php/Un … _Interface
    https://wiki.archlinux.org/index.php/UEFI_Bootloaders
    https://wiki.archlinux.org/index.php/GRUB_EFI_Examples
    The main problem with booting a Mac in EFI mode is that some systems won't activate all their hardware in this way, so with some models you can end up with a network adapter or video display or sound that doesn't work. Other models are fine, though; you'll just have to give it a try and see if it works.
    Personally, I think the best way to do it is to use the kernel's EFI stub loader in conjunction with an EFI boot manager like rEFInd or gummiboot. Both are available as Arch packages, but it's better to install from OS X, and that process is much better documented for rEFInd than for gummiboot (although you could adapt the rEFInd documentation for gummiboot, if you liked). rEFIt can work, too, but only if the kernel includes built-in command-line options and is renamed with a ".efi" extension. These are awkward requirements, and since rEFInd is a continuation of rEFIt development, there's not much point in trying to get rEFIt to do the job.

Maybe you are looking for

  • How to remove a specific Calendar subscription?

    With the upgrade to Mavericks, my U.S. Holiday subscription in Calendar has been duplicated.  So every holiday is shown twice.  I would like to detlete one of them without deleting anything else. I had to happen for moon phases awhile ago and had to

  • Return statement in exception and consequences

    Hi, Can any one give me the explanation for my doubt? Case 1: I am having some code throwing some exception lets say arithematic exception in my try block. I caught it in the catch block and at last I am having one finally? as per normal order try bl

  • Discontinuation indicator in Material Master

    Hello, I am using discontinuation group concept in BOM which replace 1 old material with multiple folloup materials. My system ( ECC5.0) does not display discontinuation indicator 2 ( discontinue group in BOM). As a workaround I am using discontinue

  • SQL Alias for Analysis Server for SharePoint 2013

    Hi  I created a SQL Alias for my Analysis Server but somehow, It is not working. I am frequently using SQL Alias for my SQL database servers within the SharePoint 2013 and it is working correctly. Could you please guide me for this. Regards, Yogendra

  • Multiple Video Clips

    Does DVDSP4 support multiple video clips in a track? It allowed me to add a video clip after the first one but the second clip is black when I play it. This is for a dance recital where i want each section title screen to be separate from the video.