Jump to content

Crack Boot Camp for EFI v7.2


i_am...me
 Share

36 posts in this topic

Recommended Posts

Since EFI v7.2 allows booting of GUID partitions, we cannot boot in to windows since we need an MBR, but boot camp must write a boot-loader of some sort to be able to boot in to windows.

 

Here is the required ROMS

<key>DARequiredROMVersions</key>
<array>
	<string>IM41.0055.B08</string>
	<string>IM42.0071.B03</string>
	<string>IM51.0090.B03</string>
	<string>IM52.0090.B03</string>
	<string>IM61.0093.B01</string>
	<string>MP11.005C.B04</string>
	<string>MB11.0061.B03</string>
	<string>MBP11.0055.B08</string>
	<string>MBP12.0061.B03</string>
	<string>MM11.0055.B08</string>

if we can crack boot camp and make "hack camp" so it wont check the ROM we can install windows again on our machines and boot in to them.

Just a though...

Link to comment
Share on other sites

i though about it more, If we could create a program similar to acronis but for a mac. it could work, but we would need the boot files that get written to the boot camp drive.

I just tried installing windows and it installed but it wouldnt boot at all after that so i re wrote the boot loader and now im back but i couldnt boot in to the vista partition so i deleted it, thank the lord for GUID,didnt even show up in the F8 boot menu.

Link to comment
Share on other sites

This would be an interesting development... it seems possible now. I just used the 'reverse-Boot-Camp' phrase to explain to a co-worker how I got Leopard on my Dell. Imagine using Boot Camp on a reverse Boot Camp box.

 

/mindblown.

Link to comment
Share on other sites

rEFIt might work, but doesnt boot camp just work as partitioning software and the real tricks like BIOS emulation and such are left to the Mac's firmware?

Boot Camp is a Unix based app. i plugged the main file in to a hex editor and i saw that it writes something called "MDosStandard" or sumthing like that to the partition. And it wounldnt really be bio emulation it would be MBR emulation.

 

check the hex dump above

Link to comment
Share on other sites

If you are using a pc, you already have a chance to use Windows Genuinely. Why bother bootcamp, which is a bridge for mac to pc?

 

I am just wondering if there is a way to run your windows from vm or parallels (their bootcamp option)...

Link to comment
Share on other sites

If you are using a pc, you already have a chance to use Windows Genuinely. Why bother bootcamp, which is a bridge for mac to pc?

 

I am just wondering if there is a way to run your windows from vm or parallels (their bootcamp option)...

With EFI v.7.2 you can boot GUID partition tables, so no more NTFS or FAT32 Booting thats why we need boot camp. i have a feeling it write a boot loader to the boot camp partition since there is very small difference to the EFI im running and a real mac is running

Link to comment
Share on other sites

Because you're not running EFI!

 

rEFIt won't work either.

 

There's a big difference between a fancy version of the Darwin bootloader which is basically like Natit/Nvinject for booting, and actually having EFI firmware on your machine. Some of you don't seem to get what isn't a very subtle distinction!

Link to comment
Share on other sites

Because you're not running EFI!

 

rEFIt won't work either.

 

There's a big difference between a fancy version of the Darwin bootloader which is basically like Natit/Nvinject for booting, and actually having EFI firmware on your machine. Some of you don't seem to get what isn't a very subtle distinction!

 

Did you even read was EFI v 7.2 was about?

http://netkas.org/?p=36

Link to comment
Share on other sites

With EFI v.7.2 you can boot GUID partition tables, so no more NTFS or FAT32 Booting thats why we need boot camp. i have a feeling it write a boot loader to the boot camp partition since there is very small difference to the EFI im running and a real mac is running

 

Hehe, as I didn't go that far with EFI 7.2 to catch up with what ToH has done, I will stick with my MBR P/T and run old multi-boot on PC. Don't wanna waste time to play Boomerang! :P:D

Link to comment
Share on other sites

Because you're not running EFI!

 

rEFIt won't work either.

 

There's a big difference between a fancy version of the Darwin bootloader which is basically like Natit/Nvinject for booting, and actually having EFI firmware on your machine. Some of you don't seem to get what isn't a very subtle distinction!

 

Yeah, isn't all the EFI flashing just an EFI emulator running in the BIOS, and not a true EFI firmware?

Link to comment
Share on other sites

Gents, please don't get distracted by all the "is it or isn't it EFI" stuff.. fact is each release of pc-efi moves closer to functioning like true EFI, even though it certainly began as a clever hack to the darwin bootloader.

 

Previously, the idea of running bootcamp on a hackintosh was pointless, due to all the differences between the hardware. With GUID partitions now coming into play, its functionality might be not only useful, but necessary in order to dual boot, and the strides being made with pc-efi functionality these days, it certainly deserves a second look.

Link to comment
Share on other sites

No, because it's important for people to know. The number of times I've been asked stupid questions like 'will my computer's BIOS be erased' and 'will my computer go dong' beggars belief.

 

It didn't just begin as a clever hack to the Darwin bootloader. It is still very much a clever hack to said bootloader. I'm not for a moment saying it's not a good thing. It's very important to OSX86 users as it makes life much easier for us (i.e. by bypassing the need for device injector kexts in the long term, allowing us to use vanilla updates from Software Update, etc.) I just want to make sure people understand what it actually is.

 

No matter how good this modified Darwin bootloader gets, it will never be the same as running on a real EFI system. EFI modules are written to hand over values such as those needed to initialise the graphics card or HDA codec with no work on the user's behalf. With a hacked bootloader we still need to know what EFI would have reported to the OS and 'hard code' that into the bootloader. It will always have limitations when compared to a real Mac, especially when new hardware comes along on the Apple side, and we spend weeks working out how to get it to initialise correctly. If we had real EFI, we could just load the Apple modules for said hardware and forgo the reverse engineering. Plus, we will never be able to use a totally unmodifed Apple install disk.

 

Anyway, back to the topic, why can't we just create hybrid MBR/GPT disks like Bootcamp does and then Windows should boot fine? We don't actually need Bootcamp to do that, do we?

Link to comment
Share on other sites

Anyway, back to the topic, why can't we just create hybrid MBR/GPT disks like Bootcamp does and then Windows should boot fine? We don't actually need Bootcamp to do that, do we?

 

That actually spounds like a useful suggestion.. what does a hybrid GPT/MBR disk look like & how would one go about making one?

Link to comment
Share on other sites

Well i have 1 drive as mbr which is my xp and the other as guid which is leopard and both work just great only prob i have now with guid is the fact that now in windows with macdrive it cant see the apple partitions :)

other than that its great i use software updates straight from apple replace kernel with patched and bobs ya auntie good job all developers well done

Link to comment
Share on other sites

I didnt want boot camp so when i hold the the option key while booting i would get the whole nice boot menu. I wanted it so i could be able to boot windows on my system, Now that i can re-size partitions as i wish when ever i want...

 

But when i looked through the lines the only thing it checks is the IOTree for the boot rom version.

Took the two lines out in the whole think and it still says to update my boot rom...

Link to comment
Share on other sites

 Share

×
×
  • Create New...