China DOS Union

Learning... Thank you very much, the original poster...

The Lenovo machine reported last time had 4 partitions, but minitow only detected one partition problem. Today, after testing again, removing /nohp, the result is still the same. I wanted to back up the MBR under Windows but got an error and the operation was aborted. I suspect that there might be a Lenovo protection program at work.

Enter DOS and run minito, but there is no result.

Switch to using dspt, and the detected hard disk data is correct. Backed up the first sector data. Found that the data in the partition part is a bit different from the usual ones, not sure if this is the reason for minito's detection error. Attached part of the partition table data for reference.

80 01 01 00 07 FE FF FF 3F 00 00 00 81 14 2A 01
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 C1 FF 0F FE FF FF C0 14 2A 01 3E 21 9D 03
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
55 AA

-------------------------------
Today, ran the tool by the author of dpit under Windows and could get the correct partition. It seems that this software still needs to be improved.

Is there a virtual disk that has been overlooked?

8001010007FEFFFF3F00000081142A01
00000000000000000000000000000000
0000C1FF0FFEFFFFC0142A013E219D03
00000000000000000000000000000000
55AA

Such a partition table, the boot code should only recognize the first partition. Because there is a break in the middle. MINITO also handles it this way. To be consistent with the real situation. To change it to recognize all is very easy, just remove one line of code.

[ Last edited by GOTOmsdos on 2007-6-28 at 08:41 PM ]

Oh, I gave a -1 score by pressing the middle mouse button, sorry about that,

Originally posted by GOTOmsdos at 2007-6-28 20:38:

Such a partition table, the boot code should only recognize the first partition. Because there is a break in the middle. MINITO also handles it this way. It is to be consistent with the real situation. To change it to recognize all is very easy, just remove a sentence...

The problem is that DOS can recognize other partitions and perform operations, but MINITO fails to display them and cannot automatically handle Ghost backups. Moreover, Ghost can recognize other partitions.

I'll have a look..

[ Last edited by GOTOmsdos on 2007-9-5 at 06:52 PM ]

Um, now just change it over....

[ Last edited by GOTOmsdos on 2007-12-21 at 09:41 AM ]

It has been corrected.. Immediately upload it..

minito source code (correct 0 value partition entry bug)
The bug where partitions with a value of 0 in the partition entry cannot be recognized has been corrected...

Thanks for the update, hard work.

Thanks to the LZ for providing such a good program. But the LZ has released several versions in different threads. Also, there are Todisk and MiniTO. Now I don't know which is the latest. It is suggested that the LZ organize the previous threads and concentrate them in one thread, leaving only the latest updated and more useful version. Continue to support the LZ's unremitting efforts. Thanks for you on behalf of everyone.

Thanks for the encouragement and attention. For development, it is indeed necessary to have versions, reflecting a certain continuity and design history. Also, there are version numbers after the program names,,, the one at the bottom is naturally the latest.

Regarding the issue of Todisk and MiniTO:
Originally, there was no MiniTO. Only Todisk. It was added with the function of processing partition table information from Todisk at the suggestion of netizens. But considering the suggestion of some netizens for something compact, the main function of the original Todisk was removed, and now it has become MiniTO. This is the origin of "MINI". They have respective functions (after writing, there was no time, and I can't remember if all the functions of MiniTO have been included in Todisk... I have this idea, so that with one device, all functions are integrated...)

I'm very grateful. I hope I can learn from the post owner.
[email protected]
QQ:395807028