中国DOS联盟

Originally posted by cchessbd at 2007-4-20 04:19:


This should have no impact on grub and the like; they are just boot loaders and managers.
It may be related to the drivers in your boot disk.
It is best to test if the problem exists in pure DOS.

http://zhenlove.com.cn/cndos/fileup/files/Avlgomgr_2007m_v2.103.zip

This is the latest AVLGO!
If you have doubts, please use AVLGO to load any bootable DOS disk, and please run the modified version program in pure DOS without loading any drivers to test!
If there is no problem, please reply!!!!

I hope you can respect the opinions of friends and hope you can refute other people's posts with facts!





The following is the situation of my test:
I used AVLGO to load Lao Ge's and xusen's DOS disks, and the modified version had an error when running in pure DOS without loading any drivers, and continued to execute after pressing Enter 4 times!

Last edited by 0451lym on 2007-4-20 at 04:54 AM ]

A perfect program should not require users to face intermediate errors. One of the lessons programmers must learn is how to detect and handle exceptions. Since everyone uses MINITO to display partition information, there should be no prompts that a certain partition is unformatted or cannot be read, and there should be no information like inserting a floppy disk. Especially after the remaining capacity display function was added, the error has been persistent. If it can't be fixed, it might be better to remove it. Or, for unformatted or non-FAT partitions, leave the remaining capacity blank instead of using some string as a substitute. Different boot environments can very likely affect the program's operation, and there are numerous examples of this. It's important to test the generality in environments like GRUB.

It's found that MINITO indeed only reads and analyzes the partition table. Adding the parameter IFS is actually just the program internally speculating the drive letter arrangement according to IFS habits, rather than, like PSI, conducting a comparison and analysis of partition information according to the already allocated drive letters after IFS runs. So MINITO will not assign a drive letter to the second primary FAT partition (in a virtual machine) according to its own drive letter algorithm. Then, when adding the IFS parameter, it will be found that it is completely chaotic with the drive letters after actual IFS runs, because MINITO analyzes without relying on actual IFS but follows its own algorithm (proof: the program runs normally without IFS).

It's hard to say which is better or worse. But one thing is that since the -IFS parameter is added, it doesn't analyze and judge according to the actual IFS operation result but goes its own way. Fortunately, no abnormal situation of IFS in actual machines has been found yet.

Originally posted by 0451lym at 2007-4-20 04:45:


http://zhenlove.com.cn/cndos/fileup/files/Avlgomgr_2007m_v2.103.zip

This is the latest AVLGO!
If you have doubts, please use AVLGO to load any bootable DOS disk, please do not load ... under pure DOS

I have downloaded the avlgomgr you uploaded,
Loading my own img can run minito normally.

I don't know why there is a problem when loading any IMG with AVLGO on my machine, but it's okay with GRUB.
And when using AVLGO to load any IMG, there is no such problem when running software with other partition tables!

According to reason, this phenomenon shouldn't exist because: AVLGO is a disk virtual boot tool built on Grub 0.97. Why is this exactly?

Last edited by 0451lym on 2007-4-20 at 05:59 AM ]

At everyone's request, everyone's opinions are still very reasonable, and now the problem is basically solved.

1. Now the alternative version is canceled. When running the standard version, add the parameter: -nohp at the end.

2. By default, support for floppy disks is canceled, so there will be no annoying warnings. To support, add the parameter: -floppy at the end.

3. When encountering an unformatted or problematic partition (FAT/NTFS), there will be no annoying warnings. Only the normal warning given by MINITO will appear, and then continue to execute.

The problem of not displaying the drive letters of FAT primary partitions after the first one has nothing to do with IFS. IFS is loading NTFS/LINUX!

The NTFS primary partition after the first primary partition loaded by IFS is normally added by MINITO.

This is due to the virtual machine. It is not allocated by it, but caused by the virtual machine. It has nothing to do with IFS and MINITO.

MINITO is consistent with pure DOS.. Being consistent with pure DOS is the hard truth, right?

It has been updated and uploaded, see the first post.

If there are any problems, you can continue to put them forward. As long as time allows, it will be improved.

Last edited by GOTOmsdos on 2007-4-20 at 06:44 AM ]

OK, the floppy disk warning is no longer prompted!

minito -d1 displays information for disk1
minito -d displays
1 A...
2 disk1...

There is obviously a contradiction here.

This -D refers not only to the hard disk but to all disks (including floppy disks)
-D1 refers only to the hard disk, because floppy disks are not numbered, and it's not correct to number from 0 because there are two floppy disks, and the hard disk numbering should be in line with GHOST, starting from 1, so floppy disks cannot be numbered

The first one is the serial number, followed by the hard disk number, and floppy disks have no number

This is not contradictory

Last edited by GOTOmsdos on 2007-4-20 at 06:50 AM ]

