increase version to 1.4.4, update change log
Recent Commits to fdisk:master
-
increase version to 1.4.4, update change log
-
fix error which displays part type id as FAT32 instead of FAT16
fix error which displays part type id as FAT32 instead of FAT16
-
version 1.4.3
version 1.4.3
-
allow creation of primary despite being out of drive letters
allow creation of primary despite being out of drive letters
-
do not assign drive "letters" >Z and display ? for drives without letter
do not assign drive "letters" >Z and display ? for drives without letter
-
fix inappropriate warning of inaccessible ext. if there is no defined
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
-
do not make a primary active when created via cmdline interface
do not make a primary active when created via cmdline interface It turned out to be a backwards incompatible change to FDISK 1.3.4 shipped with FreeDOS 1.3, breaking the installation process if the BIOS is configured to boot from hard disk.
-
fix loader trying to boot from active partition missing valid signature
fix loader trying to boot from active partition missing valid signature
-
changes.md: add missing newline
changes.md: add missing newline
-
update date in .LSM file
update date in .LSM file
-
update changes.md
update changes.md
-
update changes.md
update changes.md
-
remove non-existant userint2.h from zipfiles.txt
remove non-existant userint2.h from zipfiles.txt
-
prevent creation of more drives than drive letters available (cmdline)
prevent creation of more drives than drive letters available (cmdline)
-
move Nth_Log_Part_Defined() to pcompute.c
move Nth_Log_Part_Defined() to pcompute.c move Nth_Log_Part_Defined() to pcompute.c
-
fix disk corruption when inserting more than 23 log. part on one disk
fix disk corruption when inserting more than 23 log. part on one disk
-
make sure /del /log:n parameter matches n-th displayed log. part.
make sure /del /log:n parameter matches n-th displayed log. part.
-
update changelog, increase version to 1.4.0
update changelog, increase version to 1.4.0
-
remove linker file when cleaning up
remove linker file when cleaning up
-
tell user if drive could not be created because we run out of letters
tell user if drive could not be created because we run out of letters
-
make sure we compute largest free space, and not ANY free space
make sure we compute largest free space, and not ANY free space
-
fix critical error where disk is wiped when deleting logical
fix critical error where disk is wiped when deleting logical The error occurred if there were 23 logical partitions defined for a drive. FDISK then wrote a zeroed-out EMBR to sector 0.