#6301: DriveSetup writes MBR inconsistent with anyboot image. --------------------------------------+------------------------------------- Reporter: preroll | Owner: stippi Type: bug | Status: new Priority: normal | Milestone: R1 Component: Applications/DriveSetup | Version: R1/alpha2 Resolution: | Keywords: MBR boot CHS bits Blocked By: | Has a Patch: 1 Platform: x86 | Blocking: --------------------------------------+------------------------------------- Comment (by starsseed): haiku_loader does not work on my laptop (see the bug #4408 #5539 #5696 #5720) so, I can't test on it. Neither on my desktop system whom BIOS doesn't care about CHS informations... But I remember having problems to create a valid MBR/partition-table for my USB key, and I never completely understood why! (now I create the MBR and the partition from windows and copy the boot-code area from an AnyBoot-image with dd) Preroll, did you test the patch ? @Bonefish[[BR]] Note that: - FF FF FF implies a disks with UUID partition table (EFI) then EF FF FF would be better - since DriveSetup creates the first partition at sector CHS={01 02 00} (i.e. Cylinder=0/Head=1/sector=2 or LBA=40) it seems it does not take care about the disk geometry. I think it's not correct : the 1st partition should be aligned on the 1st sector (2nd,3rd,4th partition should be aligned on head*sector - 1st sector/Head 0). -- Ticket URL: <http://dev.haiku-os.org/ticket/6301#comment:5> Haiku <http://dev.haiku-os.org> Haiku - the operating system.