Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About Mrcollins

  • Rank
    InsanelyMac Protégé
  • Birthday 08/31/1982

Contact Methods

  • MSN
  • Website URL
  1. OSX EFI bootloader

    Do you happen to know what efi modules we are missing. I have a dump somewhere of the x64 efi modules from a mac pro. Thanks, MRCollins
  2. EFiX: OSx86 gone commercial?

    It looks to me from the video that it is DUET (tianocore.org), compiled with the graphics option turned on, runing a custom bootloader like rEFIt. Other that the graphcs based bootloader, I made the same thing that boots 2k8 server via efi. What's holding me back is an UEFI /EFI x64 HFSPlus driver to do the OS X install.
  3. Were Back !

    The project isn't completely dead. Some are still working on it in our off time. I currently have windows server 2008 x64 booting from UEFI with DUET. I also compiled an x64 version of rEFIt although I haven't got the graphics mode to work as of yet, but the text mode works just dandy. I need to find an x64 compatable HFSplus efi driver before I can continue on with OS X. A dump of all the EFI files from an x64 EFI Mac would probably be benificail as well.
  4. -Archive- Macefix86 2006 -Archive-

    When is say 32-bit I mean not running in the 64-bit extended mode but also not in the 16-bit real mode. Basically 32-bit protected running with out physical address extentions (PAE). the first address possible should be 0xFF800000and just keep subtracting 0x400000 from that. the signature should line up on on off those addresses. As far as what I was talking about with the boot loader, one could write an asembly boot block that gets the processor in to 32-bit protected, loads the registers on the Processor with the Table address, or what ever else was needed (I can't remember at this point) and do a jump into the correct section of EFI or load the EFI shell from a disk or even just embed the efi shell onto the said "boot disk".
  5. -Archive- Macefix86 2006 -Archive-

    Honestly, searching for the Signatures in RAM will probably be your best bet. Kiko and I had discussed this in a bit of detail, but as I don't have an EFI board im kinda stuck. If you can get to the RAM before it is over written, the signature should still be there even after an os is loaded. (most OSes will not write 0s to ram on bootup.) the EFI_SYSTEM_TABLE_POINTER is a struckt made up of two uint64 and a uint32 the struct sits on a 4M boundary basically multiples of 0x400000 acording to the EFI spec section 16.4.2 or 3 you should do a search for the EFI_SYSTEM_TABLE_SIGNATURE to find it the signature is 0x5453595320494249 it is followed by the table pointer and then by a crc32 of the first two structures With this info we know the boundarys we need to look at and its should start at the 4gig limit, 0xFFFFFFFF, for 32-bit systems and work backwards. Like I said, don't have an EFI board otherwise I would try to find the address of this myself. Once we have the address of the Table we should be able to find the addresses needed to call the EFI shell and make it happy. Once the addresses are found a simple boot sector should be able to accomplish most of what we want.