Creating your own EmpireEFI (the easy way)

Its a small gift from me. Lately I’ve been very busy with real life. Thats the reason why I have not updated my blog for such a long time. Plus I’ve neglected all the e-mails which I’ve received. Anyhow as a human , I do feel that its my part as well to help and to do something for the community. Instead of taking down the whole secret down with me , I thought of sharing it on how to create your own Empire EFI disc the easy way out

I’ve included a lot of essential files and modified stuff into this customised BootCDMaker – which makes it easier to create your own bootable disc. You’re able to include your own dsdt, your own fixes and so on and so forth and even distribute it. Its pretty straight forward to use unlike plastikman’s guide which may be a bit complex. All you need is MacOS X 10.5 (should work with 10.4).
This should get you started. However if you wish to take it a step further (i.e including your own new version of chameleon) , then you may want to read this as well – Oh yeah before I forget , this is the file (click on it to download it). All you have to do is download it and put it to your Applications folder. Just execute it and you’ll have your very own customised EmpireEFI disc !
#Update : I would like to apologize to the author of BootCDMaker ,  for not crediting to his work. Anyway what I’ve done is just included essential kexts to this. The author should be thanked and yes you can visit DarwinX86 for other stuff but the thing is in French 😛

15 thoughts to “Creating your own EmpireEFI (the easy way)”

  1. your are great, I think you are one the best in our community
    I am very happy to find out amazing team in this community.
    all the best to you

  2. Hy Prasys,
    Did you ever thought about mention that this software was not made by you ? Or even thanks the author of this software since you’ve used it to design your project ?
    I know that i did not release this software under any license, but never the less you could have ask the author before distribute a derivative version? I’m ready to share my sources without any problems, but wtf just ask!!

    1. Trauma , what I can offer you is my deepest apology that I am unable to express it out. I regret for not taking the time of writing and giving credits properly . What I’ve done is that I’ve made it up and I’ve written a humble letter to you. I hope that does in fact make up.
      Cheers !

  3. ATTENTION !!!!
    The process of making mkext does delete all storage above an SPACE in path to the app! (seems some rm … cant handle spaces in path to the app.
    Q: Which kernels are within the app . I can see some “mach_kernel.test7” and “mach_kernel copy” with different dates.
    Q: I dont understand how the app (withits conent of /extra/extensions) handle the creation of the extensions + mkext. It asks after the path to the extension, but i cant set it to the ../app/…/extensions. have i copy /extensions (of the within the app) to somewhere else ?

  4. Pingback: ??????
  5. Prasys, thank you very very much for all your work here. I know you said sometimes you don’t feel appreciated for the work you have done here, but I wanted to let you know that myself and most of the people I know definitely appreciate your work!

  6. Pingback:
  7. Pingback: Kylie Batt
  8. I was wondering if I could use this boot disk for my build with an asus z8na d6 and dual xeon nehalems and boot snowleo the retail 29.99 version?
    I have tried all of the other methods I have found and have not been successfull at booting. All I ever get is a blinking cursor, its like the bios does not recognize the boot for the USB and the USB is set as the boot priority disk

  9. Pingback: Kylie Batt
  10. Pingback: Webmaster

Leave a Reply

Your email address will not be published. Required fields are marked *