|
Just to clarify:
The MBR is the first sector of a hard disk.
The bootsector is the first sector (several sectors in the case of NTFS) of a partition.
BOTH MBR and bootsector have a "dual" nature, a part that is "static" and a part that is "dynamic".
The "static" part is boot code, and given an Operating System and filesystem (and in some cases language), it will be exactly the same on all hard disks partitioned and/or formatted on that OS.
The "dynamic" part is composed of addresses, labels, serials, signatures, that are peculiar to each hard disk and that will always, at least partially, be different between two identical hard disks partitioned and/ir formatted with the same OS.
The MBR has mainly three parts: 1) Boot code - static (within same language) 2) Partition data or partition table - dynamic 3) Disk signature (only on NT/2K/XP/2003/Vista) - dynamic
The bootsector has manly four parts: 1) Boot code - static (within same language) 2) Partition and filesystem data - dynamic 3) Volume serial - dynamic 4) Volume label - dynamic
MBRfix is capable, KEEPING the dynamic data UNCHANGED, to rewrite the static data of the MBR of a HD, be aware that it will refresh or rewrite English code.
Bootsect.exe is capable, KEEPING the dynamic data UNCHANGED, to rewrite the static data of the Bootsector of a partition, be aware that it will refresh or rewrite code in the language of the source.
Programs like PTEDIT, PTEDIT32, BEEBLEBROX, MBRWIZARD, Roadkil's BOOTBUILDER, are aimed mainly to the opposite, i.e. to changing the dynamic data keeping the static ones UNCHANGED.
In the context of this app: bootsector code=partition boot code MBR code = HD boot code
first terms are more accurate.
jaclaz
--------------------
|