Eric Pouech <[EMAIL PROTECTED]> writes: > but we do export FILE_Dup2 from kernel32, which doesn't correspond to > anything either. My patch was also killing that one. Basically, > replacing one krnl386 API, and a wine only API in kernel32, with a > wine only API in winedos (which is our own, so portability of APIs is > less an issue), which I still consider worthwhile.
There are better ways of getting rid of FILE_Dup2 than moving a bunch of kernel APIs into winedos. The obvious one is to allocate new handles until we get the one we want and then free the others; not exactly efficient, but I don't think many apps calls FILE_Dup2 in a loop. -- Alexandre Julliard [EMAIL PROTECTED]