Fixed for me too! Same process as before: 4GB virtual hard drive image, boot FreeDOS 1.3 RC3 but use FDISK 1.3.4 from a virtual floppy. Use FDISK 1.3.4 to create a 3GB C: drive, and use the rest of the space for the extended partition. Inside that, create a 500MB D: logical drive, then let FDISK use the rest of the free space as the E: logical drive.
And this time, FDISK 1.3.4 reported that all free space was now used, and didn't let me create another logical drive. Output from Linux fdisk: $ fdisk -l 4gb.img *Disk 4gb.img: 4 GiB, 4294967296 bytes, 8388608 sectors* Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 *Device* *Boot* * Start* * End* *Sectors* * Size* *Id* *Type* 4gb.img1 63 6152894 6152832 2.9G b W95 FAT32 4gb.img2 6152895 8385929 2233035 1.1G 5 Extended 4gb.img5 6152958 7181054 1028097 502M 6 FAT16 4gb.img6 7181118 8385929 1204812 588.3M b W95 FAT32 Minor note: This version of FDISK prints "1.3.3" in the menu. Jim On Mon, Feb 22, 2021 at 12:09 PM tom ehlert <[email protected]> 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 > > > > _______________________________________________ > Freedos-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-devel >
_______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
