China DOS Union

Originally posted by lianjiang2004 at 2007-4-18 09:07 PM:
The test result with the latest version in the first post is the same. minito crashes, but minito- works.

As mentioned earlier, it is now found that some users' hard drives crash, and the cause is still unknown, so the alternative version is released....

The virtual machine may also need the alternative version.

This is the result of DRVTYPES

You yourself said that DRVTYPES is a third-party tool, so the situation is naturally different. It's the same principle as having NTFS/LINUX drive letters after loading NTFSPRO/IFS. DOS itself can't do it.

If you need MINITO to display the added drive letters after running DRVTYPES, I can make it for you. Add the -DRVTYPES parameter.

But I can directly access under DOS, for example, entering C: K: can both enter.

Originally posted by llztt at 2007-4-18 10:23 PM:
But I can access directly under DOS, for example, enter C: K:, can all enter

Did you run DRVTYPES or CONFIG.SYS/AUTOEXEC.BAT before? Is there DRVTYPES? DOS itself can't do it...

[ Last edited by GOTOmsdos on 2007-4-18 at 10:32 PM ]

DRVTYPES, as its name suggests, only lists the types of all drive letters under the current DOS. It's just a small command, no big deal. After I booted DOS in the virtual machine, I could directly access C: K: and confirmed it.

Oh, it's a virtual machine..
I'm not sure about this.. The situation of virtual machines can't be used as standard, pure DOS is not okay.
Wait a minute, let me try it. I didn't pay attention to this before, oh, this point, thank you!

Well, that's pretty good. Just now I tried it, and it really works!
This virtual machine is a bit out of line! It has messed up DOS without any rules!

Then will this affect the correct judgment of MINITO in the actual machine

If there are more than 2 primary partitions in the actual machine, there will be some problems when accessing them. I haven't thought of a way to access the second FAT primary partition yet. Could it be that we need to hide the first FAT primary partition first??

In the actual machine, it is not affected

Originally posted by llztt at 2007-4-18 11:17 PM:
Method to access the second FAT primary partition in the actual machine. Does it mean to hide the first FAT primary partition first??

In DOS, it's just like this

If it's not possible to test in a virtual machine, it's a bit of a pity.

Why did I get the following information when I ran TODISK --D for the first time? (Tried several times, this is the result of the first run!)
No. DRIVE CYLINDER HEAD SECTOR TOTAL GB/MB
[ 1] 1> 179707916 537665548 537661894 183377571 87 GB
[ 2] 2> 16383 16 63 156301488 74 GB

There is a file named 16383 generated in the directory (I found the file 179707916 last night)
Exit the P processing, enter the directory and run TODISK --D again, and the correct display is:
No. DRIVE CYLINDER HEAD SECTOR TOTAL GB/MB
[ 1] 1> 503 8 32 123903 60 MB
[ 2] 2> 16383 16 63 156301488 74 GB

And there are files named 16383 and 503 in the root directory of the USB flash drive, and also in the root directory of the USB flash drive

Originally posted by llztt at 2007-4-19 12:08 AM:
It's a bit of a pity if you can't test in a virtual machine.

A work-around version is okay.

No. DRIVE CYLINDER HEAD SECTOR TOTAL GB/MB
1> 179707916 537665548 537661894 183377571 87 GB
2> 16383 16 63 156301488 74 GB

When改版, there was a line of code that wasn't changed back, and now it has been changed back. I don't know if this is the reason?

Also, at the request of friend terse, the display of disk/partitions has been adjusted.

The program has been updated, see the first post.