No. N:N : N PRI/LOG ACT HIDE ID FILE SYSTEM LABEL TOTALmb FREEmb
1:1 C: 1 PRIMARY YES NO 0B FAT32 NO NAME 5130 2721
1:2 E: 3 LOGICAL NO NO 0B FAT32 NO NAME 5130 1243
1:3 F: 4 LOGICAL NO NO 0B FAT32 NO NAME 4110 2643
1:4 G: 5 LOGICAL NO NO 0B FAT32 NO NAME 4102 882
1:5 H: 6 LOGICAL NO NO 0B FAT32 31525 1383
1:6 I: 7 LOGICAL NO NO 0B FAT32 软件备份 26317 3140
2:1 J: 8 LOGICAL NO NO 07 HPFS/NTFS 76308 2047
3:1 D: 2 PRIMARY YES NO 04 FAT16(<32M) USBHDD-BOOT 962 957

Here are several suggestions:
1. It seems that the NO. item is of no use and wastes space.
2. X:Y = Z: It's better to have an equal sign in the middle, or X:Y_Z: It can be unified under one item (partition symbol).
3. The N item after the letter drive letter also seems to be of no use and can be simplified.
4. What is the use of ID? If it has no direct use, it can also be simplified! Or provide a switch to shield it!
5. Can HPFS/NTFS be changed to: NTFS/HPFS, or remove HPFS because HPFS is very rare and it seems that IFS cannot drive HPFS partitions!
6. There are 2 problems with the volume label item. One is that "NO NAME" can be replaced by a space (if it's troublesome, it can not be changed). The second is that the volume label of the USB flash drive cannot be displayed, and "USBHDD-BOOT" can be listed separately as a device item!

That's all for now! I don't know if what I said is correct, or let's see everyone's opinions!

Last edited by 0451lym on 2007-4-20 at 08:15 AM ]

Please advise: How to obtain help information?
My machine's minito is死机, now I can only use minito -nohp, but how to obtain usage help?

Originally posted by 0451lym at 2007-4-20 08:13:
No. N:N : N PRI/LOG ACT HIDE ID FILE SYSTEM LABEL TOTALmb FREEmb
1:1 C: 1 PRIMARY YES NO 0B FAT32 NO NAME 5130 2721
1:2 E: 3 LOGICAL NO NO 0B FAT ...

My opinion:
1, Support.
2, It doesn't matter, it should be okay to keep the status quo.
3, Agree.
4, ID seems to be able to be used to judge the partition type and activation status.
5, It doesn't matter, it should be okay to keep the status quo.

I also want to say a few words:
1. Can the in the NO column be removed to make it clearer (including the that appear after MINITO -D; after MINITO -D, the column has never been used!)? In fact, as 0451lym said, the NO column can be removed. This NO is actually the same as Y in X:Y, (unless it is the display of the entire disk and entire partition), even so, the meaning is not great!
2. For N:N and the following :, it is best to remove the : (this is purely a personal requirement, used for search judgment; it's okay to have it;)! Personal opinion! Of course, the most important thing is to see everyone's opinions! And the convenience in your actual processing!

Just now, I discovered a problem. The calculation of available space is obviously incorrect.

For an NTFS partition, after loading ifs, all show 2047. Even for FAT partitions, I have two FAT partitions (C: and F: in Windows). Only C: shows correctly. F: is empty with 14GB, but it shows only 2051MB.
－－－－－－－－－－－－－－－
No. N:N : N PRI/LOG ACT HIDE ID FILE SYSTEM LABEL TOTALmb FREEmb
1:1 C: 1 PRIMARY YES NO 0B FAT32 NO NAME 7538 3577
1:2 PRIMARY NO YES 17 HPFS/NTFS 7467
1:3 LOGICAL NO NO 07 HPFS/NTFS 10001
1:4 LOGICAL NO NO 07 HPFS/NTFS 15005
1:5 D: 2 LOGICAL NO NO 0B FAT32 APPZ 30004 2051
1:6 LOGICAL NO NO 07 HPFS/NTFS 44453



No. N:N : N PRI/LOG ACT HIDE ID FILE SYSTEM LABEL TOTALmb FREEmb
1:1 C: 1 PRIMARY YES NO 0B FAT32 NO NAME 7538 3577
1:2 E: 3 PRIMARY NO YES 17 HPFS/NTFS 7467 2047
1:3 F: 4 LOGICAL NO NO 07 HPFS/NTFS 10001 2047
1:4 G: 5 LOGICAL NO NO 07 HPFS/NTFS 15005 2047
1:5 D: 2 LOGICAL NO NO 0B FAT32 APPZ 30004 2051
1:6 H: 6 LOGICAL NO NO 07 HPFS/NTFS 44453 2047

The space of the NTFS partition is indeed wrong after using -nohp!

Originally posted by 0451lym at 2007-4-20 08:47:
Using -nohp causes an error in NTFS partition space!

The problem is that I can't do without -nohp. Hehe.

It is suggested to block out No. and N items. According to my level, the existence of N items increases the difficulty of batch processing. Many people use this tool for batch processing. It is suggested to arrange the output items from the perspective of facilitating batch processing. Personally, when minito is used as an auxiliary tool for one - key backup, the most important items are:
1. Active main partition number, occupied space, partition type (sometimes needed).
2. Last partition number (or other specified partition), partition type, available space.

Last edited by lianjiang2004 on 2007 - 4 - 20 at 09:19 AM ]