Jump to content

New modified BOOT-132 allows you to boot retail DVDs


f41qu3
 Share

1,286 posts in this topic

Recommended Posts

You didn't say anything about what else, if anything, is on your hard drive. How is it partitioned? GUID or MBR. If you are going to install from an Apple retail install DD, you will need to partition your drive selecting GUID.

 

Before you do anything, you might wish to read the guide supplied in this post [Guide] Boot from EFI partition, zero modification installs on Intel SSE2 or better It describes a method to keep your vanilla install in it's pristine condition while also applying the needed override extensions.

 

The boot-132 cd does not remove or install any kext after the install. It's function is to boot a patched kernel, if required, and override extensions during the boot process. Nothing more. And, that's a good thing.

 

Do some more reading before you begin. And, good luck.

 

I've read a lot about BOOT-132. It's just that some questions are not well answered around the topics.

My HD is MBR partitioned.

It has a dual-boot for Vista and Leopard.

 

Can I install Leopard with Retail DVD in my MBR partitioned HD, assuming that I don't want to use that EFI Partition method?

Link to comment
Share on other sites

I've read a lot about BOOT-132. It's just that some questions are not well answered around the topics.

My HD is MBR partitioned.

It has a dual-boot for Vista and Leopard.

 

Can I install Leopard with Retail DVD in my MBR partitioned HD, assuming that I don't want to use that EFI Partition method?

 

Short answer is no. The longer, more complicated answer is, yes - if you can modify and burn a new, almost, retail dvd. The install mpkg checks for GUID partitioning and rejects the install if not found. There are other threads in these fora that describe the process of making that modification and burning a new dvd.

 

Another option is to get an 8Gb or larger usb flash/hard drive. Format it to GUID and use disk utility to restore your retail install dvd to the usb drive. Make the install mpkg modification there. Then use the boot-132 cd to boot that drive and install from there. I know this method works. It is the one I use. Although all my drives are partitioned GUID, I still find it easier and faster to use a usb stick install drive when I want to do another, start over, install.

Link to comment
Share on other sites

Short answer is no. The longer, more complicated answer is, yes - if you can modify and burn a new, almost, retail dvd. The install mpkg checks for GUID partitioning and rejects the install if not found. There are other threads in these fora that describe the process of making that modification and burning a new dvd.

 

Another option is to get an 8Gb or larger usb flash/hard drive. Format it to GUID and use disk utility to restore your retail install dvd to the usb drive. Make the install mpkg modification there. Then use the boot-132 cd to boot that drive and install from there. I know this method works. It is the one I use. Although all my drives are partitioned GUID, I still find it easier and faster to use a usb stick install drive when I want to do another, start over, install.

 

Ok, too complicated lol

I think the best solution is to buy a new HD and use it for Leopard with GUID partition table.

 

Another question...

After installation with Retail DVD, won't AppleIntelCpuPowerManagement.kext cause kernel panic?

So I must boot with BOOT-132 CD and delete that kext, right?

Link to comment
Share on other sites

Ok, too complicated lol

I think the best solution is to buy a new HD and use it for Leopard with GUID partition table.

 

Another question...

After installation with Retail DVD, won't AppleIntelCpuPowerManagement.kext cause kernel panic?

So I must boot with BOOT-132 CD and delete that kext, right?

 

No, you don't need to remove the power management kext. That is what disabler.kext is for. It loads early in the boot process and disables the power management kext so it won't cause a problem.

 

The idea here is to make the least possible number of modifications to the vanilla install so that, later, when you run a software update it won't cause problems. If you just delete the power management kext, it could get added back in on a later update. If you disable it, then no problem with it later.

 

The same is true for any of the other extensions provided by Apple. It's better to add an extension like disabler or nvinject that won't be replaced by future updates.

Link to comment
Share on other sites

okay earlier panic fixed.

 

Now one FINAL issue I'm having!

 

I have an ATi 4870 graphics card. I'm aware no kexts or drivers etc officially exist for mac, but is it possible to kind of trick it a little? like loading on 3870 drivers so it will at least work BETTER then what it is now? I dont get any system effects without some lag here n the transparency is gone and not even an option...

 

any ideas people?

 

also one final thing, I'm slowly installing the system upgrades offline one by one to make sure i know which one messes things up if something goes wrong, but can you uninstall a system patch once its been applied?

 

Thanks!

Link to comment
Share on other sites

I have a .dmg image of Retail Leopard here but it's hard to find dual layers DVDs around here.

How can I boot the image from my HD using BOOT-132?

 

You have a few options. the best ones - IMHO - are external USB drives. If you can boot a USB drive, either through your bios or some other method, then you can use disk utility to partition an external drive and restore the .dmg image to it. Then, modify it to be able to boot, use the boot-132 cd or, use the efi partition method described here: [Guide] Boot from EFI partition, zero modification installs on Intel SSE2 or better. I personally use the efi partiton method on an 8GB SanDisk Cruzer USB stick.

Link to comment
Share on other sites

You have a few options. the best ones - IMHO - are external USB drives. If you can boot a USB drive, either through your bios or some other method, then you can use disk utility to partition an external drive and restore the .dmg image to it. Then, modify it to be able to boot, use the boot-132 cd or, use the efi partition method described here: [Guide] Boot from EFI partition, zero modification installs on Intel SSE2 or better. I personally use the efi partiton method on an 8GB SanDisk Cruzer USB stick.

 

Can I restore the .dmg image to a partition in a MBR partitioned HD?

