Jump to content


Just Joined
  • Content count

  • Joined

  • Last visited

About squallmat

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Calais, France
  1. Hello, no more responses ? I've not received my HDD yet, so i have to report my tests to the next week Anyway, some other questions : i read this page "http://rodsbooks.com/gdisk/whygdisk.html" and i would like to know what do you think about gparted/gdisk today ? gparted has evolved and fixed these problems with GPT ? About this table : "http://gparted.sourceforge.net/features.php" These features/compatibilities are for MBR and GPT disks ? Or are there limitations with GPT disks ?
  2. Hello, first thank you keshav and srs, thanks to this post i learned many things on GPT/... in few days. thx I assume using the version 1 will see a lot of regressions than using the version 2. There is no version EDK2.0.1 fixing this bug ? If this is just a problem of implementation, maybe i can see the source code (i am developer). Another, maybe really stupid, question : these EDK1 DUET UEFI64 firmware and EDK2 DuetPkg X64 firmware, can they boot 32 bits OSes ? I assume that when you have so many differents file systems on a same HDD, whatever the tool used it's very risky to move/... any of them. I was assuming, that when grub2 is loaded, it could be able to see the EFI System Partition and then propose an "auto-menu" extra to the traditional script-generated menu. I don't see this impossible, but maybe it's just an option that nobody know, or even it's just not implemented yet. (I'm personnaly still using Grub Legacy) I'll buy a HDD, i'll try the UEFI system when i'll have the time (maybe this week-end). I'll share the results here.
  3. Hello srs5694 and keshav, thanks, now i understand better the "system". Is Gnu Parted (or any other tool) able to modify HFS+ on MBR ? The features that don't work on MBR are just features like Disk Utility (tools directly depending of the HDD), but there is no risk that other more or less important features not directly related to the HDD don't work, right ? So, there is no chance that there would be regressions in the OSes utilisation if they're booted by UEFI ? This was my principle preoccupation, i don't want to use a lot of times to make a stable system using UEFI/GPT and see months after that even little regression on specific OS/functions. In fact i have the intention to install 4 systems (for the moment): - Win 7 x64 - Archlinux x64 - FreeBSD x64 - Snow Leopard And of course after some resaerch on hackintoshes i seen many methods, and what i would is a Hackintosh that would work exactly like i had really a MAC. So, not all MB can BIOS-boot on a GPT config. Is there anywhere a list of compatibilities ? Personnally i have an ASUS P5Q PRO, is it compatible ? Grub2 (and even grub1) need to be configured. Even if Grub2 as implemented a system to detect systems and reconfigure himself. - But EFI System partition contains all info in a dedicated partition, so is grub2 capable of detect automatically the systems present on the GPT_HDD ? There is no more need to reconfigure grub 2 ? - Where is your grub2 installed ? i assume in archlinux. Is there a way to install it in a separate partition dedicated for himself ? (GPT can have 128 active partitions that's it ?) About the memdisk that was the page that i read (but not completely) but i'm not sure to 100% understand the "concept" (i have sometimes difficulties to understand english texts/wordings). But from what i understood it's a simple and small image of a system to "extend" the BIOS features. Memdisk (when emulating a HDD) is for the BIOS what a virtual HDD if for an OS. Is that ? So, once the OS is launched, no matter from what (EFI or BIOS) the OS will be not even a little "different" Related question, imagine i make a system like you. many OSes, all bootable by DUET, win and mac only by DUET, the others by grub directly also : Is there a risk to alter the "stablity" of this configuration if i update (flash) my BIOS for a newer version ? An important goal for me : I would that Windows 7 to be the "default" OS : if i turn on my computer and leave for a moment, i would like to be on the desktop of windows 7 when i'm back. Is this achievable ?
  4. Hello Keshav, thanks for the reply. Maybe i mistaken (my english is far to be perfect) but it seems you contradict yourself ? Or i don't understand well the system. I was saying that there would be only one partition accessible by BIOS. This partition contains the UEFI DUET. Windows is installed in a GPT-referenced only partition. So : boot -> BIOS -> "chainload" -> partition 1 MBR -> "DUETloading" -> access to GPT partition (like windows). I used USB 3 for an example to technology usable by your installed OSes, i was not saying i would like to use an USB 3 to put DUET on him. I am just questioning about the technologies that needs to be implemented not only in the operating system but also in the BIOS/EFI to be usable like USB ports. Imagine i have my windows installed on a GPT_HDD, windows is launched : if my old BIOS was implementing USB 3.0 but not the UEFI DUET, i cannot use anymore the USB 3 technology in this windows, right ? (or i mistaken ) To extend the question. A BIOS is generally optimised for each motherboard model, i think this should be the same for EFI. Is there a list of compatibilities, differences between the MB/chipset that you have on your motherboard ? (example : Maybe used with an AMD chipset there would be some problems like parts of USB ports not functional, etc...) I just discovered the memdisk, and from what i've read it's sort of a "iso" of a system anywhere in a partition, that can be booted with a bootloader compatible like grub. But maybe i'm completely wrong. Is that a memdisk ? If yes, then to boot the UEFI, there is need to be a BIOS-accessible zone on the HDD to then "switch to EFI", no ? I don't understand, if there is a need to have a primary partition with the "system".. that means that you have to install windows on a primary partition. So, it is not possible to install windows on a extended partition. PS : i'm new to GPT/EFI/Hackintosh, so if you can be very explicit in your answer that would help me
  5. Hello everybody, i was searching for informations to install MacOS on my PC and after many research hours i found this interesting topic, first i have some questions : 1) Not counting the number of partitions, what are the benefits to install Mac on a GPT_HDD over a MBR_HDD ? (in terms of installation-ease, upgrading the OS after, etc...) 2) I've seen many infos/posts about "Hybrid MBR-GPT", a non traditional configuration. But if GPT is retrocompatible with MBR, then any "pure GPT" is a potential Hybrid configuration right ? 3) The emulated EFI DUET is used only to boot the OSes ? Or is there a "definitive replacement" of the BIOS by the EFI in the point of view of the OSes ? I think it's the second proposition that is true. But if it's that, there are possible regression right ? (not only for the AHCI mode) For example : if the BIOS implement USB 3, if the OS implement USB 3, then i can use USB 3 on a "normal" configuration. But if i now use EFI DUET to launch this OS now installed on a GPT disk, and assume that DUET don't implement USB 3 then USB 3 will not be usable ? I will try to contribute to the discussion, but it's important to note that i've never tried to use EFI DUET, use a GPT_HDD and install Mac on a PC for the moment : The person who have installed the EFI DUET on the HDD, have probably a "hybrid" configuration. I don't think that there is another way to install it on the HDD, it have to be put in a partition that can be booted from the BIOS (like a USB drive). There is a possibility to install the EFI DUET on another HDD, but it would make the GPT_HDD totally dependent of this one, this is not really a "solution". But i was thinking about an idea that i don't know if it's possible : We have to put the partition with UEFI DUET on a MBR-bootable partition on the disk. But if we configure a GPT_HDD with this idea we have to make attention to not alter this MBR partition by any GPT-scheme reconfiguration. So, is there a way in the GPT scheme to definitely define a zone of the HDD (the zone corresponding of the MBR-defined partition with DUET) to be "inalterable" ? So in other words, is there a way in a "hybrid configuration" to protect the MBR partitions from any GPT alteration (resizing, etc...) ? some other questions : Is there another way to have more than 4 active partitions ? Is it possible to boot windows on an extended partition ? (maybe with grub or a dedicated boot loader)