Unable to boot into OS X 10.6 after uninstalling Bootcamp

I tried a number of times to use bootcamp on my Intel core-duo Imac with OS X 10.6. I had uninstalled and reinstalled bootcamp from the start. Windows XP2 would start-up but then go to a black screen then reboot into the disk check page then start all over again. So I removed boot camp. After I went through the process of undoing the partition the last time I now have to hold down the option key to get the MAC disk to come up, then click on that to go into the OS. It does not show the previous windows partition since I removed it. Something must have been written to the boot sequence which prevents the restart or shut down and restart, to come up properly. I get a black screen with a very fast curser in the upper left corner of the screen. Sometimes it says there is no "system drive" available in white letters near the curser. How do I get the boot sequence to recognize my drive? I don't know to much about how the system works, though I have had this IMAC for about 4 years. Is there a command string and instruction somewhere for fixing this. Any help would be appreciated. I did not use any third party partitioning software. Thank you.

OK, I think I know what happened but don't understand why. When I was trying to use bootcamp. I had set my default drive to the Windows drive, so I didn't have to hold down the option key to go back in and try working on the Windows problem. When I blew it out of there through the disk utility, I never went back and checked it. So it may have been still looking for that drive. When I opened the preferences window as you suggested the only drive that was highlighted was the OS X 10.6 drive. It must of jumped to that when I opened it. There is no windows drive in there but maybe I needed to open that preferences window for the system to correct itself. I didn't click on it since it was already there. Now it does go into the OS X drive when I power it up. So thanks! Appreciate that.

