Chuck Guzis wrote:
I've got a few nested (via CALL) batch files that
create different
files via the > and >> redirection operators under MS-DOS 7.01.
Everything seems to work fine until I've created more than the number
of files on my CONFIG.SYS FILES= statement--whereupon I get a "File
creation error" message and DOS hangs, necessitating a reboot.
It seems as if
COMMAND.COM is keeping open any file created within a
batch script by redirection. Is this really so--or is it the case
that DOS isn't closing each batch file invoked with a CALL statement?
In my experience, DOS keeps all files open until the original parent
batch file finishes execution.
Assuming that this is a real stinker of a DOS bug, how
does one get
around it?
1. Increase FILES= (what is it set to now?)
2. Chain if at all possible (it sounds like you're going past DOS's
nominal level of recursion)
--
Jim Leonard (trixter at
oldskool.org)
http://www.oldskool.org/
Help our electronic games project:
http://www.mobygames.com/
Or check out some trippy MindCandy at
http://www.mindcandydvd.com/
A child borne of the home computer wars:
http://trixter.wordpress.com/