On 2/22/2021 10:08 AM, tom ehlert wrote:
On the virtual get-together today, we tested the new FDISK 1.3.3
with a large virtual hard disk. I wanted to report a bug from that.
I couldn't reproduce this exactly; my drives sizes were always
reportee correctly.
however I was able to produce a very close approximation when creating
logical drives through the GUI, and trashing the disk.
hopefully fixed in www.drivesnapshot.de/freedos/fdisk134.zip
Tom
Well, both Jim and I were able to reproduce this yesterday, Jim in a VM,
me on a real iron laptop (where I trashed my install, but that was
accepted).
The problem seems to be in the part of the code when you create logical
drives within the extended partition. It always seems to infer that
there is 8MB left over and when you confirm that you want to create a
drive in that (alleged?) space, that's when things go south. If you
don't do that, and just leave that little piece of slack alone, shit
happens...
And btw, this happened both with FDISK 1.2.1 and FDISK 1.3.3, so it is
likely in a different part of code than the one you looked at recently
for the update. Also, the error message that prints just before exit
complains about some cylinder values not being as expected...
Ralf
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
