"Not enough memory to process this command" after using the start command in a batch file with windows 7

Question

I am creating a batch file that should open a second batch of script in a separate cmd window. I can use all my code successfully if I use the "call" command instead of "start", but does not run the script in my own window. I got this error many times in the past and is always associated with the start command. I am changing how I am doing this process and everything works well. Why does the start command cause this error and how to fix it? Below is a sample of my code.

start "" /w "k:\Bundle Support files\record serial.cmd" 

The second batch file opens and completes all tasks except the last, which

 goto :exit :exit 

I changed the last command in the file several times and always made it through the entire batch, but the last command that would end this batch with the error "Not enough memory to process this command". This happens on several machines (various equipment) and several OS. I tried to fix IRPStackSize with no luck. Any suggestions as to why I am getting this error?

Thanks Kevin

Answer 1

I ran into a similar problem, and the solution for me was rather strange. It appears that setting the window name to nothing ("") is causing an error.

So instead

 start "" /w "k:\Bundle Support files\record serial.cmd" 

to try

 start "Placeholder Name" /w "k:\Bundle Support files\record serial.cmd" 

I can’t check if this will work in your case (and I doubt it matters since you left long ago), but I hope this helps someone experience any such errors.

Answer 2

Replace goto :exit with goto :EOF . Do not define the EOF label (it is predefined).

Answer 3

What the START command does when cmd starts. If you started START cmd, you did not expect the CMD to exit immediately - it will remain ready to use there. Thus, you will either CALL the cmd file, or finish, or START to cmd, and it will not complete, but you can complete it using the EXIT command. The problem was also resolved correctly by SEIPIA - instead of using start "" filename.cmd, put something between the quotation marks as the header, which will prevent the error.