Could someone verify this problem: when comlog.dll is in the same directory as OllyDbg.exe, OllyDbg displays the following error message when starting:

OllyDbg: OLLYDBG.EXE - DLL Initialization Failed

Initialization of the dynamic link library C:\ComLog.dll failed. The process is terminating abnormally.

The mysterious ComLog.dll is a part of ComHooks 1.0 (c) EliCZ (http://elicz.cjb.net/ , "exports" section)


Morris

Forgot to mention:

WinNT4 WS SP6a (also on WinNT4 SRV SP6a)
OllyDbg 1.09b

Morris: can you post a command line example that fails ?
i'm too lazy to dwelve deeper to see how it is used.

i can test on NT4SP6, OD 1.09b

Simply:

ollydbg <enter>

or: doubleclick the OllyDbg.exe icon

Well, further investigating the problem I renamed ComLog.dll to !ComLog.dll and the problem persisted. Then I renamed it to ComLog!.dll and the problem still persisted.

Then I renamed a help file to SomethingLog.dll and OllyDbg reported that "SomethingLog.dll is not a valid Windows NT image" (of course it is not - it is a .hlp file!).

That gave me an idea that OllyDbg tries to load all *log*.dll files that are in it's directory.

More likely ollydbg is assuming all DLLs are plugins, and when one fails to load, it gives the above error messages.

May be so.
Anyway, no other dll gives such message, and there are 21 dll there, some of which are:

ApiHooks.dll
BOOKMARK.DLL (OD plugin)
CMDLINE.DLL (OD plugin)
ComHooks.dll
ComLog.dll
CPUMON.DLL
cygwin1.dll
pdh.dll
P rocessWorks.dll