China DOS Union

Now it can basically be confirmed that the drive letter can be converted in combination with GHOST. The AUTOEXEC and CONFIG.SYS on my current machine seem to have errors! Can you post yours?

My here:
http://www.cn-dos.net/forum/viewthread.php?tid=29715&fpage=0&highlight=&page=1

Hello everyone, it's good that it can run...
I just found an extremely strange problem with code compilation, and I can't figure it out... The same code has two different results, and I'm a bit suspicious of the compiler....
It's late, I'll solve it tomorrow....
You all have worked hard too, rest well...

We three have always been very interested in the automatic batch processing of GHOST, but we have been struggling to find a stable, general-purpose, and compact software that can accurately analyze the partition format of X:Y required by GHOST after the IFS is loaded. Now the modified version of GOTOmsdos is only more than 60K, and the loading speed is also very fast, which is quite compact. It would be perfect if it is improved.

1. Correctly loading the drive letters after IFS is loaded is the key to the automatic batch processing GHOST, and realizing the correct conversion of drive letters and X:Y format. (Regarding DOS support for NTFS, my opinion is to use IFS, which has good Chinese support for reading and writing and also supports EXT partitions? NTFSPRO is still a bit worse, of course, it is best to have both, hehe)
2. If a column of the partition information analyzed by TODISK that is directly in the X:Y partition format of GHOST is added, it will be more convenient, hehe. There is no need to deliberately calculate in the batch processing. Of course, if the cost is too high, such as the code increasing too much, then it is not necessary either. (Add a sentence, if it is convenient, add a column of the X:Y partition format of GRUB, hehe)
3. If the suggestion in 2 is not possible, be sure to arrange the order of the partitions in sequence, because the batch processing needs to analyze the partition information generated by TODISK to calculate X:Y, so this order must not be wrong.
4. Fix the absolute position of various information generated by TODISK in the text more accurately. Because the batch processing analyzes these information by using absolute position numbers for positioning, there must be no changes allowed. For example, the starting sector number corresponding to START, whether the width is enough, whether it will widen when encountering a larger sector, and now it seems that the activated * and hidden * are not aligned with the top-level A and H. (Is there also a problem of widening for LABEL? It is suggested to put LABEL at the end)
5. Can a column be added to display the remaining space? Of course, the same as the suggestion in 2, if the cost is too high, give up.

The above are the requirements for the automatic batch processing GHOST. The following is about restoring the backed-up MBR DBR, which is randomly proposed.
1. Actually, I don't understand either. It is said that VISTA has tampered with 8 bytes in the MBR. The MBR repaired by tools such as FDISK cannot boot VISTA. Can the MBR of VISTA and NT be integrated into TODISK, and a parameter can be used to restore it at any time? Of course, here the MBR should be the MBR that does not include the hard disk partition table in the narrow sense. It is a random proposal, hehe.
2. WINIMAGE has a BOOTPART that can restore the DBR of NT, I think. I wonder if TODISK can refer to it.

TODISK itself is a restore backup tool, but it is used by the few of us to analyze partition information. This is not just giving suggestions, but directly customizing clothes. Please forgive the offense.

Originally posted by llztt1 at 2007-4-17 12:24 PM:
Test version 25th floor, successfully run
But there is no drive letter after loading IFS..
Is it that it cannot be loaded itself, or is the function of version 25th floor streamlined??

Yes
TODISK -P -IFS

I don't know how the program handles unpartitioned hard drives?

Just tested in qemu, MTD can't run.
It is suggested to change the name of minitodisk, hehe, I changed it for you first ^_^

1. The drive letters that can be correctly loaded after IFS are crucial for the automatic batch processing GHOST. Realize the correct conversion between drive letters and X:Y format. (Regarding DOS support for NTFS, in my opinion, using IFS is good as it is readable, writable, has good Chinese support, and also supports EXT partitions? NTFSPRO is still a bit short, of course, it's best to have both, heh heh)

Originally, the drive letters after loading NTFSPRO/IFS can be loaded.

2. If a column directly showing the GHOST X:Y partition format is added to the partition information analyzed by TODISK, it will be more convenient, heh heh. There's no need to deliberately calculate it with batch processing. Of course, if the cost is too high, such as the code increasing too much, then it's not necessary either. (Add a sentence: If it's convenient, also add a column showing the GRUB X:Y partition format, heh heh)

The partition representations (including numerical representation and drive letters) generated by TODISK/MINITO are originally completely consistent with GHOST/NTFSPRO/IFS.

4. Fix the absolute positions of various information generated by TODISK in the text to be more fixed and precise, because when batch processing analyzes these information, it locates using absolute position numbers, and changes are not allowed. For example, the starting sector number corresponding to START, whether the width is sufficient, whether it will widen when encountering larger sectors, and currently, the activated * and hidden * are not aligned with the top-level A and H. (Is there a problem of widening for LABEL? It is suggested to place LABEL at the end)

The display space is completely sufficient and will not exceed. Each item already has the maximum space. For primary partitions and hidden ones, since they are indicated by asterisks, they are deliberately close to be intuitive and vivid.

5. Can a column be added to display the remaining space? Of course, similar to suggestion 2, if the cost is too high, give it up

There is no space left for the remaining space. Even removing the numbering is not enough.


1. Actually, I don't understand either. It is said that VISTA has tampered with 8 bytes in the MBR. The MBR repaired with tools like FDISK cannot boot VISTA. Can we integrate the MBRs of VISTA and NT into TODISK and have a parameter to restore them at any time? Of course, here MBR should be the narrow sense not including the hard disk partition table. Random proposal, heh heh]
This idea is good. I don't have VISTA here, but it's easy to add the MBR code. We can consider adding it.

2. WINIMAGE has a BOOTPART that can restore the NT DBR, I think. I wonder if TODISK can refer to it

This is the same principle as adding the MBR code. It's easy to add. We can consider adding it.
This is to handle
Two types of MBRs (DOS/WIN32 VISTA)
But, DBRs are different for different operating systems. It's a bit troublesome...
Therefore, this work should still be done by the partition management tool. After all, TODISK/MINITO is mainly a disk/partition backup tool.

[ Last edited by GOTOmsdos on 2007-4-18 at 07:06 AM ]

At the request of several enthusiastic users, on the basis of cooperating with NTFSPRO/IFS, the function of cooperating with GHOST and DOS batch processing has been added. It has been updated, see the first post.

You've worked hard. Let's try it down.

Ask a basic question, how to get help information?
Under the actual machine DOS, I tried todisk- /? todisk- /h todisk- -h todisk- --hh todisk- and there was no information. How to use it?

In addition, entering todisk causes a crash. No information is given.

Originally posted by lianjiang2004 at 2007-4-18 08:31:
Ask a basic question, how to get help information?
Tried todisk- /? todisk- /h todisk- -h todisk- --hh todisk- under the actual machine DOS, no information. How to use?

In addition, entering todisk causes a crash. No information.

-d : Display all hard drives
-d2 : Display hard drive 2
-p : Display all partitions of all hard drives
-p2 : Display all partitions of hard drive 2
-p2 -NEFSPRO : Display all partitions of hard drive 2 after loading ntfs4dos and display drive letters
-p2 -ifs : Display all partitions of hard drive 2 after loading -ifs and display drive letters
-pfn : Display FAT and NTFS partitions
-p2:3 : Display partition 3 of hard drive 2
-pc: : Display C:

Thanks to the person above. Just now I tried todisk -d1 and it crashed. According to the usage you provided, I'll try again.

Tried again, todisk -p works. But todisk -p crashes. It seems my machine can't run todisk.

Here is the hard drive information output by ghost.
－－－－－－－－－－－－－－－－－－
*********************************
Date : Tue Apr 17 17:49:36 2007
Error Number: (0)
Message: Stats Dump
Version: 8.3.0.1331 (Nov 28 2005, Build=1331)
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Command line arguments: -dd -dfile=c:\ggho\temp\GHSTSTAT.TXT
Active Switches :
AutoName
PathName :
DumpFile :
DumpPos : 0
FlagImplode : 0
FlagExplode : 0

Operation Details :
Total size.........0
MB copied..........0
MB remaining.......0
Percent complete...0%
Speed..............0 MB/min
Time elapsed.......0:00
Time remaining.....0:00

Program Call Stack
sub_main
main

Call Stack
Address Frame Logical Addr Module
0x000000007c92eb94 0x000000000012f8f0 KiFastSystemCallRet+0x0000000000000000
0x000000000012fbe0 0x0000000000000003 0x0000:0x0000000000000000
End Call Stack


Start heap available: 549740544
Cur heap available: 549588992
Total Memory: 802926592

Conventional Memory
Inital Conventional Memory Size = 0
Current Conventional Memory Size = 0
Allocated
33500 ghost.cpp:1386
Free

Fat details:

NTFS details:
----------------

NTFS Global Flags:
----------------
contiguousWrite=1 forceDiskClusterMapping=0
inhibitCHKDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
enable_cache=0 xfrbuflen=0
last_attr_type = 0
loadExact = 0
----------------

Disk Info :
remote.............0
drive..............0
sectors_used.......234436230
estimated_used.....0
pemax..............6
Version............0

# Ord Boot Id Ext First Num Last Used NTFS
0 0 80 b No 63 15438402 15438465 0 No
1 1 0 17 No 15438465 15293880 30732345 0 No
2 2 0 7 Yes 30732408 20482812 51215220 0 No
3 3 0 7 Yes 51215283 30732282 81947565 0 No
4 4 0 b Yes 81947628 61448562 143396190 0 No
5 5 0 7 Yes 143396253 91040292 234436545 0 No

Disk Info :
remote.............0
drive..............0
sectors_used.......0
estimated_used.....0
pemax..............0
Version............0

# Ord Boot Id Ext First Num Last Used NTFS

Fixed Drives

Drive 0 ST3120026AS 3JT44KKK
WinNT (Active)
Total Sectors 234441648
Bytes per Sector 512
MB 114473
Cylinders 14593
Heads 255
Sectors per Track 63
Successful IO Count 124

Floppy Drives

Remote Drives
AsyncIo : 0
Image Devices

Key[1] 1:1
Key[2] C:
Path C:
Desc C: 1:1 [WINXP]
Type FAT
Disk 0
Offset 63

Key[1] 1:2
Path 1:2
Desc 1:2 [pwin2k]
Type NTFS
Disk 0
Offset 15438465

Key[1] 1:3
Key[2] D:
Path D:
Desc D: 1:3 [PROGRAM]
Type NTFS
Disk 0
Offset 30732408

Key[1] 1:4
Key[2] E:
Path E:
Desc E: 1:4 [MYDATA]
Type NTFS
Disk 0
Offset 51215283

Key[1] 1:5
Key[2] F:
Path F:
Desc F: 1:5 [APPZ]
Type FAT
Disk 0
Offset 81947628

Key[1] 1:6
Key[2] G:
Path G:
Desc G: 1:6 [DV]
Type NTFS
Disk 0
Offset 143396253

Key[1] H:
Path H:
Desc H:
Type CD

Key[1] I:
Path I:
Desc I: [雅信CAT3 .5]
Type CD


*********************************