Hello Ben, thanks for reporting this. I opened a github issue at the FDISK repository containing the code for the MBR: https://github.com/FDOS/fdisk/issues/82
We may adapt BOOTNORM.ASM to work around the issue. https://github.com/FDOS/fdisk/blob/v1.3.14/source/fdisk/bootnorm.asm > P.S. If you have a later version of FreeDOS FDISK and you used an earlier > version with the /SMBR switch, *DO NOT USE THE /LOADMBR SWITCH!* You will > lose all partitioning information and probably have to wipe your disk and > reinstall everything. Use /LOADIPL in that case instead! (or the /AMBR alias, > which is what you would have been using before.) Yes, I learnt this from > experience, unfortunately. Sorry to hear that. /LOADMBR was introduced recently. It is not included in the version shipped with FreeDOS 1.3. Since introduced, there is a symmetry between /SAVEMBR and /LOADMBR. Means that while /SAVEMBR stores the whole boot sector, /LOADMBR restores the whole sector. Does anyone think this is a major issue? 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
