Windows 7 and Installation Booting.

I have a strange problem here. i searched everywhere about it. but nothing in my hand.
so im opening bootcamp wizard everything is ok. i did partitioning and after mount the win 7 dvd. mac rebooted. i passed white bios screen and staying in the empty black screen with blinking white cursor. i tried this with 2 different windows 7 dvd. one of them x86 and another one is x64. but i could install vista and xp. what can i do about it.

Biggest issue for now is going online and just how secure Windows 7 along with 3rd party products are, and problems with the new UAC.
http://social.technet.microsoft.com/Forums/en-US/w7itprosecurity/thread/36046fff -ffc4-43f4-bce6-8f5f011f9296
Avast, Kaspersky seem to be the two best bets, though I wonder how much AV software does to protect. Windows 7 was running fine until a Norton 360 3.0 beta 110 live update; and there are problems with a "Symantec Service Framework" process and other features for now.
So I bought SuperAntiSpyware (SAS) to go along.
One reason for having two installs of Windows 7 (and keys) so I can test "A" on one system before applying it to "B" and I need to get better with system restore images.
The one issue has been my 2006 Mac Pro doesn't support the EFI boot screen the Windows 7 DVD (and Vista SP1 DVD) implement. I can install Windows from inside one of my three Windows OS without needing to boot from DVD and get around that.
Knowing more about Norton (yes, but Symantec's 2009 AV and NIS really do run better than Kasperky and AVG and no trouble on my systems) but it will be awhile. I would prefer they have just an AV beta for Windows 7 and then add on more, instead their "360" is trying to do too many things and too new.... Windows 7 has enough changes it will take time and work for any vendor.

Similar Messages

Maintenance Windows and Installation Deadline

I know this has been discussed many times in the past, but I wanted to clarify in my mind what I think happens.
I have a maintenance window on a collection that is daily between 3:30am and 5:30am. I create a deployment for software updates with an available time at 2:00am. I specify the installation deadline in the deployment for 3:00am.
In the Deadline behavior (user experience) I do not have either option checked (Software updates installation and System restart). So, my MW will not be ignored.
With these settings, the needed updates will be downloaded, but not installed until the start of the maintenance window at 3:30am. (in essence, the deadline should be "before" the MW if I want them to install at the next MW).
Thanks!

I did:
<![LOG[New Service Window Policy notification received.]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager" context="" type="1" thread="996" file="servicewindowmanager.cpp:217">
<![LOG[CCM::ServiceWindowManager::CServiceWindowHandler::OnPolicyCreated - A policy change has occurred. New policy has been created.]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
context="" type="1" thread="996" file="servicewindowhandler.cpp:2044">
<![LOG[    Populating instance of ServiceWindow with ID={3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA}, ScheduleString=786F1B4010100008, Type=4]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
context="" type="1" thread="996" file="servicewindowhandler.cpp:104">
<![LOG[        StartTime is 1/16/2015 3:30:00 AM]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager" context="" type="1"
thread="996" file="servicewindowhandler.cpp:176">
<![LOG[        Duration for the Service Window is Total days: 0, hours: 02, mins: 00, secs: 00]LOG]!><time="14:14:52.483+300" date="01-15-2015" component="ServiceWindowManager"
context="" type="1" thread="996" file="servicewindowhandler.cpp:106">
<![LOG[    The Service Window={3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA} has started at 1/16/2015 3:30:00 AM]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager"
context="" type="1" thread="5032" file="servicewindowhandler.cpp:1200">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:1, Type:4]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420"
file="servicewindowhandler.cpp:2258">
<![LOG[        Biggest Active Service Window has ID = {3DE9CD79-CC8A-4CDD-AD75-74191AB07BFA} having Starttime=1/16/2015 3:30:00 AM]LOG]!><time="03:30:00.071+300" date="01-16-2015"
component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1336">
<![LOG[
Duration is 0 days, 02 hours, 00 mins, 00 secs]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1337">
<![LOG[ActiveServiceWindow has 7200 seconds left]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1248">
<![LOG[Program can run! Setting *canProgramRun to TRUE]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="5420" file="servicewindowhandler.cpp:1249">
<![LOG[OnIsServiceWindowAvailable called with: Runtime:900, Type:2]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="4760"
file="servicewindowhandler.cpp:2258">
<![LOG[No Restricting Service Windows exist. It can therefore run...]LOG]!><time="03:30:00.071+300" date="01-16-2015" component="ServiceWindowManager" context="" type="1" thread="4760"
file="servicewindowhandler.cpp:1510">

Problems installing Windows 7 using Boot Camp

I have a brand new MBP Retina laptop (late 2013) with 256GB SSD. Today I tried to use Bootcamp Assistant to partition the SSD and install Windows 7 64 bit OS.
My first attempt was using a licensed Windows 7 64 bit installation DVD and my OWC external optical drive which is recognized in Finder:
I started Boot Camp Assistant, selected the boxes to download latest Windows Support Software from Apple and to Install Windows 7. I was asked to specify the size for the Windows partition and hit continue. The process was moving along, the computer restarted and then I got a black screen with a blinking white cursor (like a command line prompt) in the upper left corner of the screen and a message to press any key to reboot. Pressing any key did nothing.
As far as I could tell, the Support Software files that were on the USB drive did get installed prior to the first reboot of the system that happens after you allocate the size for the partition. After the first reboot I never got the Windows installer though, just the hanging black screen/cursor mentioned above.
I'm wondering if, after creating the partition and restarting, my computer can't see my external optical drive even though it does show up in Finder when booted to OSX because it was not reading the Win7 Install DVD at all.
While on the phone with Apple Senior Tech Support we rebooted several times holding down the Alt/Option key. The boot options were the OSX, Recovery, Windows, and EFI Boot. Choosing Windows resulted in the trackpad locking up and it just hung there. I ended up reverting the SSD back to a single partition for now.
After some discussion on the Apple forum I tried creating an ISO file from the Win7 64 bit DVD using ImgBurn software that I have installed on my Windows PC and ImgBurn indicated it had created a bootable ISO file. I copied the ISO file to the downloads folder on the MBP, plugged the empty USB drive into the MBP and tried Boot Camp Assistant again:
Choosing the appropriate option for use with an ISO file on a USB drive Boot Camp Assistant proceed to again create the partition, asked me to size it, and then it proceeded (over approximately an hour and a half) to work on copying the ISO file to the USB drive and downloaded the Support Software to the USB drive.
After the restart I got another black screen, cursor, and the messages, "No bootable device/drive found", "Press any key to reboot". Again pressing any key did not do anything. I reverted back to a single partition again, rebooted to OSX and gave up for the night.
Bottom line in either scenario is that I never get to the Windows installer screens to even attempt to install Windows on the new partition.
QUESTIONS:
I think in my situation it doesn't appear that ImgBurn created a bootable ISO file from my Win7 install DVD. The Apple Bootcamp Setup guide refers to downloading the ISO image from Microsoft but I couldn't find anything that I would be comfortable downloading.
I'd rather use my installation DVD for Windows but why isn't that process of reading the DVD from the external drive working after the restart?
Can the ISO file and Windows Support Software live on the same USB drive during installation and does the support software get installed automatically by boot camp assistant?
What am I doing wrong here? This shouldn't be this hard especially when I own a valid copy of Windows.
This is VERY frustrating. Any help or referrals to proper instruction is very much appreciated.

I was able to successfully complete the installation of Windows 7 Home Premium using Boot Camp. Turns out the problem was the Windows 7 ISO image I was initially trying to use. I called Microsoft tech support and they sent me a link (see below) from which I downloaded the Windows 7 Home Premium 64 bit ISO image. After downloading the ISO image and restarting Boot Camp Assistant the process of Boot Camp preparing and transferring the ISO image and Windows Support software to the USB drive took about 45 minutes and then everything went smoothly from there. The only thing I encountered was when I was asked what drive to install Windows on I got a message that it couldn't install on the Boot Camp drive because it needed to be in NTFS format. I clicked on the format button and then the process continued. After Windows installed the Windows Support Software from Apple started to install automatically. So far it is working well.
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/windo ws-7-home-premium-64bit-iso-download/709dcc12-d120-435d-91cd-52e1dd0f4c24

Unable to install windows 7 on boot camp partition

Hello everyone!
As the title says, I'm trying to install windows 7 on my macbook - the 2009 13 inch model- and failing at it. I have been peeking around the net and I haven't found any solutions, so here I come.
If I'm not wrong I need to format the partition, since boot camp does a FAT32 forma and it won't work for Windows 7. I do that from the windows installer, when it asks me for a driver (no idea which one it's talking about). Then it allows me to choose the partition to install windows but the installation process doesn't seem to work for some reason. I've done it before and I've had similar problems (I just kept trying things untill something worked ) but apparently I couldn't do it now to safe my life.
I hope I've been detailed enough for you to be able to help me. Thanks ^^

It depends of the OS X version you're using. If it's 10.6, insert the Mac OS X DVD and install them.
If it's 10.7 or 10.8:
1. Press X key while your Mac is starting to start into OS X.
2. Open Boot Camp Assistant, download drivers and burn them into a DVD or USB drive.
3. Start into Windows and install Boot Camp drivers

2010 Mac Pro Boot Camp - Refuses to boot Windows after installing Boot Camp drivers

Hey all,
I have a quad 3.2Ghz 2010 Mac Pro with a Radeon 5870 and 8 GB RAM.
I have 2 10000RPM WD Raptor drives, the first drive is my Lion boot drive. The 4th bay contains the second Raptor which has Windows 7 Ultimate 64 bit installed. Bay 2 has Time Machine, bay 3 has a Windows backup drive.
I had first installed Windows and the Boot Camp drivers a few months ago and everything was humming along smoothly. Monday I tried to boot into Windows and it crashed immediately after the black Booting Windows screen started to change to the login window. This happened repeatedly. Nothing changed on the system that I am aware of. Whenever I tried to boot windows again, it booted into the repair mode. That did not seem to work because after running the repair it would still not boot.
So I did what is usually required of Windows, and that was to reinstall. I reformatted the hard drive, ran Boot Camp assistant, and started the install.
Everything was peachy so far, so I tried to reinstall the Boot Camp drivers (4.0). Did a reboot. Same problem. Doh!
So I did ANOTHER reinstall, and everything was fine. But this time I tried to install the Boot Camp drivers off the os install disc that came with my Mac (3.1). Still no go!
So finally I did my third reinstall and after that I did not install Boot Camp drivers. However, I did load up the CD and individually installed drivers for the Apple Mouse, Apple Keyboard, Cinema Display, etc. No problems whatsoever. Everything is actually still humming along fine.
So it looks like running the full Boot Camp install for some reason no longer works. Which means I am missing the Apple Boot Camp control panel, but that's not really a big deal. Althought it's quite annoying to not have the functionality of the special Mac keyboard keys like volume control, etc.
Has anyone run into this? I thought it might be a hardware problem but my Mac OS X OS exhibits no problems whatsoever.
Thanks!

Thank you to The hatter.
I have a Mac Pro mid 2010 with a SSD and several internal hard disks. For some time I was trying to install Windows 7 on a fresh boot camp volume on a new WD 7200rpm 1TB hard disk. It was taking hours to install, and then I had a series of failures to reboot that proved permanent. The Window Repair utility would come up and took forever to repair the volume - but failed to actually do so, requiring completion reinstallation of the bootcamp volume. This occurred three times, between 1 day and 2 months after installation. I had already moved the Windows drive in to drive slot 1 of the Mac Pro.
Eventually I gave up and installed boot camp on a secondary partition of the SSD. This worked fine, however is limited in capacity. So yesterday I thought I would try to install Windows on the hard disk again. The Windows installer took many hours to do its thing, and eventually a message came up that the installation had failed.
I took your tip about possible hard disk failure, and ran Techtool Pro surface scan. It turns out that there are lots of bad blocks being reported. According to Micromat's documentation, the bad blocks being reported are those that may be in critical areas of the disk that cannot be mapped out. They recommend low level reinitialisation (with zeros) to map out the bad blocks, if possible. I am now running Apple's Disk Utility to do this, and fingers crossed that this reinitialisation succeeds, or I will have to replace the drive.

Unable to Install Windows 7 using Boot Camp Assistant

I recently suffered a hard disk failure. After replacing the disk, I have recovered all data with the exception of being unable to install windows 7 on a new boot camp partition. I am able to create the partition using boot camp assistant, but I am subsequently been unable to install windows following the directions provided. Any help would be appreciated. I have a late 2009 27" iMac running OSX Mavericks.

It depends of the OS X version you're using. If it's 10.6, insert the Mac OS X DVD and install them.
If it's 10.7 or 10.8:
1. Press X key while your Mac is starting to start into OS X.
2. Open Boot Camp Assistant, download drivers and burn them into a DVD or USB drive.
3. Start into Windows and install Boot Camp drivers

I just updated to OS X 10.9.2 and My boot camp assistant won't turn on.

I'm trying to install Windows 7 as I did before.
But now, when i double click the boot camp assistant on desktop it gives me the error message window and says "Boot Camp Assistant has quit unexpectedly".
Please help.

When I got the computer, boot camp assistant was on the desktop and I used it to install windows 7 before.
I have never really seen it on my applications folder and right now it isn't in my applications folder either.
Would this be the problem?
I couldn't find out how to re-download the boot camp assistant either...

Accidently shut down my Mac Book Pro during Windows 7 installation . When re-starting it says "Press any key to boot from CD or DVD". But keybord is not working . and i have the windows CD inside the drive . Pls hlp me to boot the mac again .

I have accidently shut down my Mac Book Pro during windows 7 installation . When I re started it it began to say " Press any key to boot from CD or DVD " but the keyboard is not working . So I cannot boot It and the CD is also in the drive . Please help me to boot back to Mac book Pro and give me a way to start the key bord .

Hey rudreshchoubey,
Thanks for the question. The following resource may help to resolve your issue:
Boot Camp Installation & Setup Guide
http://manuals.info.apple.com/MANUALS/1000/MA1636/en_US/boot_camp_install-setup_ 10.8.pdf
If Windows doesn’t install properly
Verify that you’re using an original, full version of the 64-bit version of Windows 7 Home Premium, Windows 7 Professional, Windows 7 Ultimate, Windows 8, or Windows 8 Pro.
Restart your Mac and hold down the Option key until one or more disk icons appear on your screen. Insert the Windows installation disc into the optical drive or insert the USB flash drive with Windows into a USB port on your Mac. Select the Windows installation disk icon, then click the arrow beneath it. Quickly press any key on your keyboard to start the installer. Follow the onscreen instructions to repair or reinstall Windows.
Thanks,
Matt M.

Lenovo U310: Clean Windows 7 Installation Guide (including Rapid Start and Caching)

Hi there,
this is the first time that I am writing such a guide/tutorial/whatever you may call it – there are probably better ones, but though not being a total computer noob, it took me almost one week to get this pretty (now again) little beast running again. So hopefully this helps some others to avoid such stupid downtimes.
A brief overview on what has happened to my original win 7 Home Premium:
As some may know, this laptop is very well usable as a “Hackintosh” called Macbook clone. So that’s what I did. It turned out to be nice, but I wanted to go back to Windows after a while, using a clean W7 Pro installation to start over. Actually an easy task, format all drives, install Windows, be happy. Just as I had been doing this for years. Unfortunately, it turned out to be a real challenge. First, I couldn’t “see” my drives during installation (and thus not install), then I got random errors during installation aborting it at different points and finally rapid start and caching didn’t work. Every time I tried to activate them (after Win installation), it crashed my PC. I even found an (official Lenovo!) guide stating to install W7 on the SSD, which worked, but sucks due to space limitations. Oh and another very nice thing: The SSD showed up during WIN installation (but not the classical hard drive) stating it was about 60 GB. So as you can see, I have had a lot of different tries and errors. Why I didn’t use Lenovo Easy Recover? As said before, I erased all partitions…
Before we start: If you have a good Windows running on the Laptop, do yourself a favor and disconnect the RAID 0 disks using the Intel Rapid Storage Application before(!!!) proceeding. It will make things much easier. And don’t forget to get all you data on an external drive or something.
Ok, now let’s start.
1.)    Prepare a USB Stick with the following driver
         http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21730 (choose f6flpy-x64.zip If you’re running a
         64-bit system (standard nowadays), take f6flpy-x86.zip if it is a 32-bit Windows, just download and copy them
         into the stick’s root directory) and plug this stick in one of the left side USB ports.
2.)    You’ll need Win 7 on either a DVD (plus external drive, for sure) or (bootable) USB stick
3.)    Connect your drive/stick (with W7) to the right side USB port.
4.)    Switch the computer on, immediately hit FN and F2. That will open the BIOS.
5.)    In the BIOS, navigate to the very right section (“save and exit”) and navigate the cursor to “load setup defaults”.
         Hit enter to approve.
6.)    After that, go to the “boot” tab and disable UEFI-boot.
7.)    Next, go one more tab to the left and set the controller setting to RAID (NOT AHCI or Compatible!!!).
8.)    Navigate the cursor down to “Intel Rapid Start” and hit enter. A submenu will pop up-
9.)    Disable the first entry in that window, that will make the rest be disabled as well.
10.) Navigate to the very right tab, this time hit save and exit.
11.) The PC restarts.
12.) Immediately hit FN and F12 to open the boot selection menu. Select to boot from your W7 DVD drive or USB
        stick.
