ThurstonX
Headphoneus Supremus
I'm sorry for late reply. I was busy with lots of schedules in this week including HE1 audition too. I only got time to check out forums today.
Maybe it has something to do with double quote " not being used so space can be issues in some cases. Normally batch script will terminate itself after finishing the command. I recommend you to try start command so it will not hold process and can also customize with priority and affinity too.
Regards,
Keetakawee
No worries, I figured you were busy.
Here's the problem: if I use Fidelizer to run my batch file, I'm always left with a command prompt window. If I run the batch file manually, I get no remaining command prompt windows.
I've played around with the batch file, but to have Fidelizer execute all three steps, I have to have foobar2000 startup as the last step. I call nircmd to hide the command prompt window, otherwise even running it manually results in a foobar2000 command window. You can test that by starting foobar2000 from the command line. Using nircmd was the easiest method I found to hide the command window. But, for whatever reason, that same command, when Fidelizer executes the batch file, results in the visible command window.
So, like I said, unless you have some specific solution, I'll leave well enough alone, as running the batch file manually works best.
As to why Fidelizer chokes on a batch file with spaces in its name, yet runs fine if I remove the spaces, that ball's in your court