> If that's the case, I don't understand the usefulness of
> inspecting the list
> of DLLs used (with Depends, chkmod32, or some other utility).
> I guess this
> is really a question for Dean, in whose hallowed footsteps I
> blindly (that
> is to say, ignorantly) trod. But if someone else can open my
> eyes, I'd be
> equally grateful.
You have to look at both lists (when using Depends) - the list of DLLs in
the lower view simply lists all the DLLs pulled in. If you see one that you
don't think should be there, then look in the tree where the specific
dependencies are shown. If msvcrt is only pulled in via a 'system' DLL, I
wouldn't worry about it too much - unless that 'system' DLL is some 3rdparty
one asking you to delete memory it allocated, or vice-versa. (I just looked
at our app and found msvcrt is pulled in by multiple system dlls:
tapi32.dll, comdlg32.dll, winspool.drv, advapi32.dll, oledlg.dll - those in
turn have dependencies on about another half-dozen dlls that pull it in -
it's a tangled web windows weaves!)
Dave Connet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
