Hi Eric, > > 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.
Thats right. Restoring a previously saved partition layout is the primary use case for /LOADMBR. In my opinion, FDISK as a partition manager should provide a way to save and / or restore partitions. > > 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. I second that. At least one user confirmation should be implemented for this. My proposal is: Require user confirmation for command line operations destroying partitions unless /Y parameter is given via command line. > > 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. To my knowledge the FreeDOS installer does not wipe the disk without consent of the user, but I have to test. Greetings, Bernd _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