13.) Click yourself through the whole process of installing Windows 7 until the page comes up where you will have
        to select where to install it.
14.) Click on “load drivers” and after a few seconds your downloaded driver should be there. Click ok to use them.
        Please do this step even if you can see your drives (SSD Disk 0, 32 GB and HDD Disk 1, 465(<-?) GB) as you
        would expect them – otherwise you’re very likely to get an error during the install process.
15.) Now erase all partitions on both drives and select the HDD as the drive to install W7 to – NOT THE SSD!!!!!
        Seriously, don’t choose the SSD.
16.) Windows will probably say that some extra partitions are necessary and so on, click ok and install Windows.
17.) After the installation has finished and you see your Desktop, I suggest you to proceed with the next steps in the
        following order to see as early as possible if you are on the right way.
18.) Install the Chipset driver, restart.
19.) Install the Intel Rapid Storage “driver” and check the box where it asks to additionally install the control center.
        Reboot.
20.) Go into BIOS (FN and F2) and enable Intel Rapid Start (the one you disabled in Step 8 and 9)
21.) Boot into Windows.
22.) Click on the Windows button, type cmd and right klick on the cmd.exe, select to run it as Admin.
23.) Now you’ll create a hibernation partition on the SSD. (which by now should be completely empty as we’ve
        deleted all partitions in step 15)
