BootCDMaker

[Trauma!]

Trauma,

 

I would like to add Snow's Extensions.mkext for Gigabyte (E)P35 & (E)P45, in AHCI mode, so that a BootCD for SL can be made on OS X 10.5.x.

Also, I included my GFX string of HD4870 1GB in com.apple.Boot.plist.

 

Just add you're SL Extensions.mket to "Extra Contents" and run BootCDMaker. If mkext is present BootCDMaker will use it.

 

Bye.

[verdant]

I too get ebios errors or failed boots using CD-RWs but not with DVD+RWs.......

[pirloui]

My SL DVD just keeps kernel panicking a second after boot. It appears to be disabler.kext not being loaded, and then appleintelcpupowermanagement causing the panick.

Are you guys using disabler? Does it have to be a certain version?

Is FakeSMC an alternative to disabler.kext?

I also tried arch=i386 -legacy but just the same.

[BladeRunner]

My SL DVD just keeps kernel panicking a second after boot. It appears to be disabler.kext not being loaded, and then appleintelcpupowermanagement causing the panick.

Are you guys using disabler? Does it have to be a certain version?

Is FakeSMC an alternative to disabler.kext?

I also tried arch=i386 -legacy but just the same.

 

FakeSMC is not an alternative for disabler. It is a replacement for dsmos. You need SL versions of nearly all the kext.

 

Look at the list of SL related kext on Stell's blog and get NullCPUPowerManagement . That should correct the KP you mentioned.

 

Also, here is a list of SL related sites & tips that came from the #snowleopard IRC channel SL related tips & sites

 

Hope it helps. Good luck.

[genzai]

Hi Trauma,

I have been using your BootCD Maker very successfully for a couple of weeks now and posted a guide up for my motherboard that uses it.

 

Is it possible to make a version that uses PCEFI 10.3 as the bootloader? Chameleon RC3 GraphicsEnabler will not work on our boards but PCEFI 10.3 does. This would really help streamline my guide since everyone could use the same com.apple.Boot.plist regardless of video card used.

 

thanks,

/g

[Trauma!]

genzai,

 

I can't certify this will work, it should normally. btw if you don't have the cdboot version of PCEFI you will have to use legacy mode.

 

To replace the bootloader "right click" on the app => "show package content" then navigate to :

 

Contents/Resources/Scripts/loaders/isolinux and replace "boot" file.

 

don't touch or change anything else, and this should work fine.

 

@ All: BootCDMaker have been updated today , look at the first post.

[miki88]

Did anyone managed to make BootCD with this? I just tried and could not make.

 

First, Extra Contents is an Alias linking to destop folder of user Tom. Probably wont work because my name is not Tom . I fixed alias to link existing folder on my computer, then copied Extensions folder form Extras in that folder. And then I copied mach_kernel , dsdt.aml and boot.plist. When I start building proces I always get this

 

24-09-18:31:26: #### Boot CD Maker starting process ####
24-09-18:31:29: Work folder created
24-09-18:31:29: Work folder populated
24-09-18:31:29: ## Mkext creation starting ##
24-09-18:31:31: Can't stat /Applications/BootCDMaker_1.2/BootCDMaker.app/Contents/Resources/Scripts/Preboot/Extra/Extensions - No such file or directory.
24-09-18:31:31: ## Mkext creation finished ##
24-09-18:31:31: ### File consistancy check failed / Extensions or mkext required ###
24-09-18:31:33: Process aborted / Cleaning up work folder

If someone knows what is the problem, please tell me .

[BladeRunner]

Did anyone managed to make BootCD with this? I just tried and could not make.

 

First, Extra Contents is an Alias linking to destop folder of user Tom. Probably wont work because my name is not Tom . I fixed alias to link existing folder on my computer, then copied Extensions folder form Extras in that folder. And then I copied mach_kernel , dsdt.aml and boot.plist. When I start building proces I always get this

 

24-09-18:31:26: #### Boot CD Maker starting process ####
24-09-18:31:29: Work folder created
24-09-18:31:29: Work folder populated
24-09-18:31:29: ## Mkext creation starting ##
24-09-18:31:31: Can't stat /Applications/BootCDMaker_1.2/BootCDMaker.app/Contents/Resources/Scripts/Preboot/Extra/Extensions - No such file or directory.
24-09-18:31:31: ## Mkext creation finished ##
24-09-18:31:31: ### File consistancy check failed / Extensions or mkext required ###
24-09-18:31:33: Process aborted / Cleaning up work folder

