dependency walker doesn't show you what it calls, only the dependencies
that were specified at compile time... it's possible to use LoadLibrary
calls that go completely unnoticed by dependency walker...
Unless you are running a really old version of Dependency Walker, you
can use its profiling feature to catch all modules, even those loaded
via LoadLibrary. The latest is at...
That is for the WINDOWS VirusScan, not the DOS (command-line) one (though scan.exe.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
