Hi Bernd,
/LOADMBR restores the whole sector. Does anyone think this is a major issue?
In that case, I think loadmbr should never be used except
when there was a previous corresponding savembr. Because
using loadmbr in another way results in deleting the whole
partition table and/or installing a new partition scheme
which will probably not fit to the size of the target disk.
Similarily, cleanmbr should never be used without plenty
of warning to the user and giving the user at least two
chances to select a less destructive option.
If the context is letting the installer work on a virtual
computer with a fresh disk image, where you expect nothing
of value could get lost, then I suggest creating a tool
to detect whether the MBR and partition table already WERE
empty in that disk image instead of automatically emptying
them. Or just offering a pre-installed disk image download.
Greetings, Eric
The documented commands are as follows (via FDISK /?):
MBR (Master Boot Record) management:
/CLEARMBR Deletes all partitions and boot code
/LOADMBR Loads part. table and code from "boot.mbr" into MBR
/SAVEMBR Saves partition table and code into file "boot.mbr"
MBR code modifications leaving partitions intact:
/IPL Installs the standard boot code into MBR <drive#>
...same as /MBR and /CMBR for compatibility
/LOADIPL Writes 440 code bytes from "boot.mbr" into MBR
Greetings, Bernd
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
