China DOS Union

The following can only be executed separately:
for %%1 in (c d e f) do command1 %%1
for %%1 in (c d e f) do command2 %%1

Can the above two commands be executed together? Under 98

Try this
for %%a in (command1 command2) do for %%b in (c d e f) do %%a %%b

Hehe! OK, I'll try it. Do I need to add /f,
it's 98 oh

Re roy:

Standalone DOS and the DOS mode of 98 both do not support nested loops. You can use the following instead:

for %%a in (command1 command2) do %comspec% /c for %%b in (c d e f) do %%a %%b

Many thanks to both of you, moderator ROY, especially WILLSORT!
The moderator reminded me that a command set can be used inside parentheses, and WILLSORT cleared up my confusion and made me understand COMMAND /C in DOS.
Thanks!

The following is quoted from willsort's post on 2004-1-26 21:29:28:
Re roy:

    Standalone DOS and the DOS mode of 98 both do not support nested loops. You can use the following instead:

    for %%a in (command1 command2) do %comspec% /c for %%b in (c d e f) do %%a %%b

A quick question: is this %comspec% the variable for DOS's command.com?

Of course it is! Using the variable can absolutely guarantee no errors

Oh, right right right, of course it is. I forgot about the set comspec=... used in some cases; I don't quite understand what you mean here by guaranteeing no errors. Could you roughly explain what errors and differences might arise from using the variable versus using it directly? Thanks

Re xiaojun:

%comspec% is assigned automatically by the system; you can just refer to it directly, no need to use set.

Brother willsort, hello!
At the DOS7.10 command line, the current directory is C:, and C: has three TXT files: 1.txt,2.txt,3.txt. D: also has three TXT files, 4.txt,5.txt,6.txt. I want to compare them. I type:
for %1 in (*.txt) do command /c for %2 in (d:\*.txt) do fc %1 %2>>abc
Then the problem appears: the contents of abc are:
1.txt compared with 4.txt
............(normal)
1.txt compared with 5.txt
Cannot find file 5.txt (the current directory is C:, so at this point it treats d:\5.txt as c:\5.txt, so it can't find it! In other words, in the FOR loop command, from the second time on it ignores d:\ and treats it as being in the current directory!!)
1.txt compared with 6.txt
Likewise it cannot find file 6.txt... and the same below...
That is to say, in the FOR loop, the first round is normal, and the rest all go wrong!
However, I'm doing this at the command line; I haven't tried it in a batch file yet, but it should be the same, right?

Second, when I use %comspec% /c instead of command /c, it says syntax error, strange!!

What's going on?

Also, at the XP command line, this problem does not occur, everything is normal.

Re gotomsdos:

　　I cannot reproduce the problem you found. The environment I used was the
Win98 DOS mode with the site's MS-DOS 7.1 installed. I likewise created the above three text files in the roots of drive C and D, and used the following command lines, both of which gave the expected results.

　　1. FOR %1 IN (*.TXT) DO COMMAND /C FOR %2 IN (D:\*.TXT) DO FC %1 %2>> E:\ABC.TXT

　　2. FOR %1 IN (*.TXT) DO %COMSPEC% /C FOR %2 IN (D:\*.TXT) DO FC %1 %2>> E:\ABC.TXT

　　Please check again your runtime environment, as well as the existence and attributes of the text files.

willsort: Under the full installation edition of MS-DOS 7.10, it can boot Win3.x, and it can also boot Win95 and Win98, so it shouldn't just be called Win98's. I know that the DOS that comes with Win98 usually cannot boot Win3.x; it isn't that pure.

gotomsdos: Please pay attention to the setting of the LFNFOR command. Try setting LFNFOR to OFF and see whether that so-called "BUG" still appears.

Thanks to both of you for replying!
willsort: thanks for testing it! The data in all respects are correct.
Wengier: OK, I'll try again according to your suggestion!