中国DOS联盟

I've asked many batch processing experts, but it's really too difficult to achieve in pure DOS. findstr can't be used. Everyone, please help. Is it possible to achieve it with the help of third-party tools? The simple introduction is as follows:

In pure DOS, running a certain DOS program Gdisk, the screen outputs text content as follows

AAA BBB CCC // The first line
xxx yyy zzz // The second line

The above letters are all substitutes, just roughly output like this (all the output strings are displayed in the pure DOS screen, no text file is generated)

Now it is required to judge the above output of Gdisk. If "A01" or "A02" appears in the second line, execute the statement go1; if not, restart

Probably like this. Can you put forward some ideas? Do you need to use third-party tools like input, askenv, aset, xset, strings, wbat, be? Can you give the general writing of the batch processing?

Last edited by xiaofking on 2008-1-14 at 01:20 PM ]

Using NSET can solve this problem!

Moderator... Can you write a few sentences according to my process?

Or can you give me a usage method of nset? I can only find this sentence on the Internet: Nset.com gets variables from the output to set, FINDCD -a|NSET CDROM=$1

You can only be achieved with the built-in find of DOS. If you just want to perform a case-insensitive search for A01, then
gdisk| find "A01" /i>nul
if errorlevel 1 goto end
:go1
::Other statements
:end

If you specify to perform a case-insensitive search for A01 in the second line, then
gdisk | find "" /v/n | find "" | find "A01" /i>nul
if errorlevel 1 goto end
:go1
::Other statements
:end

find 在纯DOS无法使用....
find in pure DOS cannot be used....

In pure DOS, you can't specify which line to search on.

find can be used... but the method you mentioned above doesn't work

In pure DOS, `find` is an external command, so you need to find a `find` for DOS.

I've tried it. Whether running nset or find, in pure DOS, it will all appear "Drive A is not ready to write" A: Abort, R: Retry, F: Fail? It proves that both nset and find are commands that need to write to the cache... It doesn't work...

Originally posted by xiaofking at 2008-1-12 00:35:
Tried it. Whether running nset or find, in pure DOS, the following appears:
"Drive A not ready to write. A: Abort, R: Retry, F: Fail?"

This proves that both nset and find are commands that require writing to the cache... It doesn't work...

Here's the answer
http://www.cn-dos.net/forum/viewthread.php?tid=36718&fpage=1&highlight=

I've read it carefully. The problem is that I can't generate a txt file, and the symbol "|" can't be used in pure DOS either. After Gdisk -a, it's directly output on the screen.

I've looked for many tools. Actually, the problem is how to achieve this function without outputting a txt file. If outputting a txt file is concerned, it's simple.

"Drive A is not ready" A: Abort, R: Retry, F: Fail?
Did you see it on floor 11

Originally posted by fastslz at 2008-1-4 12:10:
Let me guess and analyze the reason
F should be your CD-ROM drive letter. There is no find.com external command in the DOS you booted into, and the Path variable has %CDROM% or F:\....., then DOS tries to read the directory on the CD-ROM...

Let me guess and analyze the reason
Guess 1: Your computer should have a floppy drive. There is no find.com external command in the DOS you booted into, and the Path variable has A:\, then DOS tries to read the A:\ directory to find find.com, so a general error occurs reading drive A:\.

Guess 2: Your computer should have a floppy drive. There is no find.com external command in the DOS you booted into, you copied the xp find.exe to use in pure DOS. The xp find is a 32-bit subroutine. To use it in pure DOS, 32-bit support file CWSDPMI is needed. And the Path variable has A:\, then DOS tries to read the A:\ directory to find CWSDPMI.exe, so a general error occurs reading drive A:\.

Unable to generate a txt file, not because the | symbol cannot be used in pure DOS. It has been explained in Guess 2 that it is because the find command did not execute successfully. If it did not execute successfully, of course a txt file will not be generated

lmod should be able to specify lines. Can't you just output it with gdisk first? Does it have to be output on the screen?