If someone knows what is the problem, please tell me .

 

I believe the problem is that the alias you fixed is pointing to the wrong place. On my system, where the app works correctly, the alias points to:

/Users/lrh/BootCDmaker/BootCDMaker_1.1f/BootCDMaker.app/Contents/Resources/Scripts/Preboot/Extra

The alias should point inside the application Contents, not to something on your desktop.

[Trauma!]

Hy all,

 

Yeah it's seems like the alias is buggy on the last release. I'll fix that soon. Just try to move BootCDMaker folder to one place to another this should fix the alias bug.

 

I'm now working on a GUI for the app, this should fix those kind of disagreements.

 

Bye.

[miki88]

Thanks for the reply I managed do make BooCD.iso somehow. But not to boot.

 

Could not fix the alias to point inside the .app, so I opened .app contents in finder and stuffed all those things in Extra folder without using that alias. Then I run the and build the ISO successfully.

 

But now it wont boot. I have .DS_Store files inside BootCD and Preboot.dmg. They showed up because I used damn Finder. Can they be the reason? When I try to boot, it starts, that line spins some time and then starts throwing errors. I think it says there is no ramdrive and then errors start appearing. Now I dumped boot disc from CD to hardrive to see if is readable. And it is readable. It is not a bad disc, something other is wrong. And CDs are not very cheap

 

 

--------

EDIT: I have built Boot CD again but this time without Chameleo GUI and now it boots fine .

[BladeRunner]

Thanks for the reply I managed do make BooCD.iso somehow. But not to boot.

 

Could not fix the alias to point inside the .app, so I opened .app contents in finder and stuffed all those things in Extra folder without using that alias. Then I run the and build the ISO successfully.

 

But now it wont boot. I have .DS_Store files inside BootCD and Preboot.dmg. They showed up because I used damn Finder. Can they be the reason? When I try to boot, it starts, that line spins some time and then starts throwing errors. I think it says there is no ramdrive and then errors start appearing. Now I dumped boot disc from CD to hardrive to see if is readable. And it is readable. It is not a bad disc, something other is wrong. And CDs are not very cheap

 

 

--------

EDIT: I have built Boot CD again but this time without Chameleo GUI and now it boots fine .

 

If you have Toast use it to burn your iso file and not disk utility. That should clear up the problems.

 

If you don't have toast and need to use disk utility for the burn, use DVD+/- RW media for the burn and not CD media. There is a problem burning this iso to CD media that is apparently not present on DVD media.

[nathan7]

Thank you for your efforts. Any idea what to do with this?

 

 

Edit: I deleted com.apple.Boot.plist and it works, but shouldn't I be able to include mine?

[nathan7]

I replaced boot in Contents/Resources/Scripts/loaders/isolinux with PC_EFI 10.3 boot, and created a Legacy boot disc, but as far as I can tell it is still using cdboot, even when I say hide the GUI and Legacy, I still see cdboot briefly, and the GUI. The permissions on the boot file I put it were the same. Also my graphics enabler doesn't work without the default pci1 of PC_EFI 10.3. Any thoughts? Thank you.

[mitch_de]

Can i use my Extensions.mkext from my working Snow Leo (10 MB) , because i NOT use any .kext or .mkext in /Extra , i have all in /S/L/E. ?

[Trauma!]

@ mith_de :

 

Of course you can add you mkext from leopard, there is no problems with the size.

 

@ nathan7 :

 

Its sounds like the boot.plist error is stupid as a "B" and not a "b". The app looks for com.apple.boot.plist and not com.apple.Boot.plist. I'll try to fix that soon. I've done test with the stock com.apple.Boot.plist and it works fine, i can't tell for now...

 

About PCEFI, if you replace "boot" file you have to use legacy mode. If you did it must work. btw, I will not support those kind of modifications.

 

Cheers.

[Diwad]

nvm

[Azimutz]

Hey trauma.. live report

So, i'm on Leo right now doing some more tests on v1.2.. i already did some, mainly driven by kext cache stuff (updated post #9).

All went fine on those builds with the app on Desktop, even the alias. Unpacked (Archive Utility) the app on Desktop, added all stuff (except Boot.plist and mkext) with copy/paste on the alias.. no problemos.

 

I was going to post but, remembered i didn't tested using the app from my Home in another partition.

First thing i do is unpack the app.. unpacked 1.2, test the alias (right->Show Original), error "... original item cannot be found."

Same thing on 1.1, works fine.

I copy 1.2 to Desktop, unpack, test alias, works fine.

