China DOS Union

I'm encountering a problem now, which is how to determine whether IFS or NTFS4DOS is loaded in the system. Enumerating memory-resident programs will increase the size of the entire program a lot. For systems that have loaded IFS or NTFS4DOS, the way to read and write the DOS drive letters it generates is different from others. Please be patient, I'm thinking about ways to handle it.

Originally posted by lianjiang2004 at 2007-2-12 00:49:
Please translate. A few days ago, the author released a version with no restrictions and no display of drive letters and volume labels. I am now at my hometown, using a telephone to access the Internet, which is very slow. You can also download the version from 2006-12-26.
The following is the version from 061226. I don't know...

There is a small bug in the 061226 version. When displaying non-standard hard disk partition tables, the numbering will be incorrect.

[ Last edited by 19951001 on 2007-2-13 at 12:18 AM ]

Currently, the software retrieves the hard disk partitions based on the partition chain of the hard disk, so it will not retrieve the unallocated space.

To the netizens:
Many netizens have sent me messages, asking me to release the official version as soon as possible. I can only say sorry.
I am at home now and temporarily cannot release the official version. I will return to Beijing on February 26.

Hehe, you replied so many posts as soon as you came online.

Let me summarize my suggestions.

1. If the hard disk number is not specified in the parameters, it is equivalent to operating all hard disks; otherwise, we have to use the information generated by batch processing judgment to enumerate all hard disks.

2. Correctly display the drive letters after IFS and NTFSDOS are loaded.

3. Can we increase the comprehensive analysis of the partition structure, including the unallocated space, and can we display the available space of the partition? For details, refer to the result generated by PSI. This function can let users fully understand the current usage of the hard disk.

My starting point is to analyze the running results of batch processing programs for single-machine or network GHOST. PSI is good but too large, over 900KB. I hope 19951001 can free us as soon as possible, hehe.

Disk 0:
N L Type FS Size Active Hidden Label Used Free
0 G Primary NTFS 2.0 GB Yes No 778.4 MB 1.2 GB
1 Extended 996.2 MB
2 H Logical NTFS 800.1 MB No No 杯w 6.5 MB 793.5 MB
3 Logical Unform 196.1 MB
4 Primary Free 102.0 MB
5 C Primary FAT 32 596.2 MB No No 1.2 MB 595.0 MB
6 Primary Free 392.2 MB


Disk 1:
N L Type FS Size Active Hidden Label Used Free
0 I Primary NTFS 500.0 MB No No 杯w 5.1 MB 495.0 MB
1 D Primary FAT 32 500.1 MB No No 2.0 MB 498.1 MB
2 Extended 299.2 MB
3 J Logical NTFS 100.4 MB No No 杯w 2.5 MB 97.9 MB
4 K Logical NTFS 88.6 MB No No 杯w 2.5 MB 86.1 MB
5 Logical Free 110.2 MB
6 Primary Unform 100.4 MB
7 Primary Free 133.9 MB

Brother, I left a message for you in the email, but I didn't get a reply. I'm in a hurry...

### First, quote the disk information list from brother lianjiang2004, and then put forward my little suggestion.
You have released the version without volume label, but it is better to realize it through parameters. For using ghost, the volume label is not that important, but the available disk space is more important. This point has also been mentioned by the previous netizens.

Also, in the PartType column, it is better to connect with underscores for "Hide Win95 FAT32", "Linux Native" and so on to make this column regular, becoming like Hide_Win95_FAT32, Linux_Native. There is no need to connect for HPFS/NTFS which is already connected. Also, in the Act column, if it is not, write No. This can be referred to psi's list. Because when the disk result analysis is incorrect (the situation encountered by lianjiang2004), taking the value of the offset column becomes relatively important. If each column is regular, it will save a lot of batch processing analysis processes.
Of course, this is just a proposal, but if not, the value of that column can still be obtained.

At present, the most important thing is to distinguish the formatted and unformatted FAT16 partitions well.

```
dpit
No. Drv Type Volume PartType Act Offset Sectors MBytes
0:1 Primary HPFS/NTFS Yes 63 15438402 7538
0:2 Primary pwin2k Hide HPFS/NTFS 15438465 15293880 7467
0:3 Extended LBA 30732345 203704200 99464
0:4 Logic HPFS/NTFS 30732408 20482812 10001
0:5 Logic MYDATA HPFS/NTFS 51215283 30732282 15005
0:6 C: Logic APPZ Win95 FAT32 81947628 61448562 30004
0:7 Logic DV HPFS/NTFS 143396253 90831447 44351
0:8 Logic Hide FAT16 234227763 208782 101
```

Originally posted by amao at 2007-2-14 20:41:
First, quote the disk information list from brother lianjiang2004, and then put forward my little suggestion.

You have released the version without volume label, but it is better to implement it through parameters. For using ghost, the volume label is not that important, but the available disk space is more important. This point has also been mentioned by the previous netizen.

Also, for the PartType column, it is better to connect Hide Win95 FAT32, Linux Native, etc. with underscores to make this column regular, such as Hide_Win95_FAT32, Linux_Native. There is no need to connect HPFS/NTFS as it is already connected. Also, for the Act column, if it is not, write No. This can be referred to psi's list. Because when there is an incorrect analysis of the disk result (the situation encountered by lianjiang2004), taking the value of the offset column becomes relatively important. If each column is regular, it will save a lot of batch processing analysis processes.
Of course, this is just a proposal, but if not, the value of that column can still be obtained.

Currently, the most important thing is to distinguish between formatted and unformatted FAT16 partitions.

1. The function of listing disk space, I am also writing relevant code, and this function I will implement.
2. Connect with underscores, adopted
3. Adding NO for non-boot partitions, I think it is unnecessary, not adopted
4. Regarding formatted and unformatted FAT16, I once sent you a message to let you send the content of the boot sector, but you ignored me.

RE the owner
4. Regarding formatted and unformatted FAT16, I once sent you a message asking you to send the content of the boot sector, but you ignored me.

I also replied to you saying that mine is virtual in VMWare. Do you want it, and then there was no follow-up.

Originally posted by amao at 2007-2-15 00:38:
RE to the LZ
4. Regarding formatted and unformatted FAT16, I once sent you a message asking you to send the content of the boot sector, but you ignored me.

I also replied to you saying that mine is virtualized in VMWare. Do you want it, and then there was no follow-up.

I didn't receive your message

Originally posted by 19951001 at 2007-2-15 01:57:


I didn't receive your message

Sorry, it seems that it's better to send it to your dpit-displayed email in the future. I'm really sorry.

Very good software.
I want a very simple FOR WIN version. I wonder if the landlord can help me realize it. I am very grateful.
The version I want is to locate which partition of which hard disk a certain drive letter exists in. (Must be For Win)
For example: dpit e: >a.txt
The result of the output a.txt is as follows: 1:4
Or 2:4
The meaning is that 1:4 means that the E: drive letter exists in the fourth partition of the first hard disk, and 2:4 means that the E: drive letter exists in the fourth partition of the second hard disk.

Originally posted by maxfull at 2007-2-19 13:41:
Very good software.
I want a very simple FOR WIN version. I wonder if the owner can help me realize it. I am very grateful.
I want the version to locate which hard disk and which ...

Personally, I don't think it's possible. After all, this is just a specific function. At least, you need to process the output result by yourself.

Bookmarked

Originally posted by 19951001 at 2007-2-13 00:05:

DPIT adding the /ghost parameter can meet your requirement

DPIT /ghost crashes? What's going on?