Link to comment
Share on other sites

Can I restore the .dmg image to a partition in a MBR partitioned HD?

 

I believe so, but you realize, you can't install from an unmodified retail install dvd to a partition on an MBR partitioned drive. The install process checks for GUID and fails if not found. There are other threads in the forum that discuss how to modify the isntall process to bypass the GUID check.

Link to comment
Share on other sites

I believe so, but you realize, you can't install from an unmodified retail install dvd to a partition on an MBR partitioned drive. The install process checks for GUID and fails if not found. There are other threads in the forum that discuss how to modify the isntall process to bypass the GUID check.

 

Thank you for the tips.

I've found a guide in Tutorial sub-forum. Gonna try it later.

Link to comment
Share on other sites

Thank you for the tips.

I've found a guide in Tutorial sub-forum. Gonna try it later.

Hi, I didn't know you could install straight to a MBR partition, this is excellent - could you post a link to the tutorial please as I've searched and cannot find it. ;) Thanks. ;)

Link to comment
Share on other sites

i'm looking for a way to make a boot USB HDD installer image of the leopard installer so i can install leopard from the usb HDD to my internal HDD

it this something i con do with boot-123 ?

 

Short answer - yes.

 

Longer answer - I used disk utility to format an external usb drive as GUID ans then restore the retail install dvd to the partition on the usb drive. The last step was to use Munkys EFI partition boot method to make the disk boot without the boot-132 cd. Works great.

Link to comment
Share on other sites

Theoretically, if I were to get retail Leopard DVD to work for GUID and Windows XP. Since XP with 32 architecture can only detect MBR (which comes as part of the GUID?), then I can't access any of the other GUID partitions with Windows.

 

Do the 900 GMA QE/CI patches and other non-retail stuff work for retail distros or must they be patched?

Link to comment
Share on other sites

Short answer - yes.

 

Longer answer - I used disk utility to format an external usb drive as GUID ans then restore the retail install dvd to the partition on the usb drive. The last step was to use Munkys EFI partition boot method to make the disk boot without the boot-132 cd. Works great.

 

will give it a spin

Link to comment
Share on other sites

Hi there. I finally got my ds3p (not the R, but same chipset) and I'm trying to install Retail Leo using Boot 132.

 

I used the iso for noob and it doesn't work, once I put the Leo install disk and it boots, I get the grey apple screen with the little sparkling circle (beach ball?). After a while, a stop-kind-of sign and the boot doesn't keep on going.

 

I wanted to try the boot modified file which is linked in the first page, but I don't know how to edit an iso file.

 

Can you help me out?

Link to comment
Share on other sites

Just a quick guide to add kexts and make iso from OS X.

 

Download this package

 

Open terminal

 

Make a directory

mkdir newiso

copy following from the package into newiso:

- boot

- initrd.img

- isolinux.bin

- isolinux.cfg

- mboot.c32

 

to edit initrd.img set rw permission

chmod 777 newiso/initrd.img

then you should open it

hdiutil attach newiso/initrd.img

now copy the kext you need into /Volumes/initrd/Extra/Extensions/

cp -R mykext.kext /Volumes/initrd/Extra/Extensions/

I suggest you add dsmos.kext NVkush.kext and if you have alc889 also HDAenabler.kext and if you need kext to boot your root device also

One thing to notice, the kexts need this in the info.plist file:

 

		<key>OSBundleRequired</key>
	 <string>Root</string>

or

 

		<key>OSBundleRequired</key>
	 <string>Console</string>

or they will not load. To add those properties you can use nano and need to be added at the end of the plist file just before the last lines:

</dict>
</plist>

If you need a bigger image you may resize it with this comman, choose appropriate size

hdiutil resize -size 20MB newiso/initrd.img

when you are finished adding you eject your initrd image

hdiutil detach /Volumes/initrd

now you need to create your iso

hdiutil makehybrid -o new.iso newiso/ -iso -eltorito-boot newiso/isolinux.bin -no-emul-boot

and then burn new.iso with your favorite burner (first try with a cd-rw disc so you can redo it later iwthout wasting cdr disc)

 

Hi Superhai, how do I create info.plist file? I don't know how to create ;) Can teach me? Where do i put e info.plist file?

Link to comment
Share on other sites

Hi Superhai, how do I create info.plist file? I don't know how to create ;) Can teach me? Where do i put e info.plist file?

why do u need to create an info.plist file? if you're just looking for a way to create boot-132-disc loader for ur computer, u can try what's in my signature. it's easy as 1-2-3. ;)

 

+ + +

 

Picture%201.png

 

a new Finder window will open to show the "Contents" folder.

 

Picture%202.png

 

if u have a plist editor, ur plist editor will open the plist file. if not, the TextEdit app will open it.

 

Picture%203.png

 

take note of the last 4 lines.

Link to comment
Share on other sites

Hi Superhai, how do I create info.plist file? I don't know how to create ;) Can teach me? Where do i put e info.plist file?

 

You don't need to create a plist file. They already exist inside each of the kext you are using. What the guide you referenced is telling you is to edit the existing info.plist file and make sure the lines in the guide exist at the end of the plist.

 

Using Finder -> right click the kext file -> select Show Package Contents. In Contents, find Info.plist -> right click Info.plist -> select Open With -> select Property List Editor if you have the Developer Tools installed or, TextMate or, whatever text editor you have. Scroll down to the end and look.

Link to comment
Share on other sites

 Share

×
×
  • Create New...