Win2k "secret weapon" module analysis tool

It is well known that many applications of Windows not only have executable EXE files, but also need auxiliary modules. These modules are various in variety and variety, and the most famous ones are dynamic link libraries (DLLs). Also: ocx, sys, etc. Like applications can be divided into 16-bit, 32-bit, 64-bit programs, modules are also divided into 16-bit, 32-bit, and 64-bit modules. When deleting an application or an executable file, the related dynamic link library or module can't be deleted cleanly. Over time, many "junk files" that make people hate are formed. Therefore, many people who use windows usually pay attention to DLL files to study which are useful and which are useless, in order to accurately delete the useless parts, that is, to complete the so-called system weight loss, but this is not the center of this discussion. Our goal is to study the module file from another perspective. As mentioned below, it is such a tool.

a. Introduction

Windows 2000 Professional's Support Tools has a tool for analyzing module files. The English name is Dependency Walker. The literal translation is "Dependent Cruiser". This name is awkward and inconsistent in any case. The characteristics of Chinese expression. It is more appropriate to translate it into a "module parsing tool" by using validation and viewing reference materials. Unlike the above-mentioned purpose of weight loss for the system, the module parsing tool can detect: the module's affiliation, the creator, the function interface, the calling relationship, and even the programming language used to generate the module file, and the linker version used in the program chain. And so on, the parsed affiliation is displayed in an icon format similar to the directory tree. Of course, it can also display at least which associated files need to be used by the running module, together with the full path, basic address, version number, computer type, debugging information and other information of the file, which can be described as all aspects.

From the nature of this information, it is not difficult to see that this type of information is more useful for system administrators, system testers, programmers, and automated script writers. For ordinary users, the use is smaller. But it is not useless. Ordinary users can use these analysis results to eliminate system failures caused by modules. System failures caused by modules mainly include:

1. The module is missing.

2. Invalid module.

3. Execution of the exit /entry collocation error.

4. Loop error.

5. The module and computer type are incorrectly matched.

Although the tool is a support tool for win2k, it can also run in win9x, winNT3.51, winNT4.0 operating system environment, and even Windows CE. The latest version of Dependency Walker is 2.0. This version only supports parsing 32-bit or 64-bit modules, and 16-bit modules are no longer supported.

b. Usage Slightly

Unlike other tools, this tool only has a GUI version and no command line version. If you already have Support Tools installed, you can do so: "Start -> Programs -> Support Tools -> Tools -> Dependency Walker". This is also an English interface tool, and there are English help files for reference. Here's a quick introduction to the usage:

1. First click with the mouse “File