I can tell you with absolute certainty that FILES= and several of the other CONFIG.SYS commands only affect processes running within the 16 bit DOS emulator.
IPCONFIG.EXE is a 32-bit console app, and as such, is not subject to the restrictions of the 16-bit emulation environment.
This problem has been kind of intruiging. I've been poring over the MSDN docs, and have found no mentioned limits, other than exhausted system resources, that would limit the number of pipes that may be open. As I mentioned before, pipes are implemented in memory, except in the case of named pipes over a network.
What's curious, of course, is that the pipe is being explicitly closed, yet the program fails. It would be useful to know if the ActiveState perl is using _popen/_pclose pipe functions, or the Win32 API interfaces, CreatePipe, CreateNamedPipe, etc.
--Chris | [reply] |
Just scanned the AP613 source.
Didn't find any ocurrence of "CreatePipe" but 25 files contained "_popen". I think it's using either _popen or _pipe after a brief study of win32.c ( but I'm no C expert :).
/brother t0mas
| [reply] |