中国DOS联盟

This tool is used under PE, and there may be serious defects.

Originally posted by lianjiang2004 at 2008-4-8 12:30:
This tool is used under PE, and there may be serious defects.

Can you specifically talk about what types of disks the K: M: X: in the picture are?

K: It's the hard disk, correct.
M: It's the boot CD.
X: It's the memory disk after PE boot.



Last edited by lianjiang2004 on 2008-4-10 at 08:31 AM ]

Excuse me, what software is the information in the picture above from? Can it be used under DOS? Is this software used to determine partitions in your GGhost? Thanks

Originally posted by adiwdmd at 2008-4-10 08:55:
What software is displaying the information in the picture above, upstairs? Can it be used under DOS? Is this software used by you to determine partitions in GGhost? Thanks

omnifs for dos, omnifs32 for windows,
Can be used under DOS, the GGhost I use is this tool.
Good compatibility, but large size, heh heh.




Last edited by lianjiang2004 on 2008-4-10 at 09:28 AM ]

Provide the latest version of omnifs v11.0.2.1573 for download. Take it if you need it.

http://www.cn-dos.net/forum/viewthread.php?tid=38141&fpage=1

Use version 2008.2.18 to check. There are also two hard drives and one DVD drive on my machine. Boot with PE, PE is X:., execute dsptw /a /pdr and the display is normal. I also rechecked the code and found no problems for the time being. The version that reported the error in the previous post is version 2007.7.17.

Explain one thing, after finding this problem, I used the latest version, and the result was the same. Just didn't take a screenshot.
A few days ago, there were some problems with the computer, and the hard drive was reformatted. The virtual hard drive is also gone.

Also, it doesn't seem to occur in all virtual machine PE environments. But under that virtual hard drive, otherwise that result appears, and changing the PE is the same.

Speechless!!!!!

Last edited by hlytg on 2008-5-7 at 06:18 PM ]

Originally posted by lianjiang2004 at 2008-4-28 16:54:
Just to note, after discovering this problem, I used the latest version, and the result was the same. Just didn't take a screenshot.
A few days ago, there were some problems with the computer, and I re-formatted the hard drive, and the virtual hard drive is also gone.

Also, it doesn't seem to occur in all PE environments of virtual machines. But under that virtual hard drive, otherwise that result appears, and changing the PE is the same.

Please do not use this software in virtual machines. This software is not designed for virtual machine environments

Originally posted by hlytg at 2008-4-30 09:00:
It is suggested that the楼主 can add the function of modifying the partition type in the dsptw version. The more applicable place is that the partition can be modified to the esia format with a batch file under win:
Method to modify the extended partition:
First use pqed ...

The software has already realized the function you want. I hope no one will raise such ignorant questions in the future


DSPTW
/ChangeType: Change Partition Type.
type: 00-FF.
partno: Partition Number.

Originally posted by 19951001 at 2008-4-30 17:40:

Please do not use this software in a virtual machine. This software is not designed for virtual machine environments

Then that's the only way.

Originally posted by 19951001 at 2008-4-30 17:45:


The software has already realized the function you want. I hope no one will raise such a naive question in the future

DSPTW
/ChangeType: Change Partition Type.
...

It seems that this function is not available in the DOS version. I wonder if this function can be added.

DOS versions can add this function. I'll modify the program when I'm free some day.

Please ask the landlord to take a look at the parameters I suggest adding (with supplements): /mbr /r /m /n

/mbr was originally there, only restores the standard MBR (it is said to refer to XP's, which has good compatibility)
/r file name restores the specified file (when not loading /m /n, it defaults to 1~432 bytes, that is, the first 27 lines, see the red area in the picture below)
/m ordinal custom recovery byte range start byte, limited to 1~446, m - n cannot be negative
/n ordinal custom recovery byte range end byte, limited to 1~446, m - n cannot be negative





Legend:

1. Red part: MBR, theoretically occupies up to 446 bytes. In this example, it actually occupies 420 bytes. To leave some room, 432 bytes are needed (16 bytes per line * 27 lines, red part).
2. Blue part: Originally should be part of MBR, but practice proves that these 4 bytes should not be overwritten. This is the Microsoft disk digital signature area (for anti-piracy? Unknown). Clearing it cannot boot, changing it to other values will report "found new hardware" under WIN. In short, just don't touch it.
3. Yellow part: hard disk partition table
4. Orange part: end mark


Example:

1. Restore the a.mbr generated by the mother machine to the local machine (used to restore the MBR in normal cases, that is, the MBR smaller than 432 bytes)
dsptw 0 /mbr /r a.mbr or
dsptw 0 /mbr /r a.mbr /m 1 /n 432

2. Only restore the "Microsoft disk digital signature" in the a.mbr generated by the mother machine to the local machine (used for special purposes such as restoring the universal GHOSTXP anti-blue screen死机)
dsptw 0 /mbr /r a.mbr /m 441 /n 444

Landlord: Since /m /n is not urgent to use and programming may be more difficult, it can be temporarily not developed (it can be considered in the future to set a parameter for byte-level copying, backup and restoration separately, not limited to MBR, can operate any small segment of character set of any sector, just like the /D parameter, use parameters such as start bytes offset, and launch it after mature consideration).
/R is what I urgently need, it is best to complete it in these two days, thank you.

Last edited by gmy on 2008-5-7 at 09:12 PM ]