New modified BOOT-132 allows you to boot retail DVDs

[ztauhid]

I wrote the iso image on cd with the the following contents:-

 

boot

Initrd.img

isolinux

isolinux.bin

mboot.c32

 

When I try booting from the cd I get: " ISOLINUX 3.63 2008-04-10 isolinux: image checksum error, sorry...... Boot failed: press a key to retry"

 

My configuration:-

Intel Mobo DG33FB

Intel Core2 Quad (Q6600) 2.4GHz

Transcend 4GB (2GB x 2) DDR2 RAM (800)

SATA 250GB (Samsung)

nVidia 8400GS (256)

Sony Superdrive

 

Can anyone shed some light please.

Thanks

[iRule]

Does anybody have the kext files for the P45 Gigabyte motherboards ? They all seem to be using the same chipsets and controllers.

 

My motherboard is GA-EP45-DS3P.

 

Your help is appreciated

[Colonel]

I tried using boot-132 to boot the retail DVD and I'm getting all sorts of errors about StartupItems.

Anyone have any ideas?

[sheff88]

Hello! I have a problem: I installing original MacOS Leopard 10.5.4. I am for this purpose loaded with Kabyl-boot-cd. Installation is started. Sees a hard disk. But does not allow to install. Says that it is necessary to mark under the scheme apple. What to do?

[CBEugene]

I wrote the iso image on cd with the the following contents:-

 

boot

Initrd.img

isolinux

isolinux.bin

mboot.c32

 

When I try booting from the cd I get: " ISOLINUX 3.63 2008-04-10 isolinux: image checksum error, sorry...... Boot failed: press a key to retry"

This is just corrupted system files in cd image. I was in this situation too and managed it that way: you should download some other 123 cd image (there is four or five images of 123-boot) and take system files (boot, isolinux, etc) from there.

 

