I'm having some difficulty with a complex CMD file that is doing lots of manipulations. It's calling lots of other CMD's, and it is repeating this a lot (batch processing), and it is using AWK, SED and GREP a lot. The code itself works 100% OK, but sometimes it just hangs ... and it always hangs at a combined SED/AWK command. I was looking into this issue, and found that problems may occur with symptons that handles on NTVDM are causing 16-bit programs to hang, because the memory gets exhausted. I changed some .NT file, increasing "files" to a higher value, but that did not work. I know that SED, GREP and AWK work OK on a lot of different scripts, I'm just putting the system to much more stress by using this particular CMD file. To give an example, this CMD file can run up to 2 hours, constantly doing different calls (not 1 big copy command or so, I mean). Does anybody have an idea here ? Hi there.

A = Nope.