I wanted to try a really dumb experiment. Start with the same 4GB drive,
and create a bunch of 100MB partitions on it. 100MB C: drive, then an
extended partition that takes up the rest of the drive - and inside that,
create a bunch of 100MB partitions inside that. In theory, you should be
able to do this all the way up to Z:

General overview:

1. "Do you want to use large disk (FAT32) support" -> Y

2. "Create DOS partition or Logical DOS Drive" - "Create Primary DOS
Partition" - don't use maximum available size - create partition at "100"
MBytes size

... this creates a "102" MBytes C: drive

3. "Create DOS partition or Logical DOS Drive" - "Create Extended DOS
Partition" - hit Enter to create an extended DOS partition at "4001" Mbytes

4. FDISK lets you create logical drives in the extended partition. Set each
to 100MB (creates logical drives at "102" Mbytes each)


First test:

Created a bunch of 100MB logical drives in the extended partition, from D:
to Z: (until FDISK says "Maximum number of Logical DOS Drives installed")

FDISK 1.3.3 created all the partitions, and I can select "Display partition
information" in the main menu to confirm that I created C: and D: through Z:

In Linux fdisk, I can only see the C: and D: drives:

$ 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  208844  208782 101.9M  6 FAT16
4gb.img2        208845 8385929 8177085   3.9G  5 Extended
4gb.img5        208908  417689  208782 101.9M  6 FAT16



I started again with "qemu-img create 4gb.img 4G" to create a fresh (empty)
4GB virtual drive image.

Following the same process, but intentionally stopping at the Y: drive, I
can create C: and D: through Y: no problem. My output from Linux fdisk
shows C: and D: through Y:

$ 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  208844  208782 101.9M  6 FAT16
4gb.img2         208845 8385929 8177085   3.9G  5 Extended
4gb.img5         208908  417689  208782 101.9M  6 FAT16
4gb.img6         417753  626534  208782 101.9M  6 FAT16
4gb.img7         626598  835379  208782 101.9M  6 FAT16
4gb.img8         835443 1044224  208782 101.9M  6 FAT16
4gb.img9        1044288 1253069  208782 101.9M  6 FAT16
4gb.img10       1253133 1461914  208782 101.9M  6 FAT16
4gb.img11       1461978 1670759  208782 101.9M  6 FAT16
4gb.img12       1670823 1879604  208782 101.9M  6 FAT16
4gb.img13       1879668 2088449  208782 101.9M  6 FAT16
4gb.img14       2088513 2297294  208782 101.9M  6 FAT16
4gb.img15       2297358 2506139  208782 101.9M  6 FAT16
4gb.img16       2506203 2714984  208782 101.9M  6 FAT16
4gb.img17       2715048 2923829  208782 101.9M  6 FAT16
4gb.img18       2923893 3132674  208782 101.9M  6 FAT16
4gb.img19       3132738 3341519  208782 101.9M  6 FAT16
4gb.img20       3341583 3550364  208782 101.9M  6 FAT16
4gb.img21       3550428 3759209  208782 101.9M  6 FAT16
4gb.img22       3759273 3968054  208782 101.9M  6 FAT16
4gb.img23       3968118 4176899  208782 101.9M  6 FAT16
4gb.img24       4176963 4385744  208782 101.9M  6 FAT16
4gb.img25       4385808 4594589  208782 101.9M  6 FAT16
4gb.img26       4594653 4803434  208782 101.9M  6 FAT16



**This is a different problem from the other one we've been following. This
is a problem that FDISK cannot save a partition table with logical drives
up to the Z: drive, but succeeds if you only go up to the Y: drive. (This
is a rare bug.)
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to