I test again the alias in the app on another partition, brings me to the app on Desktop

I delete the app on Desktop, test the alias again, sends me to the deleted app in Trash.. wtf

 

Going to check on Snow...

 

A nice improvement on Snow is that, when we select a alias, if it points to a folder, the folder contents are showed instead of just a preview of the alias.. nice..

Same thing going on, on Snow.. with a little great difference; here the app is on the same volume as the Desktop (/Volumes/Home/Azi/blabla..), just on a different folder. It seems when unpacked on Desktop, the alias gets corrected.

 

hum.. Erase/Burn still only erases, even if the disk is already erased..

27-09-03:32:43: #### Legacy Boot CD image generated successfully ####

27-09-03:32:55: #### Boot CD burning process starting ####

27-09-03:34:05: Erase succeeded

27-09-03:34:05: #### Boot CD burning process finished ####

... and Burn, doesn't burn...

27-09-03:38:36: #### Legacy Boot CD image generated successfully ####

27-09-03:38:43: #### Boot CD burning process starting ####

27-09-03:38:43: #### Boot CD burning process finished ####

... with CD/DVD-RW.

 

Another thing i noticed.. when it's the app creating com.apple.Boot.plist, the system seems to think the file is a script

That's it.. for now..

 

See ya.

[BladeRunner]

I did some tests with v1.2 to check on the alias problem.

 

In the first test I unpacked the zip file to the desktop and then did a drag & drop of the "Extra Contents" alias to my terminal session. Then I deleted the desktop version and unpacked the zip file to a folder not on the desktop. The second drag & drop to the terminal was from that copy of the app. Notice the difference.

 

lrh ~ $ cd /Users/lrh/Desktop/BootCDMaker_1.2/BootCDMaker.app/Contents/Resources/Scripts/Preboot/Extra 
lrh ~ $ cd /Users/lrh/BootCDmaker/BootCDMaker_1.2/Extra\ Contents

 

EDIT: Ignore this! I made a mistake in the way I did the test. All the above is @#$#$%#. Sorry!

 

Update: OK! In an effort to redeem myself from the previous mistake. Here is a method to correct the alias if you don't want the app folder to exist on the desktop.

 

1) Copy the zip file to the location where you want the BootCDmaker folder to reside and unpack it.

2) Open the BootCDmaker folder and right click on the "Extra Contents" alias and select "Get Info"

3) It will most likely say that the original is located in /Users/Tom/BootCDmaker...

4) To correct this, move the "Extra Contents" alias to trash and empty trash. Then, right click the BootCDmaker app icon and select Show Contents. Drill down through Contents -> Resources -> Scripts -> Preboot and you should see a single folder called Extra. Right click Extra and select -> Make Alias. You chould now see two folders. Extra and the Extra alias. Drag the Extra alias into the BootCDmaker_1.2 folder and drop it. Now, rename the alias to "Extra Contents"

 

That should make the alias work the way Trauma! intended it to. Hope that helps until the next release corrects the problem.

[BladeRunner]

Here is another method to correct the "Alias" problem for now. It may be easier to use.

 

Open a terminal session and change directory ( CD ) into your newly unpacked BootCDmaker_1.2 folder. Remove "Extra Contents" and make a sym link to replace it.

lrh BootCDmaker $ cd BootCDmaker_1.2
lrh BootCDmaker_1.2 $ ls -l
total 2792
drwxr-xr-x@ 3 lrh  staff	 102 Sep 22 08:24 BootCDMaker.app
-rw-r--r--@ 1 lrh  staff  519424 Sep 22 08:26 Extra Contents
-rwxrwxrwx@ 1 lrh  staff	   0 Sep 10 06:18 Icon?
-rw-r--r--@ 1 lrh  staff	4189 Sep 22 08:59 ReadMe.rtf
lrh BootCDmaker_1.2 $ rm "Extra Contents"
lrh BootCDmaker_1.2 $ ln -s ./BootCDMaker.app/Contents/Resources/Scripts/Preboot/Extra MyExtras
lrh BootCDmaker_1.2 $ ls -al
total 784
drwxrwxrwx@ 7 lrh  staff   238 Sep 27 09:55 .
drwxr-xr-x  6 lrh  staff   204 Sep 27 09:53 ..
-rwxrwxrwx@ 1 lrh  staff  6148 Sep 22 07:46 .DS_Store
drwxr-xr-x@ 3 lrh  staff   102 Sep 22 08:24 BootCDMaker.app
-rwxrwxrwx@ 1 lrh  staff	 0 Sep 10 06:18 Icon?
lrwxr-xr-x  1 lrh  staff	58 Sep 27 09:55 MyExtras -> ./BootCDMaker.app/Contents/Resources/Scripts/Preboot/Extra
-rw-r--r--@ 1 lrh  staff  4189 Sep 22 08:59 ReadMe.rtf

 

