Not enough memory when running batch process

November 17, 2010 at 09:37:06
Specs: Windows XP Home Sp3, Core2 Duo / 4gb ram
XP Home SP3, Intel Core2 Duo, 4gb ram

Want a front-end for lame so I can batch process multiple files. I got all2lame.exe running with all the correct lame tags but when it tries to execute, the cmd dos window pops open and it says "Not enough quota is available to process this command."

If I type cmd.exe in the Run box in Windows and then copy/paste the command that all2lame creates for lame in the "go.bat" file, it works fine.

So this is some kind of a problem where a batch process is not being given the same memory or quota amounts that you get when running cmd.exe from the Run prompt and executing the conversions 1 by 1 (pain in the butt).

I got the same problem when I tried various .bat files (and drag-dropped folders containing my .wav files onto the .bat file, it gave me the "not enough quota...." error there as well
(such as a batch file with this in it:
@ECHO OFF
FOR /R %1 %%G IN (*.wav) DO LAME.EXE -V2 --vbr-new "%%G")

So, does anyone know how to fix this batch-related quota issue?


See More: Not enough memory when running batch process

Report •


#1
November 17, 2010 at 10:12:21
Try a fesh copy of CMD.EXE


=====================================
Life is too important to be taken seriously.

M2


Report •

#2
November 17, 2010 at 10:54:29
I've got version 5.1.2600.5512. I don't think it's cmd.exe that's the problem since it works when I do the commands manually in a brand new cmd window, it just doesn't work when the batch file launches it's own cmd window....

Report •

#3
November 17, 2010 at 11:01:07
BATs are run by CMD batch interpreter. EXE & COM ain't.


=====================================
Life is too important to be taken seriously.

M2


Report •

Related Solutions

#4
November 17, 2010 at 11:30:25
Ok...very very very weird. I somehow fixed things but it doesn't make any sense how it's fixed.

First I re-made my original batch file:
@ECHO OFF
FOR /R %1 %%G IN (*.wav) DO LAME.EXE -V2 --vbr-new -q0 --lowpass 19.7 "%%G" "%%~dpnG.mp3"
pause

I named it Lame.bat. I dragged & dropped a directory containing my .wav files onto it and it gave me the "quota" error listed above. Then, I changed the extension to "Lame.cmd" and did the same thing and it WORKED! It may have something to do with .bat files sometimes calling command.com versus cmd.exe. I guess .cmd ALWAYS calls cmd.exe, who knows... But the weird part is that I then changed Lame.cmd back to Lame.bat and it STILL worked! It's as if Windows somehow learned that I wanted lame.bat to execute with cmd.exe instead of command.com or something. Like my computer's brain was actually alive and it learned my preference simply by me changing the extension to .cmd, running it, and back to .bat.

The same goes with the standalone program I'm using which also generates a batch file called "Go.bat". At first, it didn't work. I changed it to "Go.cmd" ran it and it worked. I changed it back to "Go.bat" and it still worked. Then I deleted it, re-ran the standalone program so it'd create a new "Go.bat" file and it STILL worked. Again, Windows somehow learned my preferences.

Very very scary/strange/spooky....


Report •

#5
November 17, 2010 at 11:51:38
One more aside....after rebooting, it seems to revert back to old behavior unless I again change the extension to .cmd, execute it, and then change it back to .bat. So I'll just be leaving the extension as .cmd, that seems to be the overall fix without it reverting to the error again.

Report •

Ask Question