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?
Assuming that this is a real stinker of a DOS bug, how does one get
around it?
Cheers,
Chuck