24.) In the command prompt that we have just opened, type: (without quotas, for sure)
“diskpart” and hit the enter button
“list disk” and hit the enter button
Now you should see your ssd as disk 0 and your hdd as disk 1
If your ssd is disk 0 (that would be standard), write “select disk 0”, otherwise write: “select disk 1”, and hit the enter button.
Now write “create partition primary size=4096” and hit enter again. [if you have 4GB of ram, type 4096, if you have 8 GB of ram, use 8192]
Now write “detail disk” and hit enter to see the volume number behind the volume that we have just created (it is 4 GB or 8 respectively, should be easy to find), in my case that was “2”
Now type “select volume 2” if your 4 or 8 GB volume has number 2 as well, otherwise use the number you found out in step f. Hit enter.
Finally, type: “set id=84 override” and hit enter for one last time.
It should now say back that the id has been set successfully.
Exit the command prompt. (close)
25.) Reboot
26.) Install the Rapid Start driver. Reboot.
27.) Open the Intel Rapid Storage Application.
28.) Click on accelerate and approve the settings. Two RAID’s will be created. Reboot.
29.) Install the remaining drivers, have fun with Windows Update and that’s it!
Good luck to all of you… And hey Lenovo - wouldn't that have been your job after all these posts showing your costumers in trouble? Just my two cents...
If you want, you can now turn on UEFI-boot in BIOS.
PS: If, after installing all drivers, you happen to see one unknown device in your device manager – this one belongs to Lenovo Connect Software that came with your Laptop. (Updates FB, Email etc when PC is in sleep mode) If you install Lenovo Connect it’s going to be fine, however, I would not recommend it as it is said to use a lot of energy and cause some other problems. So just live with it, your PC is totally fine without it.
Kind regards from Shanghai

Seriously guys, I can't use my 3 days old laptop. Some help would be mostly appreciated. At this point, the network connection issue doesn't show up anymore, it's just a blank screen after reboot. I reinstall windows and do it all over again just to achieve the same result.
Now couple of things caught my attention: as I load the "6flpy-x64.zip" driver from step 14, I get a message saying I need to install signed drivers, because unsigned ones are likely to mess up the system.
Secondly, I could not find any Rapid Storage Technology drivers for Windows 7 (particularly for U310 model), so I use the Windows 8 ones (http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031455), which seems a silly thing, yet I know of no alternatives.
Could it be any of these issues to cause my problem? Or smth else? Please help!

[SOLVE] Dual Boot Windows and ArchLinux with Syslinux

Ok, i installed ArchLinux on my laptop with Windows XP (syslinux) and I cannot find get Windows to boot or mount it. I have tried to do what i can to do this but cannot. I Installed XP first like a should and something i think might be needed to know is after i created the partitions scheme (10Gb (boot partition), 50GB (XP), 80GB(was unallocated)). The installation disk formated both 2 partitions in NTFS but i installed XP on the second and Windows reported them as C and D drives. Windows being D. Thought that was bit werid thinking Windows installed the mbr on that partition. When I installed ArchLinux, it did have the boot flag set on 10GB (or C drive).
Since I installed ArchLinux, I have been unable to find a solution to mounting/booting to Windows. Installed NTFS-3G and that didn't work when i tried mount /dev/sda3 windows and i did created a folder named windows but got ...
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
Tried dmesg | tail and got
[ 76.524133] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 179.468499] ACPI: \_SB_.PCI0.LPC0.ACAD: ACPI_NOTIFY_DEVICE_CHECK event: unsupported
[ 705.472330] 8139too 0000:02:03.0 enp2s3: link down
[ 717.380879] 8139too 0000:02:03.0 enp2s3: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 726.447184] 8139too 0000:02:03.0 enp2s3: link down
[ 727.596128] ACPI: \_SB_.PCI0.LPC0.ACAD: ACPI_NOTIFY_BUS_CHECK event: unsupported
[ 732.616138] 8139too 0000:02:03.0 enp2s3: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 733.848832] 8139too 0000:02:03.0 enp2s3: link down
[ 834.062062] 8139too 0000:02:03.0 enp2s3: link up, 100Mbps, full-duplex, lpa 0x41E1
[ 2131.449211] perf samples too long (2534 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
This is when i run sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 149.1G 0 disk
|-sda1 8:1 0 9.8G 0 part /boot
|-sda2 8:2 0 1K 0 part
|-sda3 8:3 0 53.6G 0 part
`-sda5 8:5 0 85.7G 0 part /
sr0 11:0 1 1024M 0 rom
My syslinux is
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda5 rw
INITRD ../initramfs-linux.img
LABEL windows
MENU LABEL Windows
COM32 chain.c32
APPEND hd0 3
NOTE: chain is in the same directory with syslinux
I really think Windows got corrupted but not sure. Thought about repairing the mbr on windows and booting to it then reinstall syslinux but really don't want too.
Thanks in advance
Last edited by jag-ster (2014-11-27 02:12:12)

Here is the partition table:
/dev/sda1 one HUGE linux /boot primary partition (assuming ext4)
/dev/sda2 "name" of the extended partition
/dev/sda3 primary Windows partition (assuming NTFS)
/dev/sda5 logical Linux root partition (assuming ext4)
/dev/sda1 to /dev/sda4 are either all primary, or three primary and one extended. After /dev/sda4 all partitions are logical. If you're still wondering why is there no /dev/sda4, it's because you have 2 primary and one extended, so /dev/sda4 is reserved for another primary partition.
Windows problem:
The /dev/sda1 which Windows named C: is Windows equivalent of linux /boot. When you told linux to place its /boot on /dev/sda1 it formated boot files of Windows. Now you have Windows OS with no kernel. In other words there is no way to boot Windows if you don't reinstall it. Actually there is a way, but you would than screw up Arch.
Mounting problem:
You can never mount extended partition, only logical (an extended partition is made of logical partitions). You want to do:
sudo mount /dev/sda3 -t NTFS-3g -o rw,uid=YourUserName /path/where/you/want/this/partition/mounted
EDIT:
Try it this way:
- Backup all your data
- Delete every partition
- Start Windows installation
- Make only one partition (c:/ for Windows)
- Let Windows make another partition
- Make one more so you could have a data partition, which does not need to be formated to reinstall Windows
- Start Arch installation
- Get to partitioning
=Partitioning=
- /dev/sda4 extended (take the rest of the drive)
- /dev/sda5 logical /boot 512MiB
- /dev/sda6 logical / 20GiB
- /dev/sda7 logical /home (the rest)
Making a separate /home partition will come in handy when reinstalling Arch (any linux distribution), or switching between distros, because it is the equivalent of D:/ in Windows. Also consider LVM.
Last edited by bstaletic (2014-02-28 23:25:33)

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

No option to reformat during Windows XP installation under Boot Camp

Ok, I just purchased Windows XP Professional SP2 to install on my Macbook Pro via Boot Camp. I first attempted to install it last night, and ran into a variety of issues.
I went into Boot Camp Assistant, printed out the instructions, and read them carefully. I continued on to designate the size of my Windows partition, which I adjusted to 45gbs. Then I created the partition with no difficulty whatsoever. After this I inserted my Windows installation disk and restarted the computer. Upon restart, however, the computer ejected the Windows disk before the computer even got past the grey screen. I reinserted the disk and the blue installation screen appeared successfully. It came to a screen that asked me what partition I wanted to use to install Windows, and I chose Partition C (titled something like "BOOTCAMP PARTITION FAT32"). The size of this partition was 45 gbs, so I know I chose the correct partition. Now this is where I ran into my biggest problem. *After I chose my partition, I am given no option to reformat the partition. It just skips that step entirely and continues on to the installation screen.* Windows installs and restarts the computer, only to bring my to the dreaded black screen with "Disk Error" on it. I know it brings me to this screen because I did not reformat my partition. The problem is, I'm never given the option to reformat the partition during the installation.
I have tried deleting my Windows partition and creating a new one (this time 32gb), and I get the same issue. It simply does not give me the option to reformat.
I've googled this and discovered that many other Mac users have ran into this same issue. _I've also discovered that the majority of feedback they receive is that they need to reformat the drive, but this is the problem: we can't. We are not given the option._ I have no idea what to do. Please help.

I just went through the same problem you are experiencing right now. I bet you are trying to install OEM version of windows. I used an old windows upgrade and ran the repair, which brings you to the command prompt c:, run "FORMAT C: /FS FAT32" . Once this is done go back and reinstall your Windows XP OEM. Works like a charm.

Boot Camp Assistant refuses to recognize my Windows 7 Installation Disc nor my USB

I have an iMac 20inch, early 2008 model. Back when I was running Leopard I installed Windows 7 with Boot Camp from a Windows 7 Installation ISO my friend had and I burnt it to a DVD and installed it without any problems. Later, after I got tried of windows, mostly because Windows really blows unless you want to game (which is what I was using it for), and I had contracted a virus, so I deleted Windows along with my partition after backing up any data that I though I might be able to use later. Now I am fully upgraded to Lion 10.7.2 and I downloaded the Windows installation drivers and whatever else Boot Camp persuades you to download and now at the step where I choose how much of my hard drive I want to partition, after I click partition, Boot Camp refuses to recognize that my installation disc is there no matter what format I put it in. I have followed every instruction given to me and nothing has worked. I'm thinking about trying to just partition my hard drive in Disc Utilities and formatting the new partition and then copying the ISO to the partition and seeing if it'll boot up.
Anybody have any better ideas, or solutions?

Well I have tried downloaded a Windows 7 ISO, and tried mounting it on a USB flash drive and booting it from the USB, but that didn't work either (I heard that my version of OS X doesn't support that anymore because I already have an optical drive.)
BTW - what do you mean exactly by running disk utility on the DVD drive?

Can't boot Windows Vista Installation

Hi,
I installed Leopard and then used Parallels and Windows XP. Then I uninstalled Parallels an XP and used boot camp assistant to create a 32Gb partition for my Windows Vista Ultimate. When I boot from DVD I get the "Loading files..." screen but in the middle of the process the iMac turn off.
I tried to install Windows XP, the installation starts, windows copy the files and restart for the first time. Then when the second part of the installation begins, the iMac turn off.
I tried to search the discussions and google but I can't find a solution. All I found was an firmware update for a issue of with boot camp and 24" Imac.
Today I installed the news updates (10.5.1 and Graphics firmware) but the problem persist.
What should I do? A clean reinstall of OS X could help? Could Parallels created the problem? I tried to reinstall parallels and then install Vista with bootcamp, but the problem is the same.
Any ideia?
P.S. I am trying to write in English...

Hi,
I installed Leopard and then used Parallels and Windows XP. Then I uninstalled Parallels an XP and used boot camp assistant to create a 32Gb partition for my Windows Vista Ultimate. When I boot from DVD I get the "Loading files..." screen but in the middle of the process the iMac turn off.
I tried to install Windows XP, the installation starts, windows copy the files and restart for the first time. Then when the second part of the installation begins, the iMac turn off.
I tried to search the discussions and google but I can't find a solution. All I found was an firmware update for a issue of with boot camp and 24" Imac.
Today I installed the news updates (10.5.1 and Graphics firmware) but the problem persist.
What should I do? A clean reinstall of OS X could help? Could Parallels created the problem? I tried to reinstall parallels and then install Vista with bootcamp, but the problem is the same.
Any ideia?
P.S. I am trying to write in English...

Boot Camp: Early 2011 MacBook Pro boots to black screen with blinking cursor after windows 7 installation.

I bought and downloaded the windows 7 ultimate edition 64 bit iso, then proceeded to perform a correct burn to a DVD one at the slowest speed and one at the fastest. all went well. so I open Boot Camp assistant and follow the instructions to the letter, downloaded the driver support to the flash drive. partitioned my drive with more than enough room 150 gb. its starts its install. I get through everything seamlessly where I put in my info all with the exception of my activation code. yet it still continues to finalize the install and does another restart. boots back up to either A. black screen saying press any key to boot to my install disk. B. if I take it out just a white curser. also I read it may be because I had the flash drive in while I was trying to boot so I removed it as well, same result. any input would be much appreciated.

Boot Camp- Windows installation boots to black screen with blinking cursor.

Windows 7 and Installation Booting.

Similar Messages

Maybe you are looking for