fix inappropriate warning of inaccessible ext. if there is no defined
Recent Commits to fdisk:master
-
fix inappropriate warning of inaccessible ext. if there is no defined
-
only complain if ext is unusable if there is any defined
only complain if ext is unusable if there is any defined
-
fix spelling errors
fix spelling errors
-
fix spelling
fix spelling
-
do not write back unusable extended partition
do not write back unusable extended partition
-
update change log
update change log
-
inform user about inaccessible ext on cmdline operations for log drv
inform user about inaccessible ext on cmdline operations for log drv
-
do not display logical drives via /info if ext part is inaccessible
do not display logical drives via /info if ext part is inaccessible
-
show if extended partition is inaccessible when when deleting logical
show if extended partition is inaccessible when when deleting logical
-
make sure to reject disks with more than 23 logical partitions
make sure to reject disks with more than 23 logical partitions
-
remove trailing space
remove trailing space
-
update changes, doc and version number
update changes, doc and version number
-
remove some commented out code
remove some commented out code
-
bootnorm.asm: fix potential bug on INT10 usage
bootnorm.asm: fix potential bug on INT10 usage
-
add /NOIPL argument to prevent writing IPL on MBR initialization
add /NOIPL argument to prevent writing IPL on MBR initialization IPL area is filled with zero instead. Some BIOSes contain heuristics which allow them to skip the device upon boot if they detect the first bytes of the IPL being zero. FreeDOS 1.3 installation under VMware accidentally works because of this, because FDISK 1.3 fails to write proper boot code when initializing the MBR. The INT 18 method introduced to the boot code via 301ba27 should render this obsolete.
-
bootnorm.asm: issue INT 18 on boot failure
bootnorm.asm: issue INT 18 on boot failure