PS: sorry for my bad english :-(

[Foodie Monster]

I need your help guys

 

I can't go pass the screen that asks me to select my drives. I choose 80 or 81, then I press ENTER.

 

The prompt takes me to the "boot:" again, I press ENTER and takes me back to the previous drive selection menu.

 

I insert the Retail Leopard 10.5.4 into the drive and it never even spins to load !!

 

I restart the computer hoping that it'd boot from the DVD but no go..

 

What am I doing wrong ?

 

Do the HDDs have to be formatted in HFS+ ? Mine are NTFS !! Does that matter ? I have no other way of loading an operating system to format them as HFS+ !

 

Is there something that I'm not doing right ?

 

The booloader loads fine (the modified one), while the original one never loads !

 

Thanks

 

You need to use the search button. This has been answered a billion times, and like 5 times by myself alone in this very thread. Why the hell are you all so lazy is beyond me. Just follow these 2 links and read CAREFULLY. And once you are done reading, READ THEM AGAIN.

 

1: http://forum.insanelymac.com/index.php?s=&...st&p=863304

2: http://forum.insanelymac.com/index.php?s=&...st&p=863348

 

And here's MACinized's take on the same procedure in case mine isn't clear enough.

 

3: http://forum.insanelymac.com/index.php?s=&...st&p=863453

 

Next time, use the search function.

[OriginalMACNUT]

I need your help guys

 

I can't go pass the screen that asks me to select my drives. I choose 80 or 81, then I press ENTER.

 

The prompt takes me to the "boot:" again, I press ENTER and takes me back to the previous drive selection menu.

 

I insert the Retail Leopard 10.5.4 into the drive and it never even spins to load !!

 

I restart the computer hoping that it'd boot from the DVD but no go..

 

What am I doing wrong ?

 

Do the HDDs have to be formatted in HFS+ ? Mine are NTFS !! Does that matter ? I have no other way of loading an operating system to format them as HFS+ !

 

Is there something that I'm not doing right ?

 

The booloader loads fine (the modified one), while the original one never loads !

 

Thanks

[iRule]

Guys, it turned out that my Leopard DVD was the cause of the problem. I burnt it using Disk Utility and it worked fine. No need to bash yourself up, and yes, I DO search before I post any question.

[sheff88]

I have updated Kalyway 10.5.2 through AppleUpdate. I was loaded with Kabyl-boot-cd. Loading has almost passed successfully. There was a desktop background, the mouse cursor, then it began to carry out cyclically "login window started" But the kernel after all was loaded! What to do?

[Dannyarr]

Having issues adding a kext to the images. The original BOOT-KABYL-BUMBY.iso fails to boot completely. Just gives a (i think checksum) error. The generic.iso works. So I tried following the guide to add a kext to it, however the resulting iso does not boot. It's as if it's not there at all and the PC boots into windows.

 

I would appreciate any help. I am creating the .iso on my iBook running Leopard and then burning it with ImgBurn on my PC. I tried just running the .iso in VirtualBox and it doesn't work there either so I don't think burning is the issue but rather the .iso creation on the iBook.

[Goz]

From my experience the GA-P35-DS3L is a mess to use with Boot-132. Really, it's a mess.

 

-Stell

 

I have to agree...

[coreduo0099]

Hello,

 

I have been trying to get the EFI booting working and wanted to test on a spare ATA drive laying around. I have driven myself crazy trying to get a system working. I am very confident that my cd isos are good.

 

But, no matter if I have the proper kexts or not, I cannot get past the waiting for boot message.

 

 

After I had given up, i decided to take my perfectly working 10.5.5 system multi boot drive which is Disk0s2 and just for the heck of it type in rd=disk0s2 at the chameleon darwin boot prompt. (fully expecting it to boot) (s1=windows, s2=primary osx, s3=emergency osx). It does not work, yet if I let it timeout and enter nothing, it does work.

 

I also added rd=disk0s2 to my boot.plist under kernel flags and it will not boot until I remove that section of the plist file.

 

This seems completely wacky.. I am using an intel 915GV chipset with a P4.

 

But I guess it does explain somewhat why my ISOs never would work. Heck, even the boot disk seems to lose itself when the rd=disk0s2 parameter is entered.

 

Any ideas?

 

BTW, I built the working 10.5.5 system using ideneb 1.3 using the 9.4 stagexnv kernel, ICH patch, and AC97 patch. Works flawless as a non-efi mbr based system. (unless I specify the rd= command at the chameleon darwin loader prompt. (is this a chameleon issue?)

 

Thanks

[RS197768]

I couldn't find it in the topic. But is bootcamp fully working with this method? Or is it still possible to dual-boot. This because i need a native XP install for work. But i would like to have OSX for other simple internet etc etc when i am travelling or when i am in Hotels. Or should i just use kalyway/jas/iatkos/ideneb etc etc.

 

Please advice.

[mickeytwotimes]

just wanted to let you all know, i got a mostly functional install using this method.. just in case some of you dont know at the prompt try typing in 9f when asking for the drive to boot from, that ought to get you the option for dvd. i used this on an HP a6120n, installed on an extra hard drive- version 10.5.4

 

i have to start the osx boot process (even after install) with the "modified" boot kabyl bumby disc found on the first page of this thread, and had to wipe that extra hard drive and partition it guid, just so ya know

[OriginalMACNUT]

Guys, it turned out that my Leopard DVD was the cause of the problem. I burnt it using Disk Utility and it worked fine. No need to bash yourself up, and yes, I DO search before I post any question.

 

I used to have those problems along time ago, but have switch from memorex to sony disc. This has solved all my bad media.

[santitf]

Hello.

 

I used 132 boot for p5k and a leo retail for a few weeks (before the 10.5.5 update).

 

I make an iso with the boot and leo retail and the install, chamaleon and update works fine (10.5 to 10.5.4).

 

The problem is that i try to install a fresh leo with the same method and leo installs well but system don't boot when update to 10.5.5 (do the 2 reboot but freezes before start).

 

What's the problem?

Thanks

[woodworker]

All three boot.iso (original, generic, and p35) work fine. Using –v –f when booting retail DVD (10.5.4) stops at MAC Framework successfully initialized using 16384 buffer headers and 4096 cluster IO buffer headers.

 

 

Before boot: screen and after img is loaded the message System config file ‘com.apple.boot.S/Library/Preferences/System Configuration/com.apple.boot.plist’ not found is flashed.

 

 

SATA is set at AHCI. Tried power setting S1 and S3. cpus=1, ect. All leading to the same stop point. If run without –v then the apple circle of death appears.

 

 

Have spent hours and purchase a retail version of Leopard to no avail.

 

 

Can anyone help or will I have to still dream of owing a MAC!

 

 

Thanks

[lstep]

Chameleon installs, among other things, a file called boot on your hard drive's root folder (/). Your BOOT132 CD has a boot file as well on it's own root. You need to boot from the CD, and once in OS X, replace the boot file from your root folder on your HDD with the one that's on the CD. Then, you open the disk image that's inside the BOOT132 CD (I forgot right now if it's a .iso or .dmg, but you know the one). Mount that, and inside you'll find an Extras/Extensions/ folder. Copy the Extras folder (and the Extensions folder along with the .kext inside) to your hard drive's root folder (where your boot file is, along with your System, Library, Users, etc. folders are).

 

Once that's done, rebooting without the CD should work.

 

I didn't copy the boot file and my system booted just fine (did everything else though). If one needs to add a kext onto the hard drive can it go into /Extra/Extensions? 3 kexts I have that deal with sound and restart/reboot only work when I put them in /System/Library/Extensions . I'd like to not have to do that. Is there a way to put them in /Extra/Extensions and have them work there? Perhaps the bootfile is related to all of this. If a kext is in /Extra/Extension does it disable one with the same name in Extensions in the System/Library?

 

Just a bit confused about that Extra folder.

 

ls

[Foodie Monster]

I didn't copy the boot file and my system booted just fine (did everything else though). If one needs to add a kext onto the hard drive can it go into /Extra/Extensions? 3 kexts I have that deal with sound and restart/reboot only work when I put them in /System/Library/Extensions . I'd like to not have to do that. Is there a way to put them in /Extra/Extensions and have them work there? Perhaps the bootfile is related to all of this. If a kext is in /Extra/Extension does it disable one with the same name in Extensions in the System/Library?

 

Just a bit confused about that Extra folder.

 

ls

 

You kinda almost get the idea. Basically, you *need* to replace the boot file on your HDD's root with the one that's on your BOOT132 CD. Why? Because that boot file is the one that calls for the .kext files placed in \Extras\Extensions. The reason why your system is booting just fine now is because the extensions were probably installed in the \System\Library\Extensions folder. And yes, that'll work, but as you say, if tomorrow you upgrade to, say, OS X 10.5.6, those extensions in the *real* extensions folder will probably be overwritten by the system update. However, if you put those kext files in \Extra\Extensions AND have the BOOT132's boot file in place of Chameleon's one on your HDD root, those files inside that folder will run *before* the ones on the \System\Library\Extensions run, disabling the ones that would make your system not run, without having to manually add them anywhere after each system update.

 

To wrap up: if you put that Extras folder on your HDD, and the boot file from the CD onto the HDD replacing Chameleon's boot file, you'd be a) replicating the BOOT132 CD's effect from "cancelling" the \System\Library\Extensions\ stuff while actually booting the system and future proofing so that you don't have to deal with replacing kexts after each system update.

 

I hope that clears it up, I tend to ramble.

[JaE-V]

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)

 

THX!

[lstep]

[ ]

 

To wrap up: if you put that Extras folder on your HDD, and the boot file from the CD onto the HDD replacing Chameleon's boot file, you'd be a) replicating the BOOT132 CD's effect from "cancelling" the \System\Library\Extensions\ stuff while actually booting the system and future proofing so that you don't have to deal with replacing kexts after each system update.

 

I hope that clears it up, I tend to ramble.

 

Thank you very much. That makes it very clear. It all makes sense now!

 

Just one quick followup. If I then add a kext into /Extra/Extension on the hard drive do I have to change the boot file? What permissions would the kext have to have. Is it enough to just have 777 for the /Extra and everything inside? Repairing permissions using Disk Utility will not handle anything in /Extra/Extensions .

 

ls

[Foodie Monster]

Thank you very much. That makes it very clear. It all makes sense now!

 

Just one quick followup. If I then add a kext into /Extra/Extension on the hard drive do I have to change the boot file? What permissions would the kext have to have. Is it enough to just have 777 for the /Extra and everything inside? Repairing permissions using Disk Utility will not handle anything in /Extra/Extensions .

 

ls

 

I'm not sure what you mean by "having to change the boot file". This is simple. If you want to use the \Extras\Extensions\ method of loading .kexts when your computer starts, you need to have the BOOT132 CD's boot file on your HDD's root - replacing the one that Chameleon installs for you. Once that's done, you don't need to change that file again. It's a "only once" step. After that, just dragging and dropping .kexts into the \Extras\Extensions\ folder should do the trick - I personally never changed the permissions on any of the files in there, but it may be because the correct permissions were set beforehand - again I'm not exactly sure.

[i_Geek]

have anyone tried to use it with a Shuttle K48 (barebone system) ?

 

thanks

[ReLaXXeR]

I'm not sure what you mean by "having to change the boot file". This is simple. If you want to use the \Extras\Extensions\ method of loading .kexts when your computer starts, you need to have the BOOT132 CD's boot file on your HDD's root - replacing the one that Chameleon installs for you. Once that's done, you don't need to change that file again. It's a "only once" step. After that, just dragging and dropping .kexts into the \Extras\Extensions\ folder should do the trick - I personally never changed the permissions on any of the files in there, but it may be because the correct permissions were set beforehand - again I'm not exactly sure.

 

sorry but i installed only the chameleon hdd tool and i NEVER changed the boot file and when i boot with in verbose mode i can see that all my kexts getting loaded!

 

only my applehda won't and i am searching for the problem!

so long...

relaxxer

[Solow]

sorry but i installed only the chameleon hdd tool and i NEVER changed the boot file and when i boot with in verbose mode i can see that all my kexts getting loaded!

 

only my applehda won't and i am searching for the problem!

so long...

relaxxer

 

 

Hmmm, could it be that the version of Chameleon you got already has the "Extras folder loading script" within it? That would make sense if you see your special Hackintosh kexts being loaded at boot time. Of course they might also be loaded at boot time from having installed them in your normal Extensions folder. I haven't paid that much attention to exactly when they do load. As long as it works for you - you are golden!

 

Enjoy your Hackie!