Hi,
I hope I have eliminated the most critical bugs and I am now in a cleanup
phase. I noticed that the /SMBR command to write the MBR to disk does not do
what its name suggests. It only writes the 440 code bytes to the file and fills
the rest of the 512 bytes with zero, leaving FDISK with no method to make a
backup of the partition layout.
I reworked the commands, so that the users don’t get confused:
MBR (Master Boot Record) management:
/CLEARMBR [drive#] Fills MBR with zero: deletes all part. and code
/LOADMBR [drive#] Loads part. table and code from "boot.mbr" into MBR
/SAVEMBR [drive#] Saves partition table and code into file "boot.mbr"
MBR code modifications leaving partitions intact:
/IPL [drive#] Writes the standard boot code into MBR <drive#>
...same as /MBR and /CMBR for compatibility
/CLEARIPL [drive#] Zeros 440 code bytes of MBR
/LOADIPL [drive#] Writes 440 code bytes from "boot.mbr" into MBR
/SMARTIPL [drive#] Writes DriveSmart IPL into MBR <drive#>
The /CLEARIPL is only there because that functionality existed before. I am not
sure if it does make sense at all if 55 AA marks a valid MBR. I have the
tendency to remove it unless someone intervenes, because there is also
/CLEARMBR to clean sector 0 properly.
Greetings, Bernd
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