Similar Messages

  • Can't boot into Windows 8.1 partition after apple store repair

    Can't boot into Windows 8.1 partition after apple store repair
    I went to the apple store about a week ago to get my screen fixed, and when I get it back I don't have an option to boot into my windows partition. The bootcamp partition is still there, but I can't boot into it. I can still see all of the files on the drive. When I try to boot into windows from the startup disc setting I get "no bootable device — insert boot disk and press any key” on a black screen. I went in for a dead pixel, and the guy at the genius bar ran something on my computer and went into disk utility application. I’m not sure what he was doing, but obviously that’s what messed up my windows partition. How can I be able to boot back into windows? Here's what disk utility looks like on my computer.

    Here's the output
    00000000  eb 52 90 4e 54 46 53 20  20 20 20 00 02 08 00 00  |.R.NTFS    .....|
    00000010  00 00 00 00 00 f8 00 00  3f 00 ff 00 00 b0 0e 2b  |........?......+|
    00000020  00 00 00 00 80 00 80 00  ff bf 2e 0f 00 00 00 00  |................|
    00000030  00 00 0c 00 00 00 00 00  02 00 00 00 00 00 00 00  |................|
    00000040  f6 00 00 00 01 00 00 00  05 92 d3 74 c4 d3 74 aa  |...........t..t.|
    00000050  00 00 00 00 fa 33 c0 8e  d0 bc 00 7c fb 68 c0 07  |.....3.....|.h..|
    00000060  1f 1e 68 66 00 cb 88 16  0e 00 66 81 3e 03 00 4e  |..hf......f.>..N|
    00000070  54 46 53 75 15 b4 41 bb  aa 55 cd 13 72 0c 81 fb  |TFSu..A..U..r...|
    00000080  55 aa 75 06 f7 c1 01 00  75 03 e9 dd 00 1e 83 ec  |U.u.....u.......|
    00000090  18 68 1a 00 b4 48 8a 16  0e 00 8b f4 16 1f cd 13  |.h...H..........|
    000000a0  9f 83 c4 18 9e 58 1f 72  e1 3b 06 0b 00 75 db a3  |.....X.r.;...u..|
    000000b0  0f 00 c1 2e 0f 00 04 1e  5a 33 db b9 00 20 2b c8  |........Z3... +.|
    000000c0  66 ff 06 11 00 03 16 0f  00 8e c2 ff 06 16 00 e8  |f...............|
    000000d0  4b 00 2b c8 77 ef b8 00  bb cd 1a 66 23 c0 75 2d  |K.+.w......f#.u-|
    000000e0  66 81 fb 54 43 50 41 75  24 81 f9 02 01 72 1e 16  |f..TCPAu$....r..|
    000000f0  68 07 bb 16 68 52 11 16  68 09 00 66 53 66 53 66  |h...hR..h..fSfSf|
    00000100  55 16 16 16 68 b8 01 66  61 0e 07 cd 1a 33 c0 bf  |U...h..fa....3..|
    00000110  0a 13 b9 f6 0c fc f3 aa  e9 fe 01 90 90 66 60 1e  |.............f`.|
    00000120  06 66 a1 11 00 66 03 06  1c 00 1e 66 68 00 00 00  |.f...f.....fh...|
    00000130  00 66 50 06 53 68 01 00  68 10 00 b4 42 8a 16 0e  |.fP.Sh..h...B...|
    00000140  00 16 1f 8b f4 cd 13 66  59 5b 5a 66 59 66 59 1f  |.......fY[ZfYfY.|
    00000150  0f 82 16 00 66 ff 06 11  00 03 16 0f 00 8e c2 ff  |....f...........|
    00000160  0e 16 00 75 bc 07 1f 66  61 c3 a1 f6 01 e8 09 00  |...u...fa.......|
    00000170  a1 fa 01 e8 03 00 f4 eb  fd 8b f0 ac 3c 00 74 09  |............<.t.|
    00000180  b4 0e bb 07 00 cd 10 eb  f2 c3 0d 0a 41 20 64 69  |............A di|
    00000190  73 6b 20 72 65 61 64 20  65 72 72 6f 72 20 6f 63  |sk read error oc|
    000001a0  63 75 72 72 65 64 00 0d  0a 42 4f 4f 54 4d 47 52  |curred...BOOTMGR|
    000001b0  20 69 73 20 63 6f 6d 70  72 65 73 73 65 64 00 0d  | is compressed..|
    000001c0  0a 50 72 65 73 73 20 43  74 72 6c 2b 41 6c 74 2b  |.Press Ctrl+Alt+|
    000001d0  44 65 6c 20 74 6f 20 72  65 73 74 61 72 74 0d 0a  |Del to restart..|
    000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    000001f0  00 00 00 00 00 00 8a 01  a7 01 bf 01 00 00 55 aa  |..............U.|
    00000200
    Here's a better screenshot.

  • [SOLVED]Unable to boot into the kernel I compiled, kernel panic

    I try to compile a kernel myself and boot into it, and I use virtualbox to test it. (arch guest inside my arch host)  I first copy /proc/config.gz of my guest system to the linux source code directory, rename it to .config, and just compile it. After that I copy the image under arch/x86/bzImage to /boot directory, then I follow the instruction given by the arch wiki to create an entry in grub. Here is my /etc/grub.d/40-custom:
    #!/bin/sh
    exec tail -n +3 $0
    menuentry 'Custom Entry' {
    set root=(hd0,msdos1)
    echo 'Loading Modified Linux'
    linux /boot/vmlinuz-modified
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    following is this command:
    grub-mkconfig -o /boot/grub/grub.cfg
    But after reboot I cannot boot into the new kernel, it shows "unable to mount root fs on unknown-block(0,0):
    https://img.vim-cn.com/e5/5227d8d4cc07c … ce81ee.png (choose "Advanced Option for Archlinux-> With Linux Modified")
    https://img.vim-cn.com/a9/12869edfbbca1 … 649380.png (choose "Custom Entry" on the first page directly)
    I have searched for a while but didn't find a solution. Is there anything I'm doing wrong, please?
    Last edited by Frefreak (2015-05-07 10:48:05)

    Head_on_a_Stick wrote:
    Frefreak wrote:I think I did compress it, if I remember correctly. (I actually built it several times)
    I am referring to /proc/config.gz -- this is a gzip archive and needs to be decompressed before you can use it to compile your kernel image.
    This isn't strictly true, it just makes the process easier because you're starting with a sane .config (assuming you're booted into one of Arch's official kernels at least). You can start from scratch, but you need to know what you're doing.
    Frefreak wrote:Ok, I'll rebuild everything from the beginning later.
    No need to rebuild everything, just generate an initramfs for the custom kernel. The initramfs contains modules that are specific to a the kernel image that they were generated for; this is probably why /boot/initramfs-linux.img isn't working for you.

  • Unable to boot into Windows 7

         Hello, today I was playing some video games inside of Windows 7, upon noticing that whenever the computer had an area that text could be entered, it would spam the space bar into that area. Ex. when i would hit the start menu, in the little text box that is for searching, the courser would move continuously across it, as if the space bar was being pressed. So I restarted. As normal when I heard the startup chime i pressed and held the option key to bring up the OS selection tab. But instead of bringing up the menu, it booted straight to OSX. (i tried this a few times with the same results). So I went into the bootcamp menu in settings on osx and selected windows as the startup OS. I then restarted. When the computer started up I was prompted to select Windows 7 to continue the boot process, so I did. It then went to the starting windows screen where it became stuck. I force shut down and tried again, but this time i tried to repair the disk in windows. The first time it failed to repair, then i did a memory test and when it restarted it worked. In windows i told bootcamp to use OSX as the startup disk and tried holding down option to go back to windows again, nothing, it went to osx. So in osx i went into the bootcamp menu in settings again, and selected windows and restarted. It got stuck on the selection screen in windows and i force shut down and tried again, but this time with with repair again. This time the repair was successful and it went to windows normally. So now it appears that i can only boot into windows by telling bootcamp that i want to boot into windows automatically.  Holding down the option key does not seem to bring up the disk selector. I can verify that the option key does work because i tried 'command+option+esc" and it worked. any ideas on what the frik is going on?

    Update! So apparently I believe the problem is coming from a few windows updates that are out. Whenever I repaired the disk it always uninstalled those updates. I repaired the disk again because it got stuck on bootup and when i logged back on it asked me to re install those updates. without them installed the option key thing worked again. So i guess i wont be updating this thing anymore...

  • Unable to boot into safe mode with FileVault 2 enabled

    I was trying to boot into safe mode earlier to try and fix a few things. It looks like I can't and I suspect it is because of FV2.
    When the system starts I press shift after the tone, but then I have to release shift and enter the password and then Lion will only boot into normal mode.
    I've also tried with sudo nvram boot-args="-x" from the terminal, but while it seesm that this way Lion starts to boot into safe mode, after a while it just restarts as if something crashed etc and then again, I have to enter the password for FV and all again as in a loop, i.e. Lion won't even start this way.
    So I went into the recovery mode and I could make Lion start again at least in normale mode with sudo nvram boot-args="".
    Any idea of what could be preventing Lion from entering safe mode?
    Thanks in advance

    The symptom may be unrelated to FileVault 2. I encountered the symptom with FileVault 2 disabled and with backward conversion (decryption) complete.
    Apple reference for my bug report: 152162960. If the symptoms on your Mac compare to those on mine: progress may seem to cease during safe fsck.
    Vito, as you are comfortable with the nvram command, please try the following:
    sudo nvram boot-args="-v -x"
    Restart the computer and note the last verbose lines that appear before you sense that progress has ceased. Then please add a note of those lines to this topic.
    Additional questions
    What model is your Mac?
    What type of disk for the startup volume?
    How many files on that volume?
    Approximately how large are the attributes file and catalog file? (You might gain this information with a demo version of iDefrag.)
    My current envronment
    MacBookPro5,2
    8 GB memory
    startup from internal 320 GB rotational disk, Serial-ATA, Hitachi HTS723232L9SA62 (probably Travelstar 7K320)
    3,961,791 files
    495,744 folders /* not including the root folder */
    catalog file 3.0 GB, not fragmented
    attributes file 2.2 GB, not fragmented.
    At http://www.wuala.com/grahamperrin/public/2012/01/09/a/?mode=gallery file speedy.txt includes details of the volume.

  • Unable to boot into Rescue and Recovery environnem​ent

    Hi everyone!
    I had my PC with windows XP factory installed. I migrated to Windows Vista. I didn't take the time to read the appropriate way to migrate and now I'm having big issues with all the ThinkVantage suite. So what I want to do is re-image my PC. I can see that the RnR partition (EISA Configuration partition is still there. (I've seen it in the Computer Management Console).
    Now, when I press the ThinkVantage button when my pc Boots, it only gives me the choice to either go in the BIOS, or select the boot drive. Of course, the RnR partition doesn't appear in my list! I'm kind of stuck here. I went on lenonvo's website, and there is a tool that will create a recovery diskette, but my laptop doesn't have a diskette reader... plus the application is written in 16 bits... so there's no way I can read it under Windows Vista.
    Anyone has an idea on how I could get my comptuer to boot into RnR so that I can re-image my pc?
    Thanks!
    Oli

    Hi,
    first I would like to explain one thing, so that we are on the same page with the RnR partition.
    Vista and XP are using different RnR partitions and the location of these aprtitions is placed on the HDD is different way, so that it can be used in conjuction with your Operating system.
    So in the time, where you have used the XP and OS, the RnR partition was placed in the partition table on the end/back. DIrectly after you upgraded to the Vista and did not made any changes to the RnR partition, than it is still on the end/back, which is not the corect way. Becase the Vista should use the RnR partition, that should be placed on the begind/start/in the front of all the other partitions.
    So in case there was no change made to the RnR partition, like relocation, or reinstall using the Vista RnR version, then you will not be able to boot into it.
    So here is what I would advice you to do:
    - reinstall, or download and install the Vista version of RnR (the latest version) => this will rewrite the partition table and in case of need it will create the RnR partition.
    - use bmgr32.exe , which is located on your HDD by default to rewrite the partition table. Please start it from command line in follwing way:
    bmgr32.exe /phil
    ==> this will bring you all the command line options and you can use it based on this.
    NOTE:
    Plase note, that once you captured some backups using the XP version of RnR , or a different version of RnR, then it's not possible to restor the backups using a different version.
    Simple: you must use the exact same version of RnR for backup and also for the  restore process.
    Let me know, if you have any more informations to this situation.
    Cheers

  • [SOLVED] Unable to boot into fresh install (UEFI, gummiboot)

    Hello to you all,
    I installed arch linux on my new Lenovo E130 following Beginner's guide. After install, when I rebooted the system I'm dropped into emergency shell. Whole log:
    :: running early hook [udev]
    :: running hook [udev]
    :: Triggering uevents...
    :: performing fsck on '/dev/sda1'
    fsck: fsck.vfat: not found
    fsck: error 2 while executing fsck.vfat for /dev/sda1
    ERROR: fsck failed on '/dev/sda1'
    :: mounting '/dev/sda1' on real root
    mount: unknown filesystem type 'vfat'
    You are now being dropped into an emergency shell.
    /dev/sda1 is my UEFI partition in fat32 filesystem, mounted to /boot in fstab. Also it's wierd that fsck is trying to run on this partition as it's entery in fstab is
    /dev/sda1 /boot vfat defaults 0 0
    so no fsck is expected? Also I tried linux-lts kernel and installing dostools and than mkinitcpio to renew all the hooks, the error is still the same.
    Thanks for all your help.
    Last edited by kokice12 (2013-12-27 00:54:35)

    My root is on ext4 partition, let me just show you my fstab
    /dev/sda1 /boot vfat defaults 0 0
    /dev/sda2 none swap defaults 0 0
    /dev/sda3 / ext4 rw,relatime,data=ordered 0 1
    I really don't know why is it forcing fsck on partition with pass=0 in fstab?
    And thank you

  • [Solved] Windows 7 and Arch Dual boot- unable to boot into Windows7

    Had to reformat computer and reinstall windows and Arch on two separate hard drives (Dual boot) .
    Windows 7 was the first install on SDA: (/dev/sda1 - system reserved 100mb, /dev/sda2 - 20gb)
    Arch on SDB: (/dev/sdb1- boot 94mb, /dev/sdb2- swap, /dev/sdb3 - root, /dev/sdb4 - /home)
    Installed grub2 on /dev/sda. now grub bootloader loads Arch fine. Also shows Windows 7 (on /dev/sda1).
    But when chosen Windows 7, it does not load and loops back again to boot loader screen.
    In BIOS i have set disk drive SDB as first boot option.
    If i choose SDA as first boot option in BIOS, same scenario is repeated.
    I have gone through mostly all the pages related to the topic but i can not co-relate the solution
    to my exact situation due to limited knowledge.
    Can somebody pls help me as to how to edit grub.cfg so as to point it to load windows 7?
    the entry related to windows 7 reads as follows:-
    quote
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menue$
            insmod part_msdos
            insmod ntfs
            set root='hd0,msdos1'
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint$
            else
              search --no-floppy --fs-uuid --set=root F010D97410D941F0
            fi
            chainloader +1
    unquote
    for Arch set root value is hd1,msdos1 and working fine.
    Thanks and regards.
    Last edited by commsanjay (2012-10-14 08:08:54)

    This is exactly why I have chosen to use windows MBR and syslinux
    https://wiki.archlinux.org/index.php/Wi … oot-loader
    Last edited by ackt1c (2012-10-14 02:32:55)

  • Unable to boot into setup/safe/recovery mode....please help

    Hi,
    About to bin this imac I have (trying to fix this for someone at my work place) as I'm seriously wasting time....
    Usual issue: Users do not know any of the passwords for the accounts on this machine.
    Machine: iMac (circa 2010/2011)
    OS: 10.5.8
    Build: 9L31a
    S/N: YM8300VLZE4
    What I have tried:
    Switching on, holding shift key   (nothing happens - just loads to normal login screen)
    Switching on, holding cmd+s (nothing happens - just loads to normal login screen)
    Switching on, holding alt/option key (nothing happens - just loads to normal login screen
    I have tried the above with holding the keys down when switched on, as soon as the chime starts, with releasing the keys when I see the apple logo, releasing the keys when I see apple logo then spinny thing.....
    Same thing happesn - NOTHING.....Just goes straight to the usual login screen......
    I don't have a CD on me and I'm mega frustrated

    Cancel the above.....Apple keyboard bust - the cmd keys not working.....I suspect this is the frustration of many thousands of users too...
    Just clag in a standard windows keyboard and hold down windows key +s to get to single user mode.....
    Later

  • How to get back into Mac OS X Leopard after installin Bootcamp

    OK have finally installed Bootcamp and now want to get back to the safe world of Mac again, however although I have been following the instructions in the manual which tell me either to...
    a) set the default operating system in Windows by clicking on the Boot Camp system tray item (which doesn't seem to exist) or if it does is so hidden that I cannot find it, or,
    b) select an operating system during startup by holding down the option key (which is impossible as I don't have such a key on my non mac wired keyboard)
    neither of them seem to work. Whatever I do I cannot get back into my Mac operating system.
    If anyone has any ideas as to what I can try I would appreciate your help.
    Thanks

    Hello:
    I believe the following should help. In Windows XP, make your way to C:\Program Files\Bootcamp. You should see an icon labeled "kbdMgr". Double click that and look for the tab labeled "Startup Disk". Click your Mac OS volume as the startup disk. By now, you should also see the gray diamond for the Bootcamp manager in your system tray. Clicking that brings up a menu that allows you to restart in Mac OSX or enter the Bootcamp control panel where you can select a startup disk.
    Bryan

  • How do I boot into recovery mode with wireless keyboard

    I am unable to boot into recovery mode using either cmd-R or holding down the alt key. How is it supposed to work?
    Message was edited by: Niklas Brunberg (better title)

    I understand your concerns - I'm glad both of my machines are dual bootable (just in case) and I have my Snow Leopard install disks..... However, this is what Apple has decided, so we need to find the best way to deal with it. Personally, I've tested the recovery mode several times and, at least on my machine, it was not reliable (i.e. it wouldn't work - I tried it again and it did, but it spent more than an hour downloading the entire 4 GB installer again and then another 30 minutes installing it), and on a third try, I found that it had vanished because I had cloned by drive. When you clone, only your system is cloned, not the extra partition.
    So, I've decided to rely on a) my bootable clones and b) a copy of the installer (.dmg) in case my clones fail. I don't feel comfortable relying on something that requires an internet connection and a full download to work. But, that works for me; you may want to take a different approach.

  • 2009 Macbook unable to boot in any fashion

    I was recently given a broken Macbook from a friend who didn't want it anymore, and had no interest in fixing it. It's a 13.3" Macbook from 2009 with a 2.0GHz Core 2 Duo processor, 2GB of 1066MHz RAM, and an Nvidia GeForce 9400M. Since I can't get it to boot, and am not super familiar with Apple OS's (I'm more of a linux guy to be honest), I'm not entirely sure which version of OS X it's running, but from the production date my best guess would be Snow Leopard.
    So now to the problem.The first time I turned it on it booted to the login screen with no problem. Unfortunately that was the only time it worked. Now when I press the power button, it goes to the gray screen with the Apple logo, and the progresses to a blank blue screen. After approximately 5 seconds the screen goes black, and flickers in a somewhat periodic manner until I manually turn off the computer. In an attempt to fix it I tried to boot it in safe mode, but experienced the same problem. Next I tried to boot it off of an Ubuntu Live USB, but was unable to access the boot menu, and was therefore unable to boot off the flash drive.
    After doing a bit more research, I tried resetting the PRAM and NVRAM. I started the computer, pressing and continuing to hold the "option-command-p-r" key combination before the gray screen as per the instructions given at http://support.apple.com/kb/HT1379, but encountered the same progression of screens as I previously had, thus the only reasonable assumption is that it did not successfully reset. Next I tried resetting the SMC. I removed the battery, disconnected the the power adapter, and depressed the power button for 10 seconds, but this as well had no effect.
    Next I tried to run fsck by booting into single-user mode. Though it booted to what appeared to be the functional single-user mode command line prompt, after the line ":/ root#" I was unable to type any commands, and once again had to manually shut down the computer. On another attempt to boot is single user mode the message
    :/ root# AppleIntelCPUPowerManagement: initialization complete
    Broadcom2045FamilyUSBBluetoothHCIController::start booting in single user ... will wait for later
    [HCICcontroller][configurePM] power parent ready after 1 tries
    and another try yielded a last line identical to the first line of the above message, with the lower two lines appearing above it.
    I then, tested the RAM by trying all 6 permutations of the two 1GB sticks. With each configuration I tried to boot the computer normally, in safe mode, and in single-user mode, but in all 6 configurations the computer behaved exactly like (with the exception of it spending more time on the gray screen with Apple logo during the normal boot procedure when it was being run in the 4 positions that had only 1GB of RAM rather than the standard 2GB, but that was to be expected) it had been.
    Five notes of interest.
    1) The power adapter she gave me with it is an 85 watt model, whereas the stock power adapter appears to have been a 45 watt version, but this should neither have contributed to my current problem, nor caused any damage to the computer whatsoever
    2) The computer is unable to be turned on without being unplugged and removing the battery first. That is to say, after an unsuccessful boot attempt I must remove then replace the battery in order to try again.
    3) The battery is not defective, and is capable of holding a charge
    4) The screen was replaced at some point in the last 2 - 3 months
    5) I have read of a similar problem occurring with Macbooks that have had a new hard drive installed, but as far as I can tell the hard drive in it is the stock 160GB one that came stock with the computer
    Thank you for taking the time to read this post, and for any advice or help you can provide.

    Despite nobody having answered, I'll keep updating.
    I noticed today that as well as having to remove the battery each time before trying to start the computer, it also will not start if the power adapter is plugged in.

  • Can't boot into Windows 8 Single Language 64 bit or access the BIOS screen with the F1 key

    I have in my possession right now a Lenovo E49, Model name: 3464
    I am unable to access the BIOS settings at POST by pressing the F1 key.  Neither does it respond to the Enter key when it displays the message "To interrupt normal startup, Press Enter".  I am also unable to boot into the installed OS Windows 8 Single Language 64 bit.
    For your informtion, these are the events that led to this issue.
    I accessed the BIOS settings at startup using the CHANGE PC SETTINGS option in the CHARMS menu in Windows 8 Single Languge 64 bit followed by GENERAL and ADVANCED STARTUP.  Then I chose Restart Now.  Windows restarted to produce the startup screen where I chose Troubleshoot, followed by Advanced Options and UEFI Firmware Settings, followed by Restart.  This took me to the BIOS settings screen. Once there I changed the boot settings in BIOS so that SECURE BOOT was turnned OFF.  It was in ON state prior to that.  I also changed the BOOT MODE to LEGACY ONLY.  I also changed the BOOT ORDER to boot from DVD drive first followed by the Hard Disk and USB Hard Disk.  I saved the changes by pressing F10.
    Now the computer is able to boot from the DVD Drive.  I tested this by inserting a Windows 7 Repair DVD and also a Linux Live DVD.  Mind you, I didn't mke any changes to the Hard Drive.  I'm also able to boot from a USB Hard Disk.  This too was tested by inserting a bootable USB HD that had both Windows 7 and Windows 8 OS installers.  I used only the command prompt feature in the Repair option on the Windows 8 installer to ensure that I could access the partitions on the HD.  I did not in any way install Windows 7 or 8 on the HD.
    If there is no bootable DVD or USB HD inserted, the laptop is involved in a loop that restarts followed by a message that says the following:
    "Intel Undi, PXE-2.1 (build 083)
    Copyright (C) 1997-2000 Intel Corporation
    This product is covered by one or more of the following patents:
    US5, 307, 459,  US5, 434, 872,  US5, 732, 094,  US6, 570, 884,  US6, 115, 776 and US6, 327, 625
    Realtek PCIe GBE Family Controller Series v2.41 (06/08/11)
    PXE-E61: Media test failure, check cable
    PXE-M0F: Exiting PXE ROM."
    I am positive that the current state of the BIOS is such that it does not accept any input keys like F1 and F12 at POST so that the BIOS can only be accessed through Change PC Settings in Windows 8 as I had done prior to the occurence of the issue.  Since I cannot boot up Windows 8 I cannot use this method to access the BIOS.  And since it is not possible at this stage to access the BIOS settings through the F1 key, I believe Lenovo must have surely provided another alternative to enter the BIOS.  Can you kindly tell me what other way is there to do this.  In earlier days, one could reset the BIOS by shorting the BIOS through pins on the motherboard.  Is that possible now?  Or is there some Lenovo BIOS utilily that enables me to change the BIOS setting to boot with Legacy and UEFI?  Or do I have to install Windows 8.1 64 bit in Legacy mode?

    I'll see if another member of the team can jump in here and offer more help...
    What I might imagine is that you can only access BIOS from a cold boot. Windows 8/8.1 have hybrid shutdown and don't completely shut down the machine normally, so even when it powers off, it isn't fully off and the next boot is not really a cold boot.
    Please see this KB.  I realize this assumes you can get into windows.
    As you suggest, it also seems as though you have set legacy vs UEFI and that may be why your drive is not currently booting.   Can you remove the battery on your system?  If not, is there a reset hole on the bottom?  Removing battery and AC and pressing and holding the power button several times, then re-attach AC and Battery and try to restart and press F1 to get into BIOS.  (Not familiar with models that use enter for BIOS).
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Eclipse MS-7520 - Unable to boot windows if Dimm slot A1 is used

    I am unable to boot into or install windows XP, Vista (32 and 64 bit) or Windows 7 Beta if I have any memory installed in Slot A1 - it freezes at the windows loading screen (the little green bar gets about 1/3 way across). I am able to press F8 to bring up the windows boot menu but not even safe mode will boot.
    I have 6 ram modules in total. If I populate slots as per the manual only using 4 or 5 modules I have this problem. If I populate only A0 and A1 the problem occurs. If I populate all slots except A1 it boots windows fine every time (with 10GB of RAM).
    When there is a module in slot A1 the BIOS posts fine. Going into Memory-Z shows that the module is there and lists the spd information which matches the other slots. I can even perform a memtest86 (booting dos from USB stick) on the memory and it passes multiple times (shows the full 12Gb with all 6 modules installed). It seems very odd that windows is unable to boot until the module in slot A1 is removed.
    So far I have tried updating the BIOS to the latest version (1.4), cleared the BIOS back to defaults and have even tried setting conservative memory timings and ratios manually (at 4x ratio as suggested in the forums). Tried performing fresh installs with drivers from both the MSI CD and website and running MSI live update.
    I have only had the mainboard for a week but looking through the forum I have been unable to find a fix for this specific issue. I have logged a global support ticket with MSI but since there are quite a few users around the forum I thought someone here may have had a similar issue or could possibly point out something that I may be missing, some some odd setting or something else that I can try?

    Hi.
    I did try to up the voltage all the way from 1.5 to 1.6 but no joy.
    I received a response from MSI which was to try and update to a beta Bios of 1.53. Didn't make any difference unfortunately.
    I have since talked with tech support where I purchased the board from and they have recommended to return the board and have it replaced. (They tested another board in their stock with 12Gb ram similar to mine and said it ran fine)
    I'll post an update when I receive the replacement board
    Oh, and thanks for the tip -  I appreciate it.

  • Can't boot into safe mode - PC keyboard

    My Mini can't log in. I know why -- and even how to fix it -- but I'm unable to boot into any alternate state to make the fix.
    The situation: PC keyboard (AOpen 90.00029.UB1) and a Logitech 4-button mouse, both USB native; also tried Dell PS/2 keyboard with a USB adapter. VGA adapter is connected to analog LCD. Away from home; do not have OS X install DVDs with me. LoginWindow.plist is fatally borked, but I can't get at it to undo the damage.
    Symptoms: Mini will not respond to ANY keyboard actions during boot. Cmd-s, Cmd-v, Shift, Cmd-Opt-p-r, Cmd-Opt-o-f, or even C to boot from CD (I have a PPC Ubuntu live CD, never tested prior to this disaster). No feedback to indicate anything is happening.
    If it means anything, I have the startup chime turned off by a third-party utility. Much too loud for my household.
    Anyway, the sequence of events is ALWAYS the same:
    * Power on
    * No video (not just black -- no signal)
    * CD noises
    * With actual disc in drive, CD spin-up
    * Still no video
    * CD slows slightly (if disc in drive)
    * First video activity: gray logo screen
    * Spinning gear thing
    * Black screen
    * "Starting Mac OS X" (sometimes only a brief flash)
    * Stops at blue screen with mouse cursor, no Finder
    The Mini will only respond to: (1) power button on/off; (2) power-on-and-hold to go into that firmware update mode -- get scary loud tone, flashing LED, then above sequence as usual; and (3) mouse-down to eject CD. Oh, and I can move the mouse pointer around when I get to the blue screen. Yay.
    For the past 24 hours I have been searching the net for ANY indication that a PC keyboard is capable/incapable of inducing Safe Mode (or any other mode). Can't find a firm Yes or No, or even a Sometimes/Maybe.
    Wondering if keys are mapped differently on PC keyboards -- maybe Shift isn't really Shift as far as Mac ROM is concerned, so no Safe Mode? Tried other random key combos to no avail. Can't find a "rosetta stone" for USB keyboard signalling on net to prove/disprove theory.
    First Mac, no points of reference. Hopelessly lost.
    Help.
    Randall

    Final results are in. I ordered an Apple keyboard from Amazon, plugged it into the Mini tonight and wonder of wonders, I could get into Safe Mode, Single User Mode, Pie à la Mode, you name it. Microsoft and Apple clearly have different ideas about USB keyboards at the hardware level. (And just for the record, the Mac keyboard won't get me into my PC's BIOS either.)
    Fixing the login problem took considerably longer, but that's because I overlooked the obvious and wasted a lot of time on generic boot troubleshooting: If you got yourself into trouble with defaults write, a little reading of the Man pages will lead you to defaults delete.
    Things go much smoother when you have a well defined target.
    Anyway, anyone out there with a Mini and a PC keyboard, do the Safe Boot test now. If it ain't working, do yourself a favor and get a Mac keyboard.
    Thanks for all the help.
    Randall

Maybe you are looking for