Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: All2Lame cmd.exe error? (Read 2648 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

All2Lame cmd.exe error?

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.

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

All2Lame cmd.exe error?

Reply #1 –
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 thing with All2Lame. All2Lame generates a batch file when you press "Encode", it's 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....