On Mon, Jul 17, 2000 at 09:47:13AM +0200, Uwe Bonnes wrote:
> Hallo,
>
> no quick shots :-)
>
> CRTDLL isn't a low level DLL like NTDLL. Many thinks that don't work
> with wine crtdll work with native crtdll. File handling is done
> through Api Calls into Kernel/User and so even the file handle problem
> shouldn't exist.
>
> A scan through native CRTDLL on my system lists 622 exported APIs. And
> especially Cygwin/MingW programs use a lot of them...
Ah, now I have a better view of that.
In this case (i.e. if native CRTDLL really is completely system independent)
I'd alter the loadorder to prefer the native version and
emit a warning message in the dll attach stage of the builtin CRTDLL
(i.e. in case Wine uses the builtin CRTDLL).
I don't really think we should drop CRTDLL. It's a fundamental DLL,
and besides there might be license problems with using the native one
with no-windows.
BTW, can you confirm that native CRTDLL *is* system independent ?
Maybe we should put a warning message in the dll attach stages of all
rather incompletely implemented builtin DLLs...
Andreas Mohr
