We seem to be speaking different languages. I can't explain any better so I'll just drop it.
Are you trying to say you need path redundancy for each miner app you are launching? I could add the variables and make it so it can be left blank... Id have to do some testing on how it will work, because I presently am unsure if you can call a %variable%%afterthisvariable% in such a manner. might need some creative twist if its not that simple (which DOS operations can be hinky like that). My batch is only checking for an open task name (not location) so i'd need to keep the original variable and add something like %P2A% %P2B% etc for each miner app version/location.
Im trying to undertsnd your perspective... if I can make it more versatile I am all for it.... But typically batch files are in their home directory where they are controlling stuff. I typically only use a batch in a path-registered location like c:/ or c:/windows when its something like ls.bat.... because I always #$@% up and type LS when I know damned well its not. Thanks unix.
I think what he's trying to to describe is this directory structure:
[mining-directory]
├script.bat
├[ccminer-1.8]
│ └ccminer.exe (renamed ccminer180.exe)
└[ccminer-x11evo]
└ccminer.exe (renamed ccminerx11evo.exe)
[] = Directory
This way, both versions are named the same. Since tasklist returns just the name, and not the path, you only need to search for ccminer.exe in a single for loop. This means you can launch several different versions of ccminer in parallel.