China DOS Union

The test found that it has a stronger ability to identify hard disk partition numbers than minito. Minito can only handle standard partition tables.

Agree with the person above, so I gave up on minito.

BUG report!
Non-standard partition table, hard drive number error.
There are screenshots of Acronis Disk Director, Gdisk, and dspt information in the attachment. Among them, Acronis and Gdisk are correct. Also attached is the mbr exported by dspt 0 0 1 /s.

I can't figure out how the partition above was built? Inconceivable.

Originally posted by zhangxue at 2007-8-19 02:33 PM:
BUG report!
Non-standard partition table, hard drive number error.
There are screenshots of Acronis Disk Director, Gdisk, and dspt information in the attachment. Among them, Acronis and Gdisk are correct. Also attached is the mbr exported by dspt 0 0 1 /s.

I think this time it's Gdisk and adds that are wrong,

Run ghost11.0.1 to check and you'll know who's wrong.

[ Last edited by wang6610 on 2007-8-19 at 03:52 PM ]

Originally posted by lianjiang2004 at 2007-8-19 03:36 PM:
How was the partition above built? Inconceivable.

Both aefdisk or gdisk can be used.

How does the logical partition end up on both sides of the primary partition? Isn't the logical partition supposed to be only under the extended partition?
The last logical partition doesn't seem to be under the extended partition. Or the next primary partition is under the extended partition. I really don't understand.
I'm really ignorant.

1. ntfs4dos can also identify each partition and the order is correct.
2. When all partitions are formatted as fat32, there are no obstacles for DOS to access, which should mean there is no problem.
3. As for dspt, it is just a little bit deviated in order.
4. The most important thing is that no matter it is right or wrong, the detection program should also truly display the situation, even if it is wrong.

Originally posted by zhangxue at 2007-8-19 14:33:
BUG report!
Non-standard partition table, hard drive number error.
There are screenshots of Acronis Disk Director, Gdisk, and dspt information in the attachment. Among them, Acronis and Gdisk are correct. Also attached is the mbr exported by dspt 0 0 1 /s.

Thanks for testing the software, I will find out the problem as soon as possible

TO zhangxue:
Please test this version to see if there are any issues.

[ Last edited by 19951001 on 2007-8-21 at 06:46 AM ]

Still the same, no change

From the picture you provided, the capacity of the entire extended partition is nearly 12 GB, and the sum of the capacities of all partitions after the extended partition is exactly this value, which means your last primary partition is generated within the extended partition. This partition table is indeed very special.

Ask about how the last primary partition was created? Amazing. It seems to be inconsistent with the partition rules introduced in general materials.

I estimate that this partition table is first to create a primary partition, then create an extended partition, create 3 logical partitions in the extended partition, use tools to find the absolute positions of the three logical partitions in the extended partition on the disk, write the position of the second logical partition in the extended partition into the third item in the MBR, and modify the pointer of the first logical partition in the extended partition to point to the third logical partition in the extended partition, then the above - mentioned partition table can be created.

[ Last edited by 19951001 on 2007 - 8 - 21 at 06:17 PM ]

Acronis Disk Director can create primary partitions anywhere, as long as it does not exceed the number limit of primary partitions.
dspt has another question. The situation where there is one primary partition at the front and one at the back is not considered a special partition table. In the past, IBM's one-click recovery was like this. But if the latter primary partition is set as the active partition, the first primary partition (in FAT32 format) will not show a drive letter in dspt. Actually, DOS has assigned a drive letter to it.