When you create the first string in the batch file, you are targeting a specific .exe client to start the work.
There are 2 exe clients to get paid out with NiceHash. BTC or ZCash. Versions 3.0b and 4.0a include the newer
nheqminer.exe, but not the newer version of
nheqminer_zcash.exe miner. That means if you are trying to start a batch file with command nheqminer_zcash.exe, there is no such application/exe file inside nheqminer_v0.4a folder because they never updated it. When you are creating the batch file string, you need to make sure the folder in which you put the batch file has the correct .exe application you are running and match it with the correct address, BTC or ZEC.
Examples:
Mine on NiceHash.com service as a hashing power seller, using CPU and NVIDIA GPU, using USA location:
nheqminer.exe -l usa -u
BTC-ADDRESS -t 6 -cd 0
In this example we have a quad-core CPU with hyper-threading (8 threads available) and only one NVIDIA GPU in the computer. We are mining with 6 threads on the CPU and on the whole NVIDIA GPU.
Mine on Zcash by NiceHash ZEC pool, using CPU and AMD GPUs, using EU location:
nheqminer_zcash.exe -l eu -u
ZEC-ADDRESS -t 6 -od 0 1
In this example we have a quad-core CPU with hyper-threading (8 threads available) and two AMD GPUs in the computer. We are mining with 6 threads on the CPU and on both AMD GPUs.
https://github.com/nicehash/nheqminer/releases
The other issue is, they excluded OpenCL.dll and logsetuplib.dll from newer versions. I think these are needed to run the client. I've been using nheqminer_zcash 3.0a for now.