China DOS Union

For example, I run a self-written program whose content is to COPY a file from one directory to another. When the file does not exist, DOS will prompt that the file is not found. Now I want to print the DOS prompt information into a txt file. How should I do it?

Try this batch script
@echo off
copy \1dir\1.ext 2dir>3.txt

The method of gotomsdos doesn't work

Is this okay?
if exist \1dir\1.ext copy \1dir\1.ext 2dir>3.txt
if not exist \1dir\1.ext echo File not found.

The method on the 4th floor is quite tricky! But this "File not found" isn't from copy, though. Well, it's okay. If the poster doesn't have high requirements, this will do. It's much simpler than redirecting to an incorrect device.

Use lmod

copy dir1\file1.ext dir2 > lmod /L* > 3.txt

lmod is a product of Horst Schaeffer. His products are good, but there are some minor issues under Chinese systems (it always shows "Invalid keyboard code specified" and then Chinese cannot be displayed). I really hope he can improve to support multi-language character sets.
Contact - Email: horst.schaeffer@gmx.net
Homepage: http://home.nikocity.de/horst.muc/int

Horst's software needs no introduction. Most of his software, such as WBAT, cannot cooperate well with Chinese character systems.

Is this problem unsolvable under pure DOS?!

When I use the del *.* command, if there are no files in the directory, there will be an error prompt, or if the file cannot be deleted, the same situation occurs. The method from the upstairs can't solve it, and I hope an expert can give guidance!

Handsome guy~~ Give this a try

copy ..\楼主是帅哥.txt 2>帅哥是楼主.txt

Try using errorlevel... But it seems to make the problem more complicated

Re WisdomNil:

Because in DOS, the error device cannot be explicitly redirected, and internal commands such as del/dir do not exit using INT 21/AH=4Ch, so no errorlevel is generated when an error occurs.

Therefore, so far, implementing error redirection to file output in the DOS command line or batch processing is an unsolved problem. The idea I have so far is to use a debug assembly script to redirect the error device or intercept the output of the screen buffer to a file, but it is relatively difficult to implement.

Originally posted by kcdsw at 2006-4-21 16:11:
Hey guy~~ Try this

copy ..\楼主是帅哥.txt 2>帅哥是楼主.txt

After testing, it is found that there are two types of so-called errors:
1. Command itself error
2. Parameter error

@echo off

echo Parameter error:>帅哥是楼主i.txt

echo ____________________>帅哥是楼主j.txt

echo Command itself error:>>帅哥是楼主j.txt

coby ..\楼主是帅哥.txt>>帅哥是楼主i.txt 2>>帅哥是楼主j.txt

::^^

copy 帅哥是楼主i.txt+帅哥是楼主j.txt errsum.txt

msg *<errsum.txt

del 帅哥是楼主i.txt

del 帅哥是楼主j.txt

del errsum.txt

1. The error message of "Command itself error" can be obtained by "2>";
2. The error message of "Parameter error" is obtained by ">";

[ Last edited by arding on 2006-5-11 at 15:59 ]

Re regarding:

All errors, whether they are errors of invalid command names, invalid command parameters, or errors during command execution, can be divided into two categories: those sent to standard error stderr and those sent to standard output stdout. Although both default to pointing to the console device, they use different ports.

And the copy command of cmd is somewhat special because it sends many errors through standard output, so we use >file to redirect these error messages, but most commands under DOS and CMD usually send error messages through standard error. Therefore, your dichotomy is not universal.

In addition, the error redirection discussed by the original poster is still limited to the DOS environment, and 2> in the CMD environment is not discussed.

Got it a bit. I don't have easy access to pure DOS here, and I've never delved deeply into these details. Do you mean focusing on this sentence:

Most commands usually emit their error messages through standard error.

If that's the case, can capture almost all errors using ERRORLEVEL or 2>?

[ Last edited by arding on 2006-5-12 at 09:28 ]