You can now move the BootCDmaker_1.2 folder wherever you want it to live and it should work. You can name the new "alias" folder whatever you want and it will work. You can place your files in the new alias (MyExtras) folder by copy/paste of drag/drop and it will work.

 

The new link these commands create will work wherever you place the BootCDmaker_1.2 folder because it is relative to BootCDmaker.app.

 

Hopefully this adjustment is easier to use.

[Trauma!]

Hi,

 

Thanks guy's for debugging this alias issue, but the alias is already an old story for me. With the GUI I simply suppressed it.

 

I also want to improve the mkext creation process with i386 and x86_64 mkext sliming options.

 

About about burn/erase options I'm a bit surprised it didn't worked correctly for you Azumitz, because i never noticed a single bug here. One more time in the GUI i've revisited this options, now you can erase the media and another button let you burn the ISO of your choice.

 

I also would like to add output folder selection, i didn't look after for now, but i will.

 

when it's the app creating com.apple.Boot.plist, the system seems to think the file is a script

 

What do you mean ?

 

Cheers.

[nathan7]

@ nathan7 :

 

Its sounds like the boot.plist error is stupid as a "B" and not a "b". The app looks for com.apple.boot.plist and not com.apple.Boot.plist. I'll try to fix that soon. I've done test with the stock com.apple.Boot.plist and it works fine, i can't tell for now...

 

About PCEFI, if you replace "boot" file you have to use legacy mode. If you did it must work. btw, I will not support those kind of modifications.

 

Cheers.

 

Thanks Trauma. You can see the Boot.plist error I get in my previous post #63, it cannot be denied. That happens when I put my own Boot.plist in. The BootCDMaker folder is on the desktop. Why is the error happening for me but not you?

 

I did select Legacy, but cdboot is still used, whether I say yes or no to GUI. I need pci1 and AFAIK there is no way to do that with Chameleon RC3 or it's cdboot. Can you please implement a way to use PC_EFI 10.3?

[Azimutz]

What do you mean ?

 

Check the pic.. notice kind, file name and the small icon. And when i right click to open, the default app is AppleScript Editor.

App works fine when i add the Boot.plist.. had one of those errors nathan7 mentions, can't specify what the conditions were when it occurred but, was a one time thing.

 

yeah.. sorry about all that alias posting.. just found the situation curious I read you are implementing a gui and that will make it history.

About the Erase/Burn problem, maybe it's specific with my system/drive?!? I don't see anyone else posting about it. Anyway, i consider that option handy but, superfluous. Wouldn't miss it if it didn't exist

[nathan7]

I did select Legacy, but cdboot is still used, whether I say yes or no to GUI. I need pci1 and AFAIK there is no way to do that with Chameleon RC3 or it's cdboot. Can you please implement a way to use PC_EFI 10.3?

 

 

I figured this one out. I had run BootCDMaker in non-legacy mode once before I replaced boot in the app with PC_EFI 10.3, so there was a BootCD.iso, then when I ran it again in Legacy mode, and clicked Burn, it burned BootCD.iso instead of LegacyBootCD.iso and thus still cdboot appeared when booting it.

 

So now I deleted BootCD.iso from the desktop and ran in Legacy mode. This time when I selected Burn it said it was done immediately without burning anything. Your app, Trauma, will not burn LegacyBootCD.iso.

 

I burned LegacyBootCD.iso separately, and PC_EFI 10.3 works as expected when I boot it, and my graphics work.

[Azimutz]

yup.. nice going nathan7 totally confirmed. I was only trying with legacy, since those are the only ones that work for me.

[blackosx]

Hi Trauma

 

I have just tried your BootCDMaker and I would like to say Thank You for your work. It does make creating a BootCD easy as I used to make them by hand. I have just made one, although I did edit the one your app made, but for the first time I have got a DSDT.aml working from it.

 

When I get some more time I will have another go and see if I can improve my attempt.

 

So thanks again

 

EDIT: I struggled to make an Extensions.mkext with just the kexts I wanted. So I ended up editing the final preboot image and adding my Extensions folder of loose kexts.

 

If anyone is interested, I have the BootCD posted here for my 10.6 guide.