China DOS Union

Re All：

Judging only from the content of this post, it really is quite original. Because many people know it can be used this way, but don't think of using it this way. It's just that the OP's last paragraph really lacked consideration, so it was only natural to provoke public anger.

As for the OP's final question, I think brother "Ultimate Warrior"'s line of thought is correct, it's just that the implementation method wasn't well considered. For editing exe files or other binary files, you absolutely must not use text editors like edit, and must use a dedicated hex editor instead.

And following the OP's line of thought, it seems this problem also needs to use commands that come with DOS, so that leaves only debug. Below is my solution. For the sake of simplicity, some detailed issues are omitted.

Note:
All numbers appearing below are hexadecimal, and calculations should also use that basis;
The contents in square brackets should be hexadecimal values; here they are named according to what they represent, and in actual operation they need to be replaced with the corresponding values according to context;
The contents in parentheses are comments and should not be entered during actual operation;

c:\windows>ren 3.exe 3.eee （change the program's extension to avoid debug's special handling of executable programs）
c:\windows>debug 3.eee
-s 100 ffff "MZ" （search for the MZ signature word in the range 100 to ffff）
: （shows matching address）
:
.... （there may be some more）
-d （display each address in turn, determine the start address of the second program from the displayed contents）
-d （assume the start of the second file Begin2 is found at xxxx1）
-n 1.eee （create file 1.eee）
-r cx （edit file length）
CX （shows the length of the original file 3.eee）
: （enter Begin2 minus 100 here, that is, the length of file 1.eee）
-w （write file 1.eee）
Writing bytes （shows number of bytes written）
-m ffff 100 （move the contents of the second file to the start at 100）
-h （use the difference to calculate the length of the second file）
（the former is the sum, the latter is the difference; the difference is the length of the third file minus the first file）
-n 2.eee （create file 2.eee）
-r cx （edit the length of file 2.eee）
CX （shows the length of the original file 1.eee）
: （enter the length of file 2.eee here）
-w （write file 2.eee）
Writing bytes （shows number of bytes written）
-q （quit DEBUG）
c:\windows>ren 1.eee 1.exe （change the program extension back）
c:\windows>ren 2.eee 2.exe

Bump

Expert above,

DEBUG may be something very easy for you people, but for those of us without an assembly background it's simply harder than climbing to heaven,

I once tried random experiments with DEBUG and made the hard disk unbootable and inaccessible. I exhausted every data recovery program under the sun and still couldn't recover it (except professional recovery). So I'm a bit afraid of random experimenting with DEBUG

If you say it, don't just make things up

That is indeed how the Benbengou software works. It first splits 3.exe into 1.exe and 2.exe; afterward it creates a batch file, and the contents of the batch file are just copy/b 1.exe+2.exe 3.exe. As for debug, I don't really understand it either.

So much time has passed and the OP still hasn't said anything. Looks like the OP doesn't know either!

Try disassembling copy

Putting on a mysterious act

Child's play. If younger people aren't very proficient with DEBUG, that's okay. I'll post E32 for DOS for everyone; it can modify TXT and BIN files. You just need to search for MZ (because EXE files usually start with those two characters), then copy, cut, and save, and enjoy yourself. How can operating under DEBUG count as an internal employee command? Besides, if the program contains more than two MZs, would you still be so smug? Also, let me tell everyone that E32 is very easy to use. I use it to edit and modify hard disk firmware, and it's very practical, with quite good compatibility!

[ Last edited by cnch on 2006-6-30 at 12:34 ]

Child's play, garbage

This is really simple

Aren't 1.exe and 2.exe still both right there

Just delete 3.exe and keep those two

OP, stop hiding it already. If there's really an answer then say it. After you say it, everyone can give you a good beating

By the way, one more thing:
if you want to do this relying only on standard DOS internal commands, then it is absolutely impossible to implement it perfectly
^^^^^^^^^^^^
You definitely need help from third-party software (even if it's made by MS, it's still third-party)

And even with third-party software, manual intervention is still needed

Because a binary file may contain more than one MZ marker. Intelligent splitting is just a dream that can never be perfectly realized

Of course, if on the basis of the MZ marker you also add checks for the load point and relocation markers, then the success rate should be higher

But by the way, let me ask the OP, what's the use of doing it this way? It's okay for killing boring time

By the way, one more thing: we need to express praise and respect to our moderator comrade

For still taking such a serious, negative, and sincere attitude in trying to solve a thread this boring, almost garbage

That really is how a responsible good moderator acts

Thumbs up!

Two clues for everyone:

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

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

Both of these threads were posted by the OP, and after the forum conversion the OP never came online again. The email contact left behind has also become invalid. Maybe this thred will become one of the Union's great unresolved mysteries

I did a preliminary search with baidu. The OP was on forums related to wuyou, 20cn, Kanxue, microcontrollers, PXE boot, and the technical level was actually pretty good, so he probably wasn't just making things up

[ Last edited by electronixtar on 2006-7-1 at 20:52 ]