One of us is not understanding. If you know what you are doing then fine but some of your response suggests otherwise.
My changes should work as is for you, I don't know why you believe it's so complicated. Special pointers? TSR? You've
lost me. I was commenting on how I would need to code an app such as a TSR to be able to be "multithreaded" in DOS....  more rambling than anything.

I have been doing something similar for over a year (monitoring miner tasks), it's just that all my executables already had
the same name so I didn't have to rename them.

You said "The 'tasks' do not have the same name;  they have the same executable name." What's the diffreence? Doesn't
tasklist /FI IMAGENAME return the file name of the executable? correct.  that function only returns the filename of the active process, or the way I have it, it is searching the task manager for a specific process filename.

Shortcuts wouldn't solve the problem because it would hide the taskname from the batch script, that is the opposite of what
I want to do. How would the task then be monitored? launching the process attaches a taks name or window title to it.  you can't fetch this value AFAIK.  I see no reason to add directory structure to a system that's supposed to be in one place.  "small footprint" concept

I don't see the relevance of the Window title or how my changes affect your use of it. so you can see what algo's are currently running.  otherwise you would have sit and watch shares until a block changes... then you can visually see the algo name that is currently running.  I did this for the benefit of the people using the script more than anything

You say I'm trying to add definition as to which one is running. On the contrary I'm trying to abstract it so the task monitor
doesn't have to to pick the taskname based on the algo, they are all the same. its not based on the algo, it's based on the name of the miner app.  if I could use one version of the app for all tasks, then I would happily do so.  but there's no x11evo support in ccminer180 or ccminer176.  Thus the reasoning for adding the algo name to that version of ccminer so I know what its for.  I can see how directories could help fix this, but its way less code and things to update in the end changing the miner app filename instead

I agree that it would make the script less universal but when you consider that with your implementation a user would have to ensure
all executables and the batch file are in the same dir. With my changes a user would only have to define variables for each path.
It doesn't have to be done by editting the file, shell variables will do.  Isn't this the original idea, to keep it together?  Plus, shell variables are what I am after.  I am trying to stay as close to the system level as possible