Windows批处理：在由一个称为“批处理”的cmd窗口中运行命令？

Question

I want to run a batch-file A which calls/starts another batch-file B which opens a new cmd-window. Then I want to run a user-defined command in this new cmd-window. This command is only recognized after running file B or in this new cmd-window, but the call of the command itself should be written in file A (file B is set and can't be changed). How can I do this?

As far as I understand the behavior, I can't access a cmd-window opened by another batch-file. I wrote a simple test case to show you the problem, see below.

I already tried call and start . If I run batch-file B manually in a cmd-window, I can run the user defined command in the same window because the current cmd window is "updated" and the command is recognized.

Simple test case: In this example all commands following call scriptB.bat in file A are ignored (probably because the commands are run in the old cmd-window which is "overridden" by the new cmd-window opened in B which is now active). How can I pass the commands, especially the user-defined one, to the new cmd-window?

scriptA.bat:

@echo off

echo Start script!
call scriptB.bat
%user_command%
echo End script!
pause

scriptB.bat:

@echo off

set user_command=echo USER COMMAND!
cmd

Output:

Start script!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
*my Path*>

Answer 1

After re-reading the Q it became apparent that the user wanted to have variables set in both scripts, and then somehow over-ride the values set in Script B with those in Script A which wee being set after the fact.

That is not possible without changing Script B to be reading the info for the variable names from the registry using WMIC and having Script A use SetX , or by having Script A write to a file and Script B read from the file.

However, this woudl create a Race condition as Script A may be setting that values before or after Script B checks.

Further Script B can not be modified anyway, and if it could then it could just be set up to use a normal SET Command in Script A and then have script B use those variables.