PE> Now the reason that cvp let's me open 15 files, is 
 PE> because it allocates fileno's of 5-19, this time 
 PE> WITHOUT skipping 6 and 12!

 PE> Now, can anyone explain WHY cvp would do such a thing, 
 PE> and secondly, given that it CAN, does this mean that I

I'll bet it has nothing to do with cvp directly (someone else up the parent
tree is using those file handles already),  but has to do with the
equivalent of a "start /i".

What happens if you start a session with "start /i" and run your
compile from there?




 PE> and changed that last "720D" to "EB0D" to always jump 
 PE> (succeed) as oppose to only succeeding if the number 
 PE> was less than 20.

And now you are _for sure_ overwriting some memory beyond
the crt's statically allocated _files[20] array.

I don't think it is possible to get around this problem by patching cl.exe.


--- Maximus/2 3.00