January 13, 2010 at 01:48My struggle or how to solve boot problem in boot camp
A topic for those who have encountered the problem of installing windows xp on a mac using boot camp. I dedicate to those who, like me, fought with a terrible obsessive message about the absence of "\ system32 \ hal.dll "But this is in the finale, and if someone is not interested in reading, you can open and read the items in bold. And before that, a little background describing my attempts to solve.
So, the chief brought his aimak, which we had to put on the operating system, which for some reason everyone scolds, but humbly humbles themselves before the monopolist, and nevertheless puts it in. No matter how you say it, you can’t always do without windows. there was a new one for me - to install Windows in real time it through boot camp.
The task seemed quite simple, since there is everything for this. And the corresponding utilities, and the driver disk, and everything else in the form of desire and opportunity. Then everything is simple. We break up the bootkamp partitions, assign 100 gigs for Windows (in my case), reboot and catch the boot from the CD.
I must say that I stuck the compact on duty - another "resuscitator", where there is all-all-all and even windows. This disk helped me hundreds of times. And what was my surprise when an error popped up on the screen. Having driven its code into Yandex, I learned from members of the forum that it’s not kosher to use pirated disks, and the bootcamp for launching with a CD definitely needs a license, and not a directory with windows lost in the directory tree somewhere. This was the first pitfall .
Well, no problem. I have licensed windows xp in my warehouse. I must say that my boss is quite a conservative person, and all these new products in the form of whists and sevens do not take into the spirit, so the overwhelmed license of Khryushka turned out to be very helpful.
I unpack it, take out the entire disk sparkling like Elton John, and boot up. Everything went fine. Further, when it was necessary to select partitions, I left Fat 32. I still install it for the first time, and I did not want to change the default scripts. As there is everything by default, I’ll leave it.
The time has come to the first reboot and ... Nothing happens. Disk Error. And that was the second pitfall. I ran to the Internet, after which I found someone post on the forum where the author said to the same poor fellow "Dude, it's no good to use FAT-32, do the NTFS partition." Well ... Once such a thing. We reboot, load the disk with Windows, select the partition, say format it in NTFS. He does it all safely, copies files, comes to the first reboot and ...
\ system32 \ hal.dll ... That's it. Arrived. Again, nothing works, again on the Internet. There comrades write to the same suckers: but there was no need to format NTFS, read the manuals. "How is this to be understood, gentlemen?" I thought. Some write - format. The second "YYY, teapot, who does this, you must leave fat-32." What are the mutually exclusive paragraphs in Apple? The next couple of hours I spent trying to apply a variety of tips. Including "you format in NTFS, then bootkamp delete this section and make the same size of a fat." All this seemed nonsense, sucked from a finger, but who knows, maybe it will save. The most characteristic, experienced makovody said that the behavior of the bootkamp very much depends on the computer model and software version, so no one could give out universal recipes like that. I had to think it out myself.
As you already guessed, in the first version of the error with FAT on the face, we probably have some kind of problem with determining the partition, but with ntfs things are still better. At a minimum, it is already trying to boot. And I decided to act in this direction. I must say that the item "convert section to ntfs" categorically did not work for me, I do not know why. And then I decided - it means you have to do it manually, although they wrote on the forums that it would not work.
What I've done?
1) The bootkamp creates a partition. FAT-32
2) We are loaded with life-cd. Personally, I only got hooked by infra cd
Further, I thought that I needed to start some partition magic, but I was unpleasantly surprised that he sees 32 as an unformatted partition, I couldn’t do anything with it. Then the command line remained - convert c: / fs: ntfs ... And this also had no effect - he does not want to, he swears with an error.
Here it is necessary to make one more digression. When you install windows or break some partitions with some other Windows tool, the bootkamp starts working incorrectly with them. It turns out that before the Windows partition bootkamp places part of its information. I don’t know what is there, how he uses it. But if you demolish the fat-32 partition that the bootkamp created, and create a new partition - these wonderful bytes are erased by the newly created partition, and as a result we see what I'm writing about. Partition magic resolutely did not see this magic mini-section, and also offered an unacceptable solution for me - to tear down the veil and re-make ntfs.
And then I take it and use the simplest solution - well, to hell with all this conversion. Take and format what is. But not the way I'm used to - you take down the portion, create it again .. And I went to "my computer", with the right mouse button and woo, then you know. My reasoning was already at the level of a freshman blonde: FAT-32 was probably created on the principle of "that's from this sector to the very end, understand?". And, probably, when I format in NTFS, the beginning of this section will go exactly from the same place, without touching the magic bytes of the bootkamp ...
Well, you understand, when I tried everything, I can only hope for such not-so-complete action logic. And it turned out. It turned out to format ntfs, although it was difficult to wait for another.
But that's half the battle. Reboot, insert the windows license, boot from it. When choosing partitions, we see that ntfs is waiting for us, i.e. I do not need to do any manipulations. Leaving the file system unchanged ...
Bottom line - I have Windows there. I got up without any problems. It was later that I thought that it was possible to install the ntfs drivers in the poppy (for example, a paragon), and format this unfortunate partition from under disk utility ... Or else ... But, that's another story.
I don’t know how the rest of the Khabrovsk citizens, whether they faced this, also fought in other ways. But I hope that I can help at least one user with my modest note.
PS
Moved to Mac OS X
Instead of PPS
My second habratopik, so do not scold
So, the chief brought his aimak, which we had to put on the operating system, which for some reason everyone scolds, but humbly humbles themselves before the monopolist, and nevertheless puts it in. No matter how you say it, you can’t always do without windows. there was a new one for me - to install Windows in real time it through boot camp.
The task seemed quite simple, since there is everything for this. And the corresponding utilities, and the driver disk, and everything else in the form of desire and opportunity. Then everything is simple. We break up the bootkamp partitions, assign 100 gigs for Windows (in my case), reboot and catch the boot from the CD.
I must say that I stuck the compact on duty - another "resuscitator", where there is all-all-all and even windows. This disk helped me hundreds of times. And what was my surprise when an error popped up on the screen. Having driven its code into Yandex, I learned from members of the forum that it’s not kosher to use pirated disks, and the bootcamp for launching with a CD definitely needs a license, and not a directory with windows lost in the directory tree somewhere. This was the first pitfall .
Well, no problem. I have licensed windows xp in my warehouse. I must say that my boss is quite a conservative person, and all these new products in the form of whists and sevens do not take into the spirit, so the overwhelmed license of Khryushka turned out to be very helpful.
I unpack it, take out the entire disk sparkling like Elton John, and boot up. Everything went fine. Further, when it was necessary to select partitions, I left Fat 32. I still install it for the first time, and I did not want to change the default scripts. As there is everything by default, I’ll leave it.
The time has come to the first reboot and ... Nothing happens. Disk Error. And that was the second pitfall. I ran to the Internet, after which I found someone post on the forum where the author said to the same poor fellow "Dude, it's no good to use FAT-32, do the NTFS partition." Well ... Once such a thing. We reboot, load the disk with Windows, select the partition, say format it in NTFS. He does it all safely, copies files, comes to the first reboot and ...
As you already guessed, in the first version of the error with FAT on the face, we probably have some kind of problem with determining the partition, but with ntfs things are still better. At a minimum, it is already trying to boot. And I decided to act in this direction. I must say that the item "convert section to ntfs" categorically did not work for me, I do not know why. And then I decided - it means you have to do it manually, although they wrote on the forums that it would not work.
What I've done?
1) The bootkamp creates a partition. FAT-32
2) We are loaded with life-cd. Personally, I only got hooked by infra cd
Further, I thought that I needed to start some partition magic, but I was unpleasantly surprised that he sees 32 as an unformatted partition, I couldn’t do anything with it. Then the command line remained - convert c: / fs: ntfs ... And this also had no effect - he does not want to, he swears with an error.
Here it is necessary to make one more digression. When you install windows or break some partitions with some other Windows tool, the bootkamp starts working incorrectly with them. It turns out that before the Windows partition bootkamp places part of its information. I don’t know what is there, how he uses it. But if you demolish the fat-32 partition that the bootkamp created, and create a new partition - these wonderful bytes are erased by the newly created partition, and as a result we see what I'm writing about. Partition magic resolutely did not see this magic mini-section, and also offered an unacceptable solution for me - to tear down the veil and re-make ntfs.
And then I take it and use the simplest solution - well, to hell with all this conversion. Take and format what is. But not the way I'm used to - you take down the portion, create it again .. And I went to "my computer", with the right mouse button and woo, then you know. My reasoning was already at the level of a freshman blonde: FAT-32 was probably created on the principle of "that's from this sector to the very end, understand?". And, probably, when I format in NTFS, the beginning of this section will go exactly from the same place, without touching the magic bytes of the bootkamp ...
Well, you understand, when I tried everything, I can only hope for such not-so-complete action logic. And it turned out. It turned out to format ntfs, although it was difficult to wait for another.
But that's half the battle. Reboot, insert the windows license, boot from it. When choosing partitions, we see that ntfs is waiting for us, i.e. I do not need to do any manipulations. Leaving the file system unchanged ...
Bottom line - I have Windows there. I got up without any problems. It was later that I thought that it was possible to install the ntfs drivers in the poppy (for example, a paragon), and format this unfortunate partition from under disk utility ... Or else ... But, that's another story.
I don’t know how the rest of the Khabrovsk citizens, whether they faced this, also fought in other ways. But I hope that I can help at least one user with my modest note.
PS
Moved to Mac OS X
Instead of PPS
My second habratopik, so do not scold