#9108: Re-writing the Intel partition map should erase the MBR
-----------------------------------------+----------------------------
Reporter: kallisti5 | Owner: bonefish
Type: enhancement | Status: new
Priority: low | Milestone: R1/beta3
Component: Partitioning Systems/Intel | Version: R1/Development
Resolution: | Keywords:
Blocked By: | Blocking: 16304
Platform: All |
-----------------------------------------+----------------------------
Comment (by pulkomandy):
I'm looking at the intel partition map initialization and there is support
for writing our bootloader introduced in 2009 in hrev33263 (pre-dating
this ticket by a few years).
As far as I can see, it is still in place and should still work.
So, I'm wondering, does DriveSetup actually call this code if it detects
that there is already a partition map and it looks "good enough"? The
userland code is not super easy to follow, between DriveSetup itself, and
the partitionning system handling in the storage kit.
But once we get to kernel side, the code in pm_initialize in the intel
partition map manager is quite straightforward and it eventually calls
WriteMBR with the "true" parameter needed to replace the boot code.
--
Ticket URL: <https://dev.haiku-os.org/ticket/9108#